So I've been using 4.4 SlimKat for quite a long time now and it has been running quite well. But earlier today out of nowhere the phone started to overheat like crazy and shut down.
I let it cool off for a bit then turned it on, and it got stuck on a bootloop on the Samsung logo.
Recovery works but whenever I try to flash or wipe anything, I get "unable to make /cache" and "Can't find log file" and formatting cache using make_ext4fs and it gets stuck on that.
And I tried installing the stock ROM using ODIN and that didn't work as well, It got stuck on "nand write start!!"
So, Does anyone have an idea on how I'd be able to fix that ?
FI would flash Philz kernel odin version. Then get to recovery, then do 'clean to install rom" then, do wipe dalvik cache, then flash a custom 4.12 rom.zip.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
FI would flash Philz kernel odin version. Then get to recovery, then do 'clean to install rom" then, do wipe dalvik cache, then flash a custom 4.12 rom.zip.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Still stuck on "NAND write start!!"
Usamovic said:
Still stuck on "NAND write start!!"
Click to expand...
Click to collapse
Which file did you flash?
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
Which file did you flash?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
This one : http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/philz_touch_6.25.0-n7000.tar.md5
I got SetupConnection.. stuck couple of time too.
Usamovic said:
This one : http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/philz_touch_6.25.0-n7000.tar.md5
I got SetupConnection.. stuck couple of time too.
Click to expand...
Click to collapse
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
How many times have you written the same post..? Ha ha... I counted 10...
nokiamodeln91 said:
How many times have you written the same post..? Ha ha... I counted 10...
Click to expand...
Click to collapse
And will continue !
Sent from my GT-N7000 using Tapatalk 2
I blame Phil.
Sent from my Nexus 5 using Tapatalk
AndroidSlave said:
I blame Phil.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It seems Phil is not having time to monitor all his threads.
forest1971 said:
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I flashed an LTA one and it ended up with NAND write start too.
I also have the yellow triangle thing under the Samsung logo now.
Usamovic said:
I flashed an LTA one and it ended up with NAND write start too.
I also have the yellow triangle thing under the Samsung logo now.
Click to expand...
Click to collapse
Should post log of odin as well.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
Should post log of odin as well.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
Usamovic said:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
Click to expand...
Click to collapse
That is the correct file.
I would do:
- make sure you have uninstalled kies. Disable all antivirus.
- download an other file and flash again.
- if not work, then flash together with the stock pit file and tick repartition. (Stock pit can be download from dr.ketan thread in the sticky.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
That is the correct file.
I would do:
- make sure you have uninstalled kies. Disable all antivirus.
- download an other file and flash again.
- if not work, then flash together with the stock pit file and tick repartition. (Stock pit can be download from dr.ketan thread in the sticky.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Still the same problem.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLT9-ORA-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
You mentioned earlier can still get into recovery? If so should try to use hg42 partition scanner.
Also I would try to use heimdall to flash. For me it works better than odin.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
You mentioned earlier can still get into recovery? If so should try to use hg42 partition scanner.
Also I would try to use heimdall to flash. For me it works better than odin.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Recovery stopped working somewhere throughout this whole thing.
Thank you so much for helping BTW, I'm fully aware it's a hassle.
Usamovic said:
Recovery stopped working somewhere throughout this whole thing.
Thank you so much for helping BTW, I'm fully aware it's a hassle.
Click to expand...
Click to collapse
While all these flashing,, are you rebooting the phone into download mode? Back to back flashing will not work,, before every flash, power off and reboot into download mode.
nokiamodeln91 said:
While all these flashing,, are you rebooting the phone into download mode? Back to back flashing will not work,, before every flash, power off and reboot into download mode.
Click to expand...
Click to collapse
Yeah, I reboot every single time.
Usamovic said:
Yeah, I reboot every single time.
Click to expand...
Click to collapse
Alright... Try another PC and cables if possible.
Related
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
EFCLEE said:
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
Click to expand...
Click to collapse
Did you select the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
jeetu1981 said:
Did you selected the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
Click to expand...
Click to collapse
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?
EFCLEE said:
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?
Click to expand...
Click to collapse
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
jeetu1981 said:
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
Click to expand...
Click to collapse
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
EFCLEE said:
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
Click to expand...
Click to collapse
Cool... Consider urself lucky this time
And click on thanks is better than million thanks, lol
Sent from my GT-N7000
I have a bricked GT-N7000.I got it this way so I'm not sure what exactly happened to it.The previous owner said he just tried to install OTA update,phone rebooted and since then its bricked.I know the guy doesnt have not a single clue about computers'n'stuff so im pretty sure this is the real reason for brick.
About the phone:
-doesnt boot,just hangs at Samsung galaxy note GT-N7000 screen
-download mode working
-recovery mode NOT working(cant access it,if I try the phone hangs at Samsung galaxy note GT-N7000 screen,then reboots afrter 6-7 minutes.after reboot just hangs at Samsung galaxy note GT-N7000 screen)
-flashing via ODIN works (everything passes) but it seems that it doesnt have any affect on it
-ADB not working because USB debugging not activated on phone
PLEASE HELP ME REVIVE IT!!!
Thanks in advance
Try flashing any old Philz kernel with pc odin, then try to boot straight into recovery. If that works then try to do all wipes and clear it ready for flashing whatever you want. If not, flash a stock 3 part gb rom and report back.
If you can enter download mode then you're not bricked, sounds like the kernel was part flashed or corrupted in some way.
Sent from my GT-N7000 using XDA Premium 4 mobile app
SpyderTracks said:
Try flashing any old Philz kernel with pc odin, then try to boot straight into recovery. If that works then try to do all wipes and clear it ready for flashing whatever you want. If not, flash a stock 3 part gb rom and report back.
If you can enter download mode then you're not bricked, sounds like the kernel was part flashed or corrupted in some way.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for trying to help.Will keep you informed with the progress
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
PhilZ-cwm6-XXLQ3-OXX-2.7.tar.md5
PhilZ-cwm6-XXLRI-AUT-3.99.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.35.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.63.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.87.6.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.88.2.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.89.4.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.90.8.tar.md5
PhilZ-cwm6-DXLSE-OLB-4.91.2.tar.md5
PhilZ-cwm6-XXLT4-OXA-4.93.6.tar.md5
PhilZ-cwm6-XXLT4-OXA-5.00.5.tar.md5
PhilZ-cwm6-XXLT5-OXX-5.03.0.tar.md5
PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
PhilZ-cwm6-XXLT9-ORA-5.08.5.tar.md5
PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5
Tried with all of the above and cant get past Samsung galaxy note GT-N7000 screen.Am I doing something wrong?
bizzare187 said:
Thanks for trying to help.Will keep you informed with the progress
PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 NO LUCK,WILL KEEP TRYING
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
PhilZ-cwm6-XXLQ3-OXX-2.7.tar.md5
PhilZ-cwm6-XXLRI-AUT-3.99.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.35.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.63.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.87.6.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.88.2.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.89.4.tar.md5
PhilZ-cwm6-XXLSZ-OXA-4.90.8.tar.md5
PhilZ-cwm6-DXLSE-OLB-4.91.2.tar.md5
Click to expand...
Click to collapse
Looks like you tried enough kernels, try flashing a stock Gingerbread just as @SpyderTracks If that doesn't work then you might have a bit of a problem :/
Is unusual for it to respond as succeeding flash if there were emmc damage isn't it? Very unusual. Keep us posted with 3 part old gb rom flash. That will include bootloader which will hopefully kick it into start. Good luck.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Anyone know where I can find 3 part GB rom? All I could find so far are only single-file roms and it seems they dont work for me.
I tried with N7000XXLA3 --------2.3.6------- 2012 January---N7000OXALA3 GB rom and still no luck.its a 3 part rom like you guys suggested
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLA3_REV_05_CL1095424.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALA3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> boot.bin
<ID:0/010> Sbl.bin
<ID:0/010> param.lfs
<ID:0/010> zImage
<ID:0/010> factoryfs.img
<ID:0/010> data.img
<ID:0/010> cache.img
<ID:0/010> hidden.img
<ID:0/010> modem.bin
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010> Receive Response form LOKE
<ID:0/010> cache.img
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
<ID:0/010> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Any other ideas?
After flashing this rom, do you have access to recovery? That is volume up + home + power?
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
After flashing this rom, do you have access to recovery? That is volume up + home + power?
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
still no recovery.same as before.if i go to recovery the phone hangs at GT-N7000 screen and it reboots itself after 5-7 minutes.after that it still just hangs at GT-N7000 screen.download mode still working like it should
P.S.: i tried to enter recovery again.i holded 3 button combo for about 2 minutes.nothing new happened
Are you trying to access it without the usb cable connected? Because it could be a little tricky when it's connected. If still no recovery then.....
Check if the phone connects to adb when it's stuck on the Samsung logo. If there is a connection try command adb reboot recovery.
If no connection, Try installing any other kernel again like you did philz earlier. Not sure if you tried recovery after installing the kernel.
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
Are you trying to access it without the usb cable connected? Because it could be a little tricky when it's connected. If still no recovery then.....
Check if the phone connects to adb when it's stuck on the Samsung logo. If there is a connection try command adb reboot recovery.
If no connection, Try installing any other kernel again like you did philz earlier. Not sure if you tried recovery after installing the kernel.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
I tried to enter recovery after installing every kernel,and not just once.i tried a few times.i always try to enter recovery and download mode without usb cable.in adb i dont get connected because usb debugging is not activated on the phone.atleast i think this is the reason.will try a few more stock and custom kernels and keep you informed about the progress
Tried the folowing kernels: (almost all of them)
Custom Kernels
AbyssNote
CF-Root 5.6 CWM5
Driving Always For User Quality
Dual Boot Roms
FM Kernel
franco.Kernel
GL_NOTECORE
Goku Kernel
M1 Kernel
SpeedMod N7000 K2
SpeedMod N7000 K3
Tegrak Kernel
WizDom13 Kernel
still no luck
Sorry to ask but what method are you using to access recovery?
Sent from my GT-N7000 using XDA Premium 4 mobile app
Volume up+home+power.if i try from turned off i keep holding the buttons even after the first reebot which is sonething pretty normsl on all galaxy devices.
Sent from my GT-I9100 using XDA Premium 4 mobile app
Tried to flash CWM custom recovery with Heimdall and still cant get into the recovery??
C:\Users\Ghost\Downloads\heimdall\Heimdall>heimdall flash --KERNEL zImage --no-r
eboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading KERNEL
100%
KERNEL upload successful
Ending session...
Releasing device interface...
C:\Users\Ghost\Downloads\heimdall\Heimdall>
Try to flash a rom again this time use the original Pit file too to repartition.
Sent from my GT-I9500 using xda premium
Does anybody have bl.bin file? Need it for SBL2 partition.
Thanks
Sent from my GT-I9100 using XDA Premium 4 mobile app
C:\Users\Ghost\Downloads\heimdall\Heimdall>heimdall flash --repartition --PIT Q1
_20110914_16GB.pit --BOOT boot.bin --SBL1 sbl.bin --PARAM param.lfs --KERNEL zIm
age --CACHE cache.img --MODEM modem.bin --FACTORYFS factoryfs.img --HIDDEN hidde
n.img --verbose
I wrote this command line for Heimdall and flashing works like it should,but still no luck with booting the phone
Any new suggestions?
Hello, I've installed the newest XXLTD Firmware and I cannot seem to make a recovery install properly on it, what should I do? which recovery should I flash?
Thanks
louayd said:
Hello, I've installed the newest XXLTD Firmware and I cannot seem to make a recovery install properly on it, what should I do? which recovery should I flash?
Thanks
Click to expand...
Click to collapse
The recovery comes with the kernel for the Note. If you want a custom recovery, flash Philz kernel. If you want KitKat then flash philz kernel and then flash the latest version of Raw Kernel.
XxPixX said:
The recovery comes with the kernel for the Note. If you want a custom recovery, flash Philz kernel. If you want KitKat then flash philz kernel and then flash the latest version of Raw Kernel.
Click to expand...
Click to collapse
Could u please link me a custom that would work with my firmware? I tries the latest philz and did not work. Thnx!
XxPixX said:
The recovery comes with the kernel for the Note. If you want a custom recovery, flash Philz kernel. If you want KitKat then flash philz kernel and then flash the latest version of Raw Kernel.
Click to expand...
Click to collapse
How shoud i install omni rom on my galaxy note gtn7000 im on Android 2.3.6 and i rooted my phone?
dmo.jr said:
How shoud i install omni rom on my galaxy note gtn7000 im on Android 2.3.6 and i rooted my phone?
Click to expand...
Click to collapse
You need to get yourself on a JB Rom first
this might help
Please can anyone help solve this? Thanks
louayd said:
Please can anyone help solve this? Thanks
Click to expand...
Click to collapse
Go SEARCH AND READ in Philz thread. Direct link to his download page is PROHIBITED. One Answer though, Find XXLTC version.
commencing atskine
Jackwu696 said:
Go SEARCH AND READ in Philz thread. Direct link to his download page is PROHIBITED. One Answer though, Find XXLTC version.
Click to expand...
Click to collapse
I did already! I couldn't find recovery matching XXLTC/LTD/LT3.. any ideas? Thanks
louayd said:
I did already! I couldn't find recovery matching XXLTC/LTD/LT3.. any ideas? Thanks
Click to expand...
Click to collapse
Use the latest XXLTA. it should work. Go to philz thread, post #3 click the link with "tw only" written beside it
Jackwu696 said:
Use the latest XXLTA. it should work. Go to philz thread, post #3 click the link with "tw only" written beside it
Click to expand...
Click to collapse
Thanks but it did not work for the new firmware should I downgrade my firmware? I wanna install slimkat
louayd said:
Thanks but it did not work for the new firmware should I downgrade my firmware? I wanna install slimkat
Click to expand...
Click to collapse
Wow? Didn't work? Oh well find philz_touch_6.19.3-n7000, flash it, reboot to recovery (press vol +, home + power button). Do all wipes n formats, flash the rom
Sent from my GT-N7000 using XDA Free mobile app
Jackwu696 said:
Wow? Didn't work? Oh well find philz_touch_6.19.3-n7000, flash it, reboot to recovery (press vol +, home + power button). Do all wipes n formats, flash the rom
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-n7000.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:S
louayd said:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
philz_touch_6.19.3-n7000.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:9)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
:S
Click to expand...
Click to collapse
Did you tick re-partition?? I was telling you to flash it through stock recovery, then reboot to recovery Not by odin. Try the XXLTA vers. In stock recovery, too. If all fails, downgrade your rom to XXLTA
Sent from my GT-N7000 using XDA Free mobile app
louayd said:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-n7000.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:S
Click to expand...
Click to collapse
The file you trying to flash using Odin will no be successful. Use a TW based Philz kernel.
https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Edit: Please do not try to flash the .Zip in recovery.. this is just a compressed file. Unzip and you can flash this using ODIN..
I recommend a factory reset before flashing..
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It literally just came out today for the SM-G920T so my guess is this is stock.
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
tflogic said:
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
Click to expand...
Click to collapse
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
magda623 said:
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
Click to expand...
Click to collapse
according to this post, SuperSU Beta seems to be working fine.
tflogic said:
according to this post, SuperSU Beta seems to be working fine.
Click to expand...
Click to collapse
Possibly. However, there is no recovery for our device listed on the recovery page. The fact that recovery breaks the boot.img without root sounds shaky though. I'll try it a few different ways. DL is done. Flashing now.
Zaphodspeaks said:
https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Click to expand...
Click to collapse
Think I flash this on my.metro pcs version I flashed the tmobile 5.1.1 update on my metro pcs version it's basically the same phone
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is 100 percent stock.. from Sam Mobile..
Hell it came out early this morning.. No one has had the time yet to make a custom version..
I don't recommend updating from a Custom ROM..
If your 100 percent 5.1.1 Stock you can flash this with ODIN with no problems..
Oh its a Zipped .Tar file.. Don't try to flash the Zip.. Again do NOT try and flash the .Zip.. it will fail and you will be stupid to try..
https://support.t-mobile.com/docs/DOC-21138
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
i have a sm-g920t with an argentinian sim my firmware is G920TUEU3COK1. Can i use my SIM in this firm?
adidas123 said:
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Which functions? I haven't noticed anything missing so far.
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Hi,
I tried to flash this using odin but it did not work so I went ahead and used Samsung Smart Switch that automatically downloads 6.0.1 and flashes it. The process, however, failed and now the phone (G920T) is stuck on a blue screen that says, "An error has occurred while updating the system software. Use emergency recovery function in the Smart Switch PC software." (image: http://i.imgur.com/t401aO6.png). Rebooting the phone takes me to the same place. I'm, however, able to get into download mode. I have tried the emergency recovery in download mode as specified by this video: https://www.youtube.com/watch?v=mi7O0OvnS2E, but it still fails, giving me this error: http://i.imgur.com/t401aO6.png. Could someone help me get my phone working?
A few notes:
- My previous firmware was 5.1.1 stock, however, I had flashed a rooted kernel using odin.
- Within download mode, it says the following: swrev b:3 k:2 s:2
Thank you in advance.
EDIT: flashing with odin gives me this error: http://i.imgur.com/oGZiCow.png
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Click to expand...
Click to collapse
You using an older version of ODIN
Try Odin3_v3.10.7
Need help, Im looking for the latest modem and bootloader for this. Just the bootloader and modem. Thanks!
Zaphodspeaks said:
You using an older version of ODIN
Try Odin3_v3.10.7
Click to expand...
Click to collapse
Thanks. That worked. I didn't know there was a newer version available.
I don't suppose there will be a recovery-flashable version of this one, will it?
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Click to expand...
Click to collapse
Maybe try redownloading the file and unzipping again
---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------
BigDaddy38 said:
Maybe try redownloading the file and unzipping again
Click to expand...
Click to collapse
What Odin Are you using?
Hi I'm new to XDA. My Note 8 (N950U) won't boot past the Samsung Galaxy Note 8 powered by android screen.
I can access the download mode and have flashed the stock firmware. But as soon as it reboots it gets stuck on the same screen.
Any help regarding this is much appreciated
factory reset.
android-incredible said:
factory reset.
Click to expand...
Click to collapse
I cant enter the recovery to perform a factory reset
RPG-XDA said:
I cant enter the recovery to perform a factory reset
Click to expand...
Click to collapse
Flash all 4 files in Odin instead of using home-csc file use CSC file. This will erase phone. Also make sure your on the latest Odin and using the same bootloader version.
Sent from my SM-N950F using Tapatalk
BluePhnx said:
Flash all 4 files in Odin instead of using home-csc file use CSC file. This will erase phone. Also make sure your on the latest Odin and using the same bootloader version.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
I already tried flashing both the HOME_CSC and CSC separately, but it didn't work. I'm able to successfully flash the firmware, but the phone is still stuck at the powered by android screen.
Do you know what caused the issue in the first place? Was it just on stock and suddenly won't boot? Were you using Samfail or anything like that? Just trying to narrow down the issue, because flashing stock should usually work.
sefrcoko said:
Do you know what caused the issue in the first place? Was it just on stock and suddenly won't boot? Were you using Samfail or anything like that? Just trying to narrow down the issue, because flashing stock should usually work.
Click to expand...
Click to collapse
Yes, I was on stock Oreo. Haven't tried rooting it or installing custom recovery. I came across some posts on the S8 forum with the same issue, but the solution mentioned there isn't working for me.
https://forum.xda-developers.com/galaxy-s8/help/galaxy-s8-g950fd-stuck-logo-flash-t3647926
RPG-XDA said:
Yes, I was on stock Oreo. Haven't tried rooting it or installing custom recovery. I came across some posts on the S8 forum with the same issue, but the solution mentioned there isn't working for me.
https://forum.xda-developers.com/galaxy-s8/help/galaxy-s8-g950fd-stuck-logo-flash-t3647926
Click to expand...
Click to collapse
Which Odin version are you using?
sefrcoko said:
Which Odin version are you using?
Click to expand...
Click to collapse
Odin 3 v3.13.1
RPG-XDA said:
Odin 3 v3.13.1
Click to expand...
Click to collapse
Possible to show a screenshot of Odin after the flash? To see the log messages and firmware version being flashed?
sefrcoko said:
Possible to show a screenshot of Odin after the flash? To see the log messages and firmware version being flashed?
Click to expand...
Click to collapse
Firmware version: N950U1UES5CRF6_N950U1OYM5CRF6_ATT
Odin log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 6197 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> bksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> pmic.elf
<ID:0/003> rpm.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> keymaster.mbn
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> sec.dat
<ID:0/003> NON-HLOS.bin
<ID:0/003> storsec.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> adspso.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Still stuck at the same boot screen. Still wondering why the Odin flash is successful, but the phone doesn't seem to even have a recovery to boot into.
RPG-XDA said:
Still stuck at the same boot screen. Still wondering why the Odin flash is successful, but the phone doesn't seem to even have a recovery to boot into.
Click to expand...
Click to collapse
Use USB 2.0,Also try unplugging it mid flash, Then reboot the phone, Does it boot to the screen where it tells you to connect with Smartswitch?
Samsunguser932 said:
Use USB 2.0,Also try unplugging it mid flash, Then reboot the phone, Does it boot to the screen where it tells you to connect with Smartswitch?
Click to expand...
Click to collapse
I tried your suggestion and I now get the screen which tells me to connect to smart switch. But when I run Smart Switch, it says the connected device cannot be recognized and Emergency recovery mode doesn't list the phone
RPG-XDA said:
I tried your suggestion and I now get the screen which tells me to connect to smart switch. But when I run Smart Switch, it says the connected device cannot be recognized and Emergency recovery mode doesn't list the phone
Click to expand...
Click to collapse
Okay, Just use ODIN then to try and restore it from that screen, Maybe that will work, Also try Smartswitch from Download mode, Make sure your drivers are installed.
Samsunguser932 said:
Okay, Just use ODIN then to try and restore it from that screen, Maybe that will work, Also try Smartswitch from Download mode, Make sure your drivers are installed.
Click to expand...
Click to collapse
I have installed all my drivers, but Smartswitch still won't detect my device. After flashing with Odin it goes back to being stuck on the Powered by android screen.
RPG-XDA said:
I have installed all my drivers, but Smartswitch still won't detect my device. After flashing with Odin it goes back to being stuck on the Powered by android screen.
Click to expand...
Click to collapse
When you flash with odin select Nand Erase from your options. then youll be able to boot if you flash WITH the AP,BL,CP and CSC
me2151 said:
When you flash with odin select Nand Erase from your options. then youll be able to boot if you flash WITH the AP,BL,CP and CSC
Click to expand...
Click to collapse
I tried using the Nand Erase option as you suggested, but it didn't change anything. I was just trying various button combinations and suddenly got the grey circle with the lightning bolt, but it wasn't charging. After some time the phone turned off and I haven't been able to get to that screen again. Any idea of what that could be?
Thats just the off mode charging(also known as low power mode)
me2151 said:
Thats just the off mode charging(also known as low power mode)
Click to expand...
Click to collapse
Oh. Didn't know that But even in that mode the phone just shows that symbol, even after I disconnect it from power.
Could this be a issue with the motherboard or is it just software, because I can still get into download mode and flash successfully?