Database Develop

[Q] Galaxy Note GT-7000 Boot problem after normal restore

Hi
Firstly, I'm sorry about my incorrect english.
I have a big problem with my rooted Galaxy Note Stock ICS 4.0.4.
After a phone restore (done in the Options menu) I encountered a boot problem.
When I turn the phone on, I see the white Galaxy Note GT-7000 writing and then
the Samsung Galaxy boot logo which continues flashing all the time but the
OS isn't booting. There isn't a boot loop which restarts the phone, only the blinking
Samsung animation.
I do really not know much about Android, rooting, flashing etc so I don't know what
is the problem and what I can do to fix it.
Recently I did a data/factory reset and cache partition wipe in the recovery mode,
hoping that this could help, but that didn't change anything.
After that I flashed another stock rom (ICS 4.0.4 Switzerland (Swisscom)) with
Odin in download mode, but there's still the endless boot problem.
I read about brick and that its not recommended to wipe anyting.
What could be my problem and how could I resolve it?
I'm sorry if theres just another thread which speaks about the same problem, but I
didn't find anyone with the identical situation as mine.
I'm very grateful for any answers.

hmm.. it could be because of data partition corruption..
download this http://www.mediafire.com/download.php?ukk00n20dahxxkp
place it on external SD.. boot into recovery and choose apply update from ext storage
once done. boot into recovery again.. now ... in the new CWM. do
factory reset., wipe cache partition
advanced menu> wipe dalvik cache
reboot

Hi,
thank you for your answer. But perhaps as I turned the phone on the first time
since yesterday (i didn't do anything since), I'm not anymore able to go into recovery mode
and the boot process ends just at the white Galaxy Note writing (without bootloop, there's
only the static text)
Only the download mode works fine, but obviously I cant install your file from there...

If you can get into download mode, better flash a stock ics rom first. After the flash is successful you can try to do the procedure as in my previous post.

I tried to flash different roms (also stock ones) but the download of the "factoryfs.img" doesn't finish.
The only thing I could do is to interrupt the downloading and restart from the beginning.
I read that this problem happens sometimes and that it could be resolved rebooting the phone and
the pc, but I didn't got it working
Do you know why it doesn't work? The first time I flashed successfully, but that was the first and the last time.
I don't even get an error or a fail notification...

LSinus said:
I tried to flash different roms (also stock ones) but the download of the "factoryfs.img" doesn't finish.
The only thing I could do is to interrupt the downloading and restart from the beginning.
I read that this problem happens sometimes and that it could be resolved rebooting the phone and
the pc, but I didn't got it working
Do you know why it doesn't work? The first time I flashed successfully, but that was the first and the last time.
I don't even get an error or a fail notification...
Click to expand...
Click to collapse
If Odin stops at "factoryfs.img" you bricked your device.
(I wrote this and the following lines a few times now in the last days, but the different OP are consequently ignoring the message and try other intelligent approaches, in the end they will not succeed, because their Note is still bricked).
Solution: Samsung replaces your motherboard (that is the only real repair).
Workaround: eMMC scanner and repartition trick in hg42's threads.
Nothing else will help if your device is bricked.

ThaiDai said:
If Odin stops at "factoryfs.img" you bricked your device.
(I wrote this and the following lines a few times now in the last days, but the different OP are consequently ignoring the message and try other intelligent approaches, in the end they will not succeed, because their Note is still bricked).
Solution: Samsung replaces your motherboard (that is the only real repair).
Workaround: eMMC scanner and repartition trick in hg42's threads.
Nothing else will help if your device is bricked.
Click to expand...
Click to collapse
i know what you are getting to but till one is completely satisfied that the phone is bricked, they wouldnt go about repartitioned the memory and loose 3 GB... at least i wouldnt and i am sure no one will till all possible scenarios are exhausted, So try to be a little positive..
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
Recently I did a data/factory reset and cache partition wipe in the recovery mode,
hoping that this could help, but that didn't change anything.
After that I flashed another stock rom (ICS 4.0.4 Switzerland (Swisscom)) with
Odin in download mode, but there's still the endless boot problem.
Click to expand...
Click to collapse
You did a factory reset on stock recovery ... and then you installed a stock rom .. was Odin able to flash till the end and it said PASS?

nokiamodeln91 said:
You did a factory reset on stock recovery ... and then you installed a stock rom .. was Odin able to flash till the end and it said PASS?
Click to expand...
Click to collapse
The first time I was able to flash the stock rom successfully (said PASS), but this was the first and last time it worked...

nokiamodeln91 said:
i know what you are getting to but till one is completely satisfied that the phone is bricked, they wouldnt go about repartitioned the memory and loose 3 GB... at least i wouldnt and i am sure no one will till all possible scenarios are exhausted, So try to be a little positive..
Click to expand...
Click to collapse
You said something about loosing 3 GB repartitioning the memory. Its possible to revive the phone by this way?
Does anyone know approximately how much it will cost me to replace the motherboard of the Note?

download this PIT file http://d-h.st/FVh
now put the phone in download mode again, open odin and select the PIT file in the PIT tab. also make sure repartition is checked.
select the rom in PDA (if more that one file for rom, choose appropriate options)
connect the phone .. when the port is shows in odin flash again,,, check if this also stops at the same factoryfs
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
LSinus said:
You said something about loosing 3 GB repartitioning the memory. Its possible to revive the phone by this way?
Does anyone know approximately how much it will cost me to replace the motherboard of the Note?
Click to expand...
Click to collapse
if you have warranty thats the first one to do. if not then there is a way by repartitioning the memory to skip the bad blocks, not a guaranteed method but works most of the time. cost of motherboard is high about 350-400$

One final try. If you are able to go recovery mode,pressing volume up, home, power buttons, flash abyss kernel 4.2, do all wipes and formats and flash a custom rom such as kingdroid.
Sent from my GT-N7000 using xda premium
---------- Post added at 10:03 PM ---------- Previous post was at 10:00 PM ----------
If you don't have custom rom in your external sd card, try to copy via another note.
Sent from my GT-N7000 using xda premium

nokiamodeln91 said:
download this PIT file http://d-h.st/FVh
now put the phone in download mode again, open odin and select the PIT file in the PIT tab. also make sure repartition is checked.
select the rom in PDA (if more that one file for rom, choose appropriate options)
connect the phone .. when the port is shows in odin flash again,,, check if this also stops at the same factoryfs
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
if you have warranty thats the first one to do. if not then there is a way by repartitioning the memory to skip the bad blocks, not a guaranteed method but works most of the time. cost of motherboard is high about 350-400$
Click to expand...
Click to collapse
Thank you for your attempt helping me. Perhaps the flashing still fails (factoryfs.img could not be downloaded entirely).
Damn, 350-400$ only for the motherboard is a lot, considering that I bought this almost new phone for around 340$...
Isn't there any other way to get rid of the "brick"? I would accept any loss of memory just to get the phone working...
By the way is it a soft- or a hardbrick?

http://forum.xda-developers.com/showthread.php?t=1667886
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12

[Q] Got phone into download mode after softbrick but what next?

I bought a second hand GT-I9000 running stock OS. I want to root it, put on a new ROM and then unlock to other phone providers as its locked on Vodafone.
I have rooted a bunch of devices previously without problems but hit a big problem with this phone.
First I downloaded and installed the samsung drivers. I then plugged in the phone and it recognised it.
I am using the latest version of Odin 3.07 and downloaded the .tar file for my baseband version - XXJPY:
cf-root-xx_xeu_jpy-v1.3-busybox-1.17.1.tar
I got the phone into download mode, showing the green (yellow) triangle, added the .tar file in PDA mode with F. Reset Time and Auto Reboot on.
The bar on Odin was blue and the box said "added" so I hit start. The large first box at the top of the Odin screen (left hand side) came up with KERNEL and the whole process started but seemed to be taking ages then the phone screen scrambled.
The phone was soft bricked and I have got it back to download mode.
The problem I have now is Odin wont recognise the phone in download mode. I am installing new samsung drivers in the hope this will solve this problem.
I have got the .pit file for my phone from another thread and if I understand correctly I use this file in Odin to get the phone back to life??
If I can get it working again can anyone tell me why the root failed?

mark1holland1 said:
I bought a second hand GT-I9000 running stock OS. I want to root it, put on a new ROM and then unlock to other phone providers as its locked on Vodafone.
I have rooted a bunch of devices previously without problems but hit a big problem with this phone.
First I downloaded and installed the samsung drivers. I then plugged in the phone and it recognised it.
I am using the latest version of Odin 3.07 and downloaded the .tar file for my baseband version - XXJPY:
cf-root-xx_xeu_jpy-v1.3-busybox-1.17.1.tar
I got the phone into download mode, showing the green (yellow) triangle, added the .tar file in PDA mode with F. Reset Time and Auto Reboot on.
The bar on Odin was blue and the box said "added" so I hit start. The large first box at the top of the Odin screen (left hand side) came up with KERNEL and the whole process started but seemed to be taking ages then the phone screen scrambled.
The phone was soft bricked and I have got it back to download mode.
The problem I have now is Odin wont recognise the phone in download mode. I am installing new samsung drivers in the hope this will solve this problem.
I have got the .pit file for my phone from another thread and if I understand correctly I use this file in Odin to get the phone back to life??
If I can get it working again can anyone tell me why the root failed?
Click to expand...
Click to collapse
Hi...Hm never had this problem, maybe something went wrong with USB connection, hope you get it working...
I was using this method for rooting and there was no problems.
http://theunlockr.com/2012/10/22/how-to-root-the-samsung-galaxy-s-i9000-cf-kernel-method/
Best regards!

I cant get the phone to be recognised by my PC - damn thing comes up as unrecognised USB device!
Installingmkies, anyone ever seen this problem?

I have the phone recognised by my PC and have run the .pit file which Odin said was a success, however, the phone wont start except in download mode
how can I install anything?
do I need to install factory firmware first??

A new version of Odin is NOT DESIGNED for GT-I9000. Use Odin 1.83 and older

DumF0rGaming said:
A new version of Odin is NOT DESIGNED for GT-I9000. Use Odin 1.83 and older
Click to expand...
Click to collapse
Thanks for that.
The problem I have is that I cannot get any firmware to install - it starts fine then fails and the screen scrambles.
I have used the pit file to repartition first but it still fails

I guess you have to try install JVU via Heimdall v1.1+zadig, then root it and go directly to the newest CM

mark1holland1 said:
.....I am using the latest version of Odin 3.07.....
Click to expand...
Click to collapse
It is wrong Odin version.
Our forum mate @DumF0rGaming already wrote you correct answer, if Odin use 1.82 or 1.83, or use Heimdall as he wrote you. Odin v3.x or 4.x will usually recognize device, but instantly freeze by try to flash.

DumF0rGaming said:
I guess you have to try install JVU via Heimdall v1.1+zadig, then root it and go directly to the newest CM
Click to expand...
Click to collapse
Hi, many thanks for the information, due you have any links or information. I have not used Heimdall yet.

tetakpatak said:
It is wrong Odin version.
Our forum mate @DumF0rGaming already wrote you correct answer, if Odin use 1.82 or 1.83, or use Heimdall as he wrote you. Odin v3.x or 4.x will usually recognize device, but instantly freeze by try to flash.
Click to expand...
Click to collapse
I have got the device recognised and partitioned with the pit file using 1.83 Odin but cannot find a stock file which works
It starts and just hangs with a tiny sliver of the green bar on the phone.
Its driving me INSANE!

mark1holland1 said:
I have got the device recognised and partitioned with the pit file using 1.83 Odin but cannot find a stock file which works. It starts and just hangs with a tiny sliver of the green bar on the phone.
Click to expand...
Click to collapse
Patience, mate... cool head helps better. Use this step-by-step guide of mine where all download links still work. The workflow there is about installing Froyo stock ROM (big choice for all regions) and after that you can flash SpeedMod kernel which features CWM recovery. That ROM seems to be good ground to upgrade further to CM10x, I had no bugs at all (some people upgrading from other ROMs seem to be more prone to bugs).
Here is the guide: http://forum.xda-developers.com/showthread.php?p=44710247#post44710247
And you are sure that you have i9000?

tetakpatak said:
Patience, mate... cool head helps better. Use this step-by-step guide of mine where all download links still work. The workflow there is about installing Froyo stock ROM (big choice for all regions) and after that you can flash SpeedMod kernel which features CWM recovery. That ROM seems to be good ground to upgrade further to CM10x, I had no bugs at all (some people upgrading from other ROMs seem to be more prone to bugs).
Here is the guide: http://forum.xda-developers.com/showthread.php?p=44710247#post44710247
And you are sure that you have i9000?
Click to expand...
Click to collapse
Thanks for all this information, this is exactly what I have been looking around for the past few hours. This is an absolutely excellent write up you provided.
I still think I may have a problem as the blue bar appeared to show progress but then has stopped. The process seems to be stuck on PARAM in Odin showing this <ID:0/003> param.lfs

mark1holland1 said:
I still think I may have a problem as the blue bar appeared to show progress but then has stopped. The process seems to be stuck on PARAM in Odin showing this <ID:0/003> param.lfs
Click to expand...
Click to collapse
Well, Odin indeed needs several minutes to complete the flashing. But if really nothing changes for longer than 7-8 minutes, pull out the USB cable and then battery and repeat the procedure. Try also an older Odin version, I think 1.72 or even 1.0 work well with the i9000. Check in search field, there is an topic with all Odin versions and their compatibility.
I hope it will work next try, good luck! Post the results please.
EDIT: if Odin fails to complete the flashing, Heimdall is probably good idea. Our forum mate has sent you download link of the older version thaht works well with the i9000. Heimdall is actually more reliable flasher, but it has bit different workflow. Here is website where you can read more about it:
http://www.glassechidna.com.au/products/heimdall/
---------- Post added at 08:19 PM ---------- Previous post was at 08:00 PM ----------
mark1holland1 said:
Odin showing this <ID:0/003> param.lfs
Click to expand...
Click to collapse
"param.lfs" is actually extremely important file where the flashing shouldn't been interrupted. But its flashing should take normally only several seconds, so if the Odin stuck there and nothing changes for really long time, you can't make it worse than it already is by removing the cable....

tetakpatak said:
Well, Odin indeed needs several minutes to complete the flashing. But if really nothing changes for longer than 7-8 minutes, pull out the USB cable and then battery and repeat the procedure. Try also an older Odin version, I think 1.72 or even 1.0 work well with the i9000. Check in search field, there is an topic with all Odin versions and their compatibility.
I hope it will work next try, good luck! Post the results please.
EDIT: if Odin fails to complete the flashing, Heimdall is probably good idea. Our forum mate has sent you download link of the older version thaht works well with the i9000. Heimdall is actually more reliable flasher, but it has bit different workflow. Here is website where you can read more about it:
http://www.glassechidna.com.au/products/heimdall/
---------- Post added at 08:19 PM ---------- Previous post was at 08:00 PM ----------
"param.lfs" is actually extremely important file where the flashing shouldn't been interrupted. But its flashing should take normally only several seconds, so if the Odin stuck there and nothing changes for really long time, you can't make it worse than it already is by removing the cable....
Click to expand...
Click to collapse
It just seems to stick at the start, the bar begins and then just hangs.
Many thanks for your time on this, I am downloading Heimdall as we speak......

mark1holland1 said:
I have got the device recognised and partitioned with the pit file using 1.83 Odin... It starts and just hangs with a tiny sliver of the green bar on the phone. Its driving me INSANE!
Click to expand...
Click to collapse
Before next try, make soft reset of your phone: pull out the battery and keep power button pressed for ca 30sec.
Meanwhile, close Odin and run it again, prepare again all the files and put your phone into download mode just short before you start with flashing.
---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------
mark1holland1 said:
It just seems to stick at the start, the bar begins and then just hangs.
Many thanks for your time on this, I am downloading Heimdall as we speak......
Click to expand...
Click to collapse
Try bit older Odin version. Already 1.82 should work well...
---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------
mark1holland1 said:
...
Click to expand...
Click to collapse
Here you have Odin 1.7 and 1.82, I didn't check if download links are still active

tetakpatak said:
Before next try, make soft reset of your phone: pull out the battery and keep power button pressed for ca 30sec.
Meanwhile, close Odin and run it again, prepare again all the files and put your phone into download mode just short before you start with flashing.
---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------
Try bit older Odin version. Already 1.82 should work well...
---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------
Here you have Odin 1.7 and 1.82, I didn't check if download links are still active
Click to expand...
Click to collapse
I tried Odin 1.7 and it still sticks, this time earlier (after removing the battery and pressing power for 30 secs)
I honestly am at my wits end with this, trying Hiemdall...........

mark1holland1 said:
I tried Odin 1.7 and it still sticks, this time earlier (after removing the battery and pressing power for 30 secs)
I honestly am at my wits end with this, trying Hiemdall...........
Click to expand...
Click to collapse
Yes... as you prefer, mate. Read as first carefully how it works, as the workflow is different.

tetakpatak said:
Yes... as you prefer, mate. Read as first carefully how it works, as the workflow is different.
Click to expand...
Click to collapse
IT failed on the kernel, tried it twice
says fails to deliver data or up load it

If there is a kernel problem is the phone essentially bricked or does anyone know of a solution???

mark1holland1 said:
If there is a kernel problem is the phone essentially bricked or does anyone know of a solution???
Click to expand...
Click to collapse
Are you trying to flash Froyo stock ROM out of three files? I didn't try it with Heimdall. I know our forum mate @DumF0rGaming has mentioned recently some 2.3.6 ROM that should work particulary good with Heimdall. Check his post of last few days.
Good that your phone gives signs of life. Don't worry now, there are so many ways how it could work. We all have semi-bricked our phones on some point before and restored them again. You need patience. I would also try with several Odin versions, also try to connect the cable to different USB slot on your PC. Often it is some stupid reason that makes the flashing suddenly work.
Try also with Odin 1.0

NON ROOTED brick

As the title says the phone has not been rooted and has bricked itself. It can get to the download screen but that's about it. Odin doesn't recognize it and not sure how to flash the stock rom back on it to get it back up and running. Anyone run into this issue before.? See image for what shows up on the screen. Thanks.

update: was able to hav odin recognize the phone. I've tried this http://forum.xda-developers.com/showthread.php?t=2703006 with both the .pit and without plus the 4 files with no luck. still just restarts to same screen.

landscaped1 said:
update: was able to hav odin recognize the phone. I've tried this http://forum.xda-developers.com/showthread.php?t=2703006 with both the .pit and without plus the 4 files with no luck. still just restarts to same screen.
Click to expand...
Click to collapse
Somethings not right. If you flash the pit file make sure you flash all 4 files. I dont see a reason why it shouldnt work. If it still has that after you flash boot into recovery and factory reset. It should work. Its easy to soft brick than to hard brick. As long as you can get into download mode you should be fine.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
---------- Post added at 04:08 AM ---------- Previous post was at 03:44 AM ----------
landscaped1 said:
As the title says the phone has not been rooted and has bricked itself. It can get to the download screen but that's about it. Odin doesn't recognize it and not sure how to flash the stock rom back on it to get it back up and running. Anyone run into this issue before.? See image for what shows up on the screen. Thanks.
Click to expand...
Click to collapse
I dont know then. Only thing i would suggest is make sure you have downloaded the latest samsung drivers. Last time i couldnt get it to recognize i downloaded the latest samsung mobile drivers and tried every usb port. I also gave it a break for about 10 or 15 minutes with the phone off and it worked too. Dont know why but it did. Hope that helps. Cheers mate
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

landscaped1 said:
As the title says the phone has not been rooted and has bricked itself. It can get to the download screen but that's about it. Odin doesn't recognize it and not sure how to flash the stock rom back on it to get it back up and running. Anyone run into this issue before.? See image for what shows up on the screen. Thanks.
Click to expand...
Click to collapse
It goes straight to download screen or before this you got option to press volume up or down? Did you try to get to recovery mode by pressing combination of volume up , home button and power button then let all go when samsung logo show up with little blue writing on left top of phone. If you get to recovery try to clean cache. If you can't and after you try to flash back to stock still going straight to download mode must be hardware issue.

Why do the newer users call anything that doesn't boot properly "Bricked ?"
Believe me you'll know when and if your ever able to successfully achieve it....
Your not even rooted..lmfao

[Q] Help Note 4 Bricked - Binary Blocked by Reactivation Lock & Boot Loops

I rooted my T-Mobile Galaxy Note 4 early last week using Odin v3.09 and cf auto root and flashed TWRP recovery using Odin. I disabled Knox as SuperSU suggested, and I created a back up after root. Saturday I flashed Dynamic Kat v 3.0, and go everything set up the way I wanted it. I didn't mess with any of the security settings, other than setting a pin for the lockscreen. This morning I rebooted into recovery to create a back up, but instead of going to recovery, I got a black screen with an exclamation point and an error message saying Custom binary blocked by Reactivation Lock. Secure Fail: Recovery that would just keep looping when I tried to restart it. I tried pulling the battery and restarting, but still had the same message at restart. I then tried to run odin and cf autoroot again, but got the same message and Odin said that it failed. Now the phone just keeps boot looping on the Samsung Galaxy Note 4 powered by android screen.
If I go to the download mode the top of the screen says:
Odin Mode (High Speed)
Product Name: SM-N910T
Current Binary: Custom
System Status: : Custom
Reactivation Lock(KK): On
Knox Warranty Void: 0x1 (4)
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download : Enable
UDC Start
How can I fix this, what can I do?

Get a stock odin flashable and start over from downloadmode...
Tryna find that link or it may be samsmobile
Look here.
http://forum.xda-developers.com/showthread.php?p=55968427
If your pc does not see the phone in download mode then you need to run kies emergency firmware recovery..

Flashvetrin said:
Get a stock odin flashable and start over from downloadmode...
Tryna find that link or it may be samsmobile
Look here.
http://forum.xda-developers.com/showthread.php?p=55968427
If your pc does not see the phone in download mode then you need to run kies emergency firmware recovery..
Click to expand...
Click to collapse
Thanks, I found where someone had the same issue with the Note 3 and used kies emergency firmware recovery to fix it as well, so I started the process. It just finished, and I'm back up and running.

omega_wolf said:
Thanks, I found where someone had the same issue with the Note 3 and used kies emergency firmware recovery to fix it as well, so I started the process. It just finished, and I'm back up and running.
Click to expand...
Click to collapse
Thats good news..
[emoji1] [emoji109] [emoji106]

can you link me to where you went? fml this just happened to me after flashing same rom you did.

jrocks213 said:
can you link me to where you went? fml this just happened to me after flashing same rom you did.
Click to expand...
Click to collapse
Yea, I followed the steps posted in this thread: http://forum.xda-developers.com/showthread.php?t=2486564&page=2
1. download KIES 3 (for note 4)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
You will have to re-root after this.

omega_wolf said:
Yea, I followed the steps posted in this thread: http://forum.xda-developers.com/showthread.php?t=2486564&page=2
1. download KIES 3 (for note 4)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
You will have to re-root after this.
Click to expand...
Click to collapse
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
Click to expand...
Click to collapse
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.

jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
Click to expand...
Click to collapse
Try entering the model number and S/N and pressing Ok before connecting the phone, or double check to make sure 0s aren't Os or vice versa. It took a minute or 2 to get started on my phone, and took awhile to complete.

jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.
Click to expand...
Click to collapse
This happened to me before and this is what i did. Easier than messing kies I think. Flash cf auto root in odin with the reset and auto reboot unchecked. Very important to uncheck those. It will fail to flash. Pull out your battery and put back in. It will boot as normal. Now go into security and uncheck that reactivate crap. That feature should be disabled completely custom roms to prevent this occurance i think.

Airtioteclint said:
That feature should be disabled completely custom roms to prevent this occurance i think.
Click to expand...
Click to collapse
I agree, it wasn't checked by default when I rooted the phone, nor when I flashed another ROM, so I didn't even think to check when I flashed Dynamic Kat, but I'll be double checking gem here on out.

jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.
Click to expand...
Click to collapse
Hi, Im in the same boat, locked out, etc, I am trying kies where I dump the s/n in etc, it downloads the firmware, sees the phone then crashes, same with ODIN, the blue bar underneath the android man, starts but locks up. Does not go anywhere and freezes the phone. I have to take the battery out or leave Kies to give me an error. Any idea?

smileruk.ss said:
Hi, Im in the same boat, locked out, etc, I am trying kies where I dump the s/n in etc, it downloads the firmware, sees the phone then crashes, same with ODIN, the blue bar underneath the android man, starts but locks up. Does not go anywhere and freezes the phone. I have to take the battery out or leave Kies to give me an error. Any idea?
Click to expand...
Click to collapse
Odin flash cf autoroot, it will fail but once it restarts it will boot up to your android screen,
also you can Odin flash the full firmware, but then u need to odin flash twrp again and root.

flashing stock firmware problems

Hi all,
I'm having an odd issue. No matter whether I used Odin or Smart Switch I can simply not flash a stock firmware. Regardless of the method, the following always happens.
Downloads firmware to device
Reboots
Shows Android dude with "Installing update"
Stops half way through
Shows Android dude with "Erasing"
Disappears after few seconds
Reboots
Nothing is changed. Same as before the whole process...

liangle01 said:
Hi all,
I'm having an odd issue. No matter whether I used Odin or Smart Switch I can simply not flash a stock firmware. Regardless of the method, the following always happens.
Downloads firmware to device
Reboots
Shows Android dude with "Installing update"
Stops half way through
Shows Android dude with "Erasing"
Disappears after few seconds
Reboots
Nothing is changed. Same as before the whole process...
Click to expand...
Click to collapse
Make sure you uncheck auto reboot in Odin! Do not allow it to reboot the phone! Flash the stock firmware again and after it says success unplug the phone and immediately press and hold the volume down button and power button at the same time and when the screen comes back on select factory reset and after its finished the phone will reboot on it's own and you're done it should work correctly.

MrMike2182 said:
Make sure you uncheck auto reboot in Odin! Do not allow it to reboot the phone! Flash the stock firmware again and after it says success unplug the phone and immediately press and hold the volume down button and power button at the same time and when the screen comes back on select factory reset and after its finished the phone will reboot on it's own and you're done it should work correctly.
Click to expand...
Click to collapse
I am having a similar problem odin runs and passes, but the phone goes to the Samsung screen and has recovery is not seandroid enforcing on the top of the screen. Any ideas?

timsmooth said:
I am having a similar problem odin runs and passes, but the phone goes to the Samsung screen and has recovery is not seandroid enforcing on the top of the screen. Any ideas?
Click to expand...
Click to collapse
That's because you are trying to to root it I'm guessing? You either flashed the wrong kernel, or you actually did not turn on oem unlock in developer options. You'll need to restore it back to stock and then turn on oem unlock then flash a kernel/recovery and then retry what you're trying to do.

MrMike2182 said:
That's because you are trying to to root it I'm guessing? You either flashed the wrong kernel, or you actually did not turn on oem unlock in developer options. You'll need to restore it back to stock and then turn on oem unlock then flash a kernel/recovery and then retry what you're trying to do.
Click to expand...
Click to collapse
Fair enough. Where can I get the stock Kernel so I can get back into the OS? I keep finding bad ones with unmatching MD5s.

timsmooth said:
Fair enough. Where can I get the stock Kernel so I can get back into the OS? I keep finding bad ones with unmatching MD5s.
Click to expand...
Click to collapse
Download one of these for your phone. .
http://www.sammobile.com/firmwares/database/SM-N920P/
Make sure you uncheck auto reboot in Odin and as soon as it's done and says success disconnect the phone and immediately press and hold the volume down button and the power button at the same time and when the screen comes back up you HAVE to select factory reset wipe if you don't you'll be stuck again just let the little android dude install the update and then the phone will reboot and you'll be ok.
Unzip the md5 you get from the sammobile site and flash only the .tar

same thing
The same old firmware after rebooting.....Any ideas

liangle01 said:
The same old firmware after rebooting.....Any ideas
Click to expand...
Click to collapse
What do you mean the same old firmware? That firmware is just stock firmware so you can at least get back up and running to try rooting it again.
You asked for the stock firmware...
"I'm having an odd issue. No matter whether I used Odin or Smart Switch I can simply not flash a stock firmware. Regardless of the method, the following always happens.'
So I gave it to you.

MrMike2182 said:
Download one of these for your phone. .
http://www.sammobile.com/firmwares/database/SM-N920P/
Make sure you uncheck auto reboot in Odin and as soon as it's done and says success disconnect the phone and immediately press and hold the volume down button and the power button at the same time and when the screen comes back up you HAVE to select factory reset wipe if you don't you'll be stuck again just let the little android dude install the update and then the phone will reboot and you'll be ok.
Unzip the md5 you get from the sammobile site and flash only the .tar
Click to expand...
Click to collapse
LOL its been a long time since I have flashed or rooted, but I didn't know you can extract from an MD5, but I will do that and give it a shot. Ill let you know thx for your help.

MrMike2182 said:
Make sure you uncheck auto reboot in Odin! Do not allow it to reboot the phone! Flash the stock firmware again and after it says success unplug the phone and immediately press and hold the volume down button and power button at the same time and when the screen comes back on select factory reset and after its finished the phone will reboot on it's own and you're done it should work correctly.
Click to expand...
Click to collapse
My phone is not rooted (i like to keep it like that) all what I want is to change the CSC ( both of them are for the same country) but Odin keep failing. Any ideas plz

timsmooth said:
LOL its been a long time since I have flashed or rooted, but I didn't know you can extract from an MD5, but I will do that and give it a shot. Ill let you know thx for your help.
Click to expand...
Click to collapse
LOL it's better to extract the .tar from the md5 so it doesn't have to be verified which is what's causing it to not work for you.
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
liangle01 said:
My phone is not rooted (i like to keep it like that) all what I want is to change the CSC ( both of them are for the same country) but Odin keep failing. Any ideas plz
Click to expand...
Click to collapse
If Odin fails there's nothing I can do about it sorry.

MrMike2182 said:
Download one of these for your phone. .
http://www.sammobile.com/firmwares/database/SM-N920P/
Make sure you uncheck auto reboot in Odin and as soon as it's done and says success disconnect the phone and immediately press and hold the volume down button and the power button at the same time and when the screen comes back up you HAVE to select factory reset wipe if you don't you'll be stuck again just let the little android dude install the update and then the phone will reboot and you'll be ok.
Unzip the md5 you get from the sammobile site and flash only the .tar
Click to expand...
Click to collapse
Dag nabit I lost ALL my data. Jesus H xrst. Lucky I use cloud back up for my pictures. At least I have those. All my music is gone though. Dude thanks a million though at least I am up and running again. The process was simple enough but I would have never figured it out. Ive got a long day ahead of me now. I have to re configure my phone. Anyway, I owe you a beer.
Flashing phones never used to be this brutal. What happened?

MrMike2182 said:
What do you mean the same old firmware? That firmware is just stock firmware so you can at least get back up and running to try rooting it again.
You asked for the stock firmware...
"I'm having an odd issue. No matter whether I used Odin or Smart Switch I can simply not flash a stock firmware. Regardless of the method, the following always happens.'
So I gave it to you.
Click to expand...
Click to collapse
the new firmware (6.0.1) has a different CSC from the original (6.0.1). but when i flash it with odin nothing happened:1- my Apps,my photos....all is there.2- when i check the CSC it's the same old one..i mean it have to change isn't ???? . it's just like i have restarted my phone normal !!!!!

MrMike2182 said:
LOL it's better to extract the .tar from the md5 so it doesn't have to be verified which is what's causing it to not work for you.
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
If Odin fails there's nothing I can do about it sorry.
Click to expand...
Click to collapse
thanks for responding anyway. if you find anything please report me......
again thank you ✌✌✌

timsmooth said:
Dag nabit I lost ALL my data. Jesus H xrst. Lucky I use cloud back up for my pictures. At least I have those. All my music is gone though. Dude thanks a million though at least I am up and running again. The process was simple enough but I would have never figured it out. Ive got a long day ahead of me now. I have to re configure my phone. Anyway, I owe you a beer.
Flashing phones never used to be this brutal. What happened?
Click to expand...
Click to collapse
Shoot sorry I should have mentioned that it was going to erase everything (I found out the hard way to lol) But even if I had known that I wouldn't have been able to get them back anyway once you can't get in to change the settings to file transfer.. I'm glad I back everything up to my laptop! The phone companies are locking the phones down tightly "for our own interests they say" which is BS and totally goes against what Android open source is supposed to be about!!!
---------- Post added at 10:25 AM ---------- Previous post was at 10:23 AM ----------
liangle01 said:
the new firmware (6.0.1) has a different CSC from the original (6.0.1). but when i flash it with odin nothing happened:1- my Apps,my photos....all is there.2- when i check the CSC it's the same old one..i mean it have to change isn't ???? . it's just like i have restarted my phone normal !!!!!
Click to expand...
Click to collapse
What's wrong with your phone booting normal? I don't understand what you're trying to do.. What's the CSC have to do with anything?