Related
Ok so i followed the instructions here. http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am all rooted and everything seems to be working until i tried to boot to CWM recovery to create a back up I realized I cannot boot into CMW. I was able do while following the instructions. It seems as thought my CWM flash is not sticking? I even tried to boot to recovery from ROM manger but it still takes me to stock recovery. I tried flashing from Rom Manger, it said it was successful and then I was able to boot to CWM, but after a reboot and trying to get back to it from rom manger again or by holding volume up, home and power I cannot get back to it. Why wont my flash stick.
Please help.
abandroid said:
Ok so i followed the instructions here. http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am all rooted and everything seems to be working until i tried to boot to CWM recovery to create a back up I realized I cannot boot into CMW. I was able do while following the instructions. It seems as thought my CWM flash is not sticking? I even tried to boot to recovery from ROM manger but it still takes me to stock recovery. I tried flashing from Rom Manger, it said it was successful and then I was able to boot to CWM, but after a reboot and trying to get back to it from rom manger again or by holding volume up, home and power I cannot get back to it. Why wont my flash stick.
Please help.
Click to expand...
Click to collapse
First, are you sure you are rooted?
Second, how are you trying to flash CWM?
You need to follow the method posted in the ATT Development forum and use the CWM that was developed for AT&T. I am using the d2att touch version.
id_twin said:
First, are you sure you are rooted?
Second, how are you trying to flash CWM?
Click to expand...
Click to collapse
Yes I am rooted. I am using Odin3 v3.04 to flash RecoveryGalaxyS3USCanada.tar. I remove the battery once it shows it passes. Hold down volume up, power and home button. It will let me boot to CWM recovery this one time but after that once I reboot I have to redo the steps to get back to CWM recovery. I just tried installing recovery-clockwork-touch-5.8.4.6-d2att.zip. It said it was successful but still no go.
Issues fixed! Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
[[SOLVED]]
Alright, so I checked through a few pages on the forums, and I didn't see anyone posting about this issue I am having..
I purchased my S3 a few days ago, and instantly rooted it. I used the Odin3 v3.07 method with "root66_SPR_L10VPBLJ7.7Z" ROM. That went well and fine. Then I tried flashing CWM recovery, and when I booted into recovery, it was still the stock. So I downloaded ROM Mangager and flashed the touch CWM recovery, after it finished, it asked if I wanted to boot into recovery. I agreed. Then the phone restarted, and upon starting, it showed the SAMSUNG logo, and "recovery booting" in the top left corner for about half a second. Then it just stayed on a black screen. I could do nothing after that. I then took the battery out for about 5 minutes, threw it back in, and the phone started. So I tried to manually boot into recovery, and the same issue. Took the battery out again, phone started properly, so I then tried to get into download mode. That worked fine, so I downloaded the CWM recovery on my laptop, and connected the phone through Odin, and flashed CWM onto my phone. Odin said it passed, but I still have the same issue when I try to boot into recovery.
Any ideas on something I'm doing wrong?
It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done
m20120 said:
It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done
Click to expand...
Click to collapse
Correct; and the reason for this is because the updated stock firmware as a script basically that re-flashes stock recovery upon boot if stock isn't detected. The team epic zip removes that. After doing that; I'd recommend flashing the twrp recovery.
Need some Help!
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:
Re: [Q] Recovery Broken, Need Help
shadowcop9514 said:
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:
Click to expand...
Click to collapse
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100
Okay I did some research, and I found online that the Samsung phones need .tar.md5 not .img files for recovery.
http://forum.xda-developers.com/showthread.php?t=1484304
I did not use these directions since I don't run linux, and I wasn't going to download VMWare. Anyways, the way I fixed it, I purchased and downloaded Mobile Odin from the Play store. I put the recovery.img on my external SDcard, then opened the app. Under "recovery" I selected recovery.img and then scrolled down to "Flash" It flashed the recovery.img with no problems, then booted me into recovery. I then flashed mrRobinson_Ashaman.v2.20_signed.zip so I could uninstall some bloatware.
That last part was mostly for me, until I find a ROM I like.
CNexus said:
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100
Click to expand...
Click to collapse
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.
shadowcop9514 said:
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.
Click to expand...
Click to collapse
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100
CNexus said:
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100
Click to expand...
Click to collapse
Ok, where do I find that ?
shadowcop9514 said:
Ok, where do I find that ?
Click to expand...
Click to collapse
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100
CNexus said:
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100
Click to expand...
Click to collapse
Ok thanks!
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
ovimunt said:
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
Click to expand...
Click to collapse
May I ask what variant you are using? GT-i9195?
Then please boot your phone into download mode, this can be done by first switching of your phone completely then holding the power button, home button and volume down button until the download screen appears where you press continue. Once you have done that connect your phone using the usb cable and make sure all drivers have been installed! Once the drivers are installed start up Odin uncheck the f.rest time box and click the AP section and then select the recovery file provided by Sir Arco in the root thread.
If you need more help please ask, If it worked then still reply
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Whosat said:
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Click to expand...
Click to collapse
Thanks for the response. Yeah, I kind of realized that's what's happening. I've managed to boot into the custom recovery right after the flash and did what I had to do in there, but then after I reboot the phone again, the custom recovery is gone. Is there a way to stop stock recovery being reflashed automatically?
Also, if I want to install a custom kernel, how can I backup the current one so that I can restore it at a later date if I need to? I know how to do this on HTC phones but it all seems to be a bit different on Samsung and I don't want to mess up anything.
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Whosat said:
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Click to expand...
Click to collapse
Umm... yeah, I think it did ask but I just accidentally pressed no before reading what it said... So I guess I'll just have to flash the recovery again and then answer yes to that question.
Thanks
Yes that would be the correct way to do it.
Hope all goes well!
I installed teh wrong TWRP so i tried to install a different version via odin - but now my phone just goes to teh samsung screen and doesnt boot -
I tried to go throigh this guide http://forum.xda-developers.com/showthread.php?t=2024207 but
but it didnt work I am on the n17100 which is probably why
atm just wanna get back to my stock rom -
can i install a different twrp over this one via odin ? or should I not have done that
essentially I need to install the n7100 twrp then ill be okay - but not sure how from this loop pls help
benben333 said:
I installed teh wrong TWRP so i tried to install a different version via odin - but now my phone just goes to teh samsung screen and doesnt boot -
I tried to go throigh this guide http://forum.xda-developers.com/showthread.php?t=2024207 but
but it didnt work I am on the n17100 which is probably why
atm just wanna get back to my stock rom -
can i install a different twrp over this one via odin ? or should I not have done that
essentially I need to install the n7100 twrp then ill be okay - but not sure how from this loop pls help
Click to expand...
Click to collapse
Install and try Philz Touch recovery.
Installation link: http://forum.xda-developers.com/showthread.php?t=2201860
Instrucions link: http://forum.xda-developers.com/showthread.php?t=2028103
similar issue
Hi, I don't know if I should make a separate post but I have a similar problem.
My Note 2 is stuck on the "Samsung GALAXY Note II GT-N7100" screen at boot. Only by flashing a stock ROM through ODIN can this be fixed. When I try to install a custom recovery and ROM on it, it gets stuck again at that screen.
Can anyone help me?
chinoboy said:
Hi, I don't know if I should make a separate post but I have a similar problem.
My Note 2 is stuck on the "Samsung GALAXY Note II GT-N7100" screen at boot. Only by flashing a stock ROM through ODIN can this be fixed. When I try to install a custom recovery and ROM on it, it gets stuck again at that screen.
Can anyone help me?
Click to expand...
Click to collapse
Hold down power button for 5~10 secs. after it stucks on boot logo, and try if it reboots normally.
Or press Vol. up + Menu key and then power key for 5~10 secs it'd boot your phone into recovery mode.
m.b.jikre said:
Hold down power button for 5~10 secs. after it stucks on boot logo, and try if it reboots normally.
Or press Vol. up + Menu key and then power key for 5~10 secs it'd boot your phone into recovery mode.
Click to expand...
Click to collapse
Please reread my post. It's a persistent issue. Rebooting doesn't do anything. Recovery doesn't do anything.
What you willing to do? so I can guide you through the right way.
Sent from my GT-N7100 using XDA Premium 4 mobile app
m.b.jikre said:
What you willing to do? so I can guide you through the right way.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was wondering if anyone had a similar issue to mine and how to flash a custom rom after that. The only way I've found for the phone to work was to use ODIN to flash the stock firmware on it. After that, if I try to install a custom ROM, it goes back to the SAMSUNG screen at boot.
So if you, jikre, know how to fix this issue, I'm all ears.
This method has fixed numerous problems. Might be worth a try.
http://forum.xda-developers.com/showthread.php?t=2700479
chinoboy said:
I was wondering if anyone had a similar issue to mine and how to flash a custom rom after that. The only way I've found for the phone to work was to use ODIN to flash the stock firmware on it. After that, if I try to install a custom ROM, it goes back to the SAMSUNG screen at boot.
So if you, jikre, know how to fix this issue, I'm all ears.
Click to expand...
Click to collapse
benben333 said:
I installed teh wrong TWRP so i tried to install a different version via odin - but now my phone just goes to teh samsung screen and doesnt boot -
I tried to go throigh this guide http://forum.xda-developers.com/showthread.php?t=2024207 but
but it didnt work I am on the n17100 which is probably why
atm just wanna get back to my stock rom -
can i install a different twrp over this one via odin ? or should I not have done that
essentially I need to install the n7100 twrp then ill be okay - but not sure how from this loop pls help
Click to expand...
Click to collapse
Download a stock firmware and use ODIN v3.09 to flash it onto your phone. It should work.
http://forum.xda-developers.com/showthread.php?t=2499794
chinoboy said:
I was wondering if anyone had a similar issue to mine and how to flash a custom rom after that. The only way I've found for the phone to work was to use ODIN to flash the stock firmware on it. After that, if I try to install a custom ROM, it goes back to the SAMSUNG screen at boot.
So if you, jikre, know how to fix this issue, I'm all ears.
Click to expand...
Click to collapse
>>"Hold down power button for 5~10 secs. after it stucks on boot logo, and try if it reboots normally.
Or press Vol. up + Menu key and then power key for 5~10 secs it'd boot your phone into recovery mode."<<
If you wanted to install custom rom, if so, you can't flash it through Odin (Only for flashing for Official stuff ). Download a custom rom, whichever you wanted(Copy that rom on externel SD), reboot into recovery and by selecting 'wipe data and cache' >> 'clean to install a new rom'.
Then again coming to main menu select Install zip from sd, and redirect it to rom file which you've downloaded. In any custom rom like DN3, SenSonic they've full procedure for flashing the rom, just stick to it to install it perfectly...
Any quest?
m.b.jikre said:
>>"Hold down power button for 5~10 secs. after it stucks on boot logo, and try if it reboots normally.
Or press Vol. up + Menu key and then power key for 5~10 secs it'd boot your phone into recovery mode."<<
If you wanted to install custom rom, if so, you can't flash it through Odin (Only for flashing for Official stuff ). Download a custom rom, whichever you wanted(Copy that rom on externel SD), reboot into recovery and by selecting 'wipe data and cache' >> 'clean to install a new rom'.
Then again coming to main menu select Install zip from sd, and redirect it to rom file which you've downloaded. In any custom rom like DN3, SenSonic they've full procedure for flashing the rom, just stick to it to install it perfectly...
Any quest?
Click to expand...
Click to collapse
Jikre, I've already mentioned several times I know how to flash a recovery and custom ROM. I'm saying that the phone stops working after I try to do so.
chinoboy said:
Jikre, I've already mentioned several times I know how to flash a recovery and custom ROM. I'm saying that the phone stops working after I try to do so.
Click to expand...
Click to collapse
Got you man, i'm just saying that this problem of yours is come with the Andro v4.3 and knox bootloader. First if anyone tried to install custom recovery it get stuck on bootlogo, but that is an another factor you can reboot it manually into recovery menu.
On the end when you attempt to reboot (from recovery) it asks you to disable stock recovery and you reboot your phone normally, that's it!
Sent from my GT-N7100 using XDA Premium 4 mobile app
Ah okay, that makes sense. Unfortunately that doesn't apply to my situation. I had already been on a 4.3 custom rom for several months when the phone just died like that. As of right now, I can only get it to work if I flash a stock ROM on it.
chinoboy said:
Ah okay, that makes sense. Unfortunately that doesn't apply to my situation. I had already been on a 4.3 custom rom for several months when the phone just died like that. As of right now, I can only get it to work if I flash a stock ROM on it.
Click to expand...
Click to collapse
Just try to wipe your phone from custom recovery (Not 'Clean Flash' & It may work). Have you tried to disable to recovery at end when it asks?
m.b.jikre said:
Just try to wipe your phone from custom recovery (Not 'Clean Flash' & It may work). Have you tried to disable to recovery at end when it asks?
Click to expand...
Click to collapse
I have used both CWM and TWRP recoveries. Complete wipe every time before installing a new ROM. Still doesn't work. Only wiping and installing stock firmware through ODIN would the phone start.
chinoboy said:
I have used both CWM and TWRP recoveries. Complete wipe every time before installing a new ROM. Still doesn't work. Only wiping and installing stock firmware through ODIN would the phone start.
Click to expand...
Click to collapse
Which ROM you tried to flash? Can you upload a pic of PC Odin, showing how you flash the phone. Or just enlist the options.
Try flashing your phone by philz touch ('Wipe Data & Cache >> Clean to Install a New ROM" << Maybe your previous installation troubling to set a new one, If persist again try this method):
Instruction: http://forum.xda-developers.com/showthread.php?t=2028103
Downloads: http://goo.im/devs/philz_touch/CWM_Advanced_Edition
For flshing through PC Odin: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100/philz_touch_6.25.0-n7100.tar.md5 (For N7100 Only).
freezed on boot logog
i have tried all the things like wipe the data go to recovery and all but its still stuck