Related
Since USB jig doesn't work exactly the same way on our SGR compared to SGS II, I recommend an alternative solution.
How to make jig work?
1) Entering the Download mode:
pull the battery out -> plug jig -> insert the battery
or
turn off device -> plug jig -> press power button
2) Resetting the download counter:
Enter DM using one of those two methods above. Once you're there just remove jig, plug usb-cable and install your stock kernel (just to reset the counter) or firmware (in case you want to reset the counter and unroot simultaneously). Right after installation process is started you should see the green text: Success to erasing the record of custom OS! (You can see it on attached picture.)
Remember:
1) This method works only on DM Protocol Version 2.0, for those of you that have v. 2.1 USB jig won't work at all. In your case procedure is more complex, please visit this thread:http://forum.xda-developers.com/showthread.php?t=1528256
2)You don't have to flash the whole fw-package to reset the counter. It's ok with just stock kernel (only the .tar file though and remember that replacing the kernel WON'T UNROOT your device. To unroot and clear the counter you should reinstall your stock firmware!)
I attached some stock kernels. Please don't ask me to add more. First of all I don't have them and second... you can easily get your own by replacing boot.img from one of the tar-packages below with the original one from your preferred firmware. (USE Total Commander, don't extract packages, simply open them with [ENTER] and copy file from one package to another (F5))
I am trying the second method (insert jig and press power botton), not working. After flashing custom ROM (kernel), it simply reboots as expected (should I disable reboot option in ODIN?).
Would appreciate if someone suggests how to do it right.
Excuse me, but can you write step by step what you did. You cannot enter Download Mode? Or you entered DM and flashed FW but it didn't reset your counter?
Make sure that USB-debugging is checked.
1)enter DM with USB jig
2)remove jig
3)plug usb cable and flash STOCK firmware
It has always worked for me that way.
(Maybe I misunderstood you but...why should you disable auto-reboot option in Odin. Flashing custom kernels increases counter and it has nothing to do with the method I posted above. IT's actually totally opposite. This method is only useful if you just want to erase flashing record, but it won't let you have insecure kernel and 0 on counter.)
m.kochan10 said:
Excuse me, but can you write step by step what you did. You cannot enter Download Mode? Or you entered DM and flashed FW but it didn't reset your counter?
Make sure that USB-debugging is checked.
1)enter DM with USB jig
2)remove jig
3)plug usb cable and flash STOCK firmware
It has always worked for me that way.
(Maybe I misunderstood you but...why should you disable auto-reboot option in Odin. Flashing custom kernels increases counter and it has nothing to do with the method I posted above. IT's actually totally opposite. This method is only useful if you just want to erase flashing record, but it won't let you have insecure kernel and 0 on counter.)
Click to expand...
Click to collapse
I put USB jig in, pressed power button, phone went to download mode.
Tried uploading custom kernel, it wasn't doing the trick. However as you suggested, installing stock ROM worked! But thats quite weird as in SGS2 it works just by inserting the jig.
I agree it's weird
Hello.
I don't want to be off topic but, I would like to ask you when you flashed 2.3.6 from 2.3.4 or 2.3.5 , did your download counter increase?
Of course not it never increases when you flash stock firmware. Only if you flash custom software (with the exception of custom recovery like cwm) via Odin e.g. insecure kernels, custom roms etc.
Sent from my GT-I9103 using XDA App
hey kochan could you shed the goodie on where you get the stock 2.3.4 rom? i tried legion's stock KK5 without getting the magic green words on my screen after the the install kicked start... *frustrated*
I'm flashed 2.3.6 and this tutorial works just fine.
I did the same two days ago with 2.3.6, and everything worked as it was supposed to again. So you must check the jig.
okay.. i got a new jig from the guy, USB debugging checked, tried both methods with ZSKK5 on PDA flashed without luck... argh this is pissing me off what have I done wrong!!!
s4sixty, kochan, did you both flash the stock rom off a custom rom to clear the counter? i have tried dozens time from stock to stock. the only thing i suspect that went wrong was when i enter download mode after jigged, i m always coming from stock-to-stock flash. would that be the case?
guess i m luck out. i m trying different cable to see whether things get better... argh
Tell me: how many custom flashings do you actually have on the counter? What's the number?
i got three bro... would that be the case that i m flash-jigging from a stock to stock rom that's why i m luck out? i m trying different cable.
Ok, number is actually out of relevance (if it's different than 0). Maybe it has something to do with the cable. I thought that flashing FW rewrites bootloader (because it's inside the .tar package). So it shouldn't have major significance here since u used both 2.3.4 and 2.3.6.
You know the only thing that has to be done to succeed is to boot into Download Mode with the help of USB jig (NOT WITH 3buttons combination), then remove jig (DO NOT RESTART) and plug in usb cable directly, then just chose your firmware and press start in Odin. (I always close Kies and all processes related to it before I started any operation in Odin) It has always worked on my device. I have no idea why it doesn't work for you.
Moodaleon said:
s4sixty, kochan, did you both flash the stock rom off a custom rom to clear the counter? i have tried dozens time from stock to stock. the only thing i suspect that went wrong was when i enter download mode after jigged, i m always coming from stock-to-stock flash. would that be the case?
Click to expand...
Click to collapse
It doesn't matter dude when custom roms are installed via CWM and not Odin. I have almost always reflashed from stock to stock. But maybe...I'm not sure but it doesn't harm to start....try to flash stock again, then flash custom kernel, and then turn off mobile, insert usb jig, press and hold power button, u should boot directly into DM, then remove jig -> plug usb cable and ref lash directly. If this doesn't work, then try to find somebody with galaxy R and try the methods i posted on other handset just to make sure if it's hw-related.
yea im totally beat from jigging my SGR these couple days. ah well i guess it is time to fall to the dark side and tune the phone to a no-beater! thanks for the coaching kochan
m.kochan10 said:
Enter DM using one of those two methods above. Once you're there just remove jig, plug usb-cable and install your firmware (I've tested both 2.3.4 and 2.3.6). Right after installation process is started you should see the green text: Success to erasing the record of custom OS! (You can see it on attached picture.)
Click to expand...
Click to collapse
I've tested with 2.3.5 and works perfectly.
Best regards,
Siwy ;-)
Hi m.kochan10, can I know more about using the USB jig?
As you mentioned, after booting up using the jig, I need to unplug it and then plugin my USB cable to flash stock ROM thru Odin3. By means of stock ROM, you mean only the factoryfs.img? or the whole things including boot.img, cache.img, factoryfs.img, hidden.img, modem.bin & recovery.img?
Thanks a lot
ardatdat said:
Hi m.kochan10, can I know more about using the USB jig?
As you mentioned, after booting up using the jig, I need to unplug it and then plugin my USB cable to flash stock ROM thru Odin3.
Click to expand...
Click to collapse
Exactly!
ardatdat said:
By means of stock ROM, you mean only the factoryfs.img? or the whole things including boot.img, cache.img, factoryfs.img, hidden.img, modem.bin & recovery.img?
Thanks a lot
Click to expand...
Click to collapse
Ardatdat I'm sorry but in order to reset the counter I have always flashed the whole tar-package that included all those parts you mentioned.
Though...it's worth to test since counter gets erased immediately after installation process is started, so perhaps it can be concluded that...the first part that is being installed is responsible for resetting the number of custom flashings.
I'll try to test it today.
EDIT: IT's boot.img that makes a difference So Ardatdat...take your old .tar file and simply replace your kernel with the stock one, run Odin3 and voila No need to flash the whole FW!
I am thinking of getting an USB Jig and keeping it, just in case (rather than ordering one when needed and waiting for it, till I get it ).
I went through the FAQ's for USB Jigs in this forum. I got an SGR, and from that FAQ what USB Jig is shouldnt be specific for SGS II or SGR. Can you please confirm this before I get one as there were only couple of sellers with I9103 mentioned and most of them had mentioned I9100 specifically.
Thanks.
USB Jig is the same for every samsung device! Just the way it works, differs. On SGS it boots into download mode, removes the triangle and resets the counter right after you inserted it to your phone. On SGR it does each of those things above but not equally automatically. It works and it works effectively, but we have to insert jig, press power button and fe. reflash the stock kernel to get the same effect. No need to worry.
PS. It's so cheap so don't hesitate to buy it!
Hi,
I am tried a lot to flash stock ROM to my galaxy R but everytime it failed. I am using Windows 7 and odin. Everytime odin start writing the rom but it radomly freezes when screen autolocks or display goes off. Why this is happeing? Why can't in recovery mode screen keep itself active? I am unable to stop phone display going off. Please help me to flash my mobile as its currently unusable.
Odin log shows then removed when display goes off.
recovery mode? It has nothing to do with flashing via Odin.
To install your FW u must enter the download mode: volume down + home + power
Anyway if your screen goes off itself in recovery mode or download mode then it's an abnormal behavior that can rather indicate HW issue.
oh sorry if that is wrong term I used. I thought to flash using odin I need to go recovery mode using vol up+ power ON + Menu key combination.
What I need is just to have working phone with stock 2.3.5 ROM. Using odin it fails sometimes say 30% or 50% or even 70%. The same ROM I have flashed successfully but always touching the finger on display to active the phone screen. But same is not working now.
Reason I flashed or flashing is that my phone started radomly restarting and if I off it and wait for 2-3 hrs then it will start. So I decided to flash my phone.
Download mode doesn't auto-lock. Are you sure ur in download mode?
I had exactly the same problem of odin restart in download mode. Removing the SD card and SIM card and try flashing it.
took fr service as phone restarted often and they change the PBA(Printed board assembly) for me.
Yes, after some radom time and before rom writing finishes, screen locks(looses display so odin removes that device) and writing fails.
I have tried more that 15 times and yes all those tried without SIM and SD card.
I purchases this 4 months back only but as I have flashed it and phone is not working did I loose the warranty?
Try again with this steps
1. Download stock rom package (use checkfus)
2. Turn off ur phone now hold vol down key+home key+powerkey
3. Ur phone will boot in download mode u will see warning, press vol up to continue
4. Now open odin on ur pc, connect phone usind cable and wait till box turns yellow noe chose downloaded stock rom package in pda
5. Check auto reboot, reset time and make sure re partion is not checked and click start
6. Wait till process complet u will see progress bar on phone and odin
Sent from my GT-I9103 using Tapatalk
step by step guide for flashing Stock ROM with ODIN,
http://forum.xda-developers.com/showthread.php?t=1406664
following the steps which are mentioned in the above link if you are still facing the problem them there may be some problem with ".TAR" file better download it again and try flashing.
xlm13x,
My phone is not working and saying "firmware upgrade encountered an issue. please select recovery mode in kies". how can I re-download stock ROM?
mj.vikram,
i follows the exact same stpes from the same thread. still no luck.
can I claim the warranty as I just want to flash original rom again to see if restart problem resolves and it got failed?
Is there any limit to flash a firmware? while searching on google got some page saying there is some taint-firmware counter? what is that?
Dude....don't try to turn your device on i regular way, but press combination: volume down+home+power simultaneously. You must be able to enter the DM! (U can try removing battery and putting it back)
Recovery mode in Kies has nothing to do with rm on your phone. I really don't think Kies will help you.
There is no issue in going to download mode for me. Just its not able to keep on itself till the firmware writing completes. So now I think it looks h/w issue to me. What worries me is how to get it in normal working phone and give it to service center.
panu123 said:
There is no issue in going to download mode for me. Just its not able to keep on itself till the firmware writing completes. So now I think it looks h/w issue to me. What worries me is how to get it in normal working phone and give it to service center.
Click to expand...
Click to collapse
Ok now i got your point, phone is coming out of Download mode while flashing the stock ROM.... am i correct.
if this is the problem then there may be some issue with H/W..... if you haven't rooted your mobile and you are on stock ROM then take it to Service center...
Have u flashed any custom rom on ur phone? Is ur download counter has been increased?
Sent from my GT-I9103 using xda premium
Just take it to the service center. They won't be able to see if you rooted your device or not anyway in such case IMO. The phone is unable to boot, and reflash either. IT's clearly a HW issue. We have no power to affect download or recovery mode to be honest. I really don't think there's anybody on this forum that can help you fix DM.
what happens if sufficient battery is not there will it take power from system.
eg: if battery is only 5 % and we connected it in DM what will happen, will it continue or it will be switched off.
Thanks all for the replies. Let me confirm you all once again. My phone was using stock ROM. Never rooted it(not even knowing how to do that) Just frustrating restart issue and some google search conlcuded as I should flash stock rom.
so, I am doing that I even got success in flashing my phone after some attempts. Then for two days it worked fine. But again same problem started and I become impatient and tried to flash stock rom and it failed. Now my phone is nowhere so I can't check anything on my phone. How can I know download counter in this situation?
I heard service center need phone with stock rom installed and working and then they will take warranty claim. Is that the case?
Worried what to do with my phone now? it looks h/w issue to me also now that is why once flashing starts after some time it fails before reaching 100%.
no worries just take it to Samsung Service Center and tell them that your phone got switched off and its not starting, they will ask you to provide invoice xerox copy and flash the Firmware and give it back to you...
as you haven't tried rooting or installing Custom FW, so no need think of the Download counter.
toberabl century
Yes. I now understand what download counter is and my phone is already showing it as "NO" so its not custom ROM flashed. Hope this will be enough for me to claim warraty for my non-OS phone.
panu123 said:
Yes. I now understand what download counter is and my phone is already showing it as "NO" so its not custom ROM flashed. Hope this will be enough for me to claim warraty for my non-OS phone.
Click to expand...
Click to collapse
Give ur phone in service they will fix it for free, u havent rooted ur phone and also ur counter is zero so no need to worry about warranty void, do update what happens
Sent from my GT-I9103 using xda premium
Dude, dont tell them anything about you trying to flash stock fw. Just tell that the phone is not staying on. That should do.
It definitely seems like a hardware issue to me, so probably even they wont be able to flash a firmware and so they will start working on the hardware aspect. Just dont let them know that u tried reflashing the firmware or such coz they might try to void the warranty saying you fiddled with the phone.
Keep us updated.
I had exactly same problem as you, random restarts. It will become more frequent and troublesome if you keep the problem.
Give it to service center as your counter is 0. Your phone surely needs main board change.
I was attempting to get an insecure kernel onto my phone (I was really not very smart about it, barely knew anything about rooting and went ahead and did it anyway) And something went wrong- Odin spat out an error saying 0 complete/1 failed and when my phone wouldn't reboot, I took out the battery because I didn't want screen-burn overnight (which now I know was a retarded thing to do).
Whenever the phone boots It gets this message; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". And whenever I try to access the phone through odin, i get another error- it attempts to connect to the phone for like 15 mins then says "Device not responding- to resolve the issue, please reboot the device". This of course gives no yield, so I tried something else- I made a jig with 301k ohms of resistance, and tried using that. The only thing that this changes is when the phone reboots, instead of getting
Code:
ODIN mode
PRODUCT NAME: SGH-I727
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
I get
Code:
FACTORY MODE
PRODUCT NAME: SGH-I727
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
Any tips/pointers on what I could do? I really want to be able to use my phone again (for obvious reasons)
mr. mustache said:
I was attempting to get an insecure kernel onto my phone (I was really not very smart about it, barely knew anything about rooting and went ahead and did it anyway) And something went wrong- Odin spat out an error saying 0 complete/1 failed and when my phone wouldn't reboot, I took out the battery because I didn't want screen-burn overnight (which now I know was a retarded thing to do).
Whenever the phone boots It gets this message; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". And whenever I try to access the phone through odin, i get another error- it attempts to connect to the phone for like 15 mins then says "Device not responding- to resolve the issue, please reboot the device". This of course gives no yield, so I tried something else- I made a jig with 301k ohms of resistance, and tried using that. The only thing that this changes is when the phone reboots, instead of getting
Code:
ODIN mode
PRODUCT NAME: SGH-I727
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
I get
Code:
FACTORY MODE
PRODUCT NAME: SGH-I727
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
Any tips/pointers on what I could do? I really want to be able to use my phone again (for obvious reasons)
Click to expand...
Click to collapse
go to the the second link in my sig to flash a stock ics, then read the last part of my sig.
vincom said:
go to the the second link in my sig to flash a stock ics, then read the last part of my sig.
Click to expand...
Click to collapse
That's the problem- the phone never enters download mode. It just says "developer mode" in the top left, odin won't work on it at all.
mr. mustache said:
That's the problem- the phone never enters download mode. It just says "developer mode" in the top left, odin won't work on it at all.
Click to expand...
Click to collapse
which kernel were u trying to flash, was it for our phone
how did u get into dl mode
edit: could be driver issues, theres a odin troubleshooting section in the second link in my sig
vincom said:
go to the the second link in my sig to flash a stock ics, then read the last part of my sig.
Click to expand...
Click to collapse
Just tried it for a second time and it worked thanks so much
Now the phone boots up, but crashes immediately. I know this is because of the partial kernel I have installed- How would I be able to get the kernel on to the device if I can't access it's internal storage?
mr. mustache said:
Just tried it for a second time and it worked thanks so much
Now the phone boots up, but crashes immediately. I know this is because of the partial kernel I have installed- How would I be able to get the kernel on to the device if I can't access it's internal storage?
Click to expand...
Click to collapse
did you flash the kernel again, if u did which one is it
do a factory reset and wipe from recovery
mr. mustache said:
Just tried it for a second time and it worked thanks so much
Now the phone boots up, but crashes immediately. I know this is because of the partial kernel I have installed- How would I be able to get the kernel on to the device if I can't access it's internal storage?
Click to expand...
Click to collapse
ODIN one click or download UCLF6 from sammobile and flash in Odin.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I may be wrong but don't you flash the custom recovery in Odin and then flash the kernel from within the recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium
I got my GNP 12.2 (SM-P900) a few weeks ago and just tried to root it using Odin and download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
However it paused at cache.img and after 10 minutes or so it just failed.
I've tried it a few times, but same thing, and on start up all I get is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried Kies 3 and Kies 2.6 but they both say my device is not supported, even if I try to go into Tools and do it it says the model name is incorrect and doesn't even give me an option to enter the serial number :-\
I looked around for a stock ROM but the closest I could find was the P901 and P905 (But I am the P900)
I don't really know what to do, so any advice would be much appreciated :angel:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
jns20 said:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
Click to expand...
Click to collapse
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
ChampagneFerret said:
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
Click to expand...
Click to collapse
IIRC you need to reflash recovery and you should be able to boot up again.
muzzy996 said:
IIRC you need to reflash recovery and you should be able to boot up again.
Click to expand...
Click to collapse
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
ChampagneFerret said:
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
Click to expand...
Click to collapse
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
icem237 said:
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
Click to expand...
Click to collapse
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
ChampagneFerret said:
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
Did you use Odin 3.0.7 or 3.0.9? 3.0.7 is included with CF and MUST be used even though 3.0.9 is the latest. If odin was already installed on your PC and you used 3.0.9 bad things are going to happen.
ChampagneFerret said:
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
icem237 said:
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
Click to expand...
Click to collapse
I tried both as well, and that's exactly what happened to me. During the process, my screen went all screwy and that's when it told me the process had failed.
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Flash Stock Recovery
davschm said:
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Click to expand...
Click to collapse
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Russbad said:
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Click to expand...
Click to collapse
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
davschm said:
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
Click to expand...
Click to collapse
Stock recovery is what your device originally comes with. CWM recovery is a modified version of that and it allows you more functionality.
When I messed up my update and root, my device would not boot up at all. I flashed the stock recovery and that enabled me to successfully root. No data was lost, no factory reset was needed and all my apps and settings were unchanged.
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
bioncorp said:
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
Click to expand...
Click to collapse
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Russbad said:
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Click to expand...
Click to collapse
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
bioncorp said:
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
Click to expand...
Click to collapse
I finally got mine rooted by simply trying over and over. I re-downloaded the CF flash tool and used 7zip to extract it several times, and used a different usb port at least once. Not that I really thought there was a problem with my extraction or the download or my USB port. But from what i have seen posted, you just have to try it 3 or 4 (maybe even 10) times until you get lucky and it works.
I did at one point try to recover my Note 12.2 with the "recovery.img" instead of flashing it with a full factory re-image (which causes data loss) but that didn't work for me ether. But I later had good luck with using Odin 3.09 to flash TWRP. So at least I now have a good custom recovery and backup tool.
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
ChampagneFerret said:
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
Click to expand...
Click to collapse
FINALLY! :laugh: I got it to root!
I ended up using a different computer in the end and used Kies 2.6 for the drivers. I tried this a total of maybe 8 or 9 times, and it worked on the second attempt on the second attempt.
For the record, I left "md5" in the file when rooting, and that's when it worked.
So it's my 4th day on bootloop and i still can't figure out how to turn my phone on again.
I know how to push files to TWRP. I have Odin ready. I have 2-3 different stock ROM available.
Flashing stock rom doesn't help - even if i put Nand erase all.
Kies or Smart Switch doesn't help me neither.
Tell me what to do - please.
Bootloader, modem, rom, kernel, put files to TWRP or?
Just 2 minute of your time would be greatly appreciated. Please!
Boot into TWRP and go to Wipe, then Advanced Wipe. Check off data, cache, and internal storage, then swipe to do the wipe. Once complete, power off the phone.
Next, boot into Download Mode and flash your latest local stock firmware via Odin. Once the flash is complete, the phone will restart on its own.
The above steps put you at a clean slate. If it's still bootlooping at this point, it's most likely a hardware issue and the phone will need to be replaced.
Sevael said:
Boot into TWRP and go to Wipe, then Advanced Wipe. Check off data, cache, and internal storage, then swipe to do the wipe. Once complete, power off the phone.
Next, boot into Download Mode and flash your latest local stock firmware via Odin. Once the flash is complete, the phone will restart on its own.
The above steps put you at a clean slate. If it's still bootlooping at this point, it's most likely a hardware issue and the phone will need to be replaced.
Click to expand...
Click to collapse
i tried that. i have the same problem but the problem did NOT go away
Jaadi said:
i tried that. i have the same problem but the problem did NOT go away
Click to expand...
Click to collapse
Time to replace the phone then.
Sevael said:
Time to replace the phone then.
Click to expand...
Click to collapse
i bought it brand new in a sealed box off kijiji. i have the box but i dont know where the guy bought it from. i need the reciept to replace it. other than that, i can use warranty to get the phone repaired. i already sent it in and they changed teh battery but that didnt work. is there any way i can find out where the person bought the phone? the person is not replying to my text or calls
So Samsung sent it back to you and it was still bootlooping when you got it back? That's bizarre. I'd send it in again and attach a note.
Sevael said:
Time to replace the phone then.
Click to expand...
Click to collapse
It's not that easy to replace the phone when i have tripped my knox which means my warranty is off. That is the problem.
Immoblize said:
It's not that easy to replace the phone when i have tripped my knox which means my warranty is off. That is the problem.
Click to expand...
Click to collapse
I know, but there isn't anything else that can be done.
It sucks, but it happens. I've had phones die and I had no choice but to go out and buy a new one. It's the risk we take when tripping Knox.
Why don't you provide us with more details...:/ For example which model phone you have (920F/I/T/V/A/etc.) Bootloop means you soft bricked it afaik.
In this case use ODIN 3.10.7 and take a look here http://forum.xda-developers.com/galaxy-s6/general/project-zero-pac-firmware-pit-file-t3181133
1. Put phone in download mode + open odin ( = the phone is detected aye?)
2. Extract the FAC firmware you downloaded (if i am right it's 1 .tar file and if there are multiple you put modem in CP, bootloader in BL and phone in AP)
3. in AP put the right FAC firmware from the thread mentioned above, if its just 1 .tar file (use G920FXXU2BOG8_G920FOXX2BOG9_XEO_PAC.zip if you have the 920F)
4. In the tab "pit" select the pit file you downloaded for your device; e.g. 920F = G920F_EUR_OPEN_HIDDEN150M.pit
5. Start odin and let it succesfully finish
6. let phone reboot.. it will be on the samsung logo for maybe 10 min?
Sevael said:
I know, but there isn't anything else that can be done.
It sucks, but it happens. I've had phones die and I had no choice but to go out and buy a new one. It's the risk we take when tripping Knox.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s6/help/help-install-wrong-bootloader-modem-t3222207
Emergency mode should fix your problem.
Try to flash unikernel First.. Then de rom.. I had bootloop to.. This wil fix it
Sent from my SM-G925F using XDA Free mobile app
Quintz said:
Why don't you provide us with more details...:/ For example which model phone you have (920F/I/T/V/A/etc.) Bootloop means you soft bricked it afaik.
In this case use ODIN 3.10.7 and take a look here http://forum.xda-developers.com/galaxy-s6/general/project-zero-pac-firmware-pit-file-t3181133
1. Put phone in download mode + open odin ( = the phone is detected aye?)
2. Extract the FAC firmware you downloaded (if i am right it's 1 .tar file and if there are multiple you put modem in CP, bootloader in BL and phone in AP)
3. in AP put the right FAC firmware from the thread mentioned above, if its just 1 .tar file (use G920FXXU2BOG8_G920FOXX2BOG9_XEO_PAC.zip if you have the 920F)
4. In the tab "pit" select the pit file you downloaded for your device; e.g. 920F = G920F_EUR_OPEN_HIDDEN150M.pit
5. Start odin and let it succesfully finish
6. let phone reboot.. it will be on the samsung logo for maybe 10 min?
Click to expand...
Click to collapse
Sorry - SM-G920F
I have done it. It gives me Nand Write error all the time.
There is 1 AP file
1 BL file
1 Modem file (CP)
1 CSC file
also beside that i downloaded the Pit file for my device. Gives me nand write error all the time.
TheEndHK said:
http://forum.xda-developers.com/galaxy-s6/help/help-install-wrong-bootloader-modem-t3222207
Emergency mode should fix your problem.
Click to expand...
Click to collapse
This is the message i get from Smart Switch when trying to flash stock android from the program.