Related
I just bought a brand new T-Mobile G1 Black from Craigslist for someone in my family. While i was rooting the phone i decided to use Haykuro SPL. As soon i rebooted the phone it bricked on me and now i am pretty much freaking out.
Does Someone Knows How To Fix It ? And do you think HTC will take it back even tho i didnt bought from T-Mobile and dont even have the receipt ?!
Please guys help me.
did you bother checking which board the phone was using? pvt or dvt? did you know some people were having issues with the new spl? and how is it bricked? won't boot? stuck at g1 screen and can't enter recovery\bootloader?
try theses instuctions and tell me if they work make sure you pull the battery before holding power and home if it get you to the recovery screen you should be good. also try it with power camera
1. pulled sd card out put it in a sdcard reader and loaded the enginering bootloader
2. took battery out
3. put sd card back into g1
4. held power + home
5. while still holding power + home slid battery back in
6. when recovery showed up hit alt+w and alt+s
7. popped sdcard back out and and loaded my favorite rom version
8. put sd card back in
9. held power + home and flashed the rom and all came alive
First off, no, HTC will not take it back (maybe if you pack 200 dollars or so with it the will). What do you mean "bricked"? Can you still get into the bootloader or not? If you can't, then sorry, it is bricked for good (atleast as far as we at XDA know)
yeah unfortunately i cant make it to the bootloader...it stays on the T-Mobile G1 sign...
davil124 said:
yeah unfortunately i cant make it to the bootloader...it stays on the T-Mobile G1 sign...
Click to expand...
Click to collapse
??
The SPL loads before the G1 logo. Are you pressing back+power?
Why o people why do you not read the threads on this before you do anything. Geez. Do you not study and take precautions before you do anything?? Your most DEF screwed. If you cant get into any of the bootloader, then its bricked and no one has found a way to fix it "yet"( hopeing someone does). Please for the love of God. READ READ READ.
@futango, because people are dumb and get excited before reading, making their 2-300 dollar phone a 2-300 dollar brick. Its cool, if you saw how disastrous this forum was you would see how many topics there are on this issue, and you wouldn't have this problem. Hard lesson learned but oh well, have to deal with it until someone finds a fix, to which there isnt one now. Too bad. Next time you'll read hu? Reading is easier than spending that hard earned money....unbelieveable.
Reported.
Davil124, its seems like people are bickering again instead of trying to help you. lol.
Like what jashu said, after flashing the haykuro SPL, try holding BACK + POWER, to enter recovery mode. When in recovery mode, remove your memory card (place it in a card reader), and delete the update.zip that contains the haykuro SPL. Proceed to copy the update.zip that contains a hacked ROM (JF1.5, ADP1.5H, etc.) to your memory card. Then flash the ROM - update.zip by pressing ALT + S. This must be done after updating to the haykuro SPL (almost everyone forgets to do this, and end up looping.) Then just let it boot up (it may take a few minutes, so don't panic and pull the battery, just let it load.)
andonnguyen said:
Davil124, its seems like people are bickering again instead of trying to help you. lol.
Like what jashu said, after flashing the haykuro SPL, try holding BACK + POWER, to enter recovery mode. When in recovery mode, remove your memory card (place it in a card reader), and delete the update.zip that contains the haykuro SPL. Proceed to copy the update.zip that contains a hacked ROM (JF1.5, ADP1.5H, etc.) to your memory card. Then flash the ROM - update.zip by pressing ALT + S. This must be done after updating to the haykuro SPL (almost everyone forgets to do this, and end up looping.) Then just let it boot up (it may take a few minutes, so don't panic and pull the battery, just let it load.)
Click to expand...
Click to collapse
davil124 thats what ur sopposed to do.. i recall there's other threads on here that talks about bricked phones. im not gettin on u, people just need to understand.. if u have problems find the right thread to put ur post up.. someone will answer ur question
futango said:
Please for the love of God. READ READ READ.
Click to expand...
Click to collapse
Futango is right though. If you are going to jump into a hack without reading, you get what you deserve and you deserve what you get.
EVERYTHING ON THIS FORUM IS POTENTIALLY PHONE BRICKING.
Once you fully realize that, then you will think twice about flashing whatever update.zip someone casually posts on here.
p.s. can everyone stop treating Haykuro like some kind of god? He got a hold of some HTC pre-release builds and posted em on here. That's it.
jashsu said:
Futango is right though. If you are going to jump into a hack without reading, you get what you deserve and you deserve what you get.
EVERYTHING ON THIS FORUM IS POTENTIALLY PHONE BRICKING.
Once you fully realize that, then you will think twice about flashing whatever update.zip someone casually posts on here.
p.s. can everyone stop treating Haykuro like some kind of god? He got a hold of some HTC pre-release builds and posted em on here. That's it.
Click to expand...
Click to collapse
Jashsu you sound really jealous. lol jk. But I do agree with you. First jesusfreke was god, now haykuro. Isn't that blasphemy? lol.
But hopefully people will begin to realize the risks involved with flashing custom firmware. I've seriously looped at least 12 times (bad md5 checksums, faulty memory card, u name it lol), wiped over 100 times, but thankfully found solutions to every problem I've faced, but that was because I did my research before jumping the gun. I'm fully aware of all the risks involved, so all I can say to everyone is, proceed with caution.
andonnguyen said:
Jashsu you sound really jealous. lol jk. But I do agree with you. First jesusfreke was god, now haykuro. Isn't that blasphemy? lol.
Click to expand...
Click to collapse
I'm not jealous about having bricked about a dozen phones, i'll tell ya that
People should be approaching updaters with a serious heaping of caution, especially for something like the SPL. I won't blame Haykuro for not having fully tested the SPL before releasing it, but honestly he probably should have put up more than just a link and a wink (like I dunno some huge warnings and disclaimers). And for sure those links should have been pulled the moment that news of bricks came in. Just my two cents...
Well this sucks to hear man. Loosing a G1 is never fun...But the recent threads about the new SPL made it clear that it was only designed for the PVT. And from the looks of it, you probably have a DVT or some other derivative.
jashsu said:
I'm not jealous about having bricked about a dozen phones, i'll tell ya that
People should be approaching updaters with a serious heaping of caution, especially for something like the SPL. I won't blame Haykuro for not having fully tested the SPL before releasing it, but honestly he probably should have put up more than just a link and a wink (like I dunno some huge warnings and disclaimers). And for sure those links should have been pulled the moment that news of bricks came in. Just my two cents...
Click to expand...
Click to collapse
Haykuro is not to blame for anything. He also shouldn't have put up more info because....he can't. All of this is pretty much undocumented. It's all trial and error. If it wasn't for people like Haykuro, Dude, or JF...etc. We wouldn't have any of these new updates to our phones.
OP you should of read this first before attempting to use the new SPL.
READ THIS FIRST if you are flashing Haykuros new SPL
http://forum.xda-developers.com/showthread.php?t=516433&page=10
Bavilo said:
Haykuro is not to blame for anything. He also shouldn't have put up more info because....he can't. All of this is pretty much undocumented. It's all trial and error. If it wasn't for people like Haykuro, Dude, or JF...etc. We wouldn't have any of these new updates to our phones.
Click to expand...
Click to collapse
Let's imagine for a second that there was a room full of really thirsty kids. I walk in with an unmarked bottle of a strange looking liquid. I can't describe it because I myself don't know much about it. Would you say it would be irresponsible on my part to just leave it there with those kids who don't know any better? More to the point, would you blame me if one of those kids got sick after drinking it?
In a more perfect world, everyone would do a lot of prior research, understand the risks associated with experimental hacks, and fully accept the consequences of bricked devices. Unfortunately this is not a perfect world.
alright a appreciate some of you for been nice and try to help (that was the point for me writting this at first). And for the ones been rude and trying to act all smart ! F&@$ Off ! alright ? i need help and i learned from my mistakes. If you think i acted not rational or smart, you dont have to say anything. Just stay quite and move on and help others that need more help in the forum. Just dont come and start saying stuff that are not helping at all, and for the record i did not blame nobody for the mistake I made. I personally got a G1 running the SPL just fine, and i just didnt know that there were 2 different boards running on the G1's. So please stay away if you are not going to say anything positive, and try to help. thank you.
that sucks
Cant we all just get along
Two months agoi tried updating my phone. I did a reboot after loading a update.zip file from my sd card and my G1 didnt turn on at all. No g1 screen or any kind of response.
And now my G1 is bricked.
My question is do you think they will exchange it for me still? What should I say happened?
Alright this is enough. I think instead of treating users with bricked phones as noobs and lecturing them about being careful, we get to the point and try and help.
First off, we have a whole thread dedicated to the bricked phones now. One member is working on schematics to build an actual USB wire for a force install of a SPL to possibly repair the bricked phone issues. Right now, the plans are done, so we will see if he is able to construct the cable. However, the schematics are already uploaded, so maybe you should give a shot at it. look for the G1 brick technical think thank thread.
As I am working my way through the public transportation circuit back to my dev chair, I have a chance to ask for help if someone(s) are interested in helping the doubleshot development effort at large.
Development in the open source community is about two main points:
1. Being driven by your curiosity to learn something new or make something do whatever it does differently or better.
2. Distributing the workload of what we want or need between multiple people - many hands make light work and if everyone contributes something small collectively it turns into a whole lot of progress and success.
So here's something that would help us all out immensely even though it seems like a small issue on the surface:
.nb0 and .nbh files - how to break them down and an explanation of how exactly they work.
What they are is a proprietary format used to wrap up some of the installer files within OTA and software updates we get from HTC for this device. (Other HTC devices too)
We also need to have or have links to the software we need to break them down with.
This information and how to use it will make a tremendous difference in how quickly and effectively we can assimilate and process our official software updates and continue to deliver both S-OFF and Root solutions when they are stripped from us on OTA pushes.
I'm making too much progress on other fronts and with other issues to stop and take care of this, and the very limited searching I've been willing to spare on this front has lead to dead ends and dead (mostly megaupload) links to what we would need.
Honestly, I've got a lot of dev work I've gotten myself involved in with this device and the progress I make doing other stuff is greater then putting more time into this, based on the project files I have in process. If I was just starting with helping out on doubleshot development this would be what I would be spending time on - just where I'm at I lose momentum focusing on this.
I get PM's from people asking for advice or direction on how to help out in addition to a scattering of threads around here started by people with lot's of enthusiasm but no direction, and I definitely understand! I've been and (believe it or not) continue to be in that very same position!
Sometimes all people need is a nudge in a direction, a path pointed out to them that they can explore and learn about - this is just such a signpost on the way to becoming the developer some of you out there want to be.
Development basically = knowledge + implementation, and the more you know the more creatively you can leverage it to your advantage. We certainly have some creative people who have passed through or are here now surprising us every day.
From the impressively out of nowhere CM7 port kornyone gifted us with in the past to the jaw-dropping brute-force ICS work tbalden blazed a trail into ( and sucked a few people into along the way ) all the way down to the work XMC has been steadily chipping away at building tools for us to use and wrap it all together with - we really have some talent, passion and a lot of success in our small but effective corner of the XDA forums.
...and those are only a few of the people who have made a lot happen around here, there are and certainly have been others who have either left a mark on development for this device or continue to do so.
Excited? I am! There's so much cool stuff to do and who cares if we never get an 'official' ICS update? We (collectively) are producing software the manufacturers/carriers wish they could produce in a fraction of the time it would take them to do so.
What some may not realize, though, is that it isn't this person or that person making it happen, but the collective efforts of us all together that enhance and compliment the individual strengths we all bring to the table separately.
...and it's all built on us sharing what we know and helping each other out. Maybe some out there, especially the more casual viewers or unregistered lurkers don't realize just how much we work together - where the larger sub-forums are more scattered and individualized just because of their population.
As an aspiring dev, this should make our little corner even more appealing because that leaves a lot more new ground to cover and gives everyone who jumps in that much more of an impact on what we have available.
Maybe in other places you're the fiftieth person to make some lockring or point something out, but over here just about anything you get into is new ground for us - so we are definitely excited about everything anyone has to offer, no matter how trivial it may seem to you.
As many of you have gathered by now I'm a bit long winded at times, but it's all so exciting!
So back to the original point, which was that if someone or a handful of someone's wanted to do something to help out, and push development for the device forward but wasn't sure what to do, figuring out how those .nb0 and .nbh files work and finding some software to crack them open with would be a big help in gaining and maintaining S-OFF and Root for this device.
.nb0 files especially, because they are something within the OTA that is a single file that impacts multiple partitions, and we really haven't gotten a look inside of them at what exactly they are doing to our device and how.
The death of megaupload and sites like it cost the open source community a lot of tools that are in some cases still missing and in others maybe never to be replaced...at least not without someone taking the time to sit down and do so.
...could that be you?
gtmaster303 said:
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Click to expand...
Click to collapse
Cliff notes:
Blue6IX said:
The strength of XDA is the community itself and the knowledge it contains. If we want to truly leverage it here in the doubleshot forums, this is how it can be utilized the best.
Click to expand...
Click to collapse
Any and all info on the .nb0 or .nbh file format, anything people can gather.
How do we break them apart?
What is inside of them when we do?
What partitions does it flash it's pieces to, are the individual pieces signed or just the file itself?
Can we make these files?
...How?
.nb0 is inside the OTA packages, .nbh is a type of package like the PG59IMG.zip files, so the tools to work with them are different?
Here is an .nbh thread that could help get someone started...
NBHextract: Extract contents from NBH files with a tool but we don't have any of these files yet?
Here is the wiki page it links to which will help more:
NBH wiki page that it links to on that tool page which might help some more.
I bring up .nbh because that is one of the methods of insertion the auto-install tries to use when booting to hboot:
Blue6IX said:
When loading hboot, the files it automatically looks for on the sdcard are:
- PG59DIAG.zip
- PG59DIAG.nbh
- PG59IMG.zip
- PG59IMG.nbh
- PG59IMG.tar
- PG59IMG.aes
- PG59IMG.enc
Click to expand...
Click to collapse
...and the more people we have familiar with these files and spend time helping us to figure them out, the better equipped we will be to deal with new OTA packages and everything that goes with them.
What do we know? Collectively, here, not very much - if so, someone speak up and if not here's something people can help with.
How do we make .nbh files, or any of the other packages quoted there we don't have?
We've pretty thoroughly examined PG59IMG.zip files but the .nb0 files in them are still somewhat of a mystery - here are the ones from the 3 PG59IMG.zip files you can find links to here:
Restore to Stock
Files:
doubleshot_1-28-531-9_nb0.zip
Download Link
MD5: d5e8721090dbc048c711d7f42404286b
Size: 1.75 MB
doubleshot_1-55-531-3_nb0.zip
Download Link
MD5: dba1925982b4c5e0a41f3291942e09e0
Size: 1.75 MB
doubleshot_1-63-531-2_nb0.zip
Download Link
MD5: aaa9edc7b2c5ec91559ab01caebab8ac
Size: 1.75 MB
These zip files are in uncompressed form, simply zipped in store - small files but 2 each. Here you go, hope someone has fun with them!
Sent from a digital distance.
http://www.ubiquitense.com/technology/how-to-install-android-roms-with-nb0-file-extension/2800/
dont know if this is what you are looking for but maybe........
i think this is better?
http://android-dls.com/wiki/index.php?title=How_to_unpack_and_repack_NB0_file
tl;dr:
Blue is a noob with poor time management skills.
jk, I would love to see more people get involved with development. You can't really ***** about a lack of development and then not be willing to support it.
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Usually, all unknown file types I come across I run through winrar and see how it handles it.
Found this with a quick google:
http://filext.com/file-extension/NB0
I edited the first post, adding the second half to it starting with the quote below:
gtmaster303 said:
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Click to expand...
Click to collapse
As evidenced by my original posting, being concise is not my strong suit.
I posted that from the doubleshot while I was sitting somewhere waiting for people, and so it was a little all over the place even for me. Hope this post and the edits above clarify the intentions of this thread better?
Can someone explain how to break down the nb0 files and find tools to do it properly? See if you can sit down and crack one open and see what's inside.
See how many of the questions can be answered from above, and what other ones we don't know enough to ask are/their answer(s) are?
The doubleshot community benefits from it's developers having how-to references on the things we need to do, and pretty much everything we need to know is scattered all over XDA.
It takes time to funnel, qualify, and share that information here so we can use it.
Many more people will be able to dev for this device if they can come here and learn how to do it, and not have to resort to the XDA scavenger hunt that every other dev who started here had to go through.
If other people can see the value of and want to help out in searching out how to do things and get it here for us to use, the honest truth is that's a resource built by the developers here or not at all.
Learning how to do things and going through that experience and what the pitfalls are and finding where to get what you need to do it is basically development.
Sharing those experiences with XDA is what makes this community a resource.
Bringing it here gives people who want to dev and don't know where to start a learning project that can benefit everyone working here.
Something like this is a good trial for posing this question - there are a lot of things that we would benefit from having here and not just on XDA at large. If someone or people want to get together and solve this mystery because they were looking for a problem to solve, then here is the best way to turn that learning experience into a guide for the rest of us.
...and we can check that off our list of things we need to learn how to do.
I can make a post at some point with a concise listing of things we need to know about, with a link to a summary of what we know about each, and then we could use it as a checklist to start systematically solving our problems and making the device do what we need to do.
The strength of XDA is the community itself and the knowledge it contains. If we want to truly leverage it here in the doubleshot forums, this is how it can be utilized the best.
--------
So, when someone gets so energized by this as many of us have felt at some point - that overwhelming desire to help but complete confusion on where to start?
Go learn something we don't know and share how to do it or what it is here. We all benefit and people already here working on other things can just add how to do whatever that is to their methods.
Please don't think this is a case of me sitting here saying "i'm too lazy to learn how to do this, someone teach me" ...
...this is a case of "does anyone out there want to help explain what this is and how to use it? Here's a project if anyone wants it" ...
...i've written quite a few guides here as i've learned how to do things, and wouldn't pose this kind of question without having contributed first. So just offering a starting point to anyone else willing to do that too.
If there is interest in people taking the project on, I can make a checklist of what we need to know and we can have a point of reference on how to spend our time when looking for projects to do.
If no one's interested in learning this and sharing it here then I won't waste the time it would take to put such a list together and source everything. Eventually i'll figure this out and share it here if no one does, but we would grow as a community for others to do it. Just looking for ways to make everything work more smoothly here.
This place is whatever we make it to be, so do we want this?
You think it would help if we asked HTC dev what they're for?
I would love to help! But I don't know anything about being a Dev.
Hi Blue6IX,
I've read most of your post, but I don't quite understand to what purpose we need the contents of these files.
I mean, I got my Doubleshot, rooted/S-OFF'ed it with revolutionary/unrevoked and SIM unlocked it following this guide and installed an ICS ROM. Is there anything that prevents others from doing the same?
Also, I come from the Moto Milestone, which has a locked bootloader and no way to unlock, and still people managed to get ICS up and running (with 2.2 being the latest version Motorola wanted us to have on the device).
For the Doubleshot, you can just fire up a repo sync with CM9, get the preliminary msm8660 device tree(s) and create a doubleshot device tree. I know it will require some adaptations and coding, but IMHO this is nowhere near the problems other devices face.
Since I didn't really find any information on other hindrances, I would be glad to hear of them. Otherwise, I don't think analyzing HTC's/T-Mobile's original update files will be useful for anything?
Curiously yours,
Stefan
seidler2547 said:
...
I mean, I got my Doubleshot, rooted/S-OFF'ed it with revolutionary/unrevoked and SIM unlocked it following this guide and installed an ICS ROM. Is there anything that prevents others from doing the same?
...
Click to expand...
Click to collapse
Yea - for a while S-OFF was impossible for any device on the 1.55.531.3 software version ( or later ) with hboot 1.45.0013
There was also a time where they couldn't unlock the device and were basically stuck barely able to root.
For most people, S-ON and unlocked is the best it can get at the moment - making it pain to flash roms with custom kernels and completely unable to go back to the stock radio or hboot.
seidler2547 said:
Hi Blue6IX,
I've read most of your post, but I don't quite understand to what purpose we need the contents of these files.
...
Otherwise, I don't think analyzing HTC's/T-Mobile's original update files will be useful for anything?
Curiously yours,
Stefan
Click to expand...
Click to collapse
I cut out most of the post you made ... ( quoting a whole post unnecessarily is rather annoying ) ... But you really answered your own question here.
Do you know for certain they won't help now or in the future?
Have you checked to see?
How can you check if you can't break it open?
If you can, could you share directions how and working links to tools to do it with?
...the OTA and PG59IMG.zip packages are how the manufacturer updates the device and makes changes to things we can't - knowing how they do it can help lead to a way for us to do it.
Especially since we don't have a proper RUU and basically are left begging for scraps at the "official" software table for the device - knowing how the few legitimate software packages work we get becomes even more important.
Every time an OTA update comes out, the possibility exists to lose root, S-OFF or even a working device ( the next broken update will NOT be the first ).
As you mentioned being curious, well, you hit the nail on the head as to the entire purpose of the thread.
I'm curious, anyone serious about helping us keep root at the very least is too ( and if not, now know they should be and a bit about why ).
It's one of many, many pieces to the puzzle, but the more thoroughly we understand each puzzle piece itself, the better of a chance we have at actually putting it together.
Bottom line is we don't know, we should know, and the project of finding out and sharing it here is a great opportunity for someone who wants to learn how to be a dev and has no clue where to start.
This project is on my list, but I figured i'd post it here and create an opportunity for anyone interested in it...otherwise I'll get to it at some point.
For all the time I've put in the thread, I probably could have made progress on the answers to at least some of the questions I've posed. I'd rather see if investing that time in soliciting more participation is worthwhile. It's not something I need, but rather something WE need...
Anyone like a good mystery?
Sent from a digital distance.
wanting to know if it's possible ( obviously maybe not the right thread ) ive thought about doing this and obviously it's going to be "advance" but since androids basically computers with linux instead of windows is there anyway that i can delete all the partitions and "re install" the boot.img the system.img etc to the respect blocks and allow for downgrade through advance means? if so im willing to take on the task ( this was my brother's old s3 and it's cracked and i don't care if i destroy it so ) im willing to take one for the dev team and personally destroy my data and even the phone if it comes to it i don't care about bounties i honestly don't i just care about getting our phones back to being OUR'S not some locked down piece of plastic so if there's anyway to do so please let me know and send me links etc and if need be please explain if it would take jtag im hoping not due to well not having one lol but please if there are any devs that are willing to help me out i would appreciate it ( for links advice etc ) like i said IDC if i destroy this phone i truly don't ( i about threw it against my wall just cause i was so pissed off that it's locked down ) but if there is anyway of literally deleting ALL partitions and manually installing the OS i would appreciate it and yes i am familiar with android and linux and computers in general but as i stated im willing to take one for the team
i've made a tutorial long ago for modifying i9300 partitions, here: http://forum.xda-developers.com/galaxy-s3/development/mod-usable-space-smaller-custom-roms-t1873734
I've never had or have seen any other s3 variants, so be wary - the method might not work.
Hi,
I just bought a one s and read through the forums for root, s-off and so on.
Compared to my EVO 3D and Sensation, s-off seems to be less painfull since there are some convenient exploits around that don't need any hardware actions (as the wire trick or soft brick the device).
But I got a little bit concerned about some posts claiming that after s-off the 3g connectivity got lost,
though reading the threads of the latest/greatest custom roms, there's nothing mentioned.
There's one dedicated thread in dev section, but I found no clear statement on how this is to fix.
Some state, that simply changing rom helps to get 3g back.
Some say it's a radio thing.
One member described a method where memory block is manipulated, but this also didn't work for all.
Till now I s-offed each htc phone I owned immediately, but now I'm getting doubts.
I'd appreciate any feedback on this from you experienced ville users out there.
To save you money, time and grief DONT DO IT.
Surely me and most everyone else is thankful that these guys spend time developing and tinkering but I screwed 2 One S,
that is when those disclaimers kick in, and I also looked, not exhaustively, for a skilled JTAG tech/user, the guy I sent it to
said he couldn't figure it out.
Maybe someone here can; most people that JTAG said that doing it to that phone is hard because it has to be taken apart.
Honestly, S-Off would make sense if its a new device to come in the market, as you have noticed, most ROMs and apps just
disappeared and the latest radio put together by someone in here is a 1.35.XX.XX. Since ROMs are limited, and most developers
dont even bother with this device just leave it alone. If flashing the radios is what you want, try the Aroma radio installer for Sense,
if I remember correctly, I think I flashed a radio while running SlimROM and the radio did not reset after reboot.
P.S. If you decide to do it, before hand, find a JTAG tech that has experience with it and can fix this problem, and post it here, please.
I'm still holding on to it in case I find such a person.
sns00 said:
To save you money, time and grief DONT DO IT.
Surely me and most everyone else is thankful that these guys spend time developing and tinkering but I screwed 2 One S,
that is when those disclaimers kick in, and I also looked, not exhaustively, for a skilled JTAG tech/user, the guy I sent it to
said he couldn't figure it out.
Maybe someone here can; most people that JTAG said that doing it to that phone is hard because it has to be taken apart.
Honestly, S-Off would make sense if its a new device to come in the market, as you have noticed, most ROMs and apps just
disappeared and the latest radio put together by someone in here is a 1.35.XX.XX. Since ROMs are limited, and most developers
dont even bother with this device just leave it alone. If flashing the radios is what you want, try the Aroma radio installer for Sense,
if I remember correctly, I think I flashed a radio while running SlimROM and the radio did not reset after reboot.
P.S. If you decide to do it, before hand, find a JTAG tech that has experience with it and can fix this problem, and post it here, please.
I'm still holding on to it in case I find such a person.
Click to expand...
Click to collapse
OP is four month old ...
I never screwed up ANY HTC phone, because they are pretty nice to handle. If the phone fits the prerequisites S-OFF is easy to gain. That users screw their phones by wrong handling is not the dev's fault
Well, good for you:victory:. Since you know so much, why not show everyone else how to properly handle the device?
Did not mentioned methods/names, so I think I did not offended anyone. If software/hardware did not break, there wouldn't
be a disclaimer on the device and on the software.
That the post is 4 months old is irrelevant, we are not the only ones with One S. Next time provide a solution along with criticism.
If this post offended anyone in any way shape or form, complain to a moderator so my post can be erased.
LS.xD said:
OP is four month old ...
I never screwed up ANY HTC phone, because they are pretty nice to handle. If the phone fits the prerequisites S-OFF is easy to gain. That users screw their phones by wrong handling is not the dev's fault
Click to expand...
Click to collapse
sns00 said:
Well, good for you:victory:. Since you know so much, why not show everyone else how to properly handle the device?
Did not mentioned methods/names, so I think I did not offended anyone. If software/hardware did not break, there wouldn't
be a disclaimer on the device and on the software.
That the post is 4 months old is irrelevant, we are not the only ones with One S. Next time provide a solution along with criticism.
If this post offended anyone in any way shape or form, complain to a moderator so my post can be erased.
Click to expand...
Click to collapse
I'm fine with your post I try to help in any case I can. Since today I "bricked" one Samsung phone by following a incorrect guide from another forum, cost me 40$ to repair the bootloader. But that can happen and its totally okay for me and I won't stop modding phones just because of it. For most users S-OFF works without any problem and grant a lot of benefits. So just because you screwed up two One S you can't tell other members to don't set their phone S-OFF as it will probably brick...
Dude, they will do whatever they want with their devices, regardless of what you , me or anyone say.
And the same way you can speak your piece, I can speak my piece, so do not tell me that I can't say this or that. If you don't like what others have to say, there's a number of things you could do instead of reading what I type.
Just sharing an experience that things can go wrong, as it just happened to you. S-Off'ing a phone is something I wouldn't pontificate to a regular user, because if things don't work out I'm not going to pay for a replacement or repair costs. That mod is a "at your own risk" as most other mods are. Do you realize we are a minority, a big chunk of the world don't even install themes on their devices, millions of locked bootloaders, billions of S-On devices and I had nothing to do with it; what are you going to do about that?
S-On works for me, so far, with my M8 GPe, I don't earn a living working with phones or anything related to it, I don't even know how to make a simple app, so what I post is not the gospel, as I assumed it is implied.
"For MOST users S-OFF works..." I rest my case.
LS.xD said:
I'm fine with your post I try to help in any case I can. Since today I "bricked" one Samsung phone by following a incorrect guide from another forum, cost me 40$ to repair the bootloader. But that can happen and its totally okay for me and I won't stop modding phones just because of it. For most users S-OFF works without any problem and grant a lot of benefits. So just because you screwed up two One S you can't tell other members to don't set their phone S-OFF as it will probably brick...
Click to expand...
Click to collapse
sns00 said:
"For MOST users S-OFF works..."
Click to expand...
Click to collapse
Most off the poeple, who set their HTC One S and other HTC devices S-OFF, still enjoy a working phone after this modification.
Better?
I just got one question left.
After you broke one HTC One S, why you did you risk doing (probably the same thing) again?
Hi. I've been wanting to root my phone for a while now, but since as I am still a kid, I asked my parents if I could. They didn't like the idea of bricking. I tried to explain how low the risks are to them, but no.
I'm pretty sure that hearing professional's opinions on it would atleast help to change their mind.
You may be thinking, since im only a kid, that I dont know all this types of stuff? Well, I spend most of my time on the computer and I generally am really good with them.
I know a good of C++, but thats beside the topic.
(I would be using kingroot's one click since I have a nexus 5)
Thank you, and best regards,
R3pix.
R3pix said:
Hi. I've been wanting to root my phone for a while now, but since as I am still a kid, I asked my parents if I could. They didn't like the idea of bricking. I tried to explain how low the risks are to them, but no.
I'm pretty sure that hearing professional's opinions on it would atleast help to change their mind.
You may be thinking, since im only a kid, that I dont know all this types of stuff? Well, I spend most of my time on the computer and I generally am really good with them.
I know a good of C++, but thats beside the topic.
(I would be using kingroot's one click since I have a nexus 5)
Thank you, and best regards,
R3pix.
Click to expand...
Click to collapse
I'm going to have to give you a thumbs down on rooting.
If you need king root to root a nexus, you don't know what your doing and shouldn't root.
bweN diorD said:
I'm going to have to give you a thumbs down on rooting.
If you need king root to root a nexus, you don't know what your doing and shouldn't root.
Click to expand...
Click to collapse
I know how to root without KR, but it seems like the easiest way.. (I meant since it supports it)
R3pix said:
I know how to root without KR, but it seems like the easiest way.. (I meant since it supports it)
Click to expand...
Click to collapse
i can root any nexus the right way in under 5 minutes. how is that difficult? and better to use the trash root that king gives you?
no one is going to support your petition to be allowed to root, when your using king on a nexus.
dont believe me? go post exactly what you posted here in the n5 forum. they will flame you mercilessly, i guarantee it.
im being nice about the situation, trust me lol
It's pretty damn hard to actually brick a Nexus. Permanently, anyway. In fact, I'm not sure it's even possible. With TWRP recover you can just restore from a back-up if you screw something up, and as long as you can boot into download mode, you can always just reflash the factory firmwares from a PC.
However, I think the method you'd use is less important than the question of why you want or think you need to root in the first place. If it's to learn about Android, programming, app making, etc for a future career (or even just a hobby) then I think it's a great idea. But not on your Nexus 5, if that's your only phone. Even if you screw something up, but not permanently, you still don't want to be without your phone for however long it takes to fix it.
I don't know how much money might be at your disposal (or your parents), but my suggestion would be to look on Swappa or eBay for something cheap to play around and learn with. Like a Nexus 4 or Galaxy S3. Both can be had for under $100 if you don't mind a little wear and tear. Heck, there's a brand new 16GB Nexus 4 listed right now for $123. If you can afford just a bit more, a second Nexus 5 for ~$150 would be an even better device to learn on, since it has official Marshmallow 6.0. Heck, a Nexus 7 tablet would be learning device, with its bigger screen.
You've already shown commendable responsibility in asking your parents and not just going ahead behind their backs, so I'll say this to you: If you want to convince your parents to let you try, or better yet, get the second device to experiment with, explain to them that a smartphone isn't a phone anymore. It's a computer that fits in your pocket that you can make calls with. And a Nexus is like a home-built PC that doesn't require restore disks and impossible-to-find drivers to fix if you happen to screw something up. And frankly, screwing up and learning how to fix your mistakes and not make others is all part of the knowledge process. Trust me, we've all done it.
But, if you want to root just to get free gems and gold and screenshot Snapchat pictures without the other party knowing, then that's an entirely different thing. And I'm not your parents.
Reasons for bricking a device.
Which are the major reasons which results into a useless bricked device?? I frequently use xposed modules and my device is mtk 6592 chipset one.
Please throw some light on my querry. Thanks
SKDesignsuccw said:
Which are the major reasons which results into a useless bricked device?? I frequently use xposed modules and my device is mtk 6592 chipset one.
Please throw some light on my querry. Thanks
Click to expand...
Click to collapse
the #1 way to brick your device from rooting, or any other mod is user error.