Hi All,
I've managed to break my phone and need some helps.
Background info:
I own a Samsung GT-i9305 which I purchased from Optus (Australian carrier) a few months ago. When I first got the phone I installed CF root, TWRP and a custom rom (illusion_i9305-2.6.stable-OFFICIAL). Everything was fine and dandy until a few days ago when the phone started randomly restarting every time I pressed the power/lock button. After researching the issue I found that the power button was simply stuck and only needed a light tap to fix the issue, (This is were Sh!t hit the fan) However because of my ignorance and lack of knowledge I automatically assumed it was the custom rom, so I began flashing everything until my phone was no longer functional. (My flash counter is 14 currently)
Issue: My phone no longer boots a ROM and have had some weird errors within TWRP that don't make sense to me (hoping someone with more knowledge than I can assist)
Errors:
Unable to mount system (when installing a rom, please note: this has only occurred twice and seems to be intermittent)
Work done to device: (using Odin v03.7)
Multiple flashes of CF root
Multiple flashes of TWRP & CWM
Multiple attempts at installing custom .zip Roms within TWRP (I prefer TWRP over CWM)
- You get the basic idea, frantically flashing everything to try and fix the issue. -
Current issue:
I've currently got TWRP 2.6.3.0 on the phone but when I install a custom ROM it doesn't boot, only stays on the loading screen.
NOTE: I performed a full wipe on the phone and a full wipe after installing the custom ROM but it still wont boot
ROM: illusion_i9305-2.6.stable-OFFICIAL (only because it worked)
I've tried to include all the information I can however if you need more info just ask. I'm looking for a way to either reset my phone to the stock ROM (with a download link, as the ones i've tried are horribly slow) or an alternative way to fix my issue. Clear instructions are much appreciated.
EDIT:
- I have downloaded "I9305XXBMA5_I9305OPSBMA1_OPS.zip" and extracted the .tar.md5
- I received the below error when trying to flash the stock Optus image to the device
ODIN LOG:
<OSM> Please wait..
<OSM> I9305XXBMA5_I9305OPSBMA1_I9305XXBLL5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<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> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> __Xmit Write fail
<ID:0/006> XmitData Fail..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
RESOLVED!
Solution:
Flash Stock ROM I9305XXALI5_I9305OPSALI5_OPS (Optus Aus ROM 4.1.2)
Changing to an earlier firmware version resolved all issues. This thread can now be closed.
Hello everyone!
After browsing the forums and reading through some of the information available on bricked Galaxy Note N7000 devices, I decided to post a thread about my specific issue, given that it happened spontaneously, on a device which was never modded/rooted in any way, and which has been kept gingerly for almost four years! I will provide a brief, step-by-step overview of the issue as well as the different attempts at addressing it that have already been undertaken, in the hope that some of you will be so kind as to give me your opinion on what I could do next!
- A couple days ago, I received a phone call, and, as usual, I connected my headphones to the device. I immediately heard a crackling noise from them, as the device rebooted itself.
- I noticed that the device was stuck on the Samsung Galaxy Note GT - N7000 black and white logo. As a result, I tried turning it off, and connecting it to my charger. The grey battery icon popped up, and was quickly substituted by the green "charging" icon with moving dots. After a few minutes, I tried turning on the phone again, and it was stuck on the splash screen once more.
- I tried going into the recovery menu, which I successfully did, and, upon rebooting from it, the phone moved past the splash screen to the pink and purple Samsung animated logo; that was quickly followed by a screen I had never seen before, a password bar, and the message "Enter password to use encrypted device storage". Not knowing what to do, I turned off the device.
- the next logical step was to contact Samsung Italy, and I was told to try wiping cache and data from the recovery menu and attempt a restore to factory settings. Nothing particular happened, as the phone got once again stuck on the Note splashscreen, and the recovery menu showed a series of red lines, containing information such as:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system ((No such file or directory))
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
- Next step was to take the phone to a local repair shop, where I was told that flashing the firmware was really my only option, given the functioning download and recovery menus; I left the phone with the technician, who called me later in the evening asking me if the phone was still under warranty. I told him there was no warranty, so he attempted to install a custom recovery menu via Odin, namely the following versions of PhilZ: PhilZ-cwm6-XXLSZ-OXA-4.93.6.tar and PhilZ-cwm6-XXLTA-ATL-5.15.0.tar. Upon seeing the failed install, he decided to wait for the firmware to finish its download (abysmal connection speeds in my area) and try flashing it.
- The following morning, I joined the technician in his office as he showed me that the phone could now no longer access recovery mode, seeing as the custom recovery install failed, and the flash attempt counter had gone up to three (like I mentioned earlier, I took great care not to do anything too fancy with this phone, seeing as it's my work phone), with a yellow warning sign appearing under the splash screen.
- The technician's attempt to install stock firmware (N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5) was met with failure. Odin fails at the "NAND Write" step, as shown by the following log (I replicated it at home):
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> cache.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- attempting to install a PIT file via Odin to repartition the device (filename: Q1_20110914_16GB) was also met with failure (the error message said something like "failed to repartition"), but, as I didn't pay enough attention to the steps taken by the technician to be able to replicate the operations at home - like I said, I've never done this before.
To sum up, the phone is showing the following symptoms:
- battery icon not changing from grey to green
- stock recovery menu not accessible due to a failed attempt at installing a custom recovery menu (+3 custom flash counter)
- yellow triangle on splash screen, where the device remains stuck indefinitely
- download mode still accessible, device recognized by Odin, firmware flash fails at NAND Write Start
I really hope some of you will be able to give me your two cents on how to proceed! Thank you in advance for any and all help!
Lightside
Sounds tough, but you did right by pouring everything you know on the problem here.
First I'd try to use the stock partition available here: http://forum.xda-developers.com/showthread.php?t=2642299
Then look for a PhilZ recovery in this forum to Odin flash.
If it works, then proceed to flash a stock rom via recovery.
If not, then try the partition method with a stock rom. I used the guide provided in the link above and it worked flawlessly.
I'd wait for other members to pour in their thoughts on this if they're gracious enough but you're still welcome to try this
AutumQueen92 said:
Sounds tough, but you did right by pouring everything you know on the problem here.
First I'd try to use the stock partition available here: http://forum.xda-developers.com/showthread.php?t=2642299
Then look for a PhilZ recovery in this forum to Odin flash.
If it works, then proceed to flash a stock rom via recovery.
If not, then try the partition method with a stock rom. I used the guide provided in the link above and it worked flawlessly.
I'd wait for other members to pour in their thoughts on this if they're gracious enough but you're still welcome to try this
Click to expand...
Click to collapse
Hello, and thank you for your advice! I have just tried flashing the pit file provided in the thread you linked, and this is the Odin log:
<ID:0/012> Added!!
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: I've tried every Odin version I could get my hands on, and attempted using all 5 custom pit files. I even tried reflashing PhilZ-cwm6-XXLTA-ATL-5.15.0.tar, to no avail. Have I exhausted all my options?
Lightside said:
Hello everyone!
After browsing the forums and reading through some of the information available on bricked Galaxy Note N7000 devices, I decided to post a thread about my specific issue, given that it happened spontaneously, on a device which was never modded/rooted in any way, and which has been kept gingerly for almost four years! I will provide a brief, step-by-step overview of the issue as well as the different attempts at addressing it that have already been undertaken, in the hope that some of you will be so kind as to give me your opinion on what I could do next!
- A couple days ago, I received a phone call, and, as usual, I connected my headphones to the device. I immediately heard a crackling noise from them, as the device rebooted itself.
- I noticed that the device was stuck on the Samsung Galaxy Note GT - N7000 black and white logo. As a result, I tried turning it off, and connecting it to my charger. The grey battery icon popped up, and was quickly substituted by the green "charging" icon with moving dots. After a few minutes, I tried turning on the phone again, and it was stuck on the splash screen once more.
- I tried going into the recovery menu, which I successfully did, and, upon rebooting from it, the phone moved past the splash screen to the pink and purple Samsung animated logo; that was quickly followed by a screen I had never seen before, a password bar, and the message "Enter password to use encrypted device storage". Not knowing what to do, I turned off the device.
- the next logical step was to contact Samsung Italy, and I was told to try wiping cache and data from the recovery menu and attempt a restore to factory settings. Nothing particular happened, as the phone got once again stuck on the Note splashscreen, and the recovery menu showed a series of red lines, containing information such as:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system ((No such file or directory))
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
- Next step was to take the phone to a local repair shop, where I was told that flashing the firmware was really my only option, given the functioning download and recovery menus; I left the phone with the technician, who called me later in the evening asking me if the phone was still under warranty. I told him there was no warranty, so he attempted to install a custom recovery menu via Odin, namely the following versions of PhilZ: PhilZ-cwm6-XXLSZ-OXA-4.93.6.tar and PhilZ-cwm6-XXLTA-ATL-5.15.0.tar. Upon seeing the failed install, he decided to wait for the firmware to finish its download (abysmal connection speeds in my area) and try flashing it.
- The following morning, I joined the technician in his office as he showed me that the phone could now no longer access recovery mode, seeing as the custom recovery install failed, and the flash attempt counter had gone up to three (like I mentioned earlier, I took great care not to do anything too fancy with this phone, seeing as it's my work phone), with a yellow warning sign appearing under the splash screen.
- The technician's attempt to install stock firmware (N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5) was met with failure. Odin fails at the "NAND Write" step, as shown by the following log (I replicated it at home):
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> cache.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- attempting to install a PIT file via Odin to repartition the device (filename: Q1_20110914_16GB) was also met with failure (the error message said something like "failed to repartition"), but, as I didn't pay enough attention to the steps taken by the technician to be able to replicate the operations at home - like I said, I've never done this before.
To sum up, the phone is showing the following symptoms:
- battery icon not changing from grey to green
- stock recovery menu not accessible due to a failed attempt at installing a custom recovery menu (+3 custom flash counter)
- yellow triangle on splash screen, where the device remains stuck indefinitely
- download mode still accessible, device recognized by Odin, firmware flash fails at NAND Write Start
I really hope some of you will be able to give me your two cents on how to proceed! Thank you in advance for any and all help!
Lightside
Click to expand...
Click to collapse
OMG this is the condition of my GS2 , my note is perfect, im trying something tomorrow, will let you know
coko___bear said:
OMG this is the condition of my GS2 , my note is perfect, im trying something tomorrow, will let you know
Click to expand...
Click to collapse
At this point, I appreciate any and all help, so thanks for replying
Up?
Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 and 3.12.3 but in the two cases it fails with this error :
Code:
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )
Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 , 3.11 and 3.12.3 but in the two cases it fails with this error :
Code:
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )
(whitch version i should use to flash 920F or V or A ? )
My phone will keep itself stuck in reboot.
I can 3 button it to get to the downloading screen or the blue options screen.
In the downloading screen, I am able to connect Odin. I tried ADP to firmware and twrp...both failed (multiple times).
On start, it shows blue script reboot...then dead android with red exclamation triangle...then to the blue script menu. From this, I have tried:
- reboot (arrives back at same screen)
- reboot to bootloader
- apply update from SD card...says can not mount card (I tried loading disk image onto SD card to reflash that way)
- wipe data/factory reset...tries and quickly fails - something or other found, stays stuck
- clear cache...seems to do that and then leave me at the same screen
- mount system - asks me to do something that I do not at all understand
I tried downloading Kies3...it says it can not help me because I do not have a code from the old computer...?
I also tried downloading dr.phone.
Nothing seems to help.
I found out about Odin, firmware, twrp, windowsdiskimager, etc. ALL FROM THIS SITE... So, I am trying my best to understand all of this terminology and the processes.
However, after spending all day trying to solve this, I am feeling totally stumped...
Please help : )
Screen presently reads:
Android Recovery
MMB29M.N910T3UVU3EQC1
samsung/trltetmofrp/trltetmo
6.0.1/MMB29M/N910T3UVU3EQC1
user/release-keys
Use volume up/down and power
Reboot system now
reboot to bootloader
apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Power off
_____
Supported API: 3
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
-------------------------------------------------------------
After trying Odin (3.09) and twrp (twrp-3.0.2-0-trltetmo.img.tar), this is the screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FAP LOCK: ON
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
Custom Binary(recovery) Blocked by FAP Lock
...android image
downloading...
Do not turn off target!!
------------------------------------------------------------
ODIN LOG:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have fixed mine with same symptoms.
After two years of intensive use my n910t stuck at boot logo .
I heated the emmc with hot air and voila the phone booted normally just i broked my front cam
I downgraded to official lollipop version to get more battery life and much cooler cpu in my opinion !