Develop Bugs

[Q] Can an S-OFF Desire help any dev's? I have one now.

Okay, YES I know this is on the limit for this sub-forum, but give me a minute to explain...
1. I have no Desire experience, hang out in the Nexus forums myself
2. I have an S-OFF Desire at the moment
3. I have no idea if this is commonly available or even useful
4. I SEARCHED (want the list: "s-off", "s-on", "unlocked bootloader", "bootloader", "unlocked H-BOOT", "H-BOOT", "is this worth my time", etc)
...and I only want relevant attention for 12 hours or so...
So, mods and peeps, bear with me... either please politely say "no" and close the thread or say "yes" and pm me.
gracis

it must usefull if you can clone the SPL out

If you could dump the hboot, it would definitely be worth a quick prod and a poke to see if its any use!

We need a dump of this!
Sent from my HTC Desire using XDA App

i hope this is useful and maybe a step forward to unlocking nand

[SteveJobsMode=ON]
This is fantastic. Its absolutely brilliant, Amazing, Beautiful that we found a device with S-OFF.
[SteveJobsMode=OFF]
How do you dump it??

I have fastboot but not adb... tell me how?
Code:
BRAVO UNKNOWN SHIP S-OFF
HBOOT-0.75.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-(I just upgraded this)
05-Mar-2010

djmcnz said:
I have fastboot but not adb... tell me how?
Code:
BRAVO UNKNOWN SHIP S-OFF
HBOOT-0.75.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-(I just upgraded this)
05-Mar-2010
Click to expand...
Click to collapse
Unfortionally google didnt have the answer

StrongOneX said:
Unfortionally google didnt have the answer
Click to expand...
Click to collapse
And you felt we all needed that confirmation?

I hope a dev sees this and helps you dump the SPL

sorry for my ignorance, but what exactly is this S-Off? can someone give me a run down?
Cheers

could this be any help
http://www.gotontheinter.net/content/fastboot-cheat-sheet

StrongOneX said:
could this be any help
http://www.gotontheinter.net/content/fastboot-cheat-sheet
Click to expand...
Click to collapse
Yes, thanks although I know all of that (I make a quite popular rom for the Nexus)... I need the spl instructions... I have an offer for assistance on this tomorrow.

a simialr thread posted for the n1,
hxxp://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/311351/build-version-erd56c/
there is some adb stuff you might want to try.
ps, whats your boot animation look like?

merlin051 said:
a simialr thread posted for the n1,
hxxp://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/311351/build-version-erd56c/
there is some adb stuff you might want to try.
ps, whats your boot animation look like?
Click to expand...
Click to collapse
Just the android text with slight shimmer... nothing too exciting...
Had a look at the post... nothing new I'm afraid...

Without know to much about it, i might think you need to use dump_image to dump the address block of the spl.
The nand architecture address layout might already be known.

DesirableHTC said:
sorry for my ignorance, but what exactly is this S-Off? can someone give me a run down?
Cheers
Click to expand...
Click to collapse
It's short for security off. A hboot with s-off will allow us to flash and boot custom images trough fastboot. Fastboot can be accessed by booting the phone while holding down the back key. Hboot is the second deepest partition on an Android phone, only beaten by the radio, radio bootloader is almost never used flashing from.
Things it can do for us... the most important command in fastboot is the boot command. It's not really helpful for end users, but developers can use it to boot their custom images before flashing to see if it works with the phone without risking anything. Since it's deeper than recovery it may give us write access to the system partition while normal booted (?). Hboot is also often called SPL (maybe not on desire, but at least on other devices), a hboot with security disabled is often called engineering's SPL.
My knowledge on this is mainly based on other devices. Some may be wrong or misleading. If anyone sees something wrong, please let me know.

I think its not the problem to extract the spl and patch it to s-off the problem is to flash it (it must be signed) or the SPL partition is r/o there some German users that ere very near to System r/w just wait they will post it!

This has nothing to do with hboot. His CID is most likely set to supercid, eg 11111111.
S-off allows non-signature rom flashing, full rw nand access.
@ts: could you come on irc? Irc.freenode.net , ny nick is IEF.
I'm part of a team thats investigating this. Info from your phone
WILL help a lot! Just pm me asap please

Okay, have now slept...
So, it seems this is indeed relevant for this sub-forum so I'll reply here rather than via pm.
Where I am:
have root
have new radio
have fastboot access
do not have adb access
can not flash any kernels here in XDA
I'm not a muppet and have adb working fine for my Nexus but for the life of me can not get it working on this Desire. HTC Sync does not recognise the phone as connected in any mode (Win7 & XP). I've used the Google and HTC drivers. I've used driver tools to remove the registry entries and reconnect phone, no joy. Although I do get "HTC Android Phone USB Disk".
I can't flash a kernel via a recovery .zip. In fact, even if I flash a rom from here on XDA the kernel fails to install. Bad block are reported on the boot partition which I realise is common. This does however mean that if I install a custom kernel to get a dump it will have to be VERY small.
I've had a few questions asking if I'm willing to dump it. Well, of course I am, that's why I posted...
I am trying to secure the device for the weekend EDIT: I have the phone for the weekend.

cant install any ruu to htc desire cdma

I dont know if someone here has posted something similar but i got a huge problem with my damn htc desire, it is cdma ive tried to install the ruu froyo but it wont let me it says model id error or cid incorrect i have made the damn goldcard and it doesn't work, this phone is pissing the hell out of me. i cant do nothing with it. could someone here tell me plz some way to install an compatible ruu. the phone only boots to fastboot, i can change it to hboot but from there nothing. plz can someone here help me i;m losing my mind.

give us some details then we MAY be able to help you.. we're not friggin' magicians here..
Firstly, the RUU's didn't work because my best bet is that you were using RUU for Bravo and not BravoC (your model) - Hence modelID error.
Secondly, if you're rooted, then you're more than likely S-OFF too so you can probably just fix it, look on my guide. (DO NOT FLASH ANY HBOOTS)

to stop us working double on this, please choose either this thread, or http://androidforums.com/htc-desire/475726-cant-install-any-ruu-htc-desire-cdma.html
It gets annoying trying to help people in several different places.
My suggestion is to stay on XDA as Bortak knows his stuff and will probably be able to help. On AF you may get stuck with me and I just havent the time.

Oooh rootSu sorry didnt knew that androis forums where from here too, my apologies for that. Ummm ok the problem. I got this htc desire bravo_c it was rooted but my brother told me that the phone started on bootloop. Then I exactly didnt knew what he did but then he said the phone was with black screen. Ok I tried some guides from here, the only problem was that it happened like some guy said here, I tried to do an ruu rom but when it started doing the progress when It was at 20% it stopped and now the phone boots only in fastboot. After the ruu now I can see whats happening with the phone but like I said it only boots on fast boot. Oh other thing now the phone is S-on and the hboot is 0.98. Let me know if u need some more details. Ill let u kno,. And sorry again for the other forum.
Sent from my SGS2 using Tapatalk

There aren't that many resources for the bravoC so you've got limited options. As far as I know there is one BravoC RUU on shipped-roms.Com, but if it's not for your network provider I don't know whether it wouldn't just break your phone..
If it is the right RUU for your network then great, use it and hope for the best. If it isn't then stay away from it and contact HTC.
you should root and s-off your phone (when/if you fix it/get it back from repair), so that these sort of problems can be sorted out easily without any hiccups.

bortak said:
There aren't that many resources for the bravoC so you've got limited options. As far as I know there is one BravoC RUU on shipped-roms.Com, but if it's not for your network provider I don't know whether it wouldn't just break your phone..
If it is the right RUU for your network then great, use it and hope for the best. If it isn't then stay away from it and contact HTC.
you should root and s-off your phone (when/if you fix it/get it back from repair), so that these sort of problems can be sorted out easily without any hiccups.
Click to expand...
Click to collapse
well this sucks umm if i contact htc they will probably say to send the phone right? man i was hoping i could fix it with the guides here i really have bad luck.
So the best thing to do now is just to contact htc and wait for what they have to say. thanks for the help, sorry for posting this thread like that, it wasn't my intention to make anyone mad or anything, its just that i was so desperate that i wanted someone to help me.

Sorry I'm not mad and it IS a different forum. But sometimes I end up helping on AF and someone else helps here and we end up either
a) both duplicating each others work
b) taking different approaches.
The risk then is you take some advise from here, some advise from there, put it all together and end up bricking your phone.

I understand thanks for the help. I called htc they told me that i have to call tomorrow because Im from Puerto Rico and their offices are close today so I gotta check tomorrow to see if they are open.

dude i have a htc cdma i rooted. installed cm7 on there..took me like 10 minutes

freshkid87 said:
dude i have a htc cdma i rooted. installed cm7 on there..took me like 10 minutes
Click to expand...
Click to collapse
Yes, well done, congratulations.. your point is? Have you read the thread? No? You just decided to post something totally irrelevant? Really? Awesome.

Bortak thanks for the help man, but my brother got an galaxy s2 so I wont b trying to fix the desire anymore.
Sent from my GT-I9100 using Tapatalk

Oh and btw dont care, the desire was rooted and it had cm too the problem was that... Whatever wont waste time on u.
Sent from my GT-I9100 using Tapatalk

bortak said:
Yes, well done, congratulations.. your point is? Have you read the thread? No? You just decided to post something totally irrelevant? Really? Awesome.
Click to expand...
Click to collapse
shut your london ass up

2.3.3 RUU ruined my Desire, HELP!?

So, some more trouble with my Desire
I flashed a new ROM, it was stuck at the end of the boot anim
Tried RUU-ing, since this worked the last time this happened
RUU worked
When the phone booted, it came to the lockscreen, but then restarted itself and now it's doing the same;
boot>boot logo>boot anim>lockscreen>reboot>repeat
I can't go to bootloader, fastboot or recovery, because FastBoot is activated by default on 2.3.3 HTC
So, what do I do?
I *think* I've got adb, the phone has S-OFF (doesn't have a recovery though, because the RUU deleted it).
Can't run RUU again, can't go to recovery
Any suggestions?
EDIT: Found a way to enter fastboot and bootloader, I guess that 'clear data' thing might be useful?
EDIT2: Running RUU again, hope it helps!

Run 2.3 ruu from bootloader or fastboot. I think it should work from fastboot.
Sent from my HTC Desire using Flashes and Thunders

Thanks, did that and phone is back to normal
But for some reason, the RUU detects the battery is <30% if on Bootloader, so I have to run it from fastboot... Weird...

Aaaa, now i see, it's you again...

Yup, get used of me asking dumb noob questions
After all, this is how professionals are made...
Or, did you learn everything by yourself? O.O
In both cases, you're full of knowledge (which I will soon obtain, if I keep destroying my phone)

someone755 said:
Yup, get used of me asking dumb noob questions
After all, this is how professionals are made...
Or, did you learn everything by yourself? O.O
In both cases, you're full of knowledge (which I will soon obtain, if I keep destroying my phone)
Click to expand...
Click to collapse
Or..... Read on how to do things properly in the first place lol
Sent from my HTC Desire

someone755 said:
Yup, get used of me asking dumb noob questions
After all, this is how professionals are made...
Or, did you learn everything by yourself? O.O
In both cases, you're full of knowledge (which I will soon obtain, if I keep destroying my phone)
Click to expand...
Click to collapse
It' won't be destroyed until you start repairing it with hammer (srpski alat )...

nlooooo said:
repairing it with hammer (srpski alat )...
Click to expand...
Click to collapse
Haha
Sent from my HTC Desire

jmcclue said:
Or..... Read on how to do things properly in the first place lol
Click to expand...
Click to collapse
That's not how I do things, apparently...
How I do things:
1.Start doing something
2.Mess up
3.Try to repair and make it worse than it was
4.Make a new thread here
5.Partially figure the answer out
6.Read someone's reply on how to REALLY repair it
7.Repeat
The hammer idea is good, it'll be useful someday when I fully brick the poor thing (hopefully not soon)
P.S.
i figured out why the phone did that, with the 'stuck at boot' thing
My Ext4 partition wasn't aligned perfectly and it was about 10% of the size it should've been -.-'
Talk about newb

someone755 said:
That's not how I do things, apparently...
How I do things:
1.Start doing something
2.Mess up
3.Try to repair and make it worse than it was
4.Make a new thread here
5.Partially figure the answer out
6.Read someone's reply on how to REALLY repair it
7.Repeat
The hammer idea is good, it'll be useful someday when I fully brick the poor thing (hopefully not soon)
P.S.
i figured out why the phone did that, with the 'stuck at boot' thing
My Ext4 partition wasn't aligned perfectly and it was about 10% of the size it should've been -.-'
Talk about newb
Click to expand...
Click to collapse
Hahaha atleast ur honest
U should partition ur sdcard with abuntu or 4ext recovery. Iv always used 4ext to partition and never had a problem.
Sent from my HTC Desire

Yeah, almost everyone on this forum is telling me to get 4EXT (which I already got, right after the last crash...)
It's even better than I expected, after reading how CWM is 'all mighty' and stuff...

Method to obtain S-OFF?

According to this thread http://forum.xda-developers.com/showthread.php?t=1632200 by 7pellc he was able to get his device into an unlocked state.
While flashing a RUU the process crashed at "WRITING USER DATA".
He then rebooted the phone and found the rom to be unusable, so he rebooted to HBOOT only to find it being stuck in RUU mode.
HBOOT still reported device to be LOCKED, and for some reason he rebooted to recovery, and then back into HBOOT finding the device in an unlocked state.
Instead of LOCKED/RELOCKED/UNLOCKED HBOOT reported only ******
He then fastboot flashed a boot.img which it accepted even though this device was never unlocked through HTCDev.
It seems to me that the exact procedure temporarily left the device in some form of unlocked state, and maybe the eMMC was actually unlocked.
If this was the case it should have been possible to perform fastboot commands to acheive SuperCID or even S-OFF:
fastboot oem writesecureflag 0
fastboot oem writecid 11111111
I am not sure anyone ever recreated his steps, and the important step is to reach the state where HBOOT reports only ****** instead of LOCKED states.
I would love to try this out myself, but I sold my HOX when SGS3 came out as it was a true unlocked device.
Some of my friends still has this phone, and they come to me when something is wrong with it, and if I can persuade them to try this on their phones I would like to try it ofcourse.
I am really sorry if anyone actually recreated the exact steps, but I have read all the threads about S-OFF, and couldn't find someone who performed the opreation, but if I'm mistaken I'm sorry, and this thread can be closed.

S-OFF not possible !

Mr Hofs said:
S-OFF not possible !
Click to expand...
Click to collapse
Please refrain from posting here if you can't contribute with anything!

spngbb said:
Please refrain from posting here if you can't contribute with anything!
Click to expand...
Click to collapse
But he's speaking the truth.. S-OFF isn't possible, and if you did some research you would know that Please refrain from asking questions before doing your research.
https://www.youtube.com/watch?v=JmvCpR45LKA

Actually if the emmc was unlocked as the op describes then it would be possible but I'm very sceptical that it actually was.
During the ruu sequence the emmc is indeed unlocked however upon rebooting it gets locked again
This is the same principal that the soff for xl uses however they strictly say you mustn't power off your device because it relocks the security.
I have spent some time looking at this exploit.
It is technically possible to have the emmc unlocked and accept fastboot commands by flashing an updated firmware. (Note it has to be an update and not the same as you already have)
Once first flash of the firmware you get an error and then have to flash again straight away but if you don't flash again you can run other commands with the emmc unlocked.
This is where this method hits a dead end.
In order to progress further we need to be in android which would normally be done with
Fastboot boot boot.IMG or fastboot oem boot however since early hboot versions. I think 1.12. this ability was removed and the command just either errors or crashes the device
Sent from my HTC One X using xda app-developers app

Agil1ty said:
But he's speaking the truth.. S-OFF isn't possible, and if you did some research you would know that Please refrain from asking questions before doing your research.
Click to expand...
Click to collapse
Oh wel, oh well...
I know that the S-OFF progress by xmoo and others has stopped/is on-hold, but saying that S-OFF is impossible is a bad attitude to solving a problem.
I did my research and did not find someone who tested out this method. So, really if you have nothing to contribute with, then please go find someone else to annoy!

bagofcrap24 said:
Actually if the emmc was unlocked as the op describes then it would be possible but I'm very sceptical that it actually was.
During the ruu sequence the emmc is indeed unlocked however upon rebooting it gets locked again
This is the same principal that the soff for xl uses however they strictly say you mustn't power off your device because it relocks the security.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Actually I came up with this idea after reading the threads about the new S-OFF method for XL.
I don't think the eMMC is actually unlocked in the RUU process, the key to achieveing this lies in the sequence of boot back and fourth from RUU mode to the stock recovery and then back to HBOOT.
If the theory is worth anything something happens in the process making HBOOT not recognize the secureflag thus reporting only *****
Ofcourse this is all theory, but who knows
As mentioned in my first post, I cannot test this out myself, and I would never have brought this up if I was able to test it and found it not to be working!

Just telling the truth ..... Sorry for letting you know a fact at the moment.
And you could be a bit nicer you know. I was not rude, bad mouthed or aggressive towards you in any way.....so i expect it the same the other way around !

spngbb said:
Oh wel, oh well...
I know that the S-OFF progress by xmoo and others has stopped/is on-hold, but saying that S-OFF is impossible is a bad attitude to solving a problem.
I did my research and did not find someone who tested out this method. So, really if you have nothing to contribute with, then please go find someone else to annoy!
Click to expand...
Click to collapse
Now now, there is no excuse to behave this way.
Sent from...... The Milky Way

Mr Hofs said:
Just telling the truth ..... Sorry for letting you know a fact at the moment.
And you could be a bit nicer you know. I was not rude, bad mouthed or aggressive towards you in any way.....so i expect it the same the other way around !
Click to expand...
Click to collapse
Sorry, but a statement like your first post in this thread is just pointless. So rude or not... We can call it stupid if you prefer!
maxilick said:
Now now, there is no excuse to behave this way.
Sent from...... The Milky Way
Click to expand...
Click to collapse
I don't follow exactly... I said please

spngbb said:
Sorry, but a statement like your first post in this thread is just pointless. So rude or not... We can call it stupid if you prefer!
Click to expand...
Click to collapse
Pfffff stupid......yeah well i can say a lot about that but i won't. Its pointless and leading to nowhere ! I will let it rest here....because you are so smart
Good luck with your s-off.....

spngbb said:
Sorry, but a statement like your first post in this thread is just pointless. So rude or not... We can call it stupid if you prefer!
I don't follow exactly... I said please
Click to expand...
Click to collapse
Pointless going on with this if you can't see, have a great day.
Sent from...... The Milky Way

[Q] I think I'm in so much trouble.... Need help please!

Hey guys,
I dropped my HTC One M8 today, and now it has a crack in the screen.
Well, I wanted to go back to the store to get it replaced under warranty, but I needed to unroot & go back to stock first.
So at home I tried to go back to stock and stuff, but it just didn't work. That is where **** hit the fan.
Right now, I can't boot into Android, can't boot intro recovery. Everytime I start my phone it boots into FASTBOOT USB, and I have the following screen: *see attachment*
I really don't know what to do, I've been searching for serveral hours and my guess is I hard-bricked it...
Please, please tell me there is a way to make it boot into android again...?

KodoKevin123 said:
Hey guys,
I dropped my HTC One M8 today, and now it has a crack in the screen.
Well, I wanted to go back to the store to get it replaced under warranty, but I needed to unroot & go back to stock first.
So at home I tried to go back to stock and stuff, but it just didn't work. That is where **** hit the fan.
Right now, I can't boot into Android, can't boot intro recovery. Everytime I start my phone it boots into FASTBOOT USB, and I have the following screen: *see attachment*
I really don't know what to do, I've been searching for serveral hours and my guess is I hard-bricked it...
Please, please tell me there is a way to make it boot into android again...?
Click to expand...
Click to collapse
Did you try to run a ruu? See if you can find a ruu for your device model and carrier you can run ruu.exe from a windows computer in fast boot USB mode

bbell101584 said:
Did you try to run a ruu? See if you can find a ruu for your device model and carrier you can run ruu.exe from a windows computer in fast boot USB mode
Click to expand...
Click to collapse
I've tried to find the correct RUU, but everytime I get an error along these lines: 'Could not verify signature'
Where could I find a correct RUU?

KodoKevin123 said:
Hey guys,
I dropped my HTC One M8 today, and now it has a crack in the screen.
Well, I wanted to go back to the store to get it replaced under warranty, but I needed to unroot & go back to stock first.
So at home I tried to go back to stock and stuff, but it just didn't work. That is where **** hit the fan.
Right now, I can't boot into Android, can't boot intro recovery. Everytime I start my phone it boots into FASTBOOT USB, and I have the following screen: *see attachment*
I really don't know what to do, I've been searching for serveral hours and my guess is I hard-bricked it...
Please, please tell me there is a way to make it boot into android again...?
Click to expand...
Click to collapse
Do you still have TWRP installed? Boot into recovery from your bootloader, and restore a backup. (You should have made one before you tried returning to stock)

xunholyx said:
Do you still have TWRP installed? Boot into recovery from your bootloader, and restore a backup. (You should have made one before you tried returning to stock)
Click to expand...
Click to collapse
I can't boot into recovery, it goes back to FASTBOOT / HBOOT every time.

KodoKevin123 said:
I've tried to find the correct RUU, but everytime I get an error along these lines: 'Could not verify signature'
Where could I find a correct RUU?
Click to expand...
Click to collapse
I got the one I use from HTC website I'm on T-Mobile and it works just fine for me maybe try changing your cid to supercid then run ruu
Did you check the ruu thread in m8 general forum

bbell101584 said:
I got the one I use from HTC website I'm on T-Mobile and it works just fine for me maybe try changing your cid to supercid then run ruu
Did you check the ruu thread in m8 general forum
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2701376 If you are talking about this thread, yes I checked it.
I downloaded several RUU's and they all say : 'MODEL-ID error, please download the correct RUU for your device'
I am going to try to change the CID to SuperCid but don't think it will work since I can't change my S-ON to S-OFF

KodoKevin123 said:
http://forum.xda-developers.com/showthread.php?t=2701376 If you are talking about this thread, yes I checked it.
I downloaded several RUU's and they all say : 'MODEL-ID error, please download the correct RUU for your device'
I am going to try to change the CID to SuperCid but don't think it will work since I can't change my S-ON to S-OFF
Click to expand...
Click to collapse
Yea being s-on I don't think you can what is your cid and what carrier do you have maybe someone can modify one of the ruus to work with your cid cause it seems the ruu is checking your cid and it doesn't match for the ruu so it isn't working. Have you tried reflashing twrp and seeing if you can enter recovery again then maybe restore one of the backups from the backups thread. I don't know how much help I can actually be cause I'm just a flasher hopefully someone with more experience and knowledge can jump in and help you I'm just suggesting what I would do in your situation. I hope you get your phone booted again though

Omg i did it
I just started the whole process again of unlocking my bootloader and stuff, using the AOI Toolkit, and I am in the PhiliZ Touch CLockworkmod now ! Thank you all for helping me, I will carefully unroot now and bring my phone back

bbell101584 said:
Yea being s-on I don't think you can what is your cid and what carrier do you have maybe someone can modify one of the ruus to work with your cid cause it seems the ruu is checking your cid and it doesn't match for the ruu so it isn't working. Have you tried reflashing twrp and seeing if you can enter recovery again then maybe restore one of the backups from the backups thread. I don't know how much help I can actually be cause I'm just a flasher hopefully someone with more experience and knowledge can jump in and help you I'm just suggesting what I would do in your situation. I hope you get your phone booted again though
Click to expand...
Click to collapse
I just got it working again, I am going to be so freaking carefull this time :S

KodoKevin123 said:
I just got it working again, I am going to be so freaking carefull this time :S
Click to expand...
Click to collapse
Glad to hear I didn't think it was hard bricked but I know it's a real frustrating feeling when you can't boot into anything

Something f**king similar here....
http://forum.xda-developers.com/htc-one-m8/help/help-t3123025
help needed please!!

Cool. Glad you got it working again.

xunholyx said:
First of all, he can't boot into system.
Second of all, everything you've mentioned needs S-Off. He is S-On.
Third of all, HTC US is different than other regions. Most of the other RUUs that have been made available are not found on HTC's websites. Most are leaked versions, I believe.
And no. It isn't in any RUU threads on XDA.
Click to expand...
Click to collapse
First of he got it fixed and booted again if you actually read the thread second of all why are you even quoting me coming at me like that with this bs as I replied in one of my posts I might be the best to help him but I was offering suggestions as no one else was helping him. Do me a favor and don't quote me no more bs like that when all I'm trying to do is help. Thank you for your unnecessary two cents

bbell101584 said:
First of he got it fixed and booted again if you actually read the thread second of all why are you even quoting me coming at me like that with this bs as I replied in one of my posts I might be the best to help him but I was offering suggestions as no one else was helping him. Do me a favor and don't quote me no more bs like that when all I'm trying to do is help. Thank you for your unnecessary two cents
Click to expand...
Click to collapse
I edited it as soon as I posted it and read ahead. I agree I should have read ahead first, but as far as nobody helping.....
Incorrect.
I started by helping him in another thread. I would have continued helping him here, but I had to go out to do real life stuff.
Anyway, the suggestions you gave wouldn't have worked.

xunholyx said:
I edited it as soon as I posted it and read ahead. I agree I should have read ahead first, but as far as nobody helping.....
Incorrect.
I started by helping him in another thread. I would have continued helping him here, but I had to go out to do real life stuff.
Anyway, the suggestions you gave wouldn't have worked.
Click to expand...
Click to collapse
That's fine my suggestions wouldn't have worked but as I said I was just trying to offer help my suggestions wouldn't have harmed him any further either but posts like the one you quoted me on makes me not want to help or offer suggestions to no one else. I've posted some useful stuff on xda though. I'm not the most technology savvy person but sometimes I do have some useful information. Like I told him I might not be the best person to help. But there's no reason to attack me for trying to help

Hey guys, thank both for the help....
But pls keep calm and "you just know what's the best for you"

bbell101584 said:
That's fine my suggestions wouldn't have worked but as I said I was just trying to offer help my suggestions wouldn't have harmed him any further either but posts like the one you quoted me on makes me not want to help or offer suggestions to no one else. I've posted some useful stuff on xda though. I'm not the most technology savvy person but sometimes I do have some useful information. Like I told him I might not be the best person to help. But there's no reason to attack me for trying to help
Click to expand...
Click to collapse
Oh. By no means did I mean to make you feel attacked.
I'm sorry if I came across that way. I was telling you that the suggestions wouldn't work and explaining why. No offense was intended whatsoever.

xunholyx said:
Oh. By no means did I mean to make you feel attacked.
I'm sorry if I came across that way. I was telling you that the suggestions wouldn't work and explaining why. No offense was intended whatsoever.
Click to expand...
Click to collapse
It's cool I'm already over it. I know there are alot more people on here smarter then me about this phone stuff. All I really know how to do is read search and flash. This is the first phone I've unlocked and rooted and stuff like that so all this is new to me anyway. So no problem man.

bbell101584 said:
It's cool I'm already over it. I know there are alot more people on here smarter then me about this phone stuff. All I really know how to do is read search and flash. This is the first phone I've unlocked and rooted and stuff like that so all this is new to me anyway. So no problem man.
Click to expand...
Click to collapse
Chances are, I'm no smarter than you are. Read and search and learn. That's what we all do here.
And sharing knowledge is what this site is based on. Please continue to try to help others.
Just don't be offended if someone corrects you. I do agree that I could have done it in a more tactful manner though. I can see how my post might have come across as abrasive, but that was not intended.