Does anyone have those files for the samsung galaxy tab? I really really need them.
no one has em eh?
My sprint samsung galaxy tab is stuck at the screen with the cell phone and computer logo. I can write files with ODIN but it always seems to fail on one of the files. It definitely does write some though!
Anyone have any idea of how I can recover? I've tried just about everything I've seen on the forums here.
If you can direct me to instructions on how to extract them I can get these for you.
I uploaded Sprint stock firmware to a while ago, I looked into the .tar file and unfortunately it doesn't look like it has those files. But you can check it out at Tab Stock - No Modem.rar
I used a roto-backup script to do a full backup some time ago and forgot that I had it till I saw this thread. This is the boot.bin and Sbl.bin from that backup, note that I've never restored these two files so I can't guarantee that they will work but they are here if you need em.
Related
Sorry to open this thread, but I'd been reading some other threads and I've seen ppl asking about it, but since it's mixed with some other topic it just get forgotten.
Anyways, I've flashed my Rogers Captivate to a AT&T 2.2 firmware, but I'm having problems with Rogers itself (they keep screwing up my bills for the last 4 months, this month they were charging me CDN$855 ><). So I decided to cancel with then and go with Bell's Vibrant. The problem I'm having is that I flashed back to Rogers stock rom, but the AT&T is still there. I pre-ordered my galaxy so I have to send via mail, I can't just return to a store. So I need to remove the AT&T logo at the start up.
Any ideas on how I do that ?? I just started using Android so a step by step would be appreciated, specially because I have to return it as soon as possible, so I don't have much time to experiment
chrislawho said:
Sorry to open this thread, but I'd been reading some other threads and I've seen ppl asking about it, but since it's mixed with some other topic it just get forgotten.
Anyways, I've flashed my Rogers Captivate to a AT&T 2.2 firmware, but I'm having problems with Rogers itself (they keep screwing up my bills for the last 4 months, this month they were charging me CDN$855 ><). So I decided to cancel with then and go with Bell's Vibrant. The problem I'm having is that I flashed back to Rogers stock rom, but the AT&T is still there. I pre-ordered my galaxy so I have to send via mail, I can't just return to a store. So I need to remove the AT&T logo at the start up.
Any ideas on how I do that ?? I just started using Android so a step by step would be appreciated, specially because I have to return it as soon as possible, so I don't have much time to experiment
Click to expand...
Click to collapse
How did you flash back to stock? ODIN? clockwork from nandroid backup?
icezar1 said:
How did you flash back to stock? ODIN? clockwork from nandroid backup?
Click to expand...
Click to collapse
Used Odin.
you need to find the stock boot.bin & param.lfs
to remove the att logo.
eugene373 said:
you need to find the stock boot.bin & param.lfs
to remove the att logo.
Click to expand...
Click to collapse
Be careful though, those 2 files are the most dangerous files to play with!
However, I believe that might be fixed if you flash the stock firmware with the option "Phone Bootloader Update" ticket. Not 100% sure though.
Can someone confirm?
icezar1 said:
Be careful though, those 2 files are the most dangerous files to play with!
However, I believe that might be fixed if you flash the stock firmware with the option "Phone Bootloader Update" ticket. Not 100% sure though.
Can someone confirm?
Click to expand...
Click to collapse
You don't need that checked if you have the boot.bin in the pda..
param.lfs is where the images are contained and param.lfs is stored on stl6
the dangerous one is the boot.bin
flash with this kernel, it doesn't have the ATT logo.
http://etc.muteheadlight.net/android/I9000_reoriented_v2.1.3.tar
If someone with a Rogers Captivate who hasn't flashed AT&T firmware could dump /dev/block/stl6 it might be helpful.
Code:
dd if=/dev/block/stl6 of=/sdcard/stl6.bin
opcow said:
If someone with a Rogers Captivate who hasn't flashed AT&T firmware could dump /dev/block/stl6 it might be helpful.
Code:
dd if=/dev/block/stl6 of=/sdcard/stl6.bin
Click to expand...
Click to collapse
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
Then make it into an odin ready or via redbend_ua & flash it.
dealnest said:
flash with this kernel, it doesn't have the ATT logo.
http://etc.muteheadlight.net/android/I9000_reoriented_v2.1.3.tar
Click to expand...
Click to collapse
Well.. if you wanna replace the ATT logo with the i9000 logo.. then go ahead
I would say that the i900 logo looks a billion times better than AT&T.
On a related note, it would be great if that freaking AT&T splash was replaceable with custom image.
rraquib said:
On a related note, it would be great if that freaking AT&T splash was replaceable with custom image.
Click to expand...
Click to collapse
Yeah the AT&T logo is very annoying. I just want my black i896 screen back.
Sent from my SAMSUNG-SGH-I897 using XDA App
hey guys hopefully someone has an answer. I have a att captivate running a.n. beta1 (child of Dg's aosp) with the Zimage from Cognition 2.3B2. I wanna remove the att splash screen and replace it with the android mask file found in framework-res.apk assets/images. It looks like this on the phone....http://dl.dropbox.com/u/14217261/IMG00009-20100820-2119.jpg. I just wanna remove that damn att screen even if its just black or the samsung galaxy s logo screen then bootanimation. any help would be awesome. (I dont mean to hijack this thread but didnt wanna get yelled at if i started a new thread)
that AT&T splash screen you guys are talking about is located in the param.lfs file that is flashed with ODIN, stored in one of the bml blocks and viewable in /.lfs in the root of the phone.
As has been shown with the Samsung Moment, this file can be flashed and replaced, but is a terrible idea. For them, replacing that file required it be under 100 KB and would lead to a brick (that is unrecoverable if I listened to noobnl correctly).
basically, it's at worst a minor annoyance and not worth the potential damage in my opinion.
I have a backup from ROM manager when I had stock firmware (rooted). Let me know if I could pull out some info from that!
Thanx for the help guys.
Well I guess the I9000 logo isn't as annoying as the AT&T. If I can't solve the problem and my return is refused, I guess i'd prefer the I9000 logo lol
I'll try to flash to that tomorrow.
iswapnil90 said:
I have a backup from ROM manager when I had stock firmware (rooted). Let me know if I could pull out some info from that!
Click to expand...
Click to collapse
Do you think it's possible to upload the ROM you have from rogers ??
Another I noticed is that now my GPS is screwed up. I was able to get a perfect lock with the rogers rom. No I'm about 1 block north and 1 east away. For basic stuff that wouldn't bother me, but if I could fix that... I tried the *#*#1472365#*#* thingie but nothing really happened. I mean, when I first start google maps I get the perfect location, but after the map loads I warp someplace else lol.
I am putting my Sprint SGT back to stock EA24 so I can recover what appears to be a mess up on my part. (Not relative to this thread) and have chosen to use the "Sprint Galaxy Tab EA24 Flasher with Odin" technique that has received excellent results for so many.
I am sitting in Oden, and it is at the
<ID:0/003> modem.bin
It has been there for a long time. How long should I wait for it to continue? Has anybody experienced this when restoring stock kernel?
seewhyphotos said:
I am putting my Sprint SGT back to stock EA24 so I can recover what appears to be a mess up on my part. (Not relative to this thread) and have chosen to use the "Sprint Galaxy Tab EA24 Flasher with Odin" technique that has received excellent results for so many.
I am sitting in Oden, and it is at the
<ID:0/003> modem.bin
It has been there for a long time. How long should I wait for it to continue? Has anybody experienced this when restoring stock kernel?
Click to expand...
Click to collapse
Yeh, this happened to me, it seemed like it wasn't responding so i just closed it and did it again, you can take a chance and do that aswell lol
I figured what else could i do, i left it for an hour
What was interesting is that I eventually stopped the process, pulled up Heimdall, put in all the individual pieces, and it failed/stalled at modem.bin also.
I stopped Heimdall, rebooted my tab back into download mode (only it was showing the Phone - Orange Triangle - Computer) and redid the Heimdall update MINUS the Modem option.
It was successful and my tab has been fine ever since. I have full 3G, Wireless, and no problems that I have identified as of yet.
It went and updated OTA to EB28 without a hitch, and since then, I have been working on a completely stock Sprint Galaxy Tab.
Go figure...
Hello all, I have just followed this guide to get back to stock on my Note
http://www.youtube.com/watch?v=msdsfnlEiwM
Using the files in the description, I have done all that was asked in the video but Odin is now stuck at boot.bin
I have tried doing the process over and over but to no avail it stays stuck at boot.bin,
What do I do??????
Fixed
JAG07 said:
Hello all, I have just followed this guide to get back to stock on my Note
http://www.youtube.com/watch?v=msdsfnlEiwM
Using the files in the description, I have done all that was asked in the video but Odin is now stuck at boot.bin
I have tried doing the process over and over but to no avail it stays stuck at boot.bin,
What do I do??????
Click to expand...
Click to collapse
I was lucky my phone did not brick, But I was also lucky I made a Nandroid backup on the day I decided to flash CM10 . So I am now back on Stock ICS. What a relief.
But to anyone lurking on here; How would I get past the Odin Boot.bin?
lucky u do a backup b4 doing stupid things ha ha ha…
normally i'll flash back stock via Mobile odin n always 100% success.
for pc odin not sure maybe someone will give u the answer.
good luck！
Glad you have resolved it.
Remember to read the stick threads on the General Forums on what not to do.
Wiping on stock ICS kernels is potentially dangerous, and we do not know what rom/kernel you came from.
Bear in mine of outdated instructions on other sites like Youtube.
Also, we do not know what phone model you have, and flashing the wrong files on your phone can cause permanent damage.
Samsung released a 16GB variant of the SM-N9005 in Hong Kong. This device comes with a slightly different PIT than the 'international' version of the phone.
I am attaching the PIT files of both.
Many people have soft bricked their phones while tinkering with the 16GB version. And then, people who updated to the KitKat bootloader have no option but to use a custom ROM because an official ROM using that bootloader and the 16GB pit is not out yet.
When trying to flash official 'international' ROMs on the 16GB device, it gives a 'invalid ext4 image' error.
Through some trial and error, I have made this out to be due to the fact that the 16GB pit file has a different size defined for the 'system' partition.
I have been trying to make a PIT file that will account for the 16GB size of the N9005 and will let people flash 'international' ROMs to their devices and have spent many hours on this project of mine.
And well, for the life of me, I cannot figure out how to make the required PIT.
The differences between the 16GB pit and the 32GB pit are in 3 partitions- System, Cache, SGPT.
Also attaching a PIT file that I made but I didn't want to give it out to the community because I wasn't confident about it and didn't wanna risk being the reason for bricking people's phones.
In this PIT, I have changed the system and the cache partition sizes to match the 32GB pit, but the SGPT partition is untouched because it confuses me.
PIT files can be opened, viewed and edited by the software PIT Magic by lyriquidperfection.
I am asking for advice/help, if anybody has any to offer.
Also, I have read the guidelines about these forums and the strict warning. I hope that this is classified as development. If not, I apologize and would request a mod to move this thread to the appropriate forum.
FeralFire said:
Samsung released a 16GB variant of the SM-N9005 in Hong Kong. This device comes with a slightly different PIT than the 'international' version of the phone.
I am attaching the PIT files of both.
Many people have soft bricked their phones while tinkering with the 16GB version. And then, people who updated to the KitKat bootloader have no option but to use a custom ROM because an official ROM using that bootloader and the 16GB pit is not out yet.
When trying to flash official 'international' ROMs on the 16GB device, it gives a 'invalid ext4 image' error.
Through some trial and error, I have made this out to be due to the fact that the 16GB pit file has a different size defined for the 'system' partition.
I have been trying to make a PIT file that will account for the 16GB size of the N9005 and will let people flash 'international' ROMs to their devices and have spent many hours on this project of mine.
And well, for the life of me, I cannot figure out how to make the required PIT.
The differences between the 16GB pit and the 32GB pit are in 3 partitions- System, Cache, SGPT.
Also attaching a PIT file that I made but I didn't want to give it out to the community because I wasn't confident about it and didn't wanna risk being the reason for bricking people's phones.
In this PIT, I have changed the system and the cache partition sizes to match the 32GB pit, but the SGPT partition is untouched because it confuses me.
PIT files can be opened, viewed and edited by the software PIT Magic by lyriquidperfection.
I am asking for advice/help, if anybody has any to offer.
Also, I have read the guidelines about these forums and the strict warning. I hope that this is classified as development. If not, I apologize and would request a mod to move this thread to the appropriate forum.
Click to expand...
Click to collapse
hi
i am a hk guy and luckly i did not buy the note3. but i wonder why the hk pit is different from european's, since i have no problem in using european roms at all. i have not read the pit files yet but i suggest you to repack the images from european roms and see if it work. if it fails, extract the images and tar them and untar the tar files in your phone, which should not be bound by the pit, if any
good luck
ykkfive said:
hi
i am a hk guy and luckly i did not buy the note3. but i wonder why the hk pit is different from european's, since i have no problem in using european roms at all. i have not read the pit files yet but i suggest you to repack the images from european roms and see if it work. if it fails, extract the images and tar them and untar the tar files in your phone, which should not be bound by the pit, if any
good luck
Click to expand...
Click to collapse
I know for a fact that repackaged ROMs don't work.
Can you explain the other idea? I didn't really understand it.
What do you mean by 'untar files in the phone'?
Also, anybody with a 16GB phone brave enough to test things?
FeralFire said:
I know for a fact that repackaged ROMs don't work.
Can you explain the other idea? I didn't really understand it.
What do you mean by 'untar files in the phone'?
Also, anybody with a 16GB phone brave enough to test things?
Click to expand...
Click to collapse
i mean, extracting the system.img, for instance, on a linux. then u can use tar command to create a tar file containing the whole system dir, just like a zip but without compression. finally push the tar file to your phone and then untar it to the /system in recovery. thats it
you don need to worry if u do it correctly, since i always use tar to upgrade my phone
ykkfive said:
i mean, extracting the system.img, for instance, on a linux. then u can use tar command to create a tar file containing the whole system dir, just like a zip but without compression. finally push the tar file to your phone and then untar it to the /system in recovery. thats it
you don need to worry if u do it correctly, since i always use tar to upgrade my phone
Click to expand...
Click to collapse
Yeah. That would work, but I want to solve this thing without using recovery. So that people can flash without tripping knox.
If people are unopposed to tripping knox, they can flash custom ROMs anyway.
I did build a tar file with heimdal using kitkat system and 16GB pit. Will upload it tomorrow in university. My net here sucks.
I built a tar file using Heimdall.
This was made using the 16GB pit but the files from the leaked Kitkat ROM.
It does not include the bootloader, so it shouldn't be harmful. Still, flash at your own risk.
Need a tester with a 16GB device. Preferably running Kitkat with the new bootloader.
But even without, we just need to see if this flashes successfully.
Try flashing it through odin. Repartition ought not to be ticked, but if it doesn't work without, try with it ticked as well.
If neither work, try it with heimdall.
https://mega.co.nz/#!xgZHRSqC!FGevxC9hims_UBt5xXPfWuII6KnFkw9drBRuywXtfFM
So, that didn't work.
Any other ideas?
I am all out.
Starting from SGS4, PITs are signed and cannot be flashed if modified.
So, you can only flash official PIT signed by Samsung.
If signature of HK version is compatible with International version then you can flash any of them.
sorg said:
Starting from SGS4, PITs are signed and cannot be flashed if modified.
So, you can only flash official PIT signed by Samsung.
If signature of HK version is compatible with International version then you can flash any of them.
Click to expand...
Click to collapse
The problem with the HK pit is the different size alloted to the system partition.
Does the signing issue extend to Heimdall as well?
I don't suggest to use any flasher except Odin. I never used Heimdall. Actually, it's possible to flash partitions to any place regardless PIT, but it may lead to different kinds of problems.
Long time ago, i've experimented with PIT on i9500. I've flashed PIT through dd (so, i've skipped signature check) and result was cycling reboot. Initial samsung static logo appear, shortly flash and then appear again. Thus, phone didn't even start to boot kernel. Luckily, Exynos has simple bootloader and work independently from PIT and other partitions. I've booted into download mode and flashed original PIT.
There is PIT signature check not only while flashing, but also while booting. You can flash modified PIT file through 3rd party flasher, but phone won't boot.
I doubt Note 3 has different behavior than SGS4. Especially, with much more complicated booting process on Snapdragon (unlike simple Exynos booting process) you are risking to get hard-brick.
latest lollipop
Any ideas that the hk version 16gb note 3 able to flash the poland lollipop firmware? I really get confuse coz same version n9005 but both cant share same firmware and ao complicated.
I've got the same question as elvin92,
is it possible to install Polish (XEO) Lollipop ROM on 16GB Note 3 with loaded N9005ZHUENJ1 (TGY) on board?
when trying to install via Odin I get:
...
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so it's Pit fault ? wrong sizes ?
Want to update to lollipop..
I have note 3 lte sm n9005 16 gb with TGY frimware and want to update to lollipop XEO... plz help? provide pit file...
So I played around with my Samsung galaxy S2 tablet.
Never done anything like this before and didnt read up on it enough.
I did not take a backup because I, to be honest, didnt think I would have to need that since the data on the device had no use for me.
Long story short.
Ive used nand erase in Odin without extrating the pit file.
So now its bricked and I need the pit file to get it back to where it was before.
Edit: 32gb model