Related
I tried using this process: http://forum.xda-developers.com/showthread.php?t=1746665 to root my phone
After the odin push of the insecure kernel the phone wouldn't boot normally.
I am able to get into download mode, but the phone won't boot.
I'd like to be able to apply a stock rom back to the phone.
When I flash this ROM through odin it fails http://forum.xda-developers.com/showthread.php?t=1737848
steves2947 said:
I tried using this process: http://forum.xda-developers.com/showthread.php?t=1746665 to root my phone
After the odin push of the insecure kernel the phone wouldn't boot normally.
I am able to get into download mode, but the phone won't boot.
I'd like to be able to apply a stock rom back to the phone.
When I flash this ROM through odin it fails http://forum.xda-developers.com/showthread.php?t=1737848
Click to expand...
Click to collapse
boot into recovery and do a factory reset... this helped me
mlemonds said:
boot into recovery and do a factory reset... this helped me
Click to expand...
Click to collapse
No luck, it doesn't get past the "samsung" screen
steves2947 said:
No luck, it doesn't get past the "samsung" screen
Click to expand...
Click to collapse
are you able to get into recovery at all, or no.
There are two 'samsung' screens that i know of, i was stuck at the step 4.
1st: 'samsung'
2nd: 'Samsung Galaxy S III'
3rd: AT&T splash screen
4th: pulsating 'samsung'
I'm going to assume you are stuck on the pulsating Samsung screen. Here is what you should do. Go into the att cwm mode (not the real cwm) by holding volume up, home button, and then power button. Wipe data/factory reset and wipe cache. Then put phone into download mode - volume down, home button, and power button. Open Odin 3.07 on computer, select the from you want to flash in the PDA field, and then plug your phone via the USB cable that came with the phone into a USB port that is connected to your computers motherboard. You should see the COM port turn blue. Flash ROM and you should be good to go.
Sent from my SAMSUNG-SGH-I747 using xda premium
Yes, I can get into recovery and into download mode.
I was able to flash cwm recovery, but can't access the external SD card to attempt to flash a rom that way.
I tried factory reset/data wipe no luck.
I think something with the kernel i loaded is corrupt, so I need to find a known good stock rom to flash via odin.
It gets to the "2nd: 'Samsung Galaxy S III'" if I go into recovery mode.
Never past the first pulsing Samsung in normal boot, or download modes.
bablon bhalco
Was able to locate a working stock rom.
"Samsung-Updates.com-SGH-I747_ATT_1_20120704210732_mk7pwhw8ij"
I appear to be back in biz now.
Here is the link for anyone else who has this issue....
samsung-updates.com/get/195/Samsung_Firmware_SGH-I747_ATT_I747UCALG1_Android_4_0_4.html
Frakin image verification.
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess. i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery. i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys. just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
jamesquags said:
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess.
i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery.
i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys.
just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
Click to expand...
Click to collapse
First of all, good job on searching before posting! :good:
Second, if you want help, try using capital letters at the start of a sentence and using paragraphs. It makes it sooo much easier to read that way.
Third, just keep trying. But from what you're saying about a file-system issue, that could be bad? It's not familiar to me anyways. Hope it didn't damage the internal SD.
If nothing else works, then try the USB-JIG to access Recovery mode. They're like $5 on eBay.
Okay, try these things.
1) Odin a non-rooted, stock ROM that comes with a 3E recovery and try to access that recovery.
If that doesn't work, move onto this step:
2) Odin a different recovery. I attached one to this post. Just unzip it and then odin it. :CWM-Recovery-LTE-SGS3-v5.tar:
Try to get recovery again after a battery pull.
If that doesn't do it, then try this next:
1) Odin a rooted ROM onto the phone.
2) Download the attached "openrecovery-twrp-2.3.1.0-d2att" and unzip it.
3) Download this ADB & Fastboot tool and extract it to your C:/ drive with subfolders using this path: "C:/Android/platform-tools/".
Here is the file to download:
http://www.androidfilehost.com/?fid=9390135922294523275
4) Rename the openrecovery-twrp-2.3.1.0-d2att to "recovery" and place it into the Platform-tools folder.
5) Open the JPEG and follow the EXACT same commands in the pic. This will install TWRP recovery for you.
Then try once again to get into recovery.
If it still doesn't work, then buy a USB Jig.
REPLY
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
jamesquags said:
"Failed to Open Serial [COM] Port".
Click to expand...
Click to collapse
Have you installed the phone drivers? They're linked from the Odin thread.
smelenchuk said:
Have you installed the phone drivers? They're linked from the Odin thread.
Click to expand...
Click to collapse
Yes i have installed the drivers. I have flashed multiple .tar files today.
jamesquags said:
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
Click to expand...
Click to collapse
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
CZ Eddie said:
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
Click to expand...
Click to collapse
After flashing the ROOTED STOCK ROM, I tried about 7 times to boot into recovery. It finally did!!! I then was able to do a wipe data and cache and I'm all set.
Thanks so much for helping me out. -jim
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go if the power button but still press the home + volume up
Sent from my SGH-I747 using Tapatalk 2
jerrycoffman45 said:
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go of the power button but still press the home + volume up
Click to expand...
Click to collapse
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
CZ Eddie said:
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
Click to expand...
Click to collapse
i dont know i have always done it that way well learned something new just tried it your way thanks
Hello, I made a very foolish decision today. I just recently rooted my phone (i747), and i am still not familiar with roms or flashing or any of that. I installed the Rom Manage app by clockworkmod onto my phone. I did no other preperation other than creating a backup through that app on my phone. Then using that app, i downloaded the CyanogenMod 10.1, directly onto my phone. It then gave me the option to wipe data which i chose not to do. It then started the installation of the rom. Everything started off okay and it looked like it installed. When it rebooted it got stuck on the CyanogenMod circle boot and no matter what i try i cannot fix it.
I cannot stress this enough. I am very new to this stuff and am not exactly sure how everything works. It is my mistake and i understand it was the outcome of my stupidity. However, all I am trying to do is fix my phone. When i try to boot into recovery mode (power, home, and up vol) it just restarts still in the boot logo. Whenever i press power, home, and volume down it says "booting a custom rom can harm your device are you sure?" but whether i choose yes or no it is still stuck.
Sorry about all the text, but can somebody please explain to me in the most noob friendly way possible how i can just get my phone in working condition? Thanks for your time
Try booting into recovery this way, in this button pressing order: Vol up + home + power. When your phone vibrates and you see the blue text in the top left corner of the screen, release just the power button.
If this gets you into recovery, you can wipe data, cache and dalvik (under advanced) to see if this clears your issue.
For future reference, don't flash ROMs in rom manager. Only use that app to update or install recovery.
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
crayonslayer said:
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
Click to expand...
Click to collapse
I would suggest to download the CM10 ROM from their thread, and copy it to an external sd card. You can reflash it from the sd card in the recovery menu.
ya, now that you know how to successfully get into recovery, i would flash a rom and gapps again via that route. check out the link in my signature. its got some stuff to look over for a safe and smooth backup & installation
Thanks!
xBeerdroiDx said:
Try booting into recovery this way, in this button pressing order: Vol up + home + power. When your phone vibrates and you see the blue text in the top left corner of the screen, release just the power button.
If this gets you into recovery, you can wipe data, cache and dalvik (under advanced) to see if this clears your issue.
For future reference, don't flash ROMs in rom manager. Only use that app to update or install recovery.
Click to expand...
Click to collapse
Thanks! I couldn't get it to boot into Recovery until I saw your post.....
Thanks. I was stuck in CM11 loop.
Is this also applicable to HTC Desire 816. sorry for crushing, I am just getting frustrated on this matter. tried using my computer to boot from fastboot and tried also pressing the power button while pressing the -Volume. But still on the same cycling LOGO. Please help me if anyone knows how to fix this. Iv also tried to open the back of my unit. but the battery is embedded to the phone.
....
wrong post
how to fix
crayonslayer said:
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
Click to expand...
Click to collapse
maybe you tried to make an advanced data wipe and selected internal storage, dalvic, cache, etc.
what you need to do is put the phone in recovery mode again, select install and then scroll down to find the OS zip that was broke when wiping, after flashing be sucessful reboot system. then turn off the phone again o get it in recovy once more, select install, scroll down but this time you must to install Gapps. to conclude you need to flash OS and Gapps again through recovery mode.
hope this help
I have a Samsung Galaxy S3 SGH-I747 (AT&T) that I updated OTA to 4.1.1 a while back. I just decided to root the phone using Odin3 V3.04 and clockworkmod.tar. I tried using clockworkmod at first but couldn't get the phone to go into CWM recovery mode. It just went into stock recovery instead. Reading further, I was told that I need to flash fixboot.tar first, then clockworkmod.tar, then flash CWM_SuperUser_3.0.7.zip file in recovery mode. When I used odin to flash fixboot.tar and rebooted, it boots the Galaxy S3 logo, at&t chime, then goes black with Amber light. It will not boot fully. I then used Odin to flash clockworkmod.tar, rebooted and it also went to blackscreen.I was then able to go into recovery mode and flash the Superuser zip file and reboot but I'm still getting the black screen. What did the fixboot.tar file do to my phone?? Can I reverse this without flashing a whole new rom? I have search the forum for severalhours now with no luck. Any help would be great.
where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates
xBeerdroiDx said:
where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates
Click to expand...
Click to collapse
I got it from this link - http://rootgalaxys3iii.com/root-at-t-galaxy-s3/
I am aware of the process you mentioned, but it would not work. It just kept going into standard recovery mode instead of custom recovery so I could never root from there. Thats when I came across this link and thought I needed to flash fixboot.tar first as it states. It did work! I was able to flash clockworkmod.tar and then root the phone, but what good does that do now that my phone is hosed at the blackscreen...There were two sites that said to use this fixboot method. I should have known better...
I just read your thred. Looks like my problem was letting the phone reboot. Is there any way to reverse the fixboot.tar I used? Maybe there is a 4.1.1 boot.tar that can put things back as they were?
via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.
xBeerdroiDx said:
via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.
OpusxXx said:
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.
Click to expand...
Click to collapse
Well, since I got no response, I did what you said and deleted everything. I still have the same problem. Phone boots to Samsung logo, does jingle and geos to blackscreen with blue light.
Back to my original question. I used the fixboot.tar and it jacked my phone where it only boots to blackscreen with blue light. Is there a fix for this???
Hi, I've managed to use Odin to install the bell with root image, phone now working with I747MVLUEMK5..downloaded clockworkmod recovery manager and used the att recovery image. Downloaded custom Roms, factory reset the phone, wiped cache and dalvik then installed the custom ROM. It installed properly but when I reboot, it won't turn on, I have to do the download mode to recover it back using the Odin. Tried different custom ROM and I made sure they are for this image MVLUEMK5... But same result, it won't boot up... Help...did I miss a step?
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
audit13 said:
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
Click to expand...
Click to collapse
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Too much work for me. There is no need to have root before installing a custom ROM.
Do this:
Use Odin to install Philz Touch Recovery from here (use the tar version in PDA, do not check auto reboot): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Once it flashes and you see Reset in the windows, pull the battery, disconnect the phone from computer, boot into recovery, wipe cache, dalvik, system, data, flash rom, reboot.
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
snyph3r said:
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
Click to expand...
Click to collapse
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
audit13 said:
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
Click to expand...
Click to collapse
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Most of the 4.3 roms take a long time at the first boot once you flash it (when I flashed S3Rx it took 3 minutes 32 seconds, I timed it because most people say I waited a long time but have no recollection of how much time) it will stay at one of the boot image screens for several minutes then it should vibrate once the blue led should illuminate and then it will finish booting.
If the wait is too much for you turn it on, set it down, walk away, find something to do, 10 minutes later come back, if it hasn't booted now make sure you followed all the instructions correctly and flashed the right stuff for the phone model you have.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
To make sure we are on the same page, is it just stuck at a boot screen or is it getting to a screen turning off and going back to the same screen repeatedly?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Try a different ROM. I use validus and it installed without a problem.
audit13 said:
Try a different ROM. I use validus and it installed without a problem.
Click to expand...
Click to collapse
I was able to flash Validus and And Candykat but could not flash Omni and Beanstalk....flashes with no error but just wont boot up...
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
snyph3r said:
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
Click to expand...
Click to collapse
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
audit13 said:
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
Click to expand...
Click to collapse
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
snyph3r said:
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
Click to expand...
Click to collapse
That is strange. I run validus on mine and WiFi is fine. Calls and data ate fine as well.
snyph3r said:
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Click to expand...
Click to collapse
Just curious... are you going into mounts and storage to format system along with the factory reset and dalvik / cache wipes ??