yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] ezynow:
Sorry to hear you are having these problems.

You guys are "wiping data/factory reset" in cwm :confused:

This has not been confirmed working yet by me---> see my original thread :mad:

I have not had any issues myself but then I have not had to do a factory reset yet. No one else has reported any issues but this is not to say it does not exist.

Can the original poster confirm whether he has done this himself first before instructing for others to do so? I am assuming he must have done this or :eek:

Can anyone post the original updater script from zip file so I can check it?
[Galaxy Tab 7.7 Android Development] jamaljmys:
could you explain by more details about that ? please..we are not technicians and we need more and more help.
[Galaxy Tab 7.7 Android Development] sk806:
Yeas. I have tried all of the wipe functions in your cwm port.

Script attached (you need to remove the ".txt" that I added just so it would upload to xda, obviously...)
[Galaxy Tab 7.7 Android Development] stefanamlappi:
Any idea how to debrick the device??
[Galaxy Tab 7.7 Android Development] theerachai:
Does anyone sucessful flash this rom without brick.

Just curious because over 100 download but not one claim that it work.
[Galaxy Tab 7.7 Android Development] sk806:
I am not sure how the build difference issue would work, as, in theory, if your device is fully wiped, the ROM would just replace everything...if recovery is not wiping properly (as eznow mentioned above), it could be a factor, although bricking seems a bit extreme). Not dismissing this, just saying, it seems odd. I have noticed that some 10.1 ROMs for wifi+3g have several carrier specific files in csc, so it may be something to do with that. I'll ask around and see...

As I mentioned before, for those two or three posters from yesterday who seemed to have followed the instructions, and got bricked, I am willing to work something out with paying for you to use JTAG (if you flashed after the issue was posted, sorry, but I can't help you...). Even though I clearly stated that this was to be flashed at your own risk and that I had only tested it, I feel this is fair.

I am also looking to see how to remove the back cover and pull the battery (which I will test on my own tablet first), as a battery pull seems to work in many cases...

Steve
[Galaxy Tab 7.7 Android Development] sk806:
Make that 200 downloads, people must have linked the DL in other sites. I just deleted from Dropbox. BTW, it seems that many people have successfully flashed it, and the bricks are a small minority, but please do chime in if you have flashed successfully, as I would also like to know.

Steve
[Galaxy Tab 7.7 Android Development] ezynow:
:mad::mad::mad::mad::mad::mad:

YOU ARE FLASHING KERNEL OVER BOOTLOADER !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

YOUR SCRIPT

ui_print("Flashing Kernel");

package_extract_file("boot.img", "/tmp/boot.img");

run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p2");

delete("/tmp/boot.img");

run_program("/sbin/busybox", "sync");

ui_print(" ");
[Galaxy Tab 7.7 Android Development] sk806:
This kernel flash method is used all the time in Smasung ROMs. Check it out. I will try to alter the script to write raw file, but that may lead to status 7 errors. Will report back.

EDIT - Are you saying that flashing kernel to mmcblk0p2 is overwriting bootloader? That's the boot partition, where else am I gonna put it? I don't think I've seen a ROM for a Samsung device that does NOT do this.
[Galaxy Tab 7.7 Android Development] sk806:
Oh, and this was done to avoid formatting to ext 4, as well, which would have been my preference, but figured it was not the best idea for a base stock ROM.
[Galaxy Tab 7.7 Android Development] ezynow:
I give up :eek:
[Galaxy Tab 7.7 Android Development] sk806:
Give up, as in I am not listening, or you are out of ideas? I am not trying to be a jerk, just want to know. This is fairly standard in Samsung ROMs. Please let me know, as I hope we can work together.

Steve
[Galaxy Tab 7.7 Android Development] ezynow:
I think I am confused myself - hopefully somebody else help you here.
[Galaxy Tab 7.7 Android Development] sk806:
OK, thanks. I am about to test a "write raw image" version, although the dd command I used does the same thing. The point is that the kernel always has to go to the boot partition. So, I am not sure that this is the problem.

Part of me wants to keep on flashing to see if I can brick (good to know JTAG is around). I will try different odin firmwares and see if that might be a problem.

Also looking into the 10.1 ROMS that have many different csc subfolders (other than TGY), but all these seem to be are network specific items like APNs and lockdowns for certain apps, nothing that would brick a device.

I an also investigating whether the wiping process in your CWM port may not have worked perfectly for the affected users. I recall this was an issue way back when for some Verizon handsets. Def not saying this is your fault at all, just a possibility.

Steve
[Galaxy Tab 7.7 Android Development] ezynow:
THE KERNEL DOES NOT GO ON BOOTLOADER PARTITION

THE TAB 7.7 has a seperate partition called ZIMAGE for kernel image

it is CERTAINLY NOT on YOUR PARTITION /dev/block/mmcblk0p2 in YOUR SCRIPT

PLEASE LEARN ABOUT PARTITIONS AND THE FUN YOU CAN HAVE WITH DD ;)
[Galaxy Tab 7.7 Android Development] sk806:
I'll look into this, but I do know about partitions and dd, and, in fact, that is how I got the partitions for my script in general, obviously...will try flashing to the "kernel" mmcblk0p5, if that's what you are referring to.
[Galaxy Tab 7.7 Android Development] sk806:
Also strange that it did not brick EVERY device that flashed it, if you are right. THis is getting interesting...
[Galaxy Tab 7.7 Android Development] sk806:
Okay, going to flash the new "kernel partition" version. Get ready JTAG....

Flashing stock firmware, recovery, etc. and will start over with root, then my new-scipt-ROM. Come on eznow, I hope you got it...:).
[Galaxy Tab 7.7 Android Development] sk806:
Well, that didn't work. Get bootloader but nothing else, probably because there is now no kernel on the boot partition...

You need kernel on the boot partition. This is known. I am not sure what is different about this device, but it seems unlikely that I could have flashed the kernel to my boot partition and had no issues. If flashing the kernel there was what you are saying, it would have bricked me and everyone else, too.

I am still checking this out. What a PITA.
[Galaxy Tab 7.7 Android Development] sk806:
Also, could you please stop with the RED ALL CAPS. I get your point, but the kernel traditionally goes on the boot partition in Android devices. Google it for example...http://bit.ly/xGnpE6.

I mean this post respectfully. I just don't think that the red all caps are adding anything. Thank you.

Steve
[Galaxy Tab 7.7 Android Development] jamaljmys:
could anyone advice where to buy JTAG on net?
[Galaxy Tab 7.7 Android Development] stefanamlappi:
I am at tje moment on a jtagger in Germany. He will call me back soon and tell me if he can do jtag.
[Galaxy Tab 7.7 Android Development] eaglerazor123:
Kernel is TOTALLY Diff from BootLoader! Kernel shouldn't go to Bootloader partition! The only Mantra in developing is EVER mess with Bootloader! Kernel should go here mmcblk0p5! Bootloader is corrupted in users case ! Try Usb Jig n c if it goes into Download Mode!
[Galaxy Tab 7.7 Android Development] stefanamlappi:
Where i can get the jig???
[Galaxy Tab 7.7 Android Development] sk806:
OK, so on this device, the kernel should flash to the "kernel" partition. Why is it different with other devices? Look around, kernels are flashed to the boot partition along with bootloader (e.g., http://androidforums.com/evo-4g-all-things-root/278898-android-partitions-kernels-explained.html). This isnt "messing" with the bootloader. This is the default for android, anyway. It may be different with Samsung devices, and I am willing to accept that I made an error. I still don't see why it works fine for most if it is "messing" with the bootloader. EVERYONE who tried this should be bricked then, and that def is not the case. I am not trying to be defensive, I just want to lay out my reasoning. Per your suggestion, I'll try mmcblk0p5 in my script again and see if it boots...

Thanks.

Steve
[Galaxy Tab 7.7 Android Development] eaglerazor123:
Nah..I never seen a Custom Rom for Samsung using Bootloader(N every Sammy)! Not in my case of development for Sammy's tho! Anyhow! Good Luck!
[Galaxy Tab 7.7 Android Development] sk806:
OK, as I said, Samsung may be different, and I may be in error. Trying the 5 partition, now. Will keep you posted...and thanks again.

Steve
[Galaxy Tab 7.7 Android Development] sk806:
I'll get one for you if you want. Just send me a PM with your delivery info.

EDIT - Oops, those were for S-2, I'll look some more...

Steve
[Galaxy Tab 7.7 Android Development] sk806:
Uh, nope, stuck at boot screen (not boot loop, at bootloader screen). This is way to f-ed up. I should stick to HTC devices...
[Galaxy Tab 7.7 Android Development] eaglerazor123:
Better than Nothing ;) Take a log & Fix it! N release a build!
[Galaxy Tab 7.7 Android Development] sk806:
Can't, as kernel ramdisk wont seem to allow debugging on as default after flash...I hate Samsung!!!

I still don't understand how some users were affected and others were not if the bootloader could be affected...ah well.
[Galaxy Tab 7.7 Android Development] sk806:
Last Word for Now

I am going to PM a developer of Samsung ROMs I trust, and ask him the deal with kernel placement on these devices. All I know is that I put it in boot partition on mine, as I have in every ROM I have ever released, and it works fine. I put it in the kernel partition, as some have advised here, and I get stuck on the boot screen with no possibility of debugging, so no logcat...

Until I hear back from the dev, I am going to withhold from speculating any further.

For those who were bricked yesterday and posted about it in this thread before I responded (that is 2-3 users, one of whom tried to modify the ROM before he flashed it), my offer of paying for JTAG stands. That is all I can do right now. You read the disclaimer, I told you about the risk, and you proceeded. I am not obliged to do anything for you, but I WANT to do the right thing here. So, let's do it, if you want.

Once I get a clear answer about kernel placement on Samsung devices, I will explain the issue (if that is, in fact, the issue).

Thanks.

Steve
[Galaxy Tab 7.7 Android Development] sk806:
BTW, looked at the script for almost every ROM for the 10.1, and......the kernel is flashed to mccblk0p3, which is boot partition for that device, no?

OK, sorry, I said I wouldn't do this...;).

Steve

PS - A user with the brick issue has his open and is pulling the battery. Will let me/us know soon, I hope.
[Galaxy Tab 7.7 Android Development] sk806:
Resonse from DEV

OK, so according to my Samsung expert source, there is a kernel partition on Samsung devices, called "boot" which is not where I placed the kernel in the ROM. Here are the main partitions for the 7.7:

0 /tmp ramdisk (null) (null)

1 /efs ext4 /dev/block/mmcblk0p1 (null)

2 /boot emmc /dev/block/mmcblk0p5 (null)

3 /recovery emmc /dev/block/mmcblk0p6 (null)

4 /cache ext4 /dev/block/mmcblk0p7 (null)

5 /system ext4 /dev/block/mmcblk0p9 (null)

6 /data ext4 /dev/block/mmcblk0p10 length=-16384

7 /preload ext4 /dev/block/mmcblk0p11 (null)

8 /emmc vfat /dev/block/mmcblk1p1 (null)

What I did was look at the 2nd partition, and, yes, like an idiot, spaced and put mccblk0p2, instead of the correct mccblk0p5 (get it, 2nd partition, must be mccblk0p2, right? Dumb ass...). SO IT IS LIKELY MY FAULT. If my damn tab hadn't booted up, this wouldn't have gotten out to the public.

Many, many apologies to those affected and the whole community. I have never has a gaffe like this happen, and I have released a ton of ROMs that thousands of people have used. Again, I stand by my mistakes and will help those 2 or 3 users who need to JTAG as a result of bricking yesterday BEFORE the issue was posted in this thread, and I responded (100% reimbursement of costs of JTAG-ing).

Also, just for clarity's sake, according to this dev, it is highly unlikely that flashing my ROM could have affected anyone's bootloader, unless there is a bootloader in the ROM, which, of course, there is not. Just wanted to clear that up, as I was accused of screwing with bootloader, which I would not do.

That being said, I will get a ROM with the correct partitioning up for extremely adventurous beta testers, after I have tested myself, of course.

Steve
[Galaxy Tab 7.7 Android Development] sk806:
One last question

For the 2 or 3 who have bricked. Was your bootloader locked or unlocked. Just curious.

Steve
[Galaxy Tab 7.7 Android Development] SeanHacker:
Too scared to say my name or something??? :D

like i said via our pm. if you give me your rom i will try and fix it. that way you can test it without putting other peoples tablets at risk.
[Galaxy Tab 7.7 Android Development] sk806:
I did test the ROM before I released it (worked just fine, as I have said many times), and I didn't put anyone's anything at risk. They willingly accepted the risk I was offering, which is a very different proposition, my friend (I am a lawyer, sorry). Further, I didn't want to say your name out of consideration, fear's got nothin' to do widit...;). I think I have the issue fixed anyway. Kernel flashes to correct partition (mmcblk0p5), and all is good. I will send to you, you can take a look, and if you change it, yes, I'll flash it. I understand the risks involved, and I ain't scared...Wouldn't be my first brick. Remember WM? Yikes...

And BTW, you Samsung people are bunch of testy MF-ers....:). Come on over to HTC Verizon phones, and I'll take y'all on, bee-atches...
[Galaxy Tab 7.7 Android Development] sk806:
Sending PM now. Let dropbox sync a bit (20 min) before trying to download. Thanks.

Steve
[Galaxy Tab 7.7 Android Development] SeanHacker:
lol. hmmm... but with your "personal testing", clearly if you had the block partitions screwed up (personal admittance on your part) you would have noticed that the boot.img didnt flash and something was wrong regardless if it flashed correctly or not bro. just saying. :D

and... on to point two. regardless if you put the disclaimer in the OP of your thread about "taking the risks of flashing this." you yourself know that you put the product out here, obviously without testing to what some might call "ready for public consumption." and it did in fact cause harm to some peoples devices. now that is not their fault for trusting a "dev". they are in fact supposed to trust developers of any product such as this. do you think people would flash windows 7 on their computers if the didn't trust the developers of it??? nope. so again... regardless of that disclaimer, it would be your fault for putting out a product that damages a device. But you are correct about not being obligated to pay for such things if it does harm a device as per your disclaimer. i've seen your posts about willing to pay for jtag so that my friend is another self admittance on your part. they are just doing what they are suppose to do and trusting you and your product. :D

Now do not take any of that as a personal attack bro. Because none of it was. I've just taken in some of the important things and now I'm relaying them to you. Some is personal opinion and some is personal experience. But i can say that no one has been unhappy with my products that i release here on XDA unless it was just some form of their personal opinion. TEST, TEST, TEST, TEST, AND MORE TESTING BRO!!! :D
[Galaxy Tab 7.7 Android Development] SeanHacker:
your init.d and my init.d look exactly the same bro??? weird considering i named them myself and setup config files for them to activate with. by the way... you forgot to grab those configs out of my rom too. so none of those will work without the configs except for the usb charge one. you could've always just given me some credit for creating such an awesome init.d set that you wanted to use. it would've been nice. :D
[Galaxy Tab 7.7 Android Development] sk806:
Fair enough. However, there was nothing i saw in the rom that was askew. Nothing. I had it going for hours, amd everything was fine! There was nothing to indicate that the f-ing boot.img didnt flash properly. Thats why i was so confused by the wrong partition thing, why the hell did it even work for me and others? Anyway, you are right, and I always do private betas, and should have this time, as well. Just new to Samsung and it worked for me, so i said, hey it must be just like all the deving i do for htc phones. I was wrong. Ive never had any complaints about my work here either over 7 years. I just screwed up by being cocky.

BTW, using new build with correct partitions, now. So far so good.

Steve
[Galaxy Tab 7.7 Android Development] SeanHacker:
yeah thats cool. learning from mistakes is always the best. it just helps the next project get even better and pushes for stability.
[Galaxy Tab 7.7 Android Development] sk806:
Oh boy. These were NOT in the rom that was released! You have a revised rom that is completely separate from that one. As i explained in my pm, I just grabbed your init.d folder as a starting point going forward. I will probably only using the zipalign script from yours (which every rom has), as I use supercharger differently and have never even used the other ones. Further, these are not even active, as I clearly stated, and, yes, i know why they are not active. Didnt i point them out to you before you even got the rom? In fact, I dont even have init.d support in the kernel yet!!

I have NEVER taken any one elses work (not that you wrote any of these scripts) without asking and giving credit. Check out my releases.
[Galaxy Tab 7.7 Android Development] SeanHacker:
i did check out your releases. :D they dont look to be popular at all. but anyways, that's besides the point . i'll discontinue helping you from here on out now because i can see that you are getting upset for some unknown reason. peace out ;)

By the way. I was only trying to help.
[Galaxy Tab 7.7 Android Development] jamaljmys:
the bootloader supposedly to be unlocked by default as mentioned in some posts here. what happened is happened dude.

thank you steve and be sure iam ready to test and use all your future work when i get my device alive.

can you help by finding the JTAG or find a information how to make it by ourselfs?

i really respect an appreciated your attitude , all of us agreed to carry the responsibility when we owned open source devices and looking to use cooked roms.

just let us solve the brick device and fly again. its addiction :D
[Galaxy Tab 7.7 Android Development] sk806:
I am upset because many in this forum seem to lack basic courtesy amd common semse. That is a closed beta thread that your little arrows are pointing to. Hence the lack of views. Also, the number of views wasnt the point, the point is that i give credit where credit is due and I can use scripts.

Further, i dont give a **** about views since August, as i havent been doing a lot of developing since that time, when i lost my house to a major flood, "bro", and have been homeless with my wife and three kids, "bro". Not everyone can spend all their free time, if they have any, developing, "bro".

This is what I mean, why dont you stop and think before posting things like im stealing your work (oh, wait, you told me that the scripts were never released and were inactive, and i didnt write them anyway?) and the lack of hits on my closed beta thread (oh, wait the thread right above my douchey little arrows is the final thread?) is evidence of some sort if lack of skills or something, when even the slightest pause to think would let you know that you just might be mistaken?

I have been nothing but gracioue and cooperative since this fiasco began, and all i have gotten in return is flaming and name calling. Anyway, after 7 years, I guess its time to go, anway. Bye bye XDA.

Y'all can KMA.
[Galaxy Tab 7.7 Android Development] SeanHacker:
Well bro. I work 2 jobs and I'm a single father of a 5 year old girl that was recently diagnosed with cancer bro. So I know about not having time bro. Read the threads sometime if need be bro.

​
[Galaxy Tab 7.7 Android Development] jamaljmys:
thank you

please read my post before your. No 78
[Galaxy Tab 7.7 Android Development] SeanHacker:
by the way. ill dev you guys a 7.7 rom soon that i'm sure you all will love. i'll need some testers due to me not owning the device. or maybe ill just go buy one... don't worry at all. there will be no chance of bricking. :D
[Galaxy Tab 7.7 Android Development] sk806:
Apologies

OK, much of this seems true to me, and the "copy and paster" label may be true of the one samsung ROM I made (which was a disaster, I admit), but take a look at my threads and credits to me for smali mods I coded for the HTC Inc. T-bolt and Inc 2, as well as my HTC ROMs for the same. I don't think it's fair to call me a copy and paster.

In any event, I do apologize for being a tool. I am having a bad day (or three), and I should not have taken it out on you, as you were trying to help. Again, apologies.

Steve

PS- Nice jab with the "bro" graphic...:)
[Galaxy Tab 7.7 Android Development] sk806:
I am very sorry to hear this. I hope she is doing well. Best wishes to you and your family.

Steve
[Galaxy Tab 7.7 Android Development] jamaljmys:
steve

you will help to get JTAG to repair our devices?
[Galaxy Tab 7.7 Android Development] SeanHacker:
Your best bet which would be the cheapest and waaaaay faster than waiting for a jtag fix would be to try a jig. They only cost a couple bucks. I'll see if I can find one for you.

EDIT- I just have to ask this. Have you tried to hold just the power button down for a really long time (like a minute or longer) to see if it will try and boot up. Because if it makes an attempt to boot its a really good sign and can be brought back to life.
[Galaxy Tab 7.7 Android Development] jamaljmys:
thank you bro.

yes i tried press long time but nothing.

what the def. between jtag and jig?

from my search i found that jig use for galaxy s family, i mean its used by micro usb. if it is workable for our tab its ok.

if i can make it by my hands it will be OK too, i mean by using resister and cut usb cable, i just want to know what the number of bins in usb cable needed to attach the resister.

could you help please?

i returned to stone ages now by using nokia3110:(
[Galaxy Tab 7.7 Android Development] SeanHacker:
I'm pretty unfamiliar with this tablet in particular but I'm looking into it and should have an answer for you by tomorro
[Galaxy Tab 7.7 Android Development] sk806:
Yes. I will pay the cost. Just send me a receipt via pm, and a paypal acct, and youll get it. If you buy a jig, same deal.

Steve