Hi Guys,
Ive managed to root my phone, install all the necessary ROM files on my internal SD card.
Unfortunately, i have now bricked my fone and i it either stays on the black screen with the initial "Samsung Galaxy S 19000" in white writing....OR...if i press the 3-button combo it takes me to "Downloading mode"
I followed a link which said to..
Step 4.Put your phone into download mode again and flash the CyanogenMod 7 initial kernel (cm7-galaxys-initial-kernel.tar file from initial CM7 package) to it as PDA without auto-reboot using Odin.
Step 5.Reboot your phone into recovery using three button combination again.
Once i tried to reboot into recovery mode...it wouldnt allow me...it only took me to downloading mode. I think its because i didnt install ClockworkMod Recovery.
I need help with the following possible solutions:
Solution A: Can i flash any ROM ONLY using Odin? At least i can get into the phone and install ClockworkMod Recovery manally.
Solution B: Is there any other way to get into Recovery Mode..so i can just wipe/reset to factory mode?
Solution C: Any other ideas??
Thanks...any help would be appreciated!
Hey,
I've recently had a friend of mine give me his phone to look at.
It's a Samsung I5801
I tried installing numerous ROM's onto this such as stock froyo and kyrillos 9.
Whenever i install through Odin i get to the stage where the data needs to be wiped through clockwork. Pretty straight forward, however when the phone is rebooted after this Odin does not detect the phone and will boot into recovery again.
Any ideas? I'm not much of a samsung kinda guy woking with htc all my life lol.
Solved.
Flashing a stock ROM, with bootloader in tact did the job. Had to say was sweating a bit as many were saying it could hard brick phone... Used European JPA.
Flash through ODIN i pray to god no one else has this problem
Wipe using Recovery
Just go in recovery mode and Wipe Cache and Dalvik-Cache.
Problem solved........
I have hard bricked my galaxy 3
I installed ClockworkMod recovery and selected to install ROM from SD card
my phone restarted and booted in samsung,s recovery mode
I selected wipe data and nothing happened for next in 2-3 mins,
So I removed battery and rebooted phone which again booted in samsung,s recovery mode for number of trials.
Then I renamed Rom Filr name to update.zip and moved it to root of SD
and rebooted in recovery and selected option Install update.zip which after some time started executing.
Phone rebooted and now it doesn't show anything else than samsung boot logo.
please help me out.
UPDATE:
Download mode and Upload mode are working but Boot menu is not working.
>>[email protected]<< said:
UPDATE:
Download mode and Upload mode are working but Boot menu is not working.
Click to expand...
Click to collapse
Just give it a try via ODIN since download mode is working
This link might help you ,
he has clearly explained the Odin process to
flash Roms and several do's and dont's
http://forum.xda-developers.com/showthread.php?t=1372414
Phone specs:
Samsung Galaxy S3 Verizon SCH-i535
It was already running KitKat 4.4.2 before I rooted
This is my first time rooting and flashing ROMs to my Samsung Galaxy s3 and I have bricked it. I'm pretty sure it can be salvaged but have yet to find anything that works.
I have written the long version for those who need it, but the short version is that I screwed up and can no longer boot into recovery mode or normal mode, I'm not even sure if Download mode is working, and my device isn't recognized by Kies or Odin on my PC so I cannot yet do a recovery from there.
As of now my phone only boots into Odin Mode (NO recovery, NO normal boot, device NOT recognized by computer programs like Kies and Odin) and gives the following info:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOM SECUREBOOT: ENABLE
BOOTLOADER AP SWREV: 2
and displays the yellow triangle error and says: Firmware upgrade encountered an issue. Please use Software repair Assistant & try again.
I tried to use Samsung Kies which has an emergency firmware tool but my device will not connect and become recognized by the program.
This is pretty much where I'm stuck.
Keep reading if you need additional info.
Steps leading up to problem:
I was able to Root the device succesfully
I then downloaded the latest CM11 package (cm-11-20140217-NIGHTLY-d2vzw.zip) and Gapps
I also downloaded the TWRP recovery img (openrecovery-twrp-2.7.1.0-d2vzw.img)
Once I had these downloaded I got the app [ROOT] Rashr - Flash Tool
I opened the app and tried to do a backup but I'm pretty sure it failed, or at least it said it failed. I couldn't find out how to check, but was not worried since I have already backed up my important files to the verizon cloud.
On the app I went to recover using other file and found the TWRP recovery img I downloaded.
From here I booted into recovery manually, but it did not bring up the TEAMWIN screen for TWRP like I've seen in other video tutorials so I rebooted into normal mode went to the Rashr app again and followed the prompt to do a Recovery boot using the TWRP img.
THIS IS WHERE THE PROBLEMS BEGAN:
It began to lead into recovery mode but it gave a message that said something along the lines that I have tried installing a custom OS and to take my phone to the nearest verizon store.
I turned it off and tried to boot back normally but got the same error.
I tried to boot into Download mode and was successful! So I thought yaay!
Read a tutorial to reload a stock version of android here: http://forum.xda-developers.com/show....php?t=2586319
I followed all the steps but when i got to 7. which said You should see your phone under ID:COM (you should also see it has been added in message) I was not seeing my phone there. I figured it may be OK since I was able to install the drivers so that meant the USB was working so I went ahead and ran Odin to recover Jelly Bean 4.3 onto the device.
My thoughts and guesses as to what the problem is:
I think that it may be because I was already running 4.4.2 and/ or didn't have the proper bootloader when I tried to do the TWRP recovery.
Am I on the right track? Thanks for any help!
You're not bricked if you can still get into Download mode. First of all the Verizon S3 on 4.3 or later has a locked bootloader - you can't install a custom recovery, and only TouchWiz based ROMs are supported using Safestrap. In order to get back up and running you need to see this thread and use the Verizon Utility, or use the Odin method with a stock 4.4.2 ROM seeing as you're on 4.4.2. However I'm surprised your computer doesn't recognize your phone, that almost sounds like more of a drivers issue than anything if your phone still gets into Odin mode. As cliche as it sounds - have you tried rebooting? It may help with a driver issue.
when i factory reset the tab and installed a rom. it started normally. i did everything normally and it showed google account manager has stopped.
so i tried going into CWM recovery mode but got me into stock recovery so factory reset the tablet and then tried wipe cache participation but shows error. I think that the problem is the cache and the dalvich. but i cant use usb debugging so i cant delete the cache and the dalvich.
:crying::crying::crying::crying::crying:
so does any body know how to fix this
thanks in advance :laugh:
Help cache partication error
yolo squad dodo said:
when i factory reset the tab and installed a rom. it started normally. i did everything normally and it showed google account manager has stopped.
so i tried going into CWM recovery mode but got me into stock recovery so factory reset the tablet and then tried wipe cache participation but shows error. I think that the problem is the cache and the dalvich. but i cant use usb debugging so i cant delete the cache and the dalvich.
:crying::crying::crying::crying::crying:
so does any body know how to fix this
thanks in advance :laugh:
Click to expand...
Click to collapse
Can anyone help me please!!!!!!!
yolo squad dodo said:
so i tried going into CWM recovery mode but got me into stock recovery
Click to expand...
Click to collapse
You are not reading what you are typing.
Obvious answer: If you end up in the STOCK RECOVERY you simply do not have a custom recovery installed (Clockworkmod as you wrote). Get yourself a copy of a recent recovery from AndroidAndi's download repository (TWRP, Clockworkmod Swipe, PhilZ Touch), and flash the .tar.md5 of the recovery with ODIN in download mode.
Obvious question: How did you flash a ROM, other than some OTA Stock Samsung update on the device itself, in the first place when you don't have a custom recovery installed in order to do so?
EDIT: What exactly do you mean by "factory reset"? Did you re-flash your tablet with a Stock ROM? If that's the case, then any custom recovery you had installed was wiped and replaced with the stock recovery. Hence why you now don't have a custom recovery anymore.
BoneWithABeagle said:
You are not reading what you are typing.
Obvious answer: If you end up in the STOCK RECOVERY you simply do not have a custom recovery installed (Clockworkmod as you wrote). Get yourself a copy of a recent recovery from AndroidAndi's download repository (TWRP, Clockworkmod Swipe, PhilZ Touch), and flash the .tar.md5 of the recovery with ODIN in download mode.
Obvious question: How did you flash a ROM, other than some OTA Stock Samsung update on the device itself, in the first place when you don't have a custom recovery installed in order to do so?
EDIT: What exactly do you mean by "factory reset"? Did you re-flash your tablet with a Stock ROM? If that's the case, then any custom recovery you had installed was wiped and replaced with the stock recovery. Hence why you now don't have a custom recovery anymore.
Click to expand...
Click to collapse
Odin won't recognise my tablet in Odin mode neither does my computer is there another to install a CWM recovery. By the the I do have back up on the phone if that helps.
By the way I am a noob
yolo squad dodo said:
Odin won't recognise my tablet in Odin mode neither does my computer is there another to install a CWM recovery. By the the I do have back up on the phone if that helps.
By the way I am a noob
Click to expand...
Click to collapse
Just to recap on the steps you should have done...
1. You downloaded the .tar.md5 of the recovery you want to install, from Android Andi's filehost, on your PC
2. You installed the Samsung USB drivers on your computer
3. You installed ODIN on your computer
4. You unplugged the tablet from the charger and powered it off
5. You took your tablet and HELD VOL-UP while you powered it back on (to get into bootloader mode)
6. You plugged the tablet in to the computer and waited for a moment while Windows was installing the driver
--- Here the story ends, according to what you wrote as you say ODIN does not find the tablet.
Well, are you sure you did the steps so far in that order? Can't be that ODIN doesn't detect the tablet when it's operational (read: no a total dead brick) and it's in download mode.
The ONLY problem possible: You installed Samsung KIES, and not just the USB drivers, on your computer. KIES interferes with ODIN. You need to exit ODIN, bring up the Task Manager (press CTRL+ALT+DELETE and select "Task Manager"), find "kies" and end the running process(es) - ignore any warning message.
If that's too complicated: Uninstall KIES and then find the "Samsung Mobile USB drivers" installation package ... with a bit of searching (just to assign some homework to you) you will the links right here in this forum section more than just once.
Once KIES is terminated, or uninstalled and just the USB drivers installed, start ODIN again ... now it should detect the tablet.
Once ODIN confirms that the tablet is detected...
7. Select the .tar.md5 of the recovery as the "PDA"
8. Flash the recovery. Once complete the tablet rebooted into the newly installed recovery.
As for on-device flashing. That's possible...
- Your installed ROM must be ROOTED (no root, no fun)
- You need Chainfire's "MobileODIN" (the free version from the Play Store would suffice), and you need to let MobileODIN install the "p311x flashkernel package" (I think with the free version you need to download it manually from Chainfire's thread and install it manually) - jump into Chainfire's thread and read on
Once you have Mobile ODIN installed it is just a matter of:
- Download the .tar.md5 of the recovery on your tablet once more (or transfer it over from your PC)
- Start Mobile ODIN
- Select the .tar.md5 of the recovery (should automatically be set as a "PDA")
- Flash and reboot into the recovery
However, as a fair warning ... as with every flashing of your device ... keep in mind something could go wrong (just to straighten it out that there's always room for user mistakes or murphy's law getting into the way ("Everything that can go wrong will go wrong"))
BoneWithABeagle said:
Just to recap on the steps you should have done...
1. You downloaded the .tar.md5 of the recovery you want to install, from Android Andi's filehost, on your PC
2. You installed the Samsung USB drivers on your computer
3. You installed ODIN on your computer
4. You unplugged the tablet from the charger and powered it off
5. You took your tablet and HELD VOL-UP while you powered it back on (to get into bootloader mode)
6. You plugged the tablet in to the computer and waited for a moment while Windows was installing the driver
--- Here the story ends, according to what you wrote as you say ODIN does not find the tablet.
Well, are you sure you did the steps so far in that order? Can't be that ODIN doesn't detect the tablet when it's operational (read: no a total dead brick) and it's in download mode.
The ONLY problem possible: You installed Samsung KIES, and not just the USB drivers, on your computer. KIES interferes with ODIN. You need to exit ODIN, bring up the Task Manager (press CTRL+ALT+DELETE and select "Task Manager"), find "kies" and end the running process(es) - ignore any warning message.
If that's too complicated: Uninstall KIES and then find the "Samsung Mobile USB drivers" installation package ... with a bit of searching (just to assign some homework to you) you will the links right here in this forum section more than just once.
Once KIES is terminated, or uninstalled and just the USB drivers installed, start ODIN again ... now it should detect the tablet.
Once ODIN confirms that the tablet is detected...
7. Select the .tar.md5 of the recovery as the "PDA"
8. Flash the recovery. Once complete the tablet rebooted into the newly installed recovery.
As for on-device flashing. That's possible...
- Your installed ROM must be ROOTED (no root, no fun)
- You need Chainfire's "MobileODIN" (the free version from the Play Store would suffice), and you need to let MobileODIN install the "p311x flashkernel package" (I think with the free version you need to download it manually from Chainfire's thread and install it manually) - jump into Chainfire's thread and read on
Once you have Mobile ODIN installed it is just a matter of:
- Download the .tar.md5 of the recovery on your tablet once more (or transfer it over from your PC)
- Start Mobile ODIN
- Select the .tar.md5 of the recovery (should automatically be set as a "PDA")
- Flash and reboot into the recovery
However, as a fair warning ... as with every flashing of your device ... keep in mind something could go wrong (just to straighten it out that there's always room for user mistakes or murphy's law getting into the way ("Everything that can go wrong will go wrong"))
Click to expand...
Click to collapse
odin recognize tablet and it got flash or what ever its called. it restarted but it didn't go into recovery but just restart as normal
I got it working by installing custom rom.
Thanks a lot by the way for the tips
yolo squad dodo said:
odin recognize tablet and it got flash or what ever its called. it restarted but it didn't go into recovery but just restart as normal
Click to expand...
Click to collapse
For future reference: keeping VOL DOWN UP held while powering on/rebooting the tablet takes you into the recovery in case you borked the system and selecting "Reboot" -> "Recovery" from within the _custom_ ROM's power menu is not an option (the Stock Samsung ROM does not have that option by default). Though keep in mind that this only works when the tablet is _NOT_ connected to the charger/computer ... when the USB cable is plugged in it seems to ignore the hardware keys.
yolo squad dodo said:
I got it working by installing custom rom.
Thanks a lot by the way for the tips
Click to expand...
Click to collapse
Great you got your recovery and custom ROM installed. Have fun.
BoneWithABeagle said:
For future reference: keeping VOL DOWN held while powering on/rebooting the tablet takes you into the recovery in case you borked the system and selecting "Reboot" -> "Recovery" from within the _custom_ ROM's power menu is not an option (the Stock Samsung ROM does not have that option by default). Though keep in mind that this only works when the tablet is _NOT_ connected to the charger/computer ... when the USB cable is plugged in it seems to ignore the hardware keys.
Great you got your recovery and custom ROM installed. Have fun.
Click to expand...
Click to collapse
Umm isn't recovery power and volume UP? At least that's how it is on my 7'' tablet and the 10'' I rooted and installed a ROM on.
jrc2
Sent from my T-Mobile S2 using Tapatalk
jrc2 said:
Umm isn't recovery power and volume UP? At least that's how it is on my 7'' tablet and the 10'' I rooted and installed a ROM on.
Click to expand...
Click to collapse
Now that you mention it... yes, you're right jrc... "VOL DOWN" == Download Mode / "VOL UP" == Recovery (I failed to recall the "UP as in update.zip" association).
HI, I'm using a Samsung Galaxy S3 Neo for the past 2 months.. Went for an upgrade to Kitkat OS. All steps were done including the zip files download, odin (latest version). Flashing was successful using odin, entered recovery mode, cleared data/cache, mounted SD card and selected the specific custom ROM zip file. But phone got stucked in "download mode" after rebooting, without pressing any keys other than the power button. I'm not able to enter the recovery mode either after this. Please help me to resolve this. Is this due to soft brick or any firmware issues?