What should I do to really have a " completely rooted N9005" ???
I need some suggestion of the "experts" about the fact that my SM-N9005 , that " seems to be rooted " ( and this is confirmed launching the app " root checker" and obtaining the result " This device has root access" ...) ...but , despite this apparent status , it provides me the following issues :
a) I cannot use CWM mode to flash any new ROM nor any other patch using .zip file ; when I try to do a flash , using the option " apply update from external storage" as in this options list :
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
it seems to start to flash but after few seconds I obtain a RED message in the bottom oif the page , like :
" E:signature verification failed"
and in yellow
--Appling Multi-CSC ...
Applied the CSC-code : XTC
Successfully applied multi-CSC
install from sdcard complete
But in reality anything happen , the sistuation is exactly the same as before ...
b) I cannot do any back up ( EFS nor other kind of back up ) ; so , every time I try to flash even using MOP ( it works, but even MOP seems to have some problem..) I get a new ROM installed but with problems... sometime the phone is blocked with the " samsung logo and the Blue led" and I need to restert it with ODIN .....and I need to reinstall all in manual mode
in order to provide to the experts additional info , here are other details
AP : N9005XXUDMJ7
CP: N9005XXUDMJ7
CSC : N9005XXDMJ4
kernel 3.4.0-201940
[email protected]#1
Wed Oct 30 16:51 ....
Build version
JSS15J.N9005XXUDMJ7
in download mode:
ODIN MODE (in red)
Product name : SM-9005
Current Binary : Samsung Official
System Status : Custom
Reacxtivation lock : OFF
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x1
Qualcom secureboot : NONE
AP SWREV : S2,T2,R2,A2,P8
Write protection : Enable
I would invite everybody able to provide any suggestion to propose some verification or even ask me any additional info to find the way to use a rooted phone as was used to do with other phones before = flash roms without this problem
Thanks in advance for any contribution
tower5 said:
What should I do to really have a " completely rooted N9005" ???
I need some suggestion of the "experts" about the fact that my SM-N9005 , that " seems to be rooted " ( and this is confirmed launching the app " root checker" and obtaining the result " This device has root access" ...) ...but , despite this apparent status , it provides me the following issues :
a) I cannot use CWM mode to flash any new ROM nor any other patch using .zip file ; when I try to do a flash , using the option " apply update from external storage" as in this options list :
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
it seems to start to flash but after few seconds I obtain a RED message in the bottom oif the page , like :
" E:signature verification failed"
and in yellow
--Appling Multi-CSC ...
Applied the CSC-code : XTC
Successfully applied multi-CSC
install from sdcard complete
But in reality anything happen , the sistuation is exactly the same as before ...
b) I cannot do any back up ( EFS nor other kind of back up ) ; so , every time I try to flash even using MOP ( it works, but even MOP seems to have some problem..) I get a new ROM installed but with problems... sometime the phone is blocked with the " samsung logo and the Blue led" and I need to restert it with ODIN .....and I need to reinstall all in manual mode
in order to provide to the experts additional info , here are other details
AP : N9005XXUDMJ7
CP: N9005XXUDMJ7
CSC : N9005XXDMJ4
kernel 3.4.0-201940
[email protected]#1
Wed Oct 30 16:51 ....
Build version
JSS15J.N9005XXUDMJ7
in download mode:
ODIN MODE (in red)
Product name : SM-9005
Current Binary : Samsung Official
System Status : Custom
Reacxtivation lock : OFF
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x1
Qualcom secureboot : NONE
AP SWREV : S2,T2,R2,A2,P8
Write protection : Enable
I would invite everybody able to provide any suggestion to propose some verification or even ask me any additional info to find the way to use a rooted phone as was used to do with other phones before = flash roms without this problem
Thanks in advance for any contribution
Click to expand...
Click to collapse
try this flash with odin http://forum.xda-developers.com/showthread.php?t=2567283
I does not work.....
jaythenut said:
try this flash with odin http://forum.xda-developers.com/showthread.php?t=2567283
Click to expand...
Click to collapse
first of all , thanks for your support
but I tried , without success , to flash this with odin ; ( I used odin 3.04 ) ; it remains " waiting" for a very long time ( 15 minutes..) without any action , any flash....
I did the test twice, same result....
Any other suggestion?
what could I do to do a deep cleaning of some wrong setting ?
tower5 said:
first of all , thanks for your support
but I tried , without success , to flash this with odin ; ( I used odin 3.04 ) ; it remains " waiting" for a very long time ( 15 minutes..) without any action , any flash....
I did the test twice, same result....
Any other suggestion?
what could I do to do a deep cleaning of some wrong setting ?
Click to expand...
Click to collapse
Strange that your phone shows "Qualcomm Secureboot: None"
In other phones it should be "Qualcomm Secureboot: Enable (CSB)"
tower5 said:
...
in download mode:
ODIN MODE (in red)
Product name : SM-9005
Current Binary : Samsung Official
System Status : Custom
Reacxtivation lock : OFF
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x1
Qualcom secureboot : NONE
AP SWREV : S2,T2,R2,A2,P8
Write protection : Enable
...
Click to expand...
Click to collapse
Your phone seems to have a peculiar setting on secureboot + SWREV configuration, and also seems to be on the (original ?) XTC (Philippines) CSC.
One of the things that I would try (given that your knox is already 0x1) would be to change CSC and write BTU MI7 firmware (and eventually check if CSC actually changed from XTC to BTU). After that you should try again writing Philz recovery.
Another thing to check would be your current bootloader version (and also the bootloader after you write BTU MI7 firmware), the command in adb is:
adb shell getprop ro.boot.bootloader
(or just "getprop ro.boot.bootloader" in a terminal prompt directly on the phone).
I found the solutions !!!!
xclub_101 said:
Your phone seems to have a peculiar setting on secureboot + SWREV configuration, and also seems to be on the (original ?) XTC (Philippines) CSC.
One of the things that I would try (given that your knox is already 0x1) would be to change CSC and write BTU MI7 firmware (and eventually check if CSC actually changed from XTC to BTU). After that you should try again writing Philz recovery.
Another thing to check would be your current bootloader version (and also the bootloader after you write BTU MI7 firmware), the command in adb is:
adb shell getprop ro.boot.bootloader
(or just "getprop ro.boot.bootloader" in a terminal prompt directly on the phone).
Click to expand...
Click to collapse
the solution was :: " apply " what is indicated in this post
http://forum.xda-developers.com/showthread.php?t=2567133
tower5 said:
the solution was :: " apply " what is indicated in this post
http://forum.xda-developers.com/showthread.php?t=2567133
Click to expand...
Click to collapse
Interesting, what firmware do you have now? And how are the switches listed in download mode? And what CSC do you have now? Do you have your IMEI back and is the phone registered on the network (and you can make/receive calls)? Is WiFi also working OK?
Hello,
I have a perfectly working phone, that doesn't want to enter into download mode. From what I've seen in other threads, it seems to be related to the laf partition. Another user with a similar problem gave me this link:
http://downloads.codefi.re/shelnutt2/g2/fixlaf/
I downloaded the version for my device (D802) but TWRP refuses to flash it:
"assert failed: run_program( " /system/bin/sh" , " /data/local/tmp//revert_aboot.sh" ) == 0
E : Error executing updater binary in zip ' /sdcard/fixlaf_d802.zip '
Error flashing zip ' /sdcard/fixlaf_d802.zip '
Updating partition details...
Any ideas? I want to go back to a 100% stock rom, I need Download mode for that.
Thanks!
CaraMuuu said:
Hello,
I have a perfectly working phone, that doesn't want to enter into download mode. From what I've seen in other threads, it seems to be related to the laf partition. Another user with a similar problem gave me this link:
http://downloads.codefi.re/shelnutt2/g2/fixlaf/
I downloaded the version for my device (D802) but TWRP refuses to flash it:
"assert failed: run_program( " /system/bin/sh" , " /data/local/tmp//revert_aboot.sh" ) == 0
E : Error executing updater binary in zip ' /sdcard/fixlaf_d802.zip '
Error flashing zip ' /sdcard/fixlaf_d802.zip '
Updating partition details...
Any ideas? I want to go back to a 100% stock rom, I need Download mode for that.
Thanks!
Click to expand...
Click to collapse
Up!
For anybody interested, probably we will get an answer here, we will see!
https://plus.google.com/118339857242349748059/posts/2t2TMncsokV
So, I fudged up here. I installed a BUMPed KK bootloader thinking my kernel and recovery were BUMPed. Was using Render Kernel, turns out the Lollipop version is BUMPed, not KK. Good job, me! Got secure boot error loop and I still had TWRP, so I flashed the JB baseband. No boot. Tried to restore a backup I had (Mahdi + Render). No boot. Well, might as well use LG Flash Tools to go back to stock. Like I haven’t done it 80 times before….Failed! Failed! Failed! . . . Failed! (I can’t remember how many times I’ve tried).
I’ve tried every which way and LG Flash Tool gives me this:
PID: NULL
IMEI: NULL
Model :
DLL : D800
BIN : LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot
SWV :
SWOV :
Model Information Check FAIL!
00000000
So, am I royally screwed?
Si me lo puedieran explicar en español mejor:l
I'm in the same boat. Did you ever solve this?
Hi Guys,
I have a problem here. I flashed a custom ROM on my note 3 yesterday ( Euphoria ). Anyway now I am having some trouble ( after rebooting the phone ). It will consistently move into the error state :
" Firmware encountered a problem.... etc "
I can boot into download mode, and I attempted via Odin to flash a recovery file ( TWRP,PhilZ,CWM etc ), but it keeps failing. I figured then to download the stock firmware, but I am not quite sure which region the phone is on. Can I download any stock SM-N9005 firmware and try to apply it ? I did try to flash a HK stock firmware, but I got this error "
" aboot.mbn
FAIL (AUTH "
On the phone I get :
SW REV CHECK FAIL: [aboot]Fused 3 > Binary 1
I believe this relates to the firmware ? But I am unsure which firmware file to use as I am unsure of the phones original region.
What else could I do from here ?
vira4783 said:
Hi Guys,
I have a problem here. I flashed a custom ROM on my note 3 yesterday ( Euphoria ). Anyway now I am having some trouble ( after rebooting the phone ). It will consistently move into the error state :
" Firmware encountered a problem.... etc "
I can boot into download mode, and I attempted via Odin to flash a recovery file ( TWRP,PhilZ,CWM etc ), but it keeps failing. I figured then to download the stock firmware, but I am not quite sure which region the phone is on. Can I download any stock SM-N9005 firmware and try to apply it ? I did try to flash a HK stock firmware, but I got this error "
" aboot.mbn
FAIL (AUTH "
On the phone I get :
SW REV CHECK FAIL: [aboot]Fused 3 > Binary 1
I believe this relates to the firmware ? But I am unsure which firmware file to use as I am unsure of the phones original region.
What else could I do from here ?
Click to expand...
Click to collapse
Try any rom if your phone is not hg. Try plan or German.
kenny1991 said:
Try any rom if your phone is not hg. Try plan or German.
Click to expand...
Click to collapse
Well I downloaded a Poland firmware and I keep getting an error relating to the system.image.ext4.
Tried various PIT files but still no luck
it happened that I restored my phone's stock rom through a nandroid backup that I had before the first time I flashed a custom ROM, then I did the unforgivable mistake to allow an OTA update, so the phone restarted and stuck at CWM every time I retsart it. I did some search and found that this can be solved by flashing the stock rom using KDZ. So, my problem now is that every time I run the KDZ updater I get the "PHONE WAS NOT FOUND" error message. I downloaded and installed the official driver provided on LG's website but still nothing new. So, anyone has an idea on how this is fixed?
Note: The phone IS IN emergency mode so this not the problem here.
Note: I gave it a try on both windows 8.1 and windows 7
The updater's log:
[R&D Test Tools Log File]
10:51:13 : Launching SW update
10:51:13 : Unpacking KDZ
10:51:26 : KDZ file extraced
10:51:31 : Files were extracted.
10:51:31 : LGMobileDL Load.
10:51:31 : Port = -2
10:51:31 : Connecting to phone
10:51:31 : PHONE WAS NOT FOUND!
10:51:33 : ===FINISHED===