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
Related
Hi all. I thing my phone is struggeling to survive.
First I'll give you some background info:
Phone is SGS3 I9300.
[ROM] Has been running Omega Rom since one of the first versions. Been running v32 since it was released (not v32.1)
[Kernel] Been running Omega's tweaked stock kernel most the time, but installed SiyahKernel 1.7rc3 some days ago.
About a week ago I recieved a 64gb SanDisk MicroSDXC card and installed Mittiadj's ExtSD2InternalSd script.
[recovery] CWM V6.0.1.2
So, what happened?
Well, when I installed the extsd2internal it wouldn't apply on boot, so per his guide, I installed Script Manager and got it working.
Some days ago I wiped system, flashed omega 32, flashed siyah kernel and flashed the extsd2internal for custom kernels.
Now the script worked without script manager.
After I installed Siyah, the phone reboted twice, about a day or 2 apart. The 3rd time it rebooted automatically, it did not manage to boot again (stopped at the Siyah boot logo,the purple eye).
From here, I switched the phone off, and using vol-up+home+power, I am SOMETIMES able to get into recovery. However, in recovery, I am able to flash cache but not dalvik, I tried flashing Omega, but it froze during the install wizard, I tried wiping system (for another attempt at Omega) but it rebbots then also.
Now the phone only gets to the White Samsung logo or to recovery (but recovery only shows version and the text)
E: can't mount /cache/recovery/command
Click to expand...
Click to collapse
If I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
Click to expand...
Click to collapse
Where can I go from here?
What has gone wrong?
I am suspecting the memory chip is fubar, but hope someone can tell me otherwise
For the record, I have tried booting with and without sim and microsd, no change comes from that.
In the mean time I guess it's time to resurrect the god'ol Nexus One
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
>>>>>>
f I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Quote:
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
This reads as totally bolocksd firmware and recovery .
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
jje
jje
Click to expand...
Click to collapse
JJEgan said:
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
Click to expand...
Click to collapse
Tried flashing CWM via ODIN, but get an error after Writing stage. (i shoulden't have done that, because before the flash counter was 0, and it showed stock, after it shows as modified
Any reason to believe that flashing a stock rom will work better than flashing CWM?
Click to expand...
Click to collapse
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
JJEgan said:
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
Click to expand...
Click to collapse
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Requiem87 said:
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
not looking so good - I think I would have another go at flashing stock - my AV/ firewall sometime stop odin trying disabling them - I suspect it wont help but hopefully it will
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
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
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
gecafe said:
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
Click to expand...
Click to collapse
In download mode you can install the last stock 4.1.2 Jelly Bean UCMD8 firmware using the program Odin follow this complete tutorial :
http://www.android.gs/flash-android...d8-update-for-the-att-samsung-galaxy-s2-i777/
After installing the stock ROM root your phone in this way:
1-Download Framaroot apk file into your device.
2-Go to Menu—>Download, locate the Frameroot apk file.
3-Press on Frameroot apk file in the Download folder. A pop-out windows ask for confirmation, press confirm/yes to proceed with Framaroot installation.
4-Once Framaroot successfully installed on your device, you shall find Framaroot icon in the Menu.
5-Press on Framaroot icon in Menu to launch the app.
6-In Framaroot user interface, choose Aragorn exploits within the list of exploits.
7-You shall now receive a exploit results: “Success… Superuser and su binary installed. You have to reboot your device”
Sent from my SGH-I777 using xda app-developers app
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gecafe said:
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
pepe100 said:
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
That's what i used, but im gonna install it again
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
gecafe said:
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
Click to expand...
Click to collapse
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
creepyncrawly said:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
Thanks mate im gonna try it, but how do i get recovery mode, i tried to do it but it didn't work, i tried this:
Press volume+ and volume- at the same time 5 seconds and later press power button, i always get to the download mode.
OK guys, i have not solved my problem but i could investigate something thanks to my friend's i777 phone, and this is:
I noticed he had Rom manager, and he said he uses it lot of times and his phone have not gotten a problem, so i tried the rom magager recovery mode (what i tried and f***** my phone), the phone worked great and did not have any problem, after trying lot of things i decided to use the NQ antivirus, and it detected the rom manager as a virus and dangerous app i had to uninstall, actually just tried it in a i777 phone, tomorow i'll try on a different phone to see if this is normal.
Im gonna keep investigating about what rom manager does after solving my problem.
creepyncrawly said:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
gecafe said:
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Click to expand...
Click to collapse
You need to try a different known good usb cable, or different ports on the computer, or even a different computer to see if you can get Odin to complete. If you are absolutely sure that the reason Odin does not complete is not due to the above, then you may have a firmware problem that is beyond my ability to help you, or you may have some kind of hardware issue.
If it were my phone, I would probably send it to Mobile Tech Videos, since they are reliable and very good, but if you are not willing to spend money, then I don't have anything else to suggest.
Edit: It occurred to me that you may not have followed the full sequence. Did you get to step 4, and if not you need to try to flash the sbl.tar by itself in the pda slot and then go back to step 1.
I have been there...
This has happened to me a couple of times. You can either do a complete flash of a stock rom and go from there, OR, you can flash a recovery kernel. There is an old Sylah image floating around. You can flash this with the Odin tool. I believe Odin 3.07 worked best for me.
SteveMurphy said:
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
Click to expand...
Click to collapse
First of all is im a newbie in XDA i saw the warning when i joined, it seems u got mad, if u cant be patient with a noob, dude just let others help me.
Thanks im gonna try another pc and cable.
Hey everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.