any progress towards figuring how to unbrick? - G1 General

or does no one care about this?

Sure people care but the info just isn't there. A Jtag cable is involved and some additional software that no one can get there hands on.

Related

Complaints!

I'm really tired of all the complaining and bickering going on in this forum lately.
It's getting out of hand.
Especially from **** heads that didn't show their faces until after the hard work was done. Those that don't show up when the forum needs something but only show up when they need something.
Where were you when we were collecting money?
Instead of complaining, did you ever think to ask some of the leaders in the forum, what you could do to give back?
Where were you when we were testing? All we needed was $5 from a few people but all I see is more cheap bastards that want free stuff and expect it to be PERFECT. NOT GOING TO HAPPEN! Think of it this way...if you bricked your device after 20 other people have successfully "patched" it, then something else is wrong. Work with people in the forum to figure out what. Keep a cool head. We know how tough it is to spend high dollar on a device then have it not work...but you use solutions here at your own risk so it's not the developers fault IT IS YOUR FAULT. Learn to post based on other postings. Don't yell and start complaining. I'm not a developer myself but contribute in other ways. If I was a developer I would leave this forum because of the verbal abuse. STOP COMPLAINING ALREADY!
Read the forum. Most of the **** has already been done. I'm not upset because people are asking questions due to not understanding something along your research. Don't get me wrong, the forum is here to help people and it's helped me a lot. I'm upset because of all the bashing going on lately. It's getting out of hand. I'm also upset because many of you that are actually benefitting from these solutions didn't show your faces until all the hard work was done. Don't tell me you couldn't afford a measly $5 or to contribute your time in some way or ask the people involved...what can I do to give back to the community I leech from.....you get my point.
Note, I'm not going to respond to ANYONE regarding this thread. Just chill the out and let's work together. If your device breaks, READ and try to educate yourself first instead of blaming the developer who took time to contribute their knowledge and provided us with a solution we needed or wanted. If you don't like how things are going....GET INVOLVED WHEN YOU NEED TO...DON'T COMPLAIN BECAUSE YOU'RE USING A SOLUTION SOMEONE WROTE ON THEIR FREE TIME TO HELP YOU OUT! MY GOD PEOPLE!
If you think you might get upset, mess your phone up, or otherwise...JUST DON'T USE THE SOLUTIONS POSTED ON THIS FORUM PERIOD.
If the above doesn't make sense...oh well. Needed to get that off my chest. I'm not a writer either so if it's all mashed together, oh well. If you're smart enough you'll get my point. If not, then just ignore the thread and go on.
Well Said ltxda. If only people would listen could curb their emotions a bit and apply logic sometimes....but then we are emotional beings.
Well I agree anyway. Everything is done at your own risk in these forums...and while we are at it...you know complaining about complainers and so forth...
..has anyone actually bricked their device (rendered it 'dead' or incapable of being restored somehow)...you know killed it?
I don't recall anyone having had that experience since... say...Olipro's unlocker. Point being...it's safe for all...and that was the intention of the SPL patch in the first place..whether simple to use or not.
C'mon friends...let's close the divide eat some humble pie together and get back to the business of progress and development...I'll leave that last bit to the devs.lol
If it helps I'll go first...Sorry if I offended anyone of late.
I meant that BTW. If it it's not good enough..sorry the offense ran so deep...sorry again.
OK...back to business
Developer Midget_1990 should be getting his X7500 within the next few days hopefully. We wanted different variants of the Athena to ensure there any and all solutions would definitely work across the board.
Custom ROMs coming soon.
Why don't we put our heads together to finalize/agree on the wish list of software that should be incorporated into the ROM/Vanilla ROM?
Has anyone found any VGA converted files for the Kaiser plug-in .cabs? That would be nice.
well said lt.. well said...
Agree with all these comments and want to add my take on the situation. All of us were newbies at some point (except for Oli I guess), and we have all been there. I remember sweating the first time I made a registry change.
1. We need to be a little patient with newbies. We want them to become a part of the community, not drive them away.
2. Saying "Just use search" or "See the Wiki" isn't always helpful. Sometimes relevant threads are 20+ pages, hard to sift through all that and figure out what is really the **** and what is some lame-ass crap from some poor soul who is as clueless as me. And have you actually looked at the Athena Wiki lately. Not much there. I would feel more sympathetic to the dismissive tone if the Wiki were more up to date. (I know, that's me too!)
** Tip for newbies, go to Advanced Search, select just the Athena forum, and search by post not thread. That may help narrow things down.
ON THE OTHER HAND:
3. I'm pretty cautious in making major changes. Flashed my Wizard ROM probably 4 times in over a year... and still waiting to flash my Advantage. I appreciate the brave souls who will flash weekly or more, I learn a lot from you guys. But I don't have the time to constantly set things back up over and over, so I wait for an upgrade that I feel confident will do what I want. Plus I know my limitations, if something really terrible happens I'm not smart enough to quickly recover. I read everything there is to read before doing anything major.
SO WHY IS IT THAT SOME PEOPLE TAKE HOME A NEW DEVICE AND FLASH AWAY WITHOUT READING A DAMN THING? Then cry that they bricked their phone? (probably not) How can we get the message of BE CAREFUL across? Look before you leap, etc. Maybe there needs to be a sticky at the very top explaining who should be messing with what. Maybe every link to a ROM should have a warning label. Something.
Sorry to go on. I really appreciate the expertise on this forum and enjoy being able to contribute in some small ways. But we need a more civil tone. I hate to see things deteriorate.
"I was once like you are now, and I know that its not easy,
To be calm when youve found something going on.
But take your time, think a lot,
Why, think of everything youve got.
For you will still be here tomorrow, but your dreams may not...."
Cat Stevens...
I think XDA-DEV is the best forum I ever seen about HTC devices. So many
thoroughbred horses here, and everybody involved in management knows how hard is to keep them working together ... Forget Customer Relationship Management
Keep this discussion clean (language, flaming et.al.). I understand the frustration, but bickering in the forum (or anywhere) is pointless.
jwzg said:
Keep this discussion clean (language, flaming et.al.). I understand the frustration, but bickering in the forum (or anywhere) is pointless.
Click to expand...
Click to collapse
Agreed. Sorry I lost it again.
thx for cleaning up the unlocker threat.
It took a while before the Hermes forum to start getting crazy. I don't have my device for a week yet and there is already a lot sh*t among members already. For the Athena, I thought this would not happen until WM7. Anyway, let's get along people.
Bickering and namecalling
I think some of the newer guys should also look in the historie of things. The hermes forum had simmilar issues with jasjamming. For lot of the developers it not just someone asking a question, but another one asking the same thing. It's can be very frustrating, and some handle it better than others. I think it's safe to say that Olipro doesn't hadle it very well, and vents his frustration at the one asking the question. Wether i agree with him or not i do understand him.
As for the people asking questions. First search if your question hasn't been asked before... If you can't find it search again.
Give as much information as you can. Be specific about versions you use. Give the output of the software you get.If you're aked to give information you have given before, just give it again. Remember you are the one wanting help, so make it easy to help you, don't make the other one search for information.
And remember one thing: Free software is often provided "as is". No guarantees and no support. Assume that if it goes wrong, that you are on your own. Any support given is a bonus. Having said that, you'll find that there are enough people willing to help as long as you are patient and polite (or at least civil).

Handroid; The android port to the Hermes

Handroid; Android on the Hermes.​
Hi all!
Ok, first off i'd just like to say i'm not as new here as I may seem - i've been stalking round these parts for 2/3 months now. Please don't flame me for that.
My only other post was on the discussion on a possible android port to the Hermes.
I liked this idea greatly, and so I decided to start the 'Handroid' project.
The idea is simple, a full port of android to the hermes. Nothing more, nothing less.
The port will be based on the linux port to the hermes as it would be foolish to let that port rust a little more while we start a new one.
We've all seen videos of android running on other pocketpc's so it's evidently possible.
But this is where I have to ask for your help. To get this port underway quickly and efficiently we need a team. And a team means that people like yourselves that feel they could help us out in some way. Help. Or even anyone you know who might have the skills required.
Handroid now has it's own wiki up Here.(That address is only a temporary one on my blog's webspace, handroid.org will be registered soon. Also, please for goodness sake don't flame because its a Work In Progress site. It will be looking much better soon.) I would love to hear from some of you soon on the wiki, or here.
Any help or even just a few points of input (or even failing that, simply encouragement) would be greatfully recieved. However, make no mistake, if this project is to suceed we need your help. I can't do this on my own.
I really hope to speak to some of you on the team soon.
Sam
Ok we will on touch!!!
Ok men if we could find anything usefull maybe pmed you must works... nice wiki...
BTW how can you do it? i have an account there too and i dont know where to start hahaha
*flames lick feet... i think*
Ok, so I take that's the first of many flames? Or was it genuine. Some how I doubt. *sigh*
Welcome !!!!
Hi,
i appreciate this attempt of getting some attention to port some alternative OS to hermes platform. Indeed it could be done and it would be in the spirit of GPL like the openmoko people did for there mobile devices.
In fact we urgently need some brave kernel hackers to push this forward, because the base of all that android stuff is a nice working kernel.
Please have a look at this thread to get an idea of the work that has been put into this: http://forum.xda-developers.com/showthread.php?t=273579
There's a lot of useful stuff
There are some barriers (arrrghh) and there are new devices drawing attention so the progress of linux port stucked a bit....
Anyway the winmob family is doing great work, so let's see how far we would come with this alternative!
Have fun,
scholbert
I am very interested and I hope I can be helpful (at least cheer leading). Though I don't know anything about the Hermes kernel, as a reverse engineer, I always hack my way out. I keep my eyes on your wiki.
Great!
Thanks for the anti-flames.... I think my feet didn't get burnt too much.
We ultimately need people with a specialism in linux driver/kernel development. However, as far as I can tell the kernel is pretty much functional, but I will check more closely later.
I'm also going to contact some developers of the other Android ports around and see if they have any advise.
Will report back soon,
Sam
Any new notice?
Anybody still working on this?

[Q] Would like to know more about rooting

We're very lucky at XDA because we get all sorts of tool kits made for us making it easy to root, and although I appreciate the hard work people put in to making our lives easier, I still very much want to learn.
Would somebody give me an insight into rooting and how the N7 was rooted?
If you wouldn't mind explaining I would be very interested into finding out.
Thanks. CJ

Suggestions for 3rd-party device hardware distributors?

I'm interested in replacing the 1/8" stereo out jack on my n4. It went out a few months back and I could have and still can start an rma with google but I enjoy DIY projects and this one would be a good learning experience. I'm just looking for suggestions or advice pertaining to aftermarket hardware components and the best route to take in acquiring them.
thanks!
Sweet, I'll check that out. Thanks.
Guess I'm just gonna have to bull**** my way past the oppressive 10 post initiation period. Time to go ask some stupid questions in the wrong categories without utilizing the search feature first.... :cyclops:

[HARDWARE] UART Cable time

I've been reverse engineering the bootloader for the G955F in an attempt to find some sort of exploit to let us root our devices and not trip the KNOX flag. It now seems like the next step is to get in to the bootloader UART.
I've looked at guides such as: https://forum.xda-developers.com/showthread.php?t=1901376 where they make a microUSB version of this cable and have attempted to replicate this with the USB-C connector by shorting the CC pins to ground with various resistances but have had no joy.
Looking at the kernel source, I can see this:
Code:
"-MHL:1K",
"-VZW Accessory:28.7K",
"-VZW Incompatible:34K",
"+RDU TA:40.2K",
"+HMT:49.9K",
"-Audiodock:64.9K",
"-USB LANHUB:80.07K",
"-Charging Cable:102K",
"+Game Pad:121K",
"+TYPE1 Charger:200K",
"+Jig USB Off:255K",
"+Jig USB On:301K",
"+Deskdock:365K",
"+TYPE2 Charger:442K",
"+Jig UART Off:523K",
"+Jig UART On:619K",
"+TA:eek:PEN",
"+USB:eek:PEN",
"+CDP:eek:PEN",
"+Undefined Charging:XXX";
Which definitely indicates that the known resistor values should work, but so far, I can not get any serial output at all. Is my assumption that USB-C cables actually have CC wires, rather than an internal resistor in the connector head correct?
UPDATE: I have attached the pinout for the UART cable.
Getting it would be amazing.
I believe This will take time
@Vatsal can you please move this to the right place?
As this forum place here is not how-to/guides/questions.
Thanks very much as always :good:
Tkkg1994 said:
@Vatsal can you please move this to the right place?
As this forum place here is not how-to/guides/questions.
Thanks very much as always :good:
Click to expand...
Click to collapse
Thread moved Sir.
Next time, kindly use the report button.
Thanks:good:
This post, posts of my own, and others I've seen SCREAM that we need a Dev Discussion section like XDA used to have (least majority of the phones I had 3-4 years ago plus had them.) Would be dev discussion only where the OP is actually working on a dev issue (root, getting dex to run sans dock, etc.) and be able to get actual help.
Unfortunately these dev type threads get buried by non dev like questions and I imagine the people capable of helping won't come in here and dig for stuff to help with.
nosympathy said:
This post, posts of my own, and others I've seen SCREAM that we need a Dev Discussion section like XDA used to have (least majority of the phones I had 3-4 years ago plus had them.) Would be dev discussion only where the OP is actually working on a dev issue (root, getting dex to run sans dock, etc.) and be able to get actual help.
Unfortunately these dev type threads get buried by non dev like questions and I imagine the people capable of helping won't come in here and dig for stuff to help with.
Click to expand...
Click to collapse
+1
I would really like to get this working but could really do with some outside input. Having this in the more general section is going to make this vanish quickly.
look what I got
@jujusito @halo87 @nosympathy @dragunbayne @Harry44
Look what I just got in the mail...
...now just to reverse engineer it and make a schematic.
happytomato said:
@[email protected]@[email protected]@Harry44
Look what I just got in the mail...
...now just to reverse engineer it and make a schematic.
Click to expand...
Click to collapse
How would would this take?
@halo87 That sentence didn't make much sense...
You should ask this kind of questions on a proper EE forums because I don't think you'll have useful answers here. We're just a bunch of clueless dudes poking with firmware files.
Excited to see that someone is working (sort of) on exploiting the bootloader and thus avoiding the knox counter
Please let us know with your future progress :good:
happytomato said:
@jujusito @halo87 @nosympathy @dragunbayne @Harry44
Look what I just got in the mail...
...now just to reverse engineer it and make a schematic.
Click to expand...
Click to collapse
Any progress on this? Trying to achieve UART myself, but so far nothing.
militiaOfDeath said:
Any progress on this? Trying to achieve UART myself, but so far nothing.
Click to expand...
Click to collapse
I actually made one and then lost it when formatting my laptop. I shall probably do it again in the next few days, possibly today. Heads up though, it is not a solution in itself. The resistor magic happens within the Anyway Jig and I think that only the S103 is compatible with USB C. In any case, watch this space. If you want to share any findings, please PM me!
happytomato said:
I've been reverse engineering the bootloader for the G955F in an attempt to find some sort of exploit to let us root our devices and not trip the KNOX flag. It now seems like the next step is to get in to the bootloader UART.
I've looked at guides such as: https://forum.xda-developers.com/showthread.php?t=1901376 where they make a microUSB version of this cable and have attempted to replicate this with the USB-C connector by shorting the CC pins to ground with various resistances but have had no joy.
Looking at the kernel source, I can see this:
Which definitely indicates that the known resistor values should work, but so far, I can not get any serial output at all. Is my assumption that USB-C cables actually have CC wires, rather than an internal resistor in the connector head correct?
Click to expand...
Click to collapse
How were you going about reverse engineering the bootloader
happytomato said:
Is my assumption that USB-C cables actually have CC wires, rather than an internal resistor in the connector head correct?
Click to expand...
Click to collapse
Doesn't usb-c spec call for a 56k resistor in the cable? I remember there being a problem with incorrectly manufactured cable having 10k resistors.
STF_TimelessGoD said:
How were you going about reverse engineering the bootloader
Click to expand...
Click to collapse
I am using IDA Pro. I wish I also had hex-rays, but that is a little out of my budget.
vermiciouskanid666 said:
Doesn't usb-c spec call for a 56k resistor in the cable? I remember there being a problem with incorrectly manufactured cable having 10k resistors.
Click to expand...
Click to collapse
I think so, but I am not 100% clear on the USB C spec. I can confirm that there are no resistors at all inside the cable though.
The pinout has now been uploaded. Happy hunting.
By the way, if anyone has an Anyway box and fancies sending it to me, I would be deeply grateful. Progress is getting slowed by how expensive it is to get hold of all of these secret Samsung parts.
someone succed to make uart cable ?

Categories

Resources