Related
Hi guys. I really need your help on this. I have a samsung galaxy S from T-mobile. I tried to add the arabic mode to make it read Arabic the correct format. This involved replacing the framework.jar file.
I have done that and I rebooted the phone to apply changes. Now the phone is stuck on the 1st boot window where it says "Galaxy S 4g Exclusively from T-mobile."
It keeps showing this window only. I have tried the hard reset method with the volume button but that did not work
Can you guys assist me what to do.
Sorry for opening this here since I already opened one before but dont know how to delete it there
ok guys I was able to go to samsung recovery Utils that has 4 options.
1- reboot system
2- reinstall package
3- delete all user data
4- delete cache data
I chose reinstall package and got the following message
install from SDcard...
Finding update packages...
opening update package...
verifying update package...
E:failed to open /mnt/internel_sd/update.zip (no such file or directory)
E: signature verification failed installation aborted
What should I do now
Thanks
Sure fire thing would be to get into download mode and Odin another rom.
Sent from my SGH-T959V using xda premium
Odin RaverX3X's KC1 ROM. http://forum.xda-developers.com/showthread.php?t=1129933
Put in the .pit file into PIT. REV00 into PDA. Phone into PHONE. CSC into CSC.
LEAVE ALL SETTINGS UNTOUCHED. Whatever the settings are when you put in the files are correct!
You can refer the bible and probably ODIN a recent version of Gingerbreak..
http://forum.xda-developers.com/showthread.php?t=1117554
Exodian said:
Sure fire thing would be to get into download mode and Odin another rom.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
how to get into download mode please
bkoon1218 said:
Odin RaverX3X's KC1 ROM. http://forum.xda-developers.com/showthread.php?t=1129933
Put in the .pit file into PIT. REV00 into PDA. Phone into PHONE. CSC into CSC.
LEAVE ALL SETTINGS UNTOUCHED. Whatever the settings are when you put in the files are correct!
Click to expand...
Click to collapse
Thank you for the reply. I think I got the hang of it but I got this message and it was stuck
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> Enter CS for MD5..
<ID:0/022> Check MD5.. Do not unplug the cable..
<ID:0/022> Please wait..
<ID:0/022> Checking MD5 finished Sucessfully..
<ID:0/022> Leave CS..
<ID:0/022> Enter CS for MD5..
<ID:0/022> Check MD5.. Do not unplug the cable..
<ID:0/022> Please wait..
<ID:0/022> Checking MD5 finished Sucessfully..
<ID:0/022> Leave CS..
<ID:0/022> Enter CS for MD5..
<ID:0/022> Check MD5.. Do not unplug the cable..
<ID:0/022> Please wait..
<ID:0/022> Checking MD5 finished Sucessfully..
<ID:0/022> Leave CS..
<ID:0/022> SetupConnection..
In download mode?
Pull battery, plug in USB/power cable, while holding both volume up & down buttons, insert battery (or a form of this procedure) and up should pop the black and yellow screen that everyone loves.
Sent from my SGH-T959V using XDA App
champ1919 said:
In download mode?
Pull battery, plug in USB/power cable, while holding both volume up & down buttons, insert battery (or a form of this procedure) and up should pop the black and yellow screen that everyone loves.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I did this and used odin but was stuck as you can see from my last post
any suggestions
A few things to try
This is likely a driver issue.
Reboot your computer then try to ODIN again. The reboot could "reset" the driver and possibly purge whatever programs may be trying to use the phone.
Are you certain you have the proper drivers installed? If you need them, check the SGS4G Bible (http://forum.xda-developers.com/showthread.php?t=1117554) and scroll down to "{USEFUL FILES}" for drivers.
Make sure other apps that may be monitoring/using that connection (like Samsung KIES). You may need to force close KIES in Task Manager.
That isn't a complete list, but a good place to start at least. After doing those things, please remove your battery, unplug your USB and go back in to download mode per champ1919's instructions above and attempt to ODIN again.
tinkererx said:
This is likely a driver issue.
Reboot your computer then try to ODIN again. The reboot could "reset" the driver and possibly purge whatever programs may be trying to use the phone.
Are you certain you have the proper drivers installed? If you need them, check the SGS4G Bible (http://forum.xda-developers.com/showthread.php?t=1117554) and scroll down to "{USEFUL FILES}" for drivers.
Make sure other apps that may be monitoring/using that connection (like Samsung KIES). You may need to force close KIES in Task Manager.
That isn't a complete list, but a good place to start at least. After doing those things, please remove your battery, unplug your USB and go back in to download mode per champ1919's instructions above and attempt to ODIN again.
Click to expand...
Click to collapse
Thank you very much for the reply. I have followed your instructions and got the drivers although I had them and I installed them. I uninstalled kies but still the same thing
an update. I have tried 2 other PCs one with win 7 32Bit, and XP 32 bit and still the same stuck on setup connection
Hmm...then I'm stumped. Perhaps more enlightened forum members can help.
Doesn't sound much like a driver issue any more, but have you tried installing PDANet on your computer? I think it uses slightly different drivers. I had tried several before one if them finally worked for me.
Update:
ok I managed to make it go to download mode but now near the end of the recovery using odin it gives me failed
It starts the download on the phone but then it reaches the end of the download and on odin shows modem and then says failed. Can anyone help
Have you tried to download the ROM again in case the download was corrupt? Also check to make sure you are putting the files in the right spot in ODIN.
In another thread, someone said that ODIN 1.85 worked more reliably than 1.7. Are you using the newer version?
Make sure you have latest Samsung drivers installed on your computer so that your computer recognizes your phone so that Odin can recognize your phone upon connection. Then try placing your USB cable into a different port also use as suggested Odin 1.85 it is a very reliable version of Odin.
Sent from my SGH-T959V using xda premium
So i have been looking through the pages, and cannot find anything pertaining to what i am looking for. I am new to ROM's and i cant find a explanation on how to install it, or flash it rather. I saw the part that said installation which has:
- Make sure you're on Gingerbread I897 Bootloaders
- If you are on EXT4, convert back to RFS (disable lagfix)
- Flash a CWM KK4 kernel
- Flash serenity zip file
- First boot takes some time
My phone is a Captivate rooted, and have tried installing roms with ROM manager, to no success because it says to reboot into ClockworkRecovery, but i have followed every instruction in the book to get to CWR but it still takes me to the stock recovery menu.
I have been at this for about two weeks looking at forums and everything to figure out how to do it on my own, but i really have given up because i have no clue.
Thanks in advanced for any advice.
So rooted & stock? Some thoughts
You need Samsung usb drivers.
adb for PC command line controls:
http://www.xda-developers.com/android/adb-easy-tutorial/
In Settings>Applications>Development toggle USB debugging on.
Use ODIN [1.85] once you put it in Download mode:
http://forum.xda-developers.com/showthread.php?t=1365805
Download mode: use adb command: adb reboot download
Bootloaders via ODIN [has its own odin copy]:
http://forum.xda-developers.com/showthread.php?t=1129821
Flash a tar of Corn 6.0.3 kernel via ODIN. This comes with its own CWM version:
http://forum.xda-developers.com/showthread.php?t=1294477
Always have a way to get back to stock if things go wrong:
http://rum.xda-developers.com/showthread.php?t=731989
Ok, so got it into download mode.
I open ODIN, but im not exactly sure what to do from there, so i tried opening ODIN then using the bootloaders.
I ran the bootloader program, went through that, it said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
dont know if im doing something out of order, but clicking start in ODIN itself doesnt do anything.
Thanks in advanced!
Buckli39 said:
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
sequence:
1.Run the Odin with built in bootloader code.
2. Phone in DL mode
3. Attach to USB. Odin will then get a yellow box indicating some com port.
Yellow com port box or it will do nothing! Perhaps you ran Odin with the phone already in DL mode & usb connected?
Sequence matters: If you used adb to get into DL then with Odin already open it should recognize it [20 seconds?]. I use a jig from MobileTechVideos $7 to get into DL, only then I usb connect to PC with Odin already running/waiting. Using adb is functionally equivalent. As the phone reboots it is not actually "connected". Once the reboot to DL happens the connection to PC is restored.
My Odin/Bootloader one-click program reports: " <ID:0/012> Added " with a yellow box with " 0:[COM12] "
4. choose Start. A green bar progress will indicate the 'progress'. It will reboot the phone.
5. You can close Odin after the "all thread completed", it will indicate a reset. Safest to wait for the reset/reboot.
It should have read: <OSM> All threads completed. (succeed 1 / failed 0)
This is just as directed on the link to the Bootloader one-click program [odin variant]
You only need the basic Odin[1.85] when flashing the Corn 6.03 tar file. In theory if one had the tar file for the bootloaders one could use the basic Odin for it, but here the bootloaders are already packaged in with an Odin executable.
okay, so i did exactly the sequence you told me, run odin/bootloader, phone into DL, then connect to usb.
I do not get the yellow com port until after i turn my phone off, out of DL mode, and back into reg mode. then it recognized it and says "Added!". i go back into DL mode and it says its disconnected ( i also waited 20 min just to make sure it didnt come back as added )
And you had said "Once the reboot to DL happens the connection to PC is restored." it is exactly the opposite, once it reboots to DL the connection seems to be severed.
If i hit start when it is present and not in DL mode but has the yellow com, it just fails anyway.
Buckli39 said:
I do not get the yellow com port until after i turn my phone off, out of DL mode, and back into reg mode. then it recognized it and says "Added!".
And you had said "Once the reboot to DL happens the connection to PC is restored." it is exactly the opposite, once it reboots to DL the connection seems to be severed.
If i hit start when it is present and not in DL mode but has the yellow com, it just fails anyway.
Click to expand...
Click to collapse
Connecting when in Normal use mode will always have Odin responding Yellow/ComPort. And yes Start will do nothing unless in DL.
I tested my sequence. Odin/Bootloaders running, PC: adb reboot download, and it did fine giving YellowBox/ComPort. Never usb disconnecting physically, only functionally as it reboots. So I dont know. I do know that sometime DL mode goes stale. Phone unresponsive if one does not take fairly prompt action. That is I cannot put in DL and put aside for 5min. If I had to do this then I would need reboot into DL again.
For the Kernel you can transfer the Corn6.03 [zip CWM version] file to some directory in the internal SD card [ not the one inserted by "you"]
Then you could use "adb reboot recovery" but the stock recovery is very limited, and it wont let you flash the kernel in recovery. Unless you first save a CWMR 3 file as update.zip on the internal sd. This was how you rooted? There is some reason stock recovery forces you to do the flash from update twice, the second time puts you in the CMW3 program[green menu, no longer blue?] where you can then flash the kernel. Look for old links/threads to the old CWM zip file.
Let me get back to you on the BLs & perhaps a link to the old CWM3.
i will keep on trying to get the DL mode to be connected, and I rooted via the super one click root program, was told it would be the easiest and fastest way
Okay so i was digging around and found some reasons why it wasnt reading my device, and i got it. i got odin to flash the file, waiting for it to start my phone back on, atm it is stuck on the att screen. i shall wait a bit and report
okay i have let it attempt to reboot by itself for about 20 minutes, all it is doing is loading to the att screen, staying there for a sec, then the screen goes black, the the att screen pops up again.. it has just been repeating that since my last post
so something messed up. i wanted functionality until you could help me out, so i was doing the last link you sent me to restore it to stock. Did that, and now it wont even turn on or get into DL mode, the only thing i can get onto the phone is:
RST_STAT =0x1
PMIC_IRQ1 =0x3c
PMIC_IRQ2 =0x0
PMIC_IRQ3 =0x0
PMIC_IRQ4 =0x0
PMIC_STATUS1 =0xc0
PMIC_STATUS2 =0x2c
Moden booting...
End modem booting.
Now start usb upload.
*
okay maybe i should wait to post, i finally got it into DL mode and installed stock rom
Buckli39 said:
...
okay maybe i should wait to post, i finally got it into DL mode and installed stock rom
Click to expand...
Click to collapse
DL mode can get scary. So many threads warn the user "I'm not responsible for your bricking your phone". Early on I spent a couple of days stuck, "soft bricked". Here too I only tell you what has worked and still works for me.
As you used the link/thread for flashing to stock that I listed perhaps you will have an easier time now.
Then select Settings >> Applications >> Development and tick "on" USB debugging [must disconnect usb cable first]
Now perhaps you can do the Odin work. I looked for where [link/thread] I had found it to no avail so I attach BLs and what I use for CWM3 and rooting. Until now I had preferred passing a thread where you could use others vetted sharing, rather than 'just my copies' of these. BL file can be used in normal Odin. The other two should be named update.zip and placed in the internal SD and flashed in Recovery. [adb reboot recovery].
On to Corn6.3 [CWM safer?] and Serenity 6.0 and subsequent & extras in Recovery.
Phone (Droid Charge) is completely unresponsive after I tried flashing to the factory ROM using Odin per this link: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11. (Two attempts to flash to this ROM aborted in CWM.)
When I used Odin, I got only <OSM> messages in the message box, ending with this one:
<OSM> All threads completed. (succeed 0 / failed 0)
The green status bar never appeared, and the "Start" button reactivated. I did this twice with repeatable results - nothing flashed. I then made the (apparently) huge mistake of removing the USB cable from the phone. It is now a paperweight. No response to power button, no response to plugging phone into wall outlet for charging (battery symbol doesn't appear).
Any ideas, or am I totally screwed?
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
My experience is nothing compared to others but I had a situation similar but for some reason I ended up using the Samsung Flash program instead of Odin and after hours of screwing around it worked.
imnuts said:
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
Click to expand...
Click to collapse
I have tried to do this. Nothing appears on the screen when I connect the phone with the volume-down button depressed.
By the way, before I flashed the ROM (or tried to) I first did the PIT thing per the following thread: [HOW-TO]Fix your phone
Additional info: here is the log of ODIN messages.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
Did you check "re-partition" in Odin before you flash?
If your phone doesn't display logo "Samsung" then your bootloader is shot. The phone is brick for good. Only by miracle it may come back to life. Just let it rest for a day then retry....it's in coma...sorry.
buhohitr said:
Did you check "re-partition" in Odin before you flash?
Click to expand...
Click to collapse
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Look, guys, I think it's clear that I'm hosed. But don't hesitate to ask for more details so that fixes can be developed to help prevent the next guy from suffering the same fate. Rooting has been an expensive, time-wasting exercise for me, and I'd rather it not be for anyone else, if possible.
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
buhohitr said:
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
Click to expand...
Click to collapse
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
The only time removing the USB cable during a flash can result in a brick is while it is flashing sbl.bin AFAIK because that is what contains the "download mode". You can usually recover it without too much trouble otherwise. I don't think that was the root cause.
Sent from my SCH-I510 using Tapatalk
MaxBuck said:
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
Click to expand...
Click to collapse
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable) you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
If I read it right you flashed just the rom with repartition selected one of those times?
Sent from my SCH-I510 using xda premium
Hindle1225 said:
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable)
Click to expand...
Click to collapse
That is correct - I can get no response whatever from my phone whether I attempt any of the following:
- going into download mode with battery removed OR installed, using the USB port directly on my computer.
- turning on the phone normally
- turning on the phone with the home button depressed
Hindle1225 said:
you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
Click to expand...
Click to collapse
Correct.
Hindle1225 said:
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
Click to expand...
Click to collapse
PIT file came from here: [HOW-TO]Fix your phone
ROM installed at the outset of this process came from here: [12-14-11][ROM][EP4D] InfinityROM
ROM I was trying to flash to came from here: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11
Hindle1225 said:
If I read it right you flashed just the rom with repartition selected one of those times?
Click to expand...
Click to collapse
Not sure what you're asking here.
Again my knowledge is very limited but all of what you described I went through and eventually recovered. I pulled the cable out while installing. It didnt see it in Odin. Says it installed but didnt. And Im sure several other things. In my mind this thing is really hard to totally brick. I reinstalled all samsung drivers, downloaded the files again but used the Samsung Flash program to get back up.I tried different ports, cables etc.I went through the stuff you are for almost 8 hours lol before I finally got it running but it did. Cant hurt to try everything one more time. If you feel it is a paper weight then and have no recourse such as warranty sell it.Crap I might buy it cheap to waste a couple of hours(lol) just to see what I could do.
MaxBuck said:
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Click to expand...
Click to collapse
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
MaxBuck said:
Not sure what you're asking here.
Click to expand...
Click to collapse
I was making sure I knew the steps you went through. If you really can't get into download mode, thats bad news.
imnuts said:
There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time.
Click to expand...
Click to collapse
This is what I was getting at.
Sent from my SCH-I510 using xda premium
imnuts said:
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
Click to expand...
Click to collapse
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
imnuts said:
...
2. Open up Odin, click PDA, and select the package you downloaded
3. Click on PIT and select the PIT file that you downloaded.
4. Get your phone into Download mode.
...
7. Press "Start" and flash the package.
Click to expand...
Click to collapse
It seems that step 2 is what you were confused on - while I can't speak to how others interpret this my interpretation is that there is something in both PDA and PIT before pressing start. I seem to remember something about folks that "unbricked" phones for something like $40 - mobiltech video or unbrickable mod are terms that come to mind. In the same How-To thread the above instructions are quoted from are folks mentioning such things at least.
Just get your phone unbricked for 40 bucks. then I would either get a new comp to flash with or borrow a friends comp. I suggest using spc latency checker on your comp to see if you have latency issues. Also, try a new cable. I have found that many cables don't work well.
Sent from my SCH-I510 using XDA App
MaxBuck said:
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
Click to expand...
Click to collapse
I'm pretty sure you did it wrongly.
Like others comment, you only need press START button once, AFTER you select PIT file and ROM file (in PDA section), tick the Re-partition (and leave the other unchanged). No need to press START button twice (it seems you press it twice? based on your explanation) ...
If you still able to enter DOWNLOADING MODE, maybe better if you try to reinstall your samsung driver and maybe change the usb port used to flash, or if needed restart your computer ... and after it is detected by ODIN, do it again in the correct way ...
Hope you can unbrick your phone ...
For what it's worth, I've flashed the PIT file by itself in Odin with no problem. Completely acceptable but like was mentioned, you shouldn't really need it in most cases, even situations like this. But I wonder if somehow Odin attempted to flash sbl.bin and failed. That has the potential to hard brick the phone for sure since that file contains download mode. Does anyone know of another way to push the bootloader files to the phone?
Sent from my SCH-I510 using Tapatalk
Did you ever get this phone recovered and/or try one of those $40 programs someone mentioned? I am in the same boat it seems. =(
I had been running Synergy R72 (with the bootloader unlocked).
Today I tried to flash CM-10 Milestone using Rom Manager. It failed. No biggy right?
The research I did suggested using Odin to flash a couple of files (VRALEC, VRAFL2, Root66). Those processes caused Odin errors too and did not complete and Odin finally got stock at "CS."
After trying to restart Odin a few times (another suggestion) I did a battery pull and restarted the phone (into DL mode) and got the dreaded "System Software not authorized by Verizon has bee found on your phone." (I was searching for the 16GB .pit file in hopes of pushing that to the phone)
Some posts suggest using Odin to get around this but I can't get Odin to even recognize the phone. I tried to use the Galaxy Tool Kit to connect to the phone but it never found it although I didn't exhaust every option on the Took Kit menu).
I think I now have a very personal relationship with the word "Bricked ."
What are my options/solutions?
So you can't put your phone into download mode at this point?
that is correct. Only lights up with the "Unauthorized" screen.
One caveat. This phone is often hard to get into that mode (half the time it boots into "normal") But I've tried to get to the DL mode more times than I care to think about. And will try some more.
Aargh.
I'd keep trying, see if ADB recognizes it and put in "adb reboot download" without the quotes. If that doesn't work, invest in or build a USB jig to force it into download mode. You're SOL without download mode.
mustbepbs said:
I'd keep trying, see if ADB recognizes it and put in "adb reboot download" without the quotes. If that doesn't work, invest in or build a USB jig to force it into download mode. You're SOL without download mode.
Click to expand...
Click to collapse
thanks for that advice. A couple of notes:
- When I do try to boot into DL I do see that tiny blue text top left as if it wants to go into DL mode.
- when you say "see if ADB recognizes it" I'm not at all sure what you refer to? I have ADB drivers on my PC. Is there something to do with those?
- I'm happy to build or buy a USB jig. what the hell is that?
Hmm. What happens if you do take it to Verizon?
mustbepbs said:
I'd keep trying, see if ADB recognizes it and put in "adb reboot download" without the quotes. If that doesn't work, invest in or build a USB jig to force it into download mode. You're SOL without download mode.
Click to expand...
Click to collapse
(I should think a bit more before typing).
I DL'd ADB and Fastboot.
Please provide the exact command strings etc.
I assume that I connect the phone via USB and turn it on. (It will display the "Unauthorized" screen.
Then do I open a command prompt and type "USB reboot download"
If that's correct I get an "error: device not found"
Running "SDK Manager" in the \lib directory returns this error:
FAILED TO EXECUTE tools\android.bat error 2
The system cannot find the file specified.
This actually gives me hope that perhaps ADB isn't correctly installed (not that I know why or how to repair).
When you get to the Unauthorized screen, did you pull the battery and then reinsert, then hold power+home+volume down? This should put it into download mode
yosterwp said:
When you get to the Unauthorized screen, did you pull the battery and then reinsert, then hold power+home+volume down? This should put it into download mode
Click to expand...
Click to collapse
Thanks for your help.
Yes, I've done that many times.
I do briefly see the phone display the tiny blue text top left that evidently presages the DL mode but it just goes "Unauthorized"
maplewood said:
Thanks for your help.
Yes, I've done that many times.
I do briefly see the phone display the tiny blue text top left that evidently presages the DL mode but it just goes "Unauthorized"
Click to expand...
Click to collapse
You can buy a usb jig from mobile tech videos, Google it. Also look up the tons of guides for adb. You get the sdk and android platform tools, from there you open a command prompt in the folder containing adb-windows.exe (I don't think they renamed it yet, you can for ease of use though to just adb.exe), put the command in adb reboot download and you should be set. Make sure your phone is connected and turned on.
Tl;Dr just look it up lol
Recovering from soft brick
yosterwp said:
When you get to the Unauthorized screen, did you pull the battery and then reinsert, then hold power+home+volume down? This should put it into download mode
Click to expand...
Click to collapse
Well the stars must have re-aligned. I can finally get into DL mode.
But I'm not sure what is on the phone so am quite clueless as to what to start rebuilding. I had been following this thread http://forum.xda-developers.com/showthread.php?t=1840030&page=5 when things went pear shaped.
I'm gonna follow the measure twice, cut once methodology next but don't know what files to try to flash to the phone. (that thread recommended VRALEC, VFRALF2 and Root66. It believe things crapped out with Root66)
<<TIME PASSES>>
Flashing VRALEC.bootchain.tar.7z worked fine.
However trying to add . BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar (or more precisely the MD5 version thereof) fails because every copy of the file I find evidently is "invalid"
Odin says:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5 is invalid.
<OSM> End...
As I've tried to download that file from different sources I'm starting to think that the problem is not in the file but in something I'm doing. ??
BTW: the phone displays the following:
Odin Mode
Product Name I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Hi!
I need help.
I have the Galaxy Note 12.2, SM-P900 (wifi only version). The device is rooted but running stock recovery and ROM.
I was using Titanium backup as I do with all of my devices and chose to "Integrate Updates Into ROM". It seemed to go successfully but things went wrong once I went to reboot the device.
Upon rebooting, I saw the Samsung logo pop up then the screen went black, not off because I could see the faint glow of the screen lights at the edges, but the screen stayed black. It wouldn't boot. I left it for 10-15 minutes and nothing.
So I then held down the buttons to get into the standard recovery mode, which worked. I tried wiping cache and rebooting. Same thing.
So next I tried going into download mode, which I did, but that's an area I'm not sure what to do with.
I opened up Kies and connected the device but it wouldn't find it.
So I left it with nothing to do until the battery ran down.
Today I picked it up again, hoping that it would magically start up. Nope.
I put it back in recovery mode, wiped cache and did a factory reset, but that didn't work. I can still get into recovery mode and odin mode.
Please help! I really am hoping that I don't have a really expensive brick.
Followup information
To followup on my original post.
I was able to successfully put the Galaxy Note 12.2 into Odin mode, load up Kies on my PC and connect the Note to the PC.
In the "ID:COM" box it now says "0:[COM5]" with a yellow background and in the "Message" box it shows "<ID:0/005> Added!!".
So can I be hopeful that I might be able to use Odin to recover the Note?!
Thanks again for any help any of you can give. It is certainly appreciated.
Download odin 3.09
Go to samsung-updates.com site (thos s not Samsung's site, but there you can find firmwares for all sam's devices).
Choose sm-p900 (your model) section and download package for your country (CSC code)
Unzip downloaded package - you should have a file ending with .md5.
Click on AP button *Center to right in Odin), and select unzipped file that ends up with md5.
Wait until file is checked by odin, it can take some time - and click start.
Important: do not tick / untick anything on left side of Odin - do not tick repartition! Leave as it is when you start Odin.
And that's it - wait iunit process ends up. In case no boot, try to wipe data / cache again.
Unable to find SM-P900 firmware for the USA?
jba.33a said:
Download odin 3.09
Go to samsung-updates.com site (thos s not Samsung's site, but there you can find firmwares for all sam's devices).
Choose sm-p900 (your model) section and download package for your country (CSC code)
Click to expand...
Click to collapse
Hi Thanks for responding so quickly and thoroughly! I went to the updates site as directed and chose my device, but none of the firmwares shown are for the US. I searched online and it shows that the codes for the US are "AWS, CLW, DOB, TMB".
Any further suggestions?
Thanks again.
jopop said:
Hi Thanks for responding so quickly and thoroughly! I went to the updates site as directed and chose my device, but none of the firmwares shown are for the US. I searched online and it shows that the codes for the US are "AWS, CLW, DOB, TMB".
Any further suggestions?
Thanks again.
Click to expand...
Click to collapse
Try BTU - since this is wifi model it shold not really matter - and BTU is British one...
I am having this same exact issue...
I had root access, downloaded Rom Manager and clicked to install TWRP and it rebooted my tablet and did the same things you describe.
I am still downloading the stock image (it's pretty huge, over 1GB) and hope that this will work
I seriously JUST got this tablet. I hope it's not a goner, otherwise that's a ton of money down the drain.... I'll post back with any results once I try running the stock image through Odin.
Edit:
OK, so I was out all day while my tablet was in perpetual blank screen-on mode after the Samsung boot animation. I left it unplugged because there was nothing I could do about it until later anyway. So I let the battery die, and I just got home, plugged it in for a few minutes, boot it up like normal (just using the power button, no Odin or stock recovery) and it prompts me to sign into all of my accounts and stuff, as if I had just gotten the device. I had to re-enter all my info, download all of my apps again, and enable developer options, so I am assuming somehow my tablet reformatted itself into factory conditions after the battery died? I even still have root and supersu on my device, so yeah. I have no idea what ROM Manager did to my device but hopefully it was nothing permanent.
If anyone is having this issue, before you mess around with Odin and trying to reflash a stock image, maybe just let the battery run down, wait a while and boot up like normal?
I'll report back here if my tablet starts going crazy for any unknown reasons, but so far, it seems OK. Hopefully it really did just do a factory image restore by itself and my precious tablet is OK!
Where did you get the stock image? I used Odin to flash a rooted ROM but Odin failed and I now get a message that says the firmware upgrade failed. I can get into download mode and Odin recognizes my tablet but I don't have a file that works. What has me panicked is that it says my Knox counter is 1! I really regret now trying to root this. All I really wanted was to be able to add more apps to multi-window. That was not worth the trouble I'm in now. Please help!
Sent from my SM-N900V using XDA Free mobile app
jopop said:
Hi Thanks for responding so quickly and thoroughly! I went to the updates site as directed and chose my device, but none of the firmwares shown are for the US. I searched online and it shows that the codes for the US are "AWS, CLW, DOB, TMB".
Any further suggestions?
Thanks again.
Click to expand...
Click to collapse
jba.33a said:
Try BTU - since this is wifi model it shold not really matter - and BTU is British one...
Click to expand...
Click to collapse
XAR is the region code that you want.
I have a copy if you are in need of it.
larkhillv said:
I am having this same exact issue...
I had root access, downloaded Rom Manager and clicked to install TWRP and it rebooted my tablet and did the same things you describe.
I am still downloading the stock image (it's pretty huge, over 1GB) and hope that this will work
I seriously JUST got this tablet. I hope it's not a goner, otherwise that's a ton of money down the drain.... I'll post back with any results once I try running the stock image through Odin.
Edit:
OK, so I was out all day while my tablet was in perpetual blank screen-on mode after the Samsung boot animation. I left it unplugged because there was nothing I could do about it until later anyway. So I let the battery die, and I just got home, plugged it in for a few minutes, boot it up like normal (just using the power button, no Odin or stock recovery) and it prompts me to sign into all of my accounts and stuff, as if I had just gotten the device. I had to re-enter all my info, download all of my apps again, and enable developer options, so I am assuming somehow my tablet reformatted itself into factory conditions after the battery died? I even still have root and supersu on my device, so yeah. I have no idea what ROM Manager did to my device but hopefully it was nothing permanent.
If anyone is having this issue, before you mess around with Odin and trying to reflash a stock image, maybe just let the battery run down, wait a while and boot up like normal?
I'll report back here if my tablet starts going crazy for any unknown reasons, but so far, it seems OK. Hopefully it really did just do a factory image restore by itself and my precious tablet is OK!
Click to expand...
Click to collapse
Vlip3 said:
Where did you get the stock image? I used Odin to flash a rooted ROM but Odin failed and I now get a message that says the firmware upgrade failed. I can get into download mode and Odin recognizes my tablet but I don't have a file that works. What has me panicked is that it says my Knox counter is 1! I really regret now trying to root this. All I really wanted was to be able to add more apps to multi-window. That was not worth the trouble I'm in now. Please help!
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
you guys are going to need a couple of things...
the XAR firmware from Sammobile.
ODIN 3.09
CF-AutoRoot from General Section and the bc3 boot img.
If you need files I have them...
Also I have thread in the general section that you can use to un-brick and fix your tablet.
I have bricked and unbricked my device several times. Just remember don't panic and you will be fine. Let me know what you guys need and we will get you up and running again.
Bizack
1st thing. When you root your tab knox gets tripped. no way around this. So if this is a deal breaker, step on it and take it back. you will not get root love however.
If you do want Root, knox is tripped so why not? Follow these steps.
1. charge your tablet.
2. Down load these files.
Recovery Boot img nb3
TWRP Custom Recovery
Stock NC5 Firmware
CF-AutoRoot (go to His Post in General Section)
When charged, boot into download mode and flash the full stock package. (PDA in 3.07, AP in 3.09 ODIN) don't mess with the check boxes, when it finisheh verifying the md5 just hit start... Go take a break...
When that is done you will be back to stock, original just like you bought it.
Now boot back in to download mode and this time you are going to flash the NB3 recovery image tar... same place in ODIN as before. ( uncheck reboot in ODIN)
When that completes, disconnect your tablet and boot it back into download mode.
When you are back in Download mode, then you can safely flash the CF-AutoRoot.... (leave checks default and flash it in same slot in ODIN.
Finally, when that reboots, go back into odin and flash the custom recovery and then you will be able to boot into recovery and make a back up, (always good to make a back up) you can restore back to point in time. (that you made the backup.)
after you are all done, you can get Xposed installed and tweak the hell out if your rom. At minimum install Titanium Back up and freeze all of the knox apps.
what is "XAR firmware"?
ornobohornish said:
what is "XAR firmware"?
Click to expand...
Click to collapse
That, for some reason, is our Region code for Samsung firmwares...
ok thanks!
Stock Firmware Recovery Failing at system.img
Bizack said:
When charged, boot into download mode and flash the full stock package. (PDA in 3.07, AP in 3.09 ODIN) don't mess with the check boxes, when it finisheh verifying the md5 just hit start... Go take a break...
Click to expand...
Click to collapse
Hi Bizack.
Thank you for coming in and giving detailed information on restoring our devices. It has been maddening to say the least.
I downloaded all of the files that you linked to and followed your instructions.
However, when during the first step for flashing the full stock package, it fails at system.img
Right now it is giving me the "Firmware upgrade encountered an issue" screen, then there is some message in Chinese or Korean at the bottom of that.
I have tried Kies Emergency Firmware Recovery and it just doesn't recognize the device as needing it or being valid I guess.
So do you have any idea why it works up until system.img?
I had previously been able to use Odin to flash the firmware for China, then replaced it with New Zealand and those never failed at system.img.
But I really want it back to US firmware.
Thanks again for any help, suggestions or advice you can give.
Jo Pop
I was continuing to try to find answers online, and there found some questions about a "pit" file when people are changing regions?
Could this be part of the problem? I had accidentally flashed the Chinese firmware and then flashed the New Zealand firmware, but since then I can never get the United States (XAR) firmware to flash.
If it is, where would I find the right PIT file?
Thanks again.
jopop said:
I was continuing to try to find answers online, and there found some questions about a "pit" file when people are changing regions?
Could this be part of the problem? I had accidentally flashed the Chinese firmware and then flashed the New Zealand firmware, but since then I can never get the United States (XAR) firmware to flash.
If it is, where would I find the right PIT file?
Thanks again.
Click to expand...
Click to collapse
Flash it again in odin, this time Check "nand erease all", this will clear out any residual crap left over from failed flash attempts.
You did get the full firmware for the p900 from me?
Sent from my SM-P900 using XDA Premium 4 mobile app
Odin Failed at erase all nand while flashing XAR NC5 firmware
Bizack said:
Flash it again in odin, this time Check "nand erease all", this will clear out any residual crap left over from failed flash attempts.
You did get the full firmware for the p900 from me?
Click to expand...
Click to collapse
Yes I downloaded all of the files you provided links to and followed your instructions again. This last time I checked "nand erase all" as I was flashing the NC5 firmware you provided.
It failed at Erase.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P900UEU1ANC5_P900XAR1ANC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Erase...
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
These problems only seem to happen when trying to flash back to the original XAR firmware. I had no problems when I had flashed the Chinese and New Zealand firmwares.
I'm at a loss, but I'm hoping that you are not.
I don't know if this helps, but on the Odin screen I have the following information:
Product Name: SM-P900
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 1
AP SWREV: A1
Also, when I go into recovery mode, on the bottom left it says that it is applying the CSC code of XAR even though the firmware currently installed on it is the XXU (New Zealand) one. EXCEPT for the one screen when you first go into download mode, before clicking up to accept, that screen is in Chinese or Korean.
If you have any other ideas, suggestions, need more info, pictures of any screens, whatever, please let me know.
My continued thanks for your help. I have spent a dozen hours on the phone with different Samsung people who have told me to do a factory reset and it will be fine, use Kies and do a recovery which never works, etc. So you have provided more actual technical help than any of them have.
Further info after Odin Fail during Erase
After I posted my last message, I went to reboot the device into recovery. It did load in, but at the bottom left there are error messages that were not there before.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I don't know if that helps more or means that I'm really screwed now.
At the top by the way it shows that the following: Android system recovery <3e> KOT49H.P900XXUANB3
jopop said:
After I posted my last message, I went to reboot the device into recovery. It did load in, but at the bottom left there are error messages that were not there before.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I don't know if that helps more or means that I'm really screwed now.
At the top by the way it shows that the following: Android system recovery <3e>
I am at a loss with the chinese firmware.
If you can live with the new zealand, go for it.
Somrthing has to have been changed witht the other firm wares if you cannot successfully flash the stock package.
You are on the nb3 recovery boot loader so you should be able to flash back to stock.
I would try and switch the usb port, remove device open kies reinstall drivers change port let the dirves re install and then try to flash it again. nand erease all and keep switching ports till it works. Find a usb2 port sometimes odin hates usb 3. Try odin 3.07 or 3.09.
I will be on the strip all week\weekend so I will try and look out for your post...
Good luck.
Sent from my SM-P900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No progress. Tried reversing what I did in the first place.
Bizack said:
jopop said:
I am at a loss with the chinese firmware.
If you can live with the new zealand, go for it.
Click to expand...
Click to collapse
So after continued no luck, even after erasing the nand when flashing the XAR firmware, I went ahead and flashed the XXU firmware, no problem. Then I realized that I initially went from XAR to the Chinese version then to the XXU. So I factory reset everything and I reflashed the Chinese firmware (P900ZCUAND4_P900CHNAND4_CHN). No problem. Flashing went fine. Rebooted into Chinese.
So I again went in to recovery, did a factory reset, then rebooted into recovery, reloaded Odin 3.09 and attempted to flash the firmware that you linked to (P900UEU1ANC5_P900XAR1ANC5_HOME.tar).
And again it failed at the system.img.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P900UEU1ANC5_P900XAR1ANC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> recovery.img
<ID:0/008> sboot.bin
<ID:0/008> system.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm at a complete loss why those other two firmwares can be flashed and reflashed with no issue, but the XAR version can not and Kies doesn't recognize it as needing help or when I try to force it to do something, it then says that it can not update my version of the device. I'm guessing that is because I am not in New Zealand or China.
Anyone have anything for this?
Click to expand...
Click to collapse
You might try getting into recovery and formatting the system partition, if stock won't try flashing the TWRP Recovery and format everything, but try system first.