Hi Guys
First time writing here,hope to finde a soluttion.
I bought a Galaxy Note 2 Verizon(sch i605),since I was not using it in Verizon I was not able to send SMS and a pop up appears all the time,telling me that the SIM is not Verizon etc
To fix those things I rooted it and installed JEDI X ROM.Everything seems fine.
I saw that the version of rom says T Mobile when Jedi X was Installed
So i thought If I will install T mobile stock ROM,In my verizon,sms and everything will work fine and I will not have anymore a rooted phone.
I used ODIN to put the file,everything seems fine,but now it has stuck in a boot loop
When I turn it on it says samsung and get restarted,all the time just restart
I can not go to recovery ,but I can get to download mode
I have tryed everything I could for 9 hours,but nothing
I sent it to a Local Service repair and they said they have Tried J TAG and no results at all
So i wana ask,What can I do?
Thank you so much in advance
It isn't bricked but perhaps you would have better luck resolving your problem posting this on the note 2 section rather than the gs4 section...
Sent from my rooted S4 blessed with whatever the latest CleanRom version may be....
Evocm7 said:
It isn't bricked but perhaps you would have better luck resolving your problem posting this on the note 2 section rather than the gs4 section...
Sent from my rooted S4 blessed with whatever the latest CleanRom version may be....
Click to expand...
Click to collapse
Thank you so much Evocm7 for the reply,what can I do?
I am so desperated
Please Moderators put this thread to Galaxy note 2 Verizon...and sorry
fredi0014 said:
Thank you so much Evocm7 for the reply,what can I do?
I am so desperated
Please Moderators put this thread to Galaxy note 2 Verizon...and sorry
Click to expand...
Click to collapse
read this thread http://forum.xda-developers.com/showthread.php?t=2024207
----------------------------------
Step 1: Download and install Odin- http://forum.xda-developers.com/atta...2&d=1340993443
Step 2: Download one of these stock VRALJB images and pit file to a windows based pc. Make sure to extract the file with 7zip, there should be a .tar file extension.
Official VRALJB 4.1.1 12/9/12- http://www.androidfilehost.com/?fid=9390214368362234374
This will wipe data and return your device to factory stock out of the box conditions. This file can only be used on devices that never took the VRALL4 or VRAMC3 OTA update. If this file is flashed on a updated device, Odin will fail @ sboot.bin.
Alternate Restore File 4.1.1 VRALJB- http://www.androidfilehost.com/?fid=9390225151984927096 This restore file is for folks currently on the latest VRALL4 or VRAMC3 OTA. The Alternate Restore File does not lock bootloader, but will unroot and replace recovery with Android Stock Recovery. To complete the bootloader lock, simply OTA update.
Root66 stock VRALJB 4.1.1 12/2/12- http://androidfilehost.com/?fid=9390210501348163619 This is our very first fully functional rooted Odin image.. Thanks MrRobinson!! This file does not wipe data, lock bootloader, or replace recovery. Its simply a easy way for folks who want to flash back to rooted stock as a stepping stone to another rom.
SCH-I605_16gb.Pit- http://www.mediafire.com/download.php?05cj895zu3tls7z
Step 3: Power device off, hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "odin or download mode".
Step 4: Open Odin and connect the oem usb cable from pc to device. The driver should automatically install( it did for me on windows 7 64bit). There should also be a "comport number" in upper left hand corner of Odin indicating communication between the pc & device.
Step 5: Click on the pit function of Odin and select the sch-i605-16gb.pit file.
Step 6: Click on the PDA function of Odin. Select the stock VRALJB image you downloaded in step 1, then select start. This operation should take less than 8 minutes before Odin will say pass/reset.
Step 7: Your device should boot back up into factory stock 4.1.1 android! However, If your device is stuck in a bootloop, power the device off, press and hold the volume up/home/power buttons until the samsung logo appears. The device will boot into recovery and from there you will need to wipe data/factory reset, then reboot.
theidoctor said:
read this thread http://forum.xda-developers.com/showthread.php?t=2024207
----------------------------------
Step 1: Download and install Odin- http://forum.xda-developers.com/atta...2&d=1340993443
Step 2: Download one of these stock VRALJB images and pit file to a windows based pc. Make sure to extract the file with 7zip, there should be a .tar file extension.
Official VRALJB 4.1.1 12/9/12- http://www.androidfilehost.com/?fid=9390214368362234374
This will wipe data and return your device to factory stock out of the box conditions. This file can only be used on devices that never took the VRALL4 or VRAMC3 OTA update. If this file is flashed on a updated device, Odin will fail @ sboot.bin.
Alternate Restore File 4.1.1 VRALJB- http://www.androidfilehost.com/?fid=9390225151984927096 This restore file is for folks currently on the latest VRALL4 or VRAMC3 OTA. The Alternate Restore File does not lock bootloader, but will unroot and replace recovery with Android Stock Recovery. To complete the bootloader lock, simply OTA update.
Root66 stock VRALJB 4.1.1 12/2/12- http://androidfilehost.com/?fid=9390210501348163619 This is our very first fully functional rooted Odin image.. Thanks MrRobinson!! This file does not wipe data, lock bootloader, or replace recovery. Its simply a easy way for folks who want to flash back to rooted stock as a stepping stone to another rom.
SCH-I605_16gb.Pit- http://www.mediafire.com/download.php?05cj895zu3tls7z
Step 3: Power device off, hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "odin or download mode".
Step 4: Open Odin and connect the oem usb cable from pc to device. The driver should automatically install( it did for me on windows 7 64bit). There should also be a "comport number" in upper left hand corner of Odin indicating communication between the pc & device.
Step 5: Click on the pit function of Odin and select the sch-i605-16gb.pit file.
Step 6: Click on the PDA function of Odin. Select the stock VRALJB image you downloaded in step 1, then select start. This operation should take less than 8 minutes before Odin will say pass/reset.
Step 7: Your device should boot back up into factory stock 4.1.1 android! However, If your device is stuck in a bootloop, power the device off, press and hold the volume up/home/power buttons until the samsung logo appears. The device will boot into recovery and from there you will need to wipe data/factory reset, then reboot.
Click to expand...
Click to collapse
PDA ONLY KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ROOT 66 OR VRALJB AND PIT FILE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
GETS STUCK HERE FOR 40 MIN AND MORE
Related
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Dolphlungegrin said:
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Click to expand...
Click to collapse
Solved.
Fix:
Resinstalled Odin (wouldn't let me run as administrator before. Reinstalled Me7 from zip (extracted). Booted up Odin. Unchecked repartion. and voila. It re-flashed successfully.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
i had the same problem. if your just trying to get unbricked i can help. (warning i am extremely new at all this). so i did the update and ever since had been trying to get root access and flash a custom ROM. i too tried to install twrp through goo manager. i kept bricking my device by trying to boot into recovery. i found out that if do a battery pull, and hold the volume down and power button (booting into recovery) but dont let go until a warning page comes up. it should warn you about installing custom roms and give you the option of continuing by pressing the volume up button, or pressing the volume down to reboot. choose to reboot and you should be back to nromal. hopes this helps and was what you where looking for.
Dolphlungegrin said:
Solved.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
Click to expand...
Click to collapse
There is currently no way to install a different rom after taking the ME7 update. You cannot go back to MDK either.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
I own a Orange Samsung S2 i9100 handset. This was working without problem until this morning where it was stuck on bootscreen. Recovery mode does not work.
I tried to update firmware using Odin 3.07 however this does not work. It fails to install.
I am now stuck with the message "Firmware upgrade encountered an error".
I cannot access SD card so rooting etc seems unlikely.
Any ideas?
Win 8 Machine
i9100
ORA-I9100XWLSY-20130606160421
Check out @Hopper8 thread about odin :thumbup:
Thanks.
I assume you are referring to this thread ( [GUIDE][Troubleshoot a failed Odin flash] )?
http://forum.xda-developers.com/showthread.php?t=2345831
I have tried recovering with the two most applicable firmware packages below. I do not know what others to try. I don't think I can use custom packages as I cannot access my SD Card?
http://www.sammobile.com/firmwares/2/
GT-I9100 Galaxy S II
PDA: I9100XWLSY
CSC: I9100ORALS8
MODEM: I9100BVLS4
Added: 2013-06-05
GT-I9100 Galaxy S II
PDA: I9100XWLSW
CSC: I9100XEULS5
MODEM: I9100XXMS2
Added: 2013-05-29
Odin does recognize my phone but each PDA update fails... Kies is installed but not running. Phone still can only go download mode and due to failed Odin update now shows no boot screen (only firmware fail message). I cnanot restore on Kies as did not use this PC before with phone.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSY_I9100BVLS4_I9100ORALS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.. *** At this point I click start
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
andrewwright said:
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
Click to expand...
Click to collapse
I have tried philz recovery steps however this also fails in Odin.
I have tried different usb ports and reinstalling drivers. However Odin can see the phone, so it may not be a USB driver/port issue.
The biggest hurdle is getting Odin to run the flash.
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Original cable used? Have you read and tried all of whats in that thread?
andrewwright said:
Original cable used? Have you read and tried all of whats in that thread?
Click to expand...
Click to collapse
Original Samsung Cable.
Followed instructions in this thread using md5 files for i900?
http://forum.xda-developers.com/showthread.php?t=2201860
Odin packages instructions: Samsung Only
They come in the form of .tar.md5 file
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into main system and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing the 3 buttons combo to for a reboot into recovery.You should see the new CWM
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
to remove yellow triangle, use TriangleAway
Click to expand...
Click to collapse
Whatever I do, Odin still seems to fall over at same place.
What do I need to perform a full factory reset? I take it use Odin to install firmware?
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Sent from a galaxy far, far away
Hopper8 said:
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Click to expand...
Click to collapse
This doesn't work. I have assumed from your suggestion that I use Odin to install firmware via Odin. This fails as well.
I now have a new SD Card I could use to load any software onto the device. However I can not get to the recovery mode screen at all (only download mode). Therefore have no idea what to do now!
I also think my phone is worse now - on download mode screen:
ODIN MODE
PRODUCT NAME: GT-I9100
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: CUSTOM
Click to expand...
Click to collapse
What guide should I use to completely factory reset the phone?
How do I check if the phone memory is correctly partitioned?
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
dmuk said:
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
Click to expand...
Click to collapse
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
niksyspidy said:
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
Click to expand...
Click to collapse
What version? I have tried 1.85, 1.87, 3.04, 3.07 - all fail.
Can I use Kies to repair if I have not previous Kies backups?
I tried to flash a new ROM today, and have had some really bad things happen just one after the other. I'll try to give the rundown as complete as possible:
I downloaded this ROM: http://forum.xda-developers.com/showthread.php?t=2565674
Threw it on my SDCard. Used TitaniumBackup, Booted into Recovery to create a save of the ROM I was using (way outdated Jelly'Beans'), cleared all the necessary settings, and loaded the new ROM. It completed successfully, but upon reboot would hang at the Samsung loading screen.
I dug into the FAQ of the above ROM, located here: http://forum.xda-developers.com/showpost.php?p=47597316&postcount=4056&nocache=1&z=2785911354639757
it says: If you didn't update the bootloader since Android 4.1.2 flash MJ5 bootloader or newer --> ND3 is latest available bootloader - find download link below
So I load back into recovery and use my restore point. I hit the link, download the BL, and use ODIN to load it up. Reboot the phone.. now it constantly flashed the boot screen, but I notice the Samsung boot now has GT-N7100 beneath the logo. What the hell. Back on the FAQ I realize it links to a BL for a completely different version of the Note 2.
I can still hold down volume/home/power and access the downloader.
Using http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1 ODIN v3.07, root66_VZW_stock_system.tar.md5, and sch-i605-16gb.pit I am attempting to return to stock. ODIN is returning these errors:
Occasionally, it will hang at Get Pit for Mapping, and never move, forcing me to unplug the device, remove the battery completely ( or else my PC will fail the software install when plugging back in) or if I turn Re-Partition off I get this error:
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any way to salvage?
Thank you in advance for advice.
UPDATE 1: Removed and reinstalled Samsung USB drivers, restarted PC.
Is it possible that I need flash to a previous bootloader to get back to the stock version outlined in the ODIN thread I linked? If so, can anyone direct me toward a filename?
jenkemdealer said:
I tried to flash a new ROM today, and have had some really bad things happen just one after the other. I'll try to give the rundown as complete as possible:
I downloaded this ROM: http://forum.xda-developers.com/showthread.php?t=2565674
Threw it on my SDCard. Used TitaniumBackup, Booted into Recovery to create a save of the ROM I was using (way outdated Jelly'Beans'), cleared all the necessary settings, and loaded the new ROM. It completed successfully, but upon reboot would hang at the Samsung loading screen.
I dug into the FAQ of the above ROM, located here: http://forum.xda-developers.com/showpost.php?p=47597316&postcount=4056&nocache=1&z=2785911354639757
it says: If you didn't update the bootloader since Android 4.1.2 flash MJ5 bootloader or newer --> ND3 is latest available bootloader - find download link below
So I load back into recovery and use my restore point. I hit the link, download the BL, and use ODIN to load it up. Reboot the phone.. now it constantly flashed the boot screen, but I notice the Samsung boot now has GT-N7100 beneath the logo. What the hell. Back on the FAQ I realize it links to a BL for a completely different version of the Note 2.
I can still hold down volume/home/power and access the downloader.
Using http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1 ODIN v3.07, root66_VZW_stock_system.tar.md5, and sch-i605-16gb.pit I am attempting to return to stock. ODIN is returning these errors:
Occasionally, it will hang at Get Pit for Mapping, and never move, forcing me to unplug the device, remove the battery completely ( or else my PC will fail the software install when plugging back in) or if I turn Re-Partition off I get this error:
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any way to salvage?
Thank you in advance for advice.
UPDATE 1: Removed and reinstalled Samsung USB drivers, restarted PC.
Is it possible that I need flash to a previous bootloader to get back to the stock version outlined in the ODIN thread I linked? If so, can anyone direct me toward a filename?
Click to expand...
Click to collapse
Well hate to tell you this but you need JTAG service. There is NO way to recover from flashing a different phones bootloader.. That is why it is a GREAT idea to read before flashing random things unto your phone
Hi to everyone,
i had a problem with my galaxy S2 i9100 with stock ROM 4.1.2 with root executed by philz temporary recovery, i hope someone may help me.
Yesterday i was taking a picture and suddenly my phone showed Galaxy S2 logo, I think started bootlooping. I tried entering in recovery mode, sometimes showed "Applying csc etc." but never entering in recovery menu, other times blank screen.
So I decided to flash stock JB ROM with odin, my phone can enter in download mode correctly and stated original samsung binary and counter 0.
I used latest branded H3G stock ROM downloaded from sammobile: I9100XWLSD_I9100HUILS4_HUI Odin recognized phone but stucks on
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100HUILS4_I9100NELS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
I followed this troubleshoot trying with multiple odin version, more cables but nothing worked. So i tried flashing philz custom kernel PhilZ-cwm6-XWLSD-OXX-4.87, odin started writing NAND but received write failed, i checked download mode and now i have custom binaries and increased counter with yellow triangle during power on.
After i tried to flash an old bootloader, and this flash was succesfully completed, but not resolved any problem.
Finally i tried to flash wipe JB leaked ROM linked in troubleshoot thread linked above with three separete files for PDA, CSC and MODEM but no luck. now when i power on, phone shows "Firmware Upgrade encountered an issue" message.
What can i do? Any suggestion will be appreciated
Try an older stock ROM with Odin (GB), and use a PIT file to repartition at the same time as flashing the ROM.
Then once you've got GB working, upgrade incrementally.
shionv plain
knuckles1978 said:
Try an older stock ROM with Odin (GB), and use a PIT file to repartition at the same time as flashing the ROM.
Then once you've got GB working, upgrade incrementally.
Click to expand...
Click to collapse
Do you mean selecting PDA from sammobile and pit file? Where can i get the stock one for pit?
I read about repartitioning with pit files that's a risky procedure that can brick phone definitively are there other safer procedures?
EDIT: Tried to flash stock ICS without pit and still not working
How can I fix this? I want to go back to stock. No root. Please see below.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!
I need help with this ASAP.
If you haven't found it already, go to Droidstyle's Restore Guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ). Section 1b has step by step instructions on how to restore the phone. Make sure you use the pit file with the correct firmware version when doing the restore.
Unless you have a Note 2 that never had a firmware update since the phone's release in 2012, then you can't use the VRALJB stock restore image. Droidstyle warned that it would fail at sboot.bin if you try it. Also, if you ever upgraded to 4.4.2, then you can't downgrade back to 4.3 or 4.1.2 because of bootloader issues.
If your phone is currently on 4.1.2 bootloader, then you can restore back to that firmware version. If it's on 4.3 bootloader, then restore back to that... and if it's on 4.4.2, then restore back to that. After returning the phone to Stock, boot into recovery and wipe cache & do a factory reset... as Odin doesn't seem to fully wipe everything.
Droidstyle's link for 4.1.2 looks to be down.... but recognized XDA Developer imnuts has the 4.1.2 VRAMC3 Odin file on his Android File Host site here: https://www.androidfilehost.com/?fid=23159073880932932
Also...if needed, here's a link to the Verizon stock 4.4.2 firmware: ( http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/ ).
Good luck!!
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
GiantsFan91 said:
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Volume up+home+power button would put phone in Recovery mode if it was functioning properly.
You need to use Volume Down+Home+Power button to put the phone back into Odin mode (aka Download mode). From there, you can Odin flash the appropriate firmware to restore the phone. If you're not sure what version of Android you had on the phone before you tried to restore it... then I'm not sure which version you should use.
I used 4.1.1 Jelly bean.
GiantsFan91 said:
I used 4.1.1 Jelly bean.
Click to expand...
Click to collapse
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
I downloaded CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar and fail! I put sch-i605-16gb.pit and CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar. No good.
mattnmag said:
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
Click to expand...
Click to collapse
How? I have no recovery. I can't get in recovery.
You need to put phone into download mode to restore with ODIN... not into recovery.
I did..i restore with ODIN. No good.
You tried to restore back to 4.1.1. It will fail at sboot.bin every time and won't work. You need to restore back to a different firmware version.... whatever version you were on before you tried to Odin flash the 4.1.1 firmware. If your phone was updated to the newest 4.4.2 firmware them you will only be able to restore back to that firmware version because the bootloader is locked.
Bricked Galaxy Note 2 while updating to 4.3
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
christherock said:
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
tried that
mattnmag said:
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
Click to expand...
Click to collapse
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i used file name I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5
and i used pit file sch-i605-16gb.pit
as stated before im still kind of new at this so any information you could provide me would help a ton.
christherock said:
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
Click to expand...
Click to collapse
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
the phone was on 4.1.2 before i attempted the update
mattnmag said:
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
Click to expand...
Click to collapse
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
christherock said:
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
Click to expand...
Click to collapse
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW/
found it
mattnmag said:
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
christherock said:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
I would still use the pit file. If you follow Droidstyle's Restore guide, (but just use the ODIN 3.10 version and the 4.4.2 firmware from Sammobile)... that will hopefully help you to get it restored.
The Sammobile site says not to have the repartition box checked.... but if you use the pit file, it automatically ticks the repartition box (which is what it's supposed to do.... so leave it ticked when using the pit file).
PS: Also make sure you're right clicking on ODIN and running it as Administrator....and disable all antivirus programs and close other running programs in the background when running Odin.
If your friend doesn't want the phone on 4.4.2 and it was never on 4.4.2 previously, then you could try reflashing 4.3 onto the phone using Odin 3.10 just to see if it would work with the newer Odin version. If it doesn't work, you could try 4.4.2.