I have a Galaxy Tab 7, T-Mobile version (although I only use wi-fi, not data). I flashed once before using Overcome and it worked perfect, but after my tab started acting crazy - constantly crashing and rebooting - I tried to re-stock and re-flash. I went through the first steps - pit, GB safe stock, T-Mobile modem...and it all went fine, except it was stuck in boot. I tried the hidden pit, which I found in a troubleshoot thread - still stuck in boot.
Then I tried the dbdata.rfs in PDA, which I came across on Fix My IT System...still stuck in boot, and now if I try to load GB safe stock in PDA, I get a fail. Twice I have unplugged in Download, because of Fail and not advancing download...and both times when connect to Odin and load dbdata.rfs in PDA it resets and I can re-enter download mode and recovery<3e>, but it's still stuck in boot.
Is there any hope for me?
If you are restocking and still failing, there is a possibility that your internal nand chip is failing. Also the fact that it suddenly start crashing initially.
There may be ways to run cm rom on external sd that is properly partitioned, if you still want to get some live out of your tab.
Sent from my GT-N7100 using xda app-developers app
priyana said:
If you are restocking and still failing, there is a possibility that your internal nand chip is failing. Also the fact that it suddenly start crashing initially.
There may be ways to run cm rom on external sd that is properly partitioned, if you still want to get some live out of your tab.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
The thought had occurred to me, although I did fix the Odin stock load fail with some further digging (re-loaded USB drivers, plugged cable into different port). Still boot looping...doesn't even boot enough to get adb logcat.
P1 add hidden doesn't help, and makes the next attempt fail, and I have to reload drivers. Same with dbdata.rfs. Although after reflashing dbdata.rfs I can get to recovery<3e> and boot into download. Checksum fails after P1_add_hidden and after dbdata.rfs, but not after USB reload and GB Stock Safe flash. Still stuck at Samsung logo, though.
Is there any way to find out if the chip is my problem for sure, short of tearing the Tab apart?
Related
I am having a problem with my Galaxy S GT-I9000. I bought it from Bell Canada, which means it is a vibrant. And due to the lag and freeze of the Bell's system, i decided to flash my phone to Froyo 2.2. It was really sucessful when I was doing my flash.
Here is some info about the firmware I use:
I used Odin 1.3, PIT: s1_odin_20100513
firmware:
CODE_I9000XXJPC.tar
MODEM_I9000XXJPC.tar
CSC_I9000OXAJPC.tar
I have no idea what version it is, I just followed a guide from Internet, but it said it is a European pack.
Here comes the Problem, the phone is working very vell for the first 10 days, no freeze issue anymore. But suddently one day, the screen went to black( I was not using the phone at that time, and when I started my random check of the phone, the screen turns off).
After I start up the phone again, the loading screen is still there, and there is sound, too. But after the big "S", the screen turns black again.
And when I pressed the home button, the Menu and ESC key turned bright, after this I think the phone is freezed, but I can still hold the Power key for a while to turn off the phone.
I tried to flash my Galaxy with other firmware, but it all show the same problem---
loading screen, startup sound, but the screen turn black after that.
If any of you could help me with this problem I will be really appreciate!!
And by the way, the 3-key combo is still working on my phone.
So I can still enter the recovery mode or the downloading screen...
And I tried everything on the recovery mode screen, factory reset, wipe, formate SD...everything, but no luck
Really need help..!
Try flashing to JM9 using the 512.pit with re-partition and do a factory reset and wipe cache when done: http://forum.xda-developers.com/showthread.php?t=802909
Then try flashing to JPM using 803.pit and tar file as PDA only and no repartition, do a factory reset and wipe cache when done: http://forum.xda-developers.com/showthread.php?t=807886
You used the 513.pit file in your previous flash, I think that it is old and not used any more.
I tried everything u said, step by step, but still not working, dunno why,
and after I flash JM9 with 512, the phone wont go into recovery mode anymore
and there is no loading screen anymore, just a logo of the Galaxy S GT-I9000 Samsung and the phone turns off.
So I decided to ignore this and flash JPM with 803 as you said , and the problem is still there, loading screen and sound, then nothing happen.
I had exactly the same problem and i have done exactly the same steps then i realized someone took out the Sdcard.
Have you check the SDcard. if in there try to format first in other phone or computer.
You fried the internal sd card, I did the same, I'm not covered through samsung or bell cuz I'm unlocked on rogers, I took it to a cell phone repair place, cost me 65 bucks to get a new motherboard, no more flashing roms for me
Sent from my GT-I9000M using XDA App
Try going in to recovery mode and post any errors that appear at the bottom of the recovery screen. it would help us find put what is really wrong with the phone.
find out what firmware bell originally had on your phone rather than JM9.
Sent from my GT-I9000 using the XDA mobile application powered by Tapatalk
if you plug in an external sd card, you will be able to access recovery mode again. i was in the same boat, and it is a corrupted/fried sdcard. i gave up after flashing 30 different roms and sent mine in for repair.
I have found a few other user with this problem but none of the solutions seem to work.
Odin gets stuck at factoryfs.rfs
I can get into download mode
I could get the phone into CWM but couldn't seem to select any zip files. Now I can't even get in there...
I formatted cache, data, and system before trying to flash (I think this was the cause)
Any ideas of how I can get the phone to work again?
As far as you are able to access the download mode, you are in the safe side
It happened to me once with Odin not to finish sucessfully the flash, I have just repeated the operation and it worked.
This is why people are now using Heimdall, it is more reliable.
remove the battery
re-insert and see if you can get it to re-charge (odin drags if your battery is near 50%)
if you can let it re-charge for an hour or so and then go back into odin, this time reflash a stock firmware but don't tick re-partition
had this situation once before and this worked for me
also check your usb connection, a loose cable can also be a factor
This generally happens when you are updating your bootloaders! And bte odin is still the best! Heimdall is not good!
Sent from my GT-I9000 using xda premium
Hey guys,
Phone was running great for nearly 6 months, was texting last night, then feel asleep when I woke up the phone was stuck at the CWM recovery screen nothing to do.
So I popped in ODIN and wanted to revert to the stock rom which usually always works, PIT FILE 512, PDA,CSC, and PHONE files were inserted, repartitioned... (Its a i9000M btw!)
THe phone rebooted and then when the unpacking started a bunch of 'E:' errors appeared /dbdata and unable to mount whatever..
I tried the PDA "dbdata.rfs" un checking the repartition box, the phone just loops at the i9000M logo (Not the S really the power on screen) it keeps cycling that...
So I tried reflashing couple of times changing pit files (unchecking repartition) I tried WIPING and factory data reset it just hangs at startup...
Any of you guys have any other tips to help me out, was running CM10 for 6 months no problems all day today and all of a sudden its dead... I Think I'm pretty knowledgeable in terms of how this phone works, have fixed and flashed a couple of these phones, help would really be appreciated!
Thanks,
Mat
try this. maybe internal storage error
http://forum.xda-developers.com/showthread.php?t=845708
Sent from my GT-I9000 using xda app-developers app
compacity said:
try this. maybe internal storage error
http://forum.xda-developers.com/showthread.php?t=845708
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Mind guiding me to what exactly can help me in here, this is a lot of stuff I haven't touched, I'm aware of basic ADB usage but not more so.
I understand there may be a partition issue?
I'll add a couple of details : So basically the phone just sat at the clockwork recovery, and would not boot, as if something was dead.
I tried a factory data reset, wiping cache all those things failed, it juts came back to clockwork, I plugged it into ODIN, popped a 512 PIT, and a stock I9000M 2.3.3 ROM repartitioned FAIL (bricked)
Unbricked it, reflashed with a 513, that was successful, but it also stopped at the 3e recovery (basically same problem) Unable to wipe or do anything to the card. Reflashed a PDA lots of forums were suggesting to fix these /dbdata errors. That brought me to staying at the GALAXY S I9000M logo it would just cycle and cycle and cycle so I reflashed a stock rom AGAIN 512, 513, 803 they all passed, first times the UNPACKING PROCEDURE FAILED, then it succeeded THEN, there would appear a short error saying it couldn't write the LOG, reset the phone now it hangs at the LOGO..
Thanks
PS. Why does a fully functioning phone, suddenly 'DIE'
I mean I'm reading through this and most of this stuff needs to be done in ADB right?
How do i get ADB To connect to a device that can't get into Android? please help
u can also read here, this are list of most problem occur n da suggested solution, juz take ur time reading, its good for u
http://forum.xda-developers.com/showthread.php?t=1841250
Sent from my GT-I9000 using xda premium
Hi everybody,
I've been at this for a couple days now, trying every solution I can come across, but nothing seems to work. My mom's Captivate decided the other day that encryption had failed (I don't think anyone ever told it to encrypt itself...). It said all I had to do was click the Reset button, but that didn't work. So back to ODIN I went.
Unfortunately, though I could swear I've used ODIN on this phone before (it was running CM10, and I'm pretty sure I messed up a couple times trying to get it on there), I can't get it to work again. I've tried the One-Click ODIN (which is what I would have used before), as well as downloading two different tar.md5s from sammobile.com and flashing them with a different ODIN.
After using the One-Click method, the phone powers on to the AT&T screen, and then it powers off, switching between different charging icons if it's plugged in. The other ODIN flashes got me to Installing packages.. after boot, but then it gave me rfs errors. So I figured I needed to flash a new PIT, but that didn't seem to help. Doesn't One-Click do that anyway?
I've tried two different USB cables and two computers (both Windows 7 SP1, one doesn't even have any antivirus program on it yet), but no luck. I had a different computer the last time I would have used ODIN on this phone. I believe this phone is a 1007 build, assuming I am looking at the right number under the battery.
Any help would be greatly appreciated. Thanks in advance!
see encryption unsuccessful thread. your internal storage is probably dead, but you can run from external sdcard with the fix described in the thread.
http://forum.xda-developers.com/showthread.php?p=21439417
Sent via Monty Pythons Flying Circus
Yeah, that's the problem
Darn. Seems like that is the problem. Simply putting in an external SD card allowed me to boot, but now I have to get CWM on it through ODIN... Thanks.
CWM via ODIN?
Does anyone know how to install CWM through ODIN? I'm back with the stock recovery, and when I try to install a ZIP it fails the signature verification (for any ZIP I try). Seems that ODIN would be the way to go.
Stock recovery won't let ya flash zip files that r not signed by samsung.
Ya have to have the zImage in a .tar file in order to flash it through Odin.
Here is the KK4 Corn Kernel thread. http://forum.xda-developers.com/showthread.php?p=18233847
I recommend the version 7.0A for what u r wanting. There is a .tar version of it there. PDA slot is the one to use in Odin for flashin a kernel.
Sent from my SAMSUNG-SGH-I747 using xda premium
Running CornKernel, repartition error
OK, I'm up and running with CornKernel. I rooted it using the ZIP (and now the phone is unbelievably slow, but it's rooted nonetheless). (I also tried the advanced CWM option to root it, but that messes the phone up.) But when I try to repartition the SD card, it says "An error occured while partitioning your SD Card. Please see /tmp/recovery.log for more details." but /tmp is empty.
Getting rid of the phone
Meh, forget about it. I'm going to sell this phone as-is or part out anything I can. I need to move on, as spending more time on this phone when it's permanently damaged is not worth it to me. (If anyone wants it by chance, just let me know...) Thanks for pointing me to what the problem was though.
...necro bump... You wouldn't still happen to be selling that would ya?
Sent from my GT-I9000 using XDA Premium 4 mobile app
Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi
It is exactly this: just another bricked Note thread.
ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi
Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?
If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?
AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.
Part of the "hardware" is your battery...