Related
Hello everyone. I want to thank you all for this site, I have learned a great deal here and appreciate all your efforts. I have a question that many new comers have asked and they have been told to go read, so thats what I will do. I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
I am not complaining, in fact I am grateful because I am getting somewhere thanks to your help, which has been more valuable than all the help Samsung and Rogers have given me washing their hands clean and leaving me with a defective phone. My problem has not been solved just yet, but I think a 2.2.1 rom will fix my problem. Ill keep reading and trying, ill get there.
I suggest you guys have a wikipage with a table with all the roms, what versions of android they are, what kernels, modems, etc they work with ( or not work with ), bugs, features, something all in 1 page for easy access. This would make it easier for people to access information. The easier it is the more people will use them and come here, the more ideas you will have, the more testers, its a win win situation!
I have been to the pages for all the roms, some of them tell you the bluetooh voice dialing is not working, most don't, id have to go looking for my answer. I have learned that for instance it seems people do not have an issue with it with froyo 2.2.1 but again, some roms tell you in the main page its 2.2.1, others don't.
I can't grasp all the information staying up at night till 4 am. Its the only time I have. I almost had a heat attack when I thought I bricked my phone, I can't afford another one. If all the important information is right there on 1 page, like links to the usb drivers, tools, roms, kernels, everything. Have the instructions to flash. Have a table with all the roms, their versions, what versions of kernels, modems, etc, they do ( or dont ) work with. maybe even some of the table cells are clickable, for instance bugs, click on it and a window pops up with a list of them.
I know all this information is in here somewhere. Thanks to everyone for it, but it needs to be on 1 page. Please make it easier for people who are new to this. You will benefit as well as them. Looking forward to being able to use voice dialing. I think it will be working by tomorrow or after tomorrow thanks to you guys. I could have done it in a day if all the information was right there .
Thanks for reading.
Try searching.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897
I have that bookmarked. It is also a sticky in this section.
But it doesn't say for instance which ones are 2.2.1, or which ones have the terrible voice dialing over bluetooth..
I do search and end up with over 15 tabs...
I am getting by, I am just saying it could be organized better for everyones benefit. It could be made so someone who has never done this before can get it done in a couple of hours if even, without keeping asking you the same questions here. I understand why people keep asking to recommend a ROM. It is not they they do not search, not all of them anyway. Things can be better organized.
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
vunuts said:
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
Click to expand...
Click to collapse
+1
The thing is that its not just the number of ROMs, but also the number of versions that are released. It would be a real pain and an added overhead for anyone maintaining it.
Also note that most devs are working too, and doing this in their free time. The little time they have to spare is taken up for making improvements. But they do release changelogs to look into.
If anyone has time, I would suggest they take it up to create a wiki and maintain it, rather than relying or asking the devs to do it.
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Madtowndave said:
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Click to expand...
Click to collapse
http://www.capfaq.com/w/ROM_Table
Looks like they have updated it!
Thanks guys, I will check that table out tomorrow.
It'd be nice if there was a modem chart as well. I know there are modems in the modem thread
forum.xda-developers.com/showthread.php?t=835272
...but near as I can tell it's not up to date, or at least the first page is not up to date (ie base Cognition runs on JL1 and Andromeda on JL2, but aren't on the first page).
If anyone knows a good and current modem reference guide, please let me know.
I can't complain too much because obviously things change all the time and it's a PITA to constantly update info...I'd volunteer but I got a 2 year old and baby 2.0 due in April.
Madtowndave said:
baby 2.0 due in April
Click to expand...
Click to collapse
made me lol at the versioning of baby
diablo009 said:
made me lol at the versioning of baby
Click to expand...
Click to collapse
Yeah it's like Richter Scale difference at least 0 to 1, and 1 to 2 kids...people that have more than 2 are either really bad at birth control, Catholic, or gluttons for punishment.
distortionist said:
I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
Click to expand...
Click to collapse
And I thought I was the only one!
Thanks pal for making my day...
Sent from my SGH-I897 using XDA App
I bricked my phone
distortionist said:
I bricked my phone
Click to expand...
Click to collapse
How? What happened?
I have no Idea what I did wrong, my goal before I started was getting voice dial over bluetooth working for me, its essential to me. It started with trying to install paragon, as per http://www.capfaq.com/w/ROM_Table mentioned above.
I was stock rogers 2.2 so I wiped it clean, and tried the update thing, it didnt work. The only step I skipped was flash to stock and the master clear since it was 2.2 recently and I did the factory wipe. It did not work but I did not brick anything just yet. I figured most people tell you to flash with the one click odin which puts stock at&t on it. I did that and the phone stopped going into download and recovery, it did not stop completely i have gone into download and recovery a few times after that but it was a battle with my phone, since it was booting, I used adt instead which worked like a charm. at&t rom was not happy on my phone, it was going into at&t reboot loops where it would just reboot the bios over and over. after trying and trying it would boot android, i was trying to fix it but each time it restarted the reboot loop would kick off. I could not go to recovery or download mode till i finally got back into the OS and used adt to tell it to go to download mode where i reflashed my stock rogers.
My phone now had at&t logo on boot before rogers, which is not that bad but i had read you can get rid of it, i tried going into download mode with the buttons but didnt try too hard, adt was easier.
I was following these instructions :
http://www.mmacleod.ca/blog/2011/01/removing-the-att-boot-screen-from-a-samsung-captivate/
it wanted me to use odin to flash a file. I used my oden 1.3, i think he says oden 1.0, I didn't think it would make a difference.
Odin started to flash and said fail. I got the screen with "android ! computer", I have been there before when I first ever tried using odin and had to fight with my phone to get to download mode at the time ( this was before at&t ever came close to the phone, i never used odin before so i probably had trouble because of inexperience ).
anyway, this time no matter what I do I cannot go to download mode, I plan on making a jig today if i find someone who sells resistors in this little town.
any help would be appreciated. I dont want to put any more roms on my phone, i just want it to work. I am worried. Ill wait till samsung releases 2.2.1 I just want my phone back to the way it was when I bought it
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
nbs11 said:
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
Click to expand...
Click to collapse
True, but once done, it would be much easier to maintain and navigate. There is going to be a lot of crossposting and people asking for insight and advice.
I'm sure we all understand the search feature in the forum, but to be honest things change topic within a thread, and where someone asks a question that is somewhat unrelated and gets a very good answer, it is not always apparent by poking through page after page of posts to find that nugget of gold. I mean, searching for 'kernel' will give literally thousands of hits. A wiki would be much better in terms of 1. Where you are starting out from 2. what you need to do what you want 3. where to find these things, and 4. maintaining updates and version revisions.
I really appreciate all the work people do here, and I have had to find everything I wanted to know the 'hard' way, but as Android grows in popularity and market percentage, more and more people are going to come here looking for this information. Pobably better to do it sooner than later.
I just read a post by roebeet (well known dev who put together the TNT Lite ROMS) and something he said made enough sense to me that I thing everyone needs to hear it.
If you are going to flash and try everything you find on this site -- you run a real risk have having problems. Everything you flash adds, changes and deletes stuff from your tablet and some of that gets carried over from ROM to ROM to program.
Just because you partition/erase/delete/overwrite does not mean your tablet content is destroyed. There are a bunch of partitions on your tablet (12?) and some are preserved and some are modified depending on what you do.
So am I saying "Don't mod you G-Tablet" or "Don't try out new stuff." NO.
1. Make real sure you know what you are doing. Too many people just rush ahead and wind up with real problems.
2. Read directions and read all the posts about others who have done the same thing you want to do.
3. When you are making changes, do them one at a time and make sure it's working right before moving on. When you change a bunch of stuff it's hard to tell what the problem/problems is and where it came from.
4. IMHO, too many people see the modding as a game and then they get mad at the dev or people who are trying to help them -- when all the time it was their own fault!
I think it would even be a good idea if someone knowledgeable could help us see if we could put together a flash which would actually delete/erase what's on a
troubled tab so it could be rebuilt. Sorry, but I don't talk enough Android yet to do that.
Think about it.
Rev
butchconner said:
I think it would even be a good idea if someone knowledgeable could help us see if we could put together a flash which would actually delete/erase what's on a
troubled tab so it could be rebuilt.
Rev
Click to expand...
Click to collapse
I would recommend running a format zip before any reloading on a Gtab whether a new rom or the stock. Just like all the computers I work on for people the first thing I do is run a program to erase the hard drive to make sure nothing old can interfere with a new reload of the operating system
Calkulin has this format zip from his rom thread or you could use the other one from here
http://forum.xda-developers.com/showthread.php?t=974422
Start fresh don't just overwrite!
ale
Calkulin's Format all is awesome
Exactly. Calkulin's format all is a life saver. It is much cleaner and faster way than to do three or four steps to clean stuff out (Invariably one forgets one of the steps which causes all the problems).
I have used this file to solve many problems going from rom to rom... Good stuff.
[Q] Should I step back and use the format zip?
notsob2002 said:
I would recommend running a format zip before any reloading on a Gtab whether a new rom or the stock. Just like all the computers I work on for people the first thing I do is run a program to erase the hard drive to make sure nothing old can interfere with a new reload of the operating system
Calkulin has this format zip from his rom thread or you could use the other one from here
http://forum.xda-developers.com/showthread.php?t=974422
Start fresh don't just overwrite!
ale
Click to expand...
Click to collapse
Two days ago I reset my gtab to stock. I have the 3389 zip saved and installed that using clockwork. I also used clockwork and did the data wipe/factory reset right before actually applying the rom.
Loading the stock VS rom removes clockwork and after reboot it pulled the OTA update and currently running the 3588 version.
I did this in anticipation of the upcoming VS update. The tablet seems to be running fine and as I said it's able to find and apply OTA updates.
Would you still recommend running this format zip, and then re-apply the 3389 I have saved?
Thanks,
Neudle
** Would like to point out there is a comment in the referenced post concerning using this format zip..."So this is a "detox" program for our gtablet that we can choose to run prior to NVflash process. And this process should not be done unless absolutely necessary, right?" "Yes, exactly..."
Neudle,
If you were at 3389 and did 3588 via OTA, I would try my recovery. If it does not
come up with your old CWM, then it should be stock recovery and you should be
good to go.
If needed, you always have the option of manually loading recovery and the 3588 update.zip into /sdcard and flashing stock again.
Rev
butchconner said:
Neudle,
If you were at 3389 and did 3588 via OTA, I would try my recovery. If it does not
come up with your old CWM, then it should be stock recovery and you should be
good to go.
If needed, you always have the option of manually loading recovery and the 3588 update.zip into /sdcard and flashing stock again.
Rev
Click to expand...
Click to collapse
Thank you for the response.
Actually I think my tablet is fine. Unless I'm really confused (which is certainly possible) 3389 was the update from late december/early january. The 3588 is the update that came up in like febuary. Isn't 3588 the most recent?
This isn't the first time I've reloaded the stock rom and it seems it always over-writes/removes the clockworkmod.
I was simply more curious if you folks do feel it's always best to use the format.zip when swapping roms?
As I said, I'm simply prepping and anticipating the upcoming update from Viewsonic and not worried about clockworkmod for the time being. From what I've seen the update includes a recovery that looks similar.
Thanks again,
Neudle
I think the OP makes an excellent point for all us weekend tinkerers. The G-Tab is my first experience with an android device and although I have experience with rooting and flashing roms and kernals on another platform (WEBOS on my Palm pre), I have spent my first few weeks with this device just reading as much as I can on these forums before trying anything myself.
I was fortunate enough to get a great deal on this tab second hand from somebody who had already flashed it with Vegantab ( I believe 5.1.1). As it stands, it pretty much does everything I need it to do and there is no reason to break what alreday works...... except that I am a weekend tinkerer...... and I am thinking that I would like to try Calkulin's rom.
At the moment, I am not sure that it represent's an upgrade over what I have and I may wait for something gingerbread or honeycomb based that people report to have a signifigant benefit over Vegan 5.1.1...although I am sure I will convince myself differently at some point.
I know that I have CWM installed and that I can use this to clear up caches and personal info before flashing another ROM. Does Calkulin's format erase this? If so, does it need to be re-installed before putting on a new ROM? I am reading posts about people flashing back to stock and receiving updates before flashing a new rom. This completely confuses me as I don't understand the benefit unless, as the OP seems to indicate, there are bits that are left over from the old ROM when a new one is flashed. Is this desirable?
Sorry if I am asking so many questions in this thread. I know that there are bits and pieces of info scattered among many threads but some of it seems contradictory and some I am sure is outdated.
Can someone either outline or point me in the right direction to a step by step that outlines the most current and least likely way to brick upgrade from Vegan to Calkulin's ROM?
Thanks
butchconner said:
2. Read directions and read all the posts about others who have done the same thing you want to do.
Click to expand...
Click to collapse
Here's my problem. Where is the step by step, this is how you take a GTab you just bought, to ROM "XYZ" the correct way? There are lots of "how to"s scattered all over this forum, but no one sticky at the top that says "Here's a step by step". Right now, I'm reading through everything again, before I try and mod my tablet, and it's a mess. It would be nice is someone+moderator made a nice, straight forward LOCKED thread that is stuck, that explains it all. The FAQ isn't quite the information necessary (in my eyes).
I'm pretty technical (engineer by trade) and if it takes me a bit to figure out how to do something, the general n00b is going to screw something up.
Just my thoughts.
h3llphyre said:
Here's my problem. Where is the step by step, this is how you take a GTab you just bought, to ROM "XYZ" the correct way? There are lots of "how to"s scattered all over this forum, but no one sticky at the top that says "Here's a step by step". Right now, I'm reading through everything again, before I try and mod my tablet, and it's a mess. It would be nice is someone+moderator made a nice, straight forward LOCKED thread that is stuck, that explains it all. The FAQ isn't quite the information necessary (in my eyes).
I'm pretty technical (engineer by trade) and if it takes me a bit to figure out how to do something, the general n00b is going to screw something up.
Just my thoughts.
Click to expand...
Click to collapse
I haven't found that to be the case at all. In fact, I've seen nothing but repetitive reinforcement of proper procedures from every knowledgeable source. If the ROM Creator says use clockworkmod to install then wipe data... well do it. If he/she says use standard recovery... well... This isn't rocket science. I've installed and tested every ROM listed here with no failures by following the included instructions. I can't believe that is an anomaly.
If you want to be truly successful, learn what each of these tools (clockworkmod, nvflash, etc.) does and more importantly what they do not do. When you educate yourself to their proper use you won't be finding yourself using a hammer when you need a screwdriver.
hotfire!,
I think that's one of the points I hoped to make in this thread.
I appreciate the "format" tips -- but I have not used it and none of the folks whose opinion I watch for have put their stamp of approval on it -- so my opinion of it is still
in the making. I will use it only cautiously until I have confidence it is good.
But as you have said, we do have a hodgepodge of stuff here. People try to do
too much too fast -- and others suggest stuff that doesn't need to be done.
For example -- if somethings crashes on my G-Tablet, I go back to a basic CWM/ROM combo that I know is good so I have a solid place to start and then rebuild. Takes a little longer, but I think it save me a lot of anquish.
So like a lot of others, I just help where I can. But I do try to be conservative and consistent making suggestions the will not "snow" the new or offend those who think
they know what they are doing.
And to everyone I suggest the wrong thing, OOOOPs, and apologies. To those who
help me an give others good help -- thank you.
Rev
K J Rad said:
I haven't found that to be the case at all. In fact, I've seen nothing but repetitive reinforcement of proper procedures from every knowledgeable source. If the ROM Creator says use clockworkmod to install then wipe data... well do it. If he/she says use standard recovery... well... This isn't rocket science. I've installed and tested every ROM listed here with no failures by following the included instructions. I can't believe that is an anomaly.
If you want to be truly successful, learn what each of these tools (clockworkmod, nvflash, etc.) does and more importantly what they do not do. When you educate yourself to their proper use you won't be finding yourself using a hammer when you need a screwdriver.
Click to expand...
Click to collapse
But therein lies the problem. There *is* a great thread on installing CWM and then ROMs using that. Step by step, it's fantastic. Installing a new kernel *is* found in some of the threads, but I wish that great thread with the CWM and ROM installation also had Kernel info.
Regardless of if you know how these tools work, it's nice to have a step by step to follow, just to ensure you're doing everything in order. I do it at work when I'm working with a new system (I write it myself) just to make sure I follow the same procedure every time. It helps when problems arise.
I'm just saying, for the n00bs, it would be nice to have a "one size fits all" thread. I was able to successfully install CWM and Vegan without a single problem, as I've been reading this forum for MONTHS, but I'm not a normal person (nor are most of the regulars here).
One thing I try to do, is demystify technology. Make it easy, explain it in simple ways while still being effective as describing what is going on, and then you don't get "stupid questions" later. Essentially, trying to run in the opposite direction that most Linux forums tend to be. Threads buried 2 years back have the info, everyone screams at the n00bs saying "USE THE SEARCH".
Love this forum, the people here are REALLY helpful, but there is room for improvement. That's all I'm saying.
h3llphyre said:
But therein lies the problem. There *is* a great thread on installing CWM and then ROMs using that. Step by step, it's fantastic. Installing a new kernel *is* found in some of the threads, but I wish that great thread with the CWM and ROM installation also had Kernel info.
Regardless of if you know how these tools work, it's nice to have a step by step to follow, just to ensure you're doing everything in order. I do it at work when I'm working with a new system (I write it myself) just to make sure I follow the same procedure every time. It helps when problems arise.
I'm just saying, for the n00bs, it would be nice to have a "one size fits all" thread. I was able to successfully install CWM and Vegan without a single problem, as I've been reading this forum for MONTHS, but I'm not a normal person (nor are most of the regulars here).
One thing I try to do, is demystify technology. Make it easy, explain it in simple ways while still being effective as describing what is going on, and then you don't get "stupid questions" later. Essentially, trying to run in the opposite direction that most Linux forums tend to be. Threads buried 2 years back have the info, everyone screams at the n00bs saying "USE THE SEARCH".
Love this forum, the people here are REALLY helpful, but there is room for improvement. That's all I'm saying.
Click to expand...
Click to collapse
Short answer: Great idea! When will you have it ready? ;-)
Long answer...
I understand what you're saying. What I'm saying is that there isn't a one size fits all answer to this "problem" (certainly not since the addition of TwoTapsX). The step by step instructions for installing ROMs, kernels, other hacks, etc. exist in the threads that contain the product (and most of those are stickied) because they aren't always identical. One "Superpost" meant to encompass all of those instructions would grow to be much too large and include far too many logical branches to be effective when you take into account the individual caveats for each. However, the methods for installing many of the products is similar in most cases even if the tools are not identical. Understanding which tool to use and how it works is the key to a successful experience.
For example are the recent cases of problems with TwoTapsX (formerly TnTLite 5.0.x). The instructions in the thread clearly stated that the users should start from a clean Viewsonic ROM without CWM (very different from other ROMs). It even stated an nvflash might be necessary if you had any problems with the install (also not usually necessary with other ROMs). Still, the overwhelming majority of users that had problems had failed to follow the instructions correctly and were unprepared to do an nvflash. These were generally not people that were new to the process, either. In cases where they were, a simple search for the error message they were getting or the condition they were experiencing turned up an answer within the first two or threes responses and virtually all of them were addressed in the original instruction thread or another recent thread with a similar title.
Another example, I still see threads daily about someone recently installing VEGAnTab 5.11 and all of a sudden their media disappears from their sdcard. This is a well known and very well documented problem with a long used successful work around. It isn't a case where their particular installation went awry, it's a known issue with the ROM. How many of those issues would need to be addressed in the "Superpost" in order to be effective and yet not be cumbersome?
To complicate things further, we now have indications that the next official release may change recovery to be incompatible with previous methods. It's possible we'll see further forking of these processes based on the developers preference of recovery which would reinforce the need to customize instructions for a particular product.
Room for improvement? Sure. I just think education is better than hand holding. I always encouraged my engineers to learn more and develop their own processes because they might actually be better, cheaper, more efficient, than whatever we currently had. I understood that MY answer might not always be the best one and I preferred to empower my associates.
All that being said... I'm all for anything that improves the community and more importantly helps its members. If you feel that it would be helpful then feel free to put something together or team with a few others to produce a document to address the issues you've identified. I'll be more than happy to link people to it if it fills a need for them just as I have to others in previous threads ;-)
Modding
You know normally I just read and lurk around here, but I can't keep my mouth shut any longer.
**WARNING** Not that I expect anyone to notice because apparently half of you can't read or don't comprehend what you do read, but anything past this point is probably not contributing to the conversation in a constructive way and should be considered as me ranting.
I have had my tab since December and have flashed every single Rom found on this forum at one time or another and the problems I see people have just amaze me. It's amazing because 9 out of 10 times it's because they didn't bother to read/comprehend the darn instructions or they are to lazy to search/read/comprehend on how to fix it or start over.
I am by no means a rocket scientist/programmer/developer/modder myself but I can read something 3-4 times first to make sure I comprehend before I go off deliberately voiding the warranty on a $400 device. And if I break it? Guess What?? There are instructions for that to if people would bother to look. Granted the information can be scattered around but if you can't be bothered to search/read then you should probably not be using a android device.
Last thing and I'll shut up. The entitlement I see coming from alot of people really makes my blood boil. You are an early adopter of bleeding edge technology, there are going to be problems and alot of them! If you didn't do research on the tab before you bought it you have no right to complain. The devs are not paid except by an occasional donation. They do this on their own time with their own equipment for the community. THEY DO NOT OWE YOU A THING, AND YOU SHOULD WORSHIP THEM SINCE WE ALL GET TO BENEFIT FROM THEIR HARD WORK!!!
Be Contented....
After tried two ROMs (TnT and NI) and finally sticked to NI, am well contented and satisfied. I think being contented may less your problem...
K J Rad said:
Short answer: Great idea! When will you have it ready? ;-)
<Plus lots of other stuff you said>
Click to expand...
Click to collapse
As you can see from my post count, I'm historically a lurker. I've literally read every single thread in the GTab section since December. The problem for me, mostly came down to once I bought the device (I research stuff to death before I pull the trigger) and was ready to try a new ROM, it was information overload. There *is* a good thread about ROMs and CWM as I said, so I followed that, after reading it 6 times to ensure there were no gotchas.
I want to try out Pershoot's kernel, but I don't feel like I've read the procedure enough times to feel confident I'll be able to do it without having to fix something I broke. So, I'll read it a few dozen times, research the tools used, and finally get to it.
End of the day, I'll probably ask the person who did the ROM thread if they wouldn't mind added text that I've put together for the Kernels (as a supplement to what he did). I do want to give back to the community.
Also, you'll hopefully be seeing some hardware mods coming soon from me, fully documented. My true love is hardware, so I'll leave the ROMs and Kernels to the software guys, and focus on improvements on the physical side of things.
Thanks for keeping the conversation friendly. Always great to hear other people's opinions on matters.
Hardware mods would be VERY cool. Just remember to put something in the thread about how to talk your wife into letting you replace the smoldering mess on the kitchen table so I'll be covered... ;-)
h3llphyre said:
Also, you'll hopefully be seeing some hardware mods coming soon from me, fully documented. My true love is hardware, so I'll leave the ROMs and Kernels to the software guys, and focus on improvements on the physical side of things.
Thanks for keeping the conversation friendly. Always great to hear other people's opinions on matters.
Click to expand...
Click to collapse
I think I speak for everyone here when I say "Bring them on!"
2 cents to add
I have worked in various areas of IT for over 30 years. Unfortunately android has not been one of them but the basic ideas are always the same. As one reader noted (with a little bit of steam coming from his ears) no one owes you anything here. You aren't paying and you're pretty lucky to have so many talented people making their efforts available to you. I, for one, am very appreciative. I do see the point however about documentation. I have been slowly (and painfully) coming up to speed on the various facets of this g-tab experience. What I find most frustrating is not the lack of directions (there are plenty if you look) or even responses (Clemsyn responded to my request for kernel updating info) but the lack of basic information. I recognize a linux type structure when I snoop around the file system. What is the relation of the ROMS to that? What exactly does clockwork do and where does it live? When you "clear caches" what exactly are you clearing? etc. I'm not expecting answers to these questions here but I think that is the problem a lot of us "caught in the middle guys" have. Sure, we can follow directions and usually everything works just the way it is supposed to but we don't know WHY. If you just blindly follow directions that makes you a "user" not an "admin" and who wants to be a user???? ha-ha What I really want to know is how/where do the more experienced people here (including devs) get their base information to know how to tinker with kernels, ROMS, etc? Where is the G-Tab Development for Dummies book hiding????
enigmas 0456,
You will find that lack of documentation is the hallmark of Android -- not just
here but everywhere. Probably more info here than most places.
Rev
Hello,
I have been reading countless stories about CWM, battery charging, and ect. and feel that people are moving forward with the wrong path. I see so many ROMs and whatnot springing up that also have many issues.
Today I found that while the new alpharev version of CWM DOES charge my phone when off, my phone wont reboot without a battery pull. Using ROM manager to update CWM, I find it does charge my battery AND allows me to start up normally. This is great, but for me and anyone else that finds this to be true for their phone.
BUT WHY!? What on earth is wrong? What does CWM do that could cause these "who the hell knows why?" cases?
I also find that when I reboot, setCPU required me to redo the insmod command to work again. That wasnt too bad, just connect via usb and copy and paste via command prompt. That was with the alpharev version of CWM. Now with the newest version, I have to UNINSTALL setCPU, reinstall, then go through the whole process of setting it up! Just cause of a reboot?
I feel that everyone has skipped a step...The basics! We need to figure out what is wrong with the codes.
I dont think its such a great idea to be cooking up ROMs when there are MAJOR issues with the basics...
Anyone agree?
Matt
No. I don't agree at all. Most users are having no SERIOUS issues at all. Most, if not all, of these issues are caused by noobish mistakes, not following directions, not reading up on ALL available info before trying a mod, and basically people just not knowing what the hell they are doing. These mods are not for everyone, yet every idiot with a smart phone thinks they need to do them. The issue with charging has been known since the first recovery was released and they acted fast to address the problem, but people don't read and don't know any better and they flash what they shouldn't. Well, they deserve the bricks they end up with IMO.
Behold_this said:
No. I don't agree at all. Most users are having no SERIOUS issues at all. Most, if not all, of these issues are caused by noobish mistakes, not following directions, not reading up on ALL available info before trying a mod, and basically people just not knowing what the hell they are doing. These mods are not for everyone, yet every idiot with a smart phone thinks they need to do them. The issue with charging has been known since the first recovery was released and they acted fast to address the problem, but people don't read and don't know any better and they flash what they shouldn't. Well, they deserve the bricks they end up with IMO.
Click to expand...
Click to collapse
Well said good sir. Well said.
EDIT: And a fellow Las Vegan. Even better.
Seriously? Very arrogant, the both of you! You assumed that most people having theses issues are screwing with things that they dont know? Some are, but not most. Not by any means. The fact that people ARE creating fixes is proof of what I am saying.
I am NOT running anyone's ROM. I am running stock.
It isnt hard, at all, to do what you guys do. The directions spell it out plain and clear, yet issues are springing up. S-OFF was easy, as was installing CWM to gain perm. root.
The issues I described rest on the shoulders of the devs. Stop blaming it on "noobs". They had nothing to do with the battery issue.
Now, people installing ROMs and all that could be blamed on ignorance, but not the basics. FIX THE BASICS before you start insulting noobs please.
Screw it..
EDIT: If it is so obvious that these issues are user related, then please explain how so? How on earth did I F up things and cause my battery to act like a turd? Where along the lines of, " DL, connect via usb and enter key" did I go wrong even though I now have S-OFF?
Where along the lines of DL the CWM file, putting on the SD card, boot into recovery and apply update (done successfully) did I screw up and cause these issues? See what I am saying? I didnt flash any rom, or mess with a radio, or anything of that sort yet am having the same issues as many others. Nor have I done any mods, or adjusted any settings available only to root users. You guys have problems with your basics. You need to recognize this and figure it out. Ever heard of having a strong foundation?
Matt
mrg02d said:
The issues I described rest on the shoulders of the devs. Stop blaming it on "noobs". They had nothing to do with the battery issue.
Now, people installing ROMs and all that could be blamed on ignorance, but not the basics.
Matt
Click to expand...
Click to collapse
How dare you sir! Do you have any idea how much time and effort goes into making these mods? Which, by the way are currently in DEVELOPER PREVIEW and by definition not for everyone! You have the nerve to demand things and basically call their work ****? You clearly have no clue. Where are your fixes smart guy? What have you done to make this community better? You don't just come in here and blame the devs (that do this work for FREE) for your problems and then think they are going to help you. It doesn't work that way. How about a little appreciation!
Behold_this said:
How dare you sir! Do you have any idea how much time and effort goes into making these mods? Which, by the way are currently in DEVELOPER PREVIEW and by definition not for everyone! You have the nerve to demand things and basically call their work ****? You clearly have no clue. Where are your fixes smart guy? What have you done to make this community better? You don't just come in here and blame the devs (that do this work for FREE) for your problems and then think they are going to help you. It doesn't work that way. How about a little appreciation!
Click to expand...
Click to collapse
How dare you blame people's issues on their ignorance? Face it bro, these things have some major issues going on, and no one knows why. Instead of ignoring them, and hoping they will get better, MAKE THEM BETTER. I am tired of seeing people shrug off issues as noob mistakes. Some are, such as flashing ROMs not meant for the phone without backing up their current ROM, but doing everything correctly and then having to hijack the battery is seriously different.
You are responsible for what you publish. Free or not! If you understand the problems people are having, and know why, then so say.
I never called anyone's work ****, you did.
Appreciation? How about showing it as well? Youve got countless people testing things for you! Doing what you cannot, by yourself! When people bring a problem to your attention, you tell them they are a noob and then dismiss it! Why? What an asshole thing to do, and a very unprofessional one at that.
I know I am not alone. People need to speak up! These are not JUST noob mistakes, there are some GENUINE MAJOR issues with the groundwork. They need to be addressed. It is insulting to see people follow the directions perfectly, find a major bug, then be told they are a noob while the problem just goes on to others. You guys called these problems "fixed" which they clearly arent. I simply brought it to your attention in a non submissive tone.
Let a MOD close my thread If I am out of line. Come on people, SAY SOMETHING!
Matt
mrg02d said:
How dare you blame people's issues on their ignorance? Face it bro, these things have some major issues going on, and no one knows why. Instead of ignoring them, and hoping they will get better, MAKE THEM BETTER. I am tired of seeing people shrug off issues as noob mistakes. Some are, such as flashing ROMs not meant for the phone without backing up their current ROM, but doing everything correctly and then having to hijack the battery is seriously different.
You are responsible for what you publish. Free or not! If you understand the problems people are having, and know why, then so say.
I never called anyone's work ****, you did.
Appreciation? How about showing it as well? Youve got countless people testing things for you! Doing what you cannot, by yourself! When people bring a problem to your attention, you tell them they are a noob and then dismiss it! Why? What an asshole thing to do, and a very unprofessional one at that.
I know I am not alone. People need to speak up! These are not JUST noob mistakes, there are some GENUINE MAJOR issues with the groundwork. They need to be addressed. It is insulting to see people follow the directions perfectly, find a major bug, then be told they are a noob while the problem just goes on to others. You guys called these problems "fixed" which they clearly arent. I simply brought it to your attention in a non submissive tone.
Let a MOD close my thread If I am out of line. Come on people, SAY SOMETHING!
Matt
Click to expand...
Click to collapse
You clearly don't get it do you? Everything here is, and has always been, a work in progress. NO ROM is EVER 100% bug proof, not even the stock stuff. So back off and stop demanding that bugs get fixed. Nobody likes to be yelled at for their hard work, especially by someone who obviously has no clue.
EDIT: I agree with you on one thing: This thread should die.
MODS please close.
Insmod is stupid to use on a permroot device. Also, for the person saying it's the noobs fault, most of the time, yes, yes it is, but they were not at fault with CWM. 4.0.1.5 claimed to fix issues, yet it did not. Also, I'm not pinning this on the devs either, nothing is completely bug-free. It's arrogant f*cks like you that is making XDA die a slow, painful death.
(EDIT: Pointed at OP and Behold_this
Jimmah555 said:
Everything here is, and has always been, a work in progress.
Click to expand...
Click to collapse
Exactly why he started this thread. There is an issue or two and there are conflicting reports that it is fixed and the OP would like to get to the bottom of it. Instead, we got some very knee-jerk reactions blaming it on the users or excuses that it is all a work in progress. That's fine, I understand how this could feel like an attack on the developers. But why not try to get to the bottom of it?
It still isn't apparent to me in one of the several threads about the battery issue if this has been solved. Some people on TMO branded phones indicated the latest version of CWM (as of a few days ago) still doesn't allow charging with the phone completely off. I'll be checking my phone shortly and will post some results. Sorry, but I would consider this a major issue. If you let your phone battery die, it can't be restarted without an extra (charged) battery or some rather McGyver-esque operations. Not something that comes up often, but if/when it does you could be SOL when you need your phone.
We have plenty of people here willing to help, but we need a little direction....
His point about "it isn't hard to do what you do" wasn't implying that developing is easy, he was implying that the directions to get S-off and install CWM were easy. Although phrased poorly, blaming it on "noobs" screwing things up is unfounded and ridiculous.
Jimmah555 said:
You clearly don't get it do you? Everything here is, and has always been, a work in progress. NO ROM is EVER 100% bug proof, not even the stock stuff. So back off and stop demanding that bugs get fixed. Nobody likes to be yelled at for their hard work, especially by someone who obviously has no clue.
EDIT: I agree with you on one thing: This thread should die.
MODS please close.
Click to expand...
Click to collapse
Before the MODS close this thread I have to agree with the OP. I understand that the DEVS work hard on their ROMs, however, no one likes flashing a bad ROM because they failed to fix the basic problems. It's even worse when a DEV releases a ROM knowing the bugs that hinder basic use, yet don't list them on the ROM description. That, IMHO, is a noob DEV. No ROM is perfect, and you do take a risk whenever you do flash a ROM, but there should never be a need for laziness. If there are many bugs, then the ROM should be released as Beta or even Alpha until the bugs hindering basic functions are worked out.
And before you flame me, I am not a noob. I have supported the rooting of android since I had the G1 running the JF mods and have rooted every one of my devices after, from the MT3G, Moto Cliq, MT4G, G2x, etc. all the way to my current Sensation and my soon to be MT4G Slide. XD
NikolaiT said:
It's arrogant f*cks like you that is making XDA die a slow, painful death.
(EDIT: Pointed at OP and Behold_this
Click to expand...
Click to collapse
Arrogant huh? Do you even know what that means? Well whatever my phone works great Captain D-bag.
You don't get it either. Nobody has a gun to your head telling you to flash a ROM to your phone, do they? It's your choice, therefore you're ultimately responsible for what goes on your phone. The devs didn't put it there, you did. I understand bugs are annoying, but that's the point of this community. As users of the ROMs we are responsible for reporting bugs and patiently waiting for a fix. The devs certainly don't like reading crap like this thread. You think it motivates them to keep working when there are people whining about stuff instead of offering pleasant, yet constructive criticism and thanks? These devs work on their own time. Nothing says they have to release anything at all to the public, but they do. Again, the mods are always a work in progress. They release things to find out bugs and fix them.
Jesus H. Christ quit your *****ing.
Guess what folks? I see NONE of you read my stickies.
Flame thread closed.
I want to do everything I can to develop for this phone. What I need from the people here is a stock flash able rom. I have made great progress on this phone but but idk how to build stock roms and at this point I'm not sure I have the mental capacity to learn it.
Sent from my MB865 using Tapatalk
So...you have made great progress doing what?
There is a Chinese ROM floating around, maybe you can use that.
I want to do everything I can to develop for this phone. What I need from the people here is a stock flash able rom. I have made great progress on this phone but but idk how to build stock roms and at this point I'm not sure I have the mental capacity to learn it.
Click to expand...
Click to collapse
LOL...
Without a stock ROM, we have been unable to develop much...
What have you developed, here?
Mostly the community is hacking the stock installed rom, and fixing what Motorola has purposefully broken, but with out a few more pieces and a working sbf, you are not going to get a "Stock" ROM.
If you really want to help out go jump into the bootloader unlock forum:
http://forum.xda-developers.com/showthread.php?t=1328714
jimbridgman said:
LOL...
Without a stock ROM, we have been unable to develop much...
What have you developed, here?
Mostly the community is hacking the stock installed rom, and fixing what Motorola has purposefully broken, but with out a few more pieces and a working sbf, you are not going to get a "Stock" ROM.
If you really want to help out go jump into the bootloader unlock forum:
http://forum.xda-developers.com/showthread.php?t=1328714
Click to expand...
Click to collapse
I use cheesecake 4 times a day every day. If I find something I compare it to what others have found.. What have I developed? Nothing more then a headache. Using the bionic safestrap I have been able to recover from 3 soft bricks. 2 of them using adb to push to the phone and 1 using the restore tool. But i had to remount /emmc to /sd-ext. But I think at this point I am done trying anything with this phone.
One more thing.. what can't we use all the stock files I've pulled from the phone to make a flash able zip?
lfaber06 said:
I use cheesecake 4 times a day every day. If I find something I compare it to what others have found.. What have I developed? Nothing more then a headache. Using the bionic safestrap I have been able to recover from 3 soft bricks. 2 of them using adb to push to the phone and 1 using the restore tool. But i had to remount /emmc to /sd-ext. But I think at this point I am done trying anything with this phone.
One more thing.. what can't we use all the stock files I've pulled from the phone to make a flash able zip?
Click to expand...
Click to collapse
Seems like you know a lot more than all of us who have been working diligently for the last 60 or so days with this phone.... Why don't you give it a try and see if you can create a flash-able zip.
You can't build a flash-able zip, because you can not zip or tar files on the filesystem that are in use, and the kernel has a ton of files open and locked. the backup software gets around this in a couple ways that we really can't do, and backups are useless to make flash-able zip from. That is why we need the sbf or fxz or source code to make a flash-able, zip or ROM.
That is why we have warned everyone over and over and over, about trying things we post, right now. The information is not to try out, it is sharing of the developers, and for those of us working on actually developing solutions for this phone. There have been so many bricks, because people are not listening.... I am actually thinking of trading my phone with a buddy to get out of this, because I am tired of hearing about all the bricking people are doing, and having to help save someone who did something to their phone that they did after we told them not to.
Unless You Know What You Are Doing Don't Try This At Home. Until we get the fxz or sbf files. I am getting tired of saying this...
P.S. doing work on the cheesecake thing does not make you a Developer. Hell I am not an Android Developer, I am a UNIX and Linux Hardware architect and UNIX and LINUX Kernel Developer, so I am am able to use all that, 20 years of experience on the Android kernel, and I have been hacking and working on phones a long time.
Now I know it is great to try things and learn, but while learning, it is best to try things we say are safe first, then once you are more comfortable with certain things, then try something daring, that you know how to do.
I am in no way trying to insult you, just realize that right now, with the little help we have on the experienced development side of things, it is real painful to get things moving forward when people don't listen, or do things they are not ready for and then keep asking for help when they killed their phone in the process.
jimbridgman said:
I am actually thinking of trading my phone with a buddy to get out of this, because I am tired of hearing about all the bricking people are doing, and having to help save someone who did something to their phone that they did after we told them not to.
Click to expand...
Click to collapse
Please don't leave us Jim. You are an incredible resource. I'm new to Android and have learned many valuable things from you.
Remember, you don't have to help every person that bricks their phone.
Jim if you try to leave we will find you! ;p
Sent from my MB865
mtnlion said:
Jim if you try to leave we will find you! ;p
Sent from my MB865
Click to expand...
Click to collapse
LOL... I am not going anywhere, I am just trying to make a point, that things like this killed the Atrix board, and I hope we don't repeat that.
We are here to help, and I wish that it would be realized that we are in "Research" mode right now, and are not to point of actually hacking, or have very many how to post yet for that reason.
You can't buy common sense but stupidity is free.
Sent from my MB865
jimbridgman said:
LOL... I am not going anywhere, I am just trying to make a point, that things like this killed the Atrix board, and I hope we don't repeat that.
We are here to help, and I wish that it would be realized that we are in "Research" mode right now, and are not to point of actually hacking, or have very many how to post yet for that reason.
Click to expand...
Click to collapse
WHEW.....You had me fixing to start looking at phone options!!! Honestly I'm to the point where I just read them and ignore them otherwise I say things I shouldn't LoL. But I will be the first to say this, IF THIS BOARD GETS AS BAD AS THE OG ATRIX DID, I WON'T HAVE A PROBLEM WALKING AWAY!
---------- Post added at 01:27 AM ---------- Previous post was at 01:01 AM ----------
mtnlion said:
You can't buy common sense but stupidity is free.
Sent from my MB865
Click to expand...
Click to collapse
You can't fix stupid either......
JRW 28 said:
WHEW.....You had me fixing to start looking at phone options!!! Honestly I'm to the point where I just read them and ignore them otherwise I say things I shouldn't LoL. But I will be the first to say this, IF THIS BOARD GETS AS BAD AS THE OG ATRIX DID, I WON'T HAVE A PROBLEM WALKING AWAY!
Click to expand...
Click to collapse
Part of the issue I think is that everyone, who is doing these things, is of the I need this now, no matter what, camp... I just came a phone that had this, so this phone should too... LOL.
Yeah if it comes to anywhere close to the OG Atrix board I am out so fast it is not funny.
The thing is that I am most of the time ignoring these posts, but when you 6 people all did something similar, or like the OP did 4 or five things that messed his phone up, because he/they were impatient, you kind of have to tell them, look if you don't like it, get another phone. Heck the OP tried to say he was helping the cause by doing these things, when it was said so many times don't try this....
jimbridgman said:
Part of the issue I think is that everyone, who is doing these things, is of the I need this now, no matter what, camp... I just came a phone that had this, so this phone should too... LOL.
Yeah if it comes to anywhere close to the OG Atrix board I am out so fast it is not funny.
The thing is that I am most of the time ignoring these posts, but when you 6 people all did something similar, or like the OP did 4 or five things that messed his phone up, because he/they were impatient, you kind of have to tell them, look if you don't like it, get another phone. Heck the OP tried to say he was helping the cause by doing these things, when it was said so many times don't try this....
Click to expand...
Click to collapse
The funny thing is the "OP" didn't do anything he was told not to due.. Instead he/I tried new approaches and have actually been able to recover from a few soft bricks at this point. We get places from trying new things not by talking down to those that try them. I'm trying to help as I own the phone too. I am not in any way "under-educated". I am a .Net developer and I am doing my best in my free time to help the community by opening up this phone to its full potential. Now, Am I impatient.... Hell Yes.. I want CM7 and ICS now. Will I get it now?.. No, but i'm trying to get the rest of you on your way. I cant believe you would try to push someone so willing away..
A better way to go about it would be to post your discoveries and share them to help others out instead of demanding things you need.
lfaber06 said:
What I need from the people here is a stock flash able rom.
Click to expand...
Click to collapse
We aren't pushing anyone away that is willing to help and we welcome everyone that is willing to hel. But when you experiment know that we might not be able to help you and we have no way back to stock. By experimenting we found root,the bionic's bootstrap and we will have to continue to experiment. Part of progress is by finding out what works and what doesn't.
We need to all work together and not against each other. But with that said if you look at the amount of recent posts with people experiencing problems and calling for help is because they didn't do any research before hand and now they are asking for help for something they could have very well prevented by patiently doing a little homework.
With the progress you have said to have made, start a new thread about it explaining the procedures you went about to recover from the soft bricks so others can benefit from them as well. I can promise you we are all very interested.
JRW 28 said:
A better way to go about it would be to post your discoveries and share them to help others out instead of demanding things you need.
We aren't pushing anyone away that is willing to help and we welcome everyone that is willing to hel. But when you experiment know that we might not be able to help you and we have no way back to stock. By experimenting we found root,the bionic's bootstrap and we will have to continue to experiment. Part of progress is by finding out what works and what doesn't.
We need to all work together and not against each other. But with that said if you look at the amount of recent posts with people experiencing problems and calling for help is because they didn't do any research before hand and now they are asking for help for something they could have very well prevented by patiently doing a little homework.
With the progress you have said to have made, start a new thread about it explaining the procedures you went about to recover from the soft bricks so others can benefit from them as well. I can promise you we are all very interested.
Click to expand...
Click to collapse
Thanks, and Very well said, I agree 100%
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.