Related
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Have you tried twrp?
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see
+1 for twrp
athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.
aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help
xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.
athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks
xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?
RyanGN2 said:
I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?
Click to expand...
Click to collapse
Did your restore boot?
Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.
RyanGN2 said:
Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.
Click to expand...
Click to collapse
Try this.
From Zen Arcade's [ROM][4.3][Dec-2013] AT&T I317-UCUBMK6/MJ4 *Stock* Rooted Odex/De-Odex/Odin thread
After flashing one of the stock packages, you may need to flash the MK6 tz.img and optionally the param.bin from the MJ4 leak. The zip below contains two Odin packages.
Try flashing the tz only package first (in Odin), then the tz+param package to see if this gets your phone to boot. You may also need to boot recovery and do a factory reset.
AT&T i317 ODIN 4.3 UCUBMK6 TZ.IMG & UCUBMJ4 (Leak) PARAM.BIN (AT&T Note 2 ONLY)
I317UCUBMK6-TZ-PARAM.zip
http://d-h.st/CDK
- Run Odin3 v3.07.exe
Download Link http://www.mediafire.com/download/77...x2/Odin307.zip
Unzip to where you can run it.
- Put your Note 2 in Download Mode
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Plug into a RELIABLE usb port and a RELIABLE usb cable (preferably the white Samsung cable) and wait for it to show up in Odin (COM5 or something like that)
Unzip the I317UCUBMK6-TZ-PARAM.zip file you downloaded
- Click the PDA slot in Odin and locate the I317UCUBMK6-TZ.tar.md5 that you downloaded and unzipped
The filename that goes into the PDA Slot is I317UCUBMK6-TZ.tar.md5
MAKE SURE IN THE OPTION AREA ONLY AUTO REBOOT AND F.RESET TIME ARE CHECKED!!!
- Click START and wait. It will complete and reboot.
Try flashing the tz only package first. See if it boots.
If not, repeat the above steps using I317UCUBMK6-TZ-PARAM.tar.md5.
You may also need to boot recovery and do a factory reset. Do this after second ODIN flash.
If your phone still hangs after second flash, pull the battery, and boot into recovery mode.Just hold down UP volume button and power button until recovery screen pops up.
Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.
RyanGN2 said:
Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.
Click to expand...
Click to collapse
Since you tried everything above and it didn't HELP..
I'm wondering have you tired the kies emergency firmware recover. I taught I screwed my phone up flashing a Odin file. Then the phone was stuck not doing anything. Couldn't boot up, nada.
But after running it thru that set up, the phone was back to completely stock...
Look HERE»»»http://goo.gl/J0P1ZX
Not sure if it'll help but worth a try right. It helped me when I was in need.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.
RyanGN2 said:
I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.
Click to expand...
Click to collapse
I'm beyond lost of what you have done and where you're at.
Appears after doing the stuff in my post #4, your phone is booting past ATT screen ???? Understand it booted into OMNI, but at least it booted.
That's all I was trying to do was to get it past the ATT screen.
If I would have know you wanted to go back to stock 4.3, you could have done this....
http://forum.xda-developers.com/showthread.php?t=2618447
You may still have too, if the OTA does not work from the CWM stock 4.1.2 ROM.
Whenever you flash ROMs rule of thumb is back up apps and anything else you want to save, with Titanium Backup or MyBackup, etc. etc. Then restore apps after new ROM is installed.
Doing a wipe/factory rest prevents residual crap from the previous ROM leftover.
Unless its an update to a ROM you already have running, and the OP says no worries, dirty flash.
69%+ of problems with ROM flashes is the flasher didn't follow instructions or half-a$$ed it and didn't wipe or factory reset.
I've been guilty of that also, so not trying to be combative or accusatory.
Good luck with OTA.
When I did the steps in post #4 it never did anything it stayed in omnirom, which I have not had a problem getting to boot. It doesn't boot when I restore from my backup created before I installed Omni with CWM. I don't like Omni and I am tired of everything root. I'm a heavy jail breaker and thought I could do this however its more learning than I wanted and want to be done with root entirely. The OTA update did fail. Should I still use the 4.3 rom above or is there something else I should that will also remove root? I did backup apps with titanium and I also backed up everything with Kies.
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Tan9890 said:
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Click to expand...
Click to collapse
Knox trigger can't be reversed.
Of course, it is a bootloader issue. Follow the procedure and it should work out well for you.
1. Use stock recovery to wipe cache and factory reset.
2. Don't use cf-auto root.
3. Download Philz recovery latest version and supersu zip file. (For Note 2 )
4. Flash Philz. Uncheck auto reboot option in ODIN. Once you get pass message, unplug. Don't start your phone yet. Boot directly into recovery.
5. Install supersu zip file
6. Reboot to check if you are rooted.
7. DN3 5.5 has given me a headache. But it must be something ---- looking at the number of people using it.
8. I prefer Dr. Ketan's V12 Touchwiz ROM.
With Aroma installer, it is almost impossible to go wrong. Support is amazing. Doc himself answers all queries as fast as he can. But choice is yours.
Press thumps up if you found this suggestion helpful.
Link to all the files: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Sent from my GT-N7100 using Tapatalk
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Tan9890 said:
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Click to expand...
Click to collapse
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Tan9890 said:
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Click to expand...
Click to collapse
Very weird. Never heard of such a thing. Btw, which recovery you are using? TWRP or CWM. Also, chk if the version is latest. The latest versions are fixed for these very issues.
Probably, flashing N7100XXUFNI1 out of the box should solve your problem.
Beyond that I don't have answers.
Sent from my GT-N7100 using Tapatalk
Snippet taken from: http://mark.candleshoreblog.com/2013/06/13/tip-steps-to-prevent-clockwork-or-any-custom-recovery-from-being-overwritten-by-factory-stock-roms-at-android-system-reboot/:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run. All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again. Do the following:
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.
That’s all there is to it.
So today i was gonna try to install a custom rom, more specifically Cyanogenmod 10.2. for my Tmobile Galaxy S3 (SGH-T999). When i went to boot into recovery, i saw the screen that is displayed right before you enter recovery, but then after that it just stayed on a black screen. I took out the battery for a few seconds and powered on my phone. Then i tried entering recovery directly through ROM Manager. I got the same black screen, but now if i try to power on my phone without entering CWM, it automatically tries to go into CWM recovery regardless. . I tried a few battery pulls and nothing has worked yet. Luckily i am able to enter download mode so i can flash the stock rom via odin and then restore my backup from the SD card later. I just wanted to know if there is a simpler fix than this so i don't have to go through the trouble of flashing stock rom again. Btw i am still on the stock rom running android 4.3 jelly bean.
Try flashing custom recovery again and make sure it's the newest.
serio22 said:
Try flashing custom recovery again and make sure it's the newest.
Click to expand...
Click to collapse
The problem was i couldn't boot up my phone in the first place because it would automatically go into recovery. I actually fixed it by going it to download mode and then pressing the down button which rebooted the phone properly. I used rom toolbox and now im just gonna stick with TWRP.
RootNoob1299 said:
The problem was i couldn't boot up my phone in the first place because it would automatically go into recovery. I actually fixed it by going it to download mode and then pressing the down button which rebooted the phone properly. I used rom toolbox and now im just gonna stick with TWRP.
Click to expand...
Click to collapse
That's what I meant, you can flash recovery in download mode but as long as you got it working its all good. And yes I highly suggest using twrp over cwm
Thanks anyway man! TWR FTW!!