got a little overzealous with some settings and made it so my phone doesn't boot past the Verizon screen. I wiped cache and didn't help, factory reset, didn't work. Tried to flash back to 0k3, finally tried to flash back to pb1. When I try pb1, it hangs at the samsung animation and when I go into recovery mode it still says system recovery is 0k3. Every rom I try to flash does not change that so I dont think my falshes are actually flashing. I'm using odin 3.10. I really just want a complete clean re-install, but cant seem to figure out how to get that to work. It's probably something very easy, but I cant find a thread that sounds 100% similar
So everything during Odin flashes looks normal, but it still doesn't take? This is very strange behavior.
Try using another USB cable/port, and if you have access to one, another computer.
Odin logs? Screenshots? Not really enough information. Maybe find a new .tar.md5?
Everything looks like it flashes normal. I've used the same files on a different device with same files and hardware and that's worked fine. It passes but when I reboot to softloader it's still ok3
kinsleia said:
Everything looks like it flashes normal. I've used the same files on a different device with same files and hardware and that's worked fine. It passes but when I reboot to softloader it's still ok3
Click to expand...
Click to collapse
Is Reactivation Lock enabled?
Nandr0idC0nsumer said:
Is Reactivation Lock enabled?
Click to expand...
Click to collapse
Its not something I've ever set and I don thave an account with Samsung. Would Odin report a "Passed" flash if it were set? I guess I'm screwed if it did get activated somehow, right?
kinsleia said:
Its not something I've ever set and I don thave an account with Samsung. Would Odin report a "Passed" flash if it were set? I guess I'm screwed if it did get activated somehow, right?
Click to expand...
Click to collapse
In Download Mode, it will say
Code:
REACTIVATION LOCK (KK): OFF
or
Code:
REACTIVATION LOCK (KK): ON
Nandr0idC0nsumer said:
In Download Mode, it will say
Code:
REACTIVATION LOCK (KK): OFF
or
Code:
REACTIVATION LOCK (KK): ON
Click to expand...
Click to collapse
Okay, its off, so not that.
Rest of info in that screen is
Product Name: SM-g900v
Current bin: Samsung official
System Status: custom (not sure what that means but it does display "Custom" with a big unlocked lock when booting, but it was doing that before it stopped working)
Qualcomm Secureboot: Enable (CSB)
rp swrev: s1, t2, r1, a2, p1
Secure Download enable
UDC start
here is my Odin log, not that I see anything unusual here:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
kinsleia said:
Okay, its off, so not that.
Rest of info in that screen is
Product Name: SM-g900v
Current bin: Samsung official
System Status: custom (not sure what that means but it does display "Custom" with a big unlocked lock when booting, but it was doing that before it stopped working)
Qualcomm Secureboot: Enable (CSB)
rp swrev: s1, t2, r1, a2, p1
Secure Download enable
UDC start
Click to expand...
Click to collapse
Try downloading the full stock PD1 Marshmallow tar from sammobile and flashing that thru odin (slow download sry)
Nandr0idC0nsumer said:
Try downloading the full stock PD1 Marshmallow tar from sammobile and flashing that thru odin (slow download sry)
Click to expand...
Click to collapse
Will I still be able to root with stock pd1?
What is your CID? 15 or 11
Having trouble getting adb commands to work. Can only seem to get it recognized if I go into "apply update from ADB" and then its only sideloaded and flashboot just "waits for device." is their another way I can get that info without being able to boot the device up fully?
kinsleia said:
Having trouble getting adb commands to work. Can only seem to get it recognized if I go into "apply update from ADB" and then its only sideloaded and flashboot just "waits for device." is their another way I can get that info without being able to boot the device up fully?
Click to expand...
Click to collapse
Okay, so download finished and I applied it, had to reboot several times but it did come up and is now on PD1. So I guess now my question is there a way to root right from where I am, or do I have to downgrade
Related
So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.
No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4
Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.
Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?
Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.
Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4
Hy, I own an S5 G900F. I flashed a stock rom latest version then my S5 root before flashing a rom Omega 2. Everything worked perfectly until I decided to change my sdcard having taken care to move all the files present on my old sd card on news.
At start of my S5 nothing worked, I have the screen that lights up with the SAMSUNG GALAXY S5 logo, powered by ANDROID but the top right I have the following message in red: kernel is not enforced seandroid and yellow: set warranty bit kernel.
I can not switch to recovery since disappeared, I just can enter download mode.
With odin so I tried to flash my S5 with stock rom (XEF-G900FXXU1ANE2-20140519102224).
Here is the odin message when I load this rom:
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> 900FXXU1ANE2_G900FOXX1AND3_G900FXXU1ANE2_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully
<OSM> ..
<OSM> Leave CS.
My S5 is well recognized by odin, it tells me blue com port 3 and
<ID:0/003> Added!
Top right of the screen of my S5 I have these messages:
ODIN MODE
PRODUCT-NAME: SM-G900F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
LOCK REACTIVATION (KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CBS)
SWREV RP: S1, T1, R1, A1, P1
UDC: START
I run flash with odin:
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
The flash stops with S5 on the screen messages:
MMC: mmc_read fail
ODIN: flash read failure
I do not know what to do! Is it a hardware brick or a simple software problem??
Thank you for trying to help me if it is possible. I hope to have been clear
best regards,
Sorry for my english, this is a google translation
Not bricked but you need to flash a pit file along with the firmware, look here http://forum.xda-developers.com/showthread.php?t=2737448 for the correct pit file or how to extract one if yours isn`t listed (need root for that).
Thank you for your quick response but I already tried to flash the pit with odin without success always with the same message MMC: mmc_read fail etc ...
SM-G900F_pit_16GB.zip (fail)
SM-G900F_pit_16GB_SER.zip (fail)
SM-G900F_pit_16GB_ETL.zip (fail)
Something, some glitch apparerently corrupted your kernel. And that (probably subsequently) corrupted your partition structure. You are soft bricked at this point.
As gee2012 suggested, you now need to flash both the PIT and a full stock image. Stop trying to flash random PIT files or you may end up hard bricked. You need to identify the correct PIT and use that one. The PIT file should match your phone model, original carrier (i.e. match your baseband) and ROM size.
Flash the correct PIT in conjunction with a full stock Odin image from the matching carrier. Note that stock firmware is flashed as a tar file, but the PIT file needs to be flashed as a PIT file, if you are trying to flash it while it's still zipped that alone will cause it to fail.
.
i having the same problem
i'm having the same problem with my sm-g3502L, i have the corect pit file and the correct rom, but always failed, please someone help me, its very important
Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else happens.
I have tried to flash the firmware again using a different PC, USB cable and even Odin version but I get the same result. Previously my device was running Android 4.3 and I wanted to upgrade to Android 4.4.2.
Here is what I get from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
--------------------------------------------------------------------------------------------------
And this is what I get when I enter download mode on my phone:
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWEREV: S2, T2, A2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
------------------------------------------------------
So you know, I have even tried flashing a number of custom recoveries such as CWM and the likes to no avail, I either get: "RECOVERY IS NOT SEANDROID ENFORCING" or "COULD NOT DO NORMAL BOOT".
Please help me out guys, I have flashed countless Samsung devices with Odin before but I have never encountered such a situation, what could be the problem here? And better yet, how can it be fixed?
edutchz said:
Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else happens.
I have tried to flash the firmware again using a different PC, USB cable and even Odin version but I get the same result. Previously my device was running Android 4.3 and I wanted to upgrade to Android 4.4.2.
Here is what I get from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
--------------------------------------------------------------------------------------------------
And this is what I get when I enter download mode on my phone:
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWEREV: S2, T2, A2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
------------------------------------------------------
So you know, I have even tried flashing a number of custom recoveries such as CWM and the likes to no avail, I either get: "RECOVERY IS NOT SEANDROID ENFORCING" or "COULD NOT DO NORMAL BOOT".
Please help me out guys, I have flashed countless Samsung devices with Odin before but I have never encountered such a situation, what could be the problem here? And better yet, how can it be fixed?
Click to expand...
Click to collapse
Hi bro i have exactly the same problem and try to flash cystom recovires and i tried to back to 4.3 byt odin give me fail
So please if you solve it tell how
try this
1. Boot to recovery, turn off the phone then press Home +
Power + Volume up
2. wipe data / factory reset
3. Wipe Cache partition
4. Remove battery and put it back after 30 seconds
5. Boot to Download Mode, turn off the phone then press
Home + Power + Volume Down then volume up
6. Flash Firmware via ODIN be sure uncheck
AUTO REBOOT and wait to be completed
7 when odin show message 'pass' unplug the cable and Remove battery again and put it back after 30 seconds
8 now switch on the mobile but don't restart it just goto to recovery mode agAin and and follow the the step 1 and 2 again
then reboot
your problem solved
its just like downgrading of mobile but it work
(if this not work the try to install custom recovery like cwm)
note: I am not responsible for any harm or brick of your mobile try it own your risk
this step are my opinion not recommendations
but I had test this method for same problem)
@android_smater bro it's won't boot to recovery at all that is the problem
altayeb hoota said:
@android_smater bro it's won't boot to recovery at all that is the problem
Click to expand...
Click to collapse
does it go automatically into download mode or just hang on when samsung galaxy grand 2 sm-g7102 apper
try to install cwm and then goto recovery mode
android_smater said:
does it go automatically into download mode or just hang on when samsung galaxy grand 2 sm-g7102 apper
try to install cwm and then goto recovery mode
Click to expand...
Click to collapse
i tried to install cwm or twrp but still nothing happen just galaxy grand2 sm-g7102 logo with blue text"recovery booting at the top"
i can't access recovery with stock recovery or any custom recovery at all
and also i can't be able to flash android 4.3 odin gives me "fail" but kitkat flashed fine but when it finished i got the same problem
edutchz said:
Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else
try to downgrade to NH6 use my thread it will work
http://forum.xda-developers.com/galaxy-grand-2/general/how-to-downgrade-to-nh6-t2913368
Click to expand...
Click to collapse
then take your mobile to service centre. .
please help me.i have this problem with grand 2
i dont know how can i fix it...please tell me..if you resolved.
For anyone who still has this problem on their Galaxy Grand 2, apparently I never found a way to fix it. But after giving up on the phone and giving it to my cousin, he was more patient than me and he left the phone powered on while stuck on the Logo screen and after say 30 minutes to 1 hour the phone booted up.
The phone works normally, however should you power it down..turning it on again will take it roughly 30 mins to an hour to get past the initial Logo screen, am not sure why but that is how it now behaves.
Try connecting it to a charger while you wait for it to boot, hopefully it will work for you as well.
Thanks
I no how to fix the problem is i think u have not downloaded of ur region
Same damn problem here
Problem seems to be related to fake Samsung Phones. I went to the Samsung assistance centre in Guangzhou (China) and they felt quite embarrassed to tell me that although I may accept to pay any fee they charge they cannot fix my phone because it is not made by Samsung and that is easily the reason why it has a faulty boot manager, probably hacked by incompetents.
Either the phone is fake or the official Samsung Service centre here is, in any case there seems to be no way around it.
I a looking now for some way to reload the original boot loader and then restart from there.
I am having exactly this same problem. I actually installed a Custom ROM from here, but the ROM had some bugs and I later decided to go back to the official firmware from Smasung, only to get stuck on the Samsung boot.
i am here with the same problem with some minor changes
my galaxy grand 2 duos showing
Could not do normal boot.
ODIN MODE
PRODUCT NAME:SM G 7102
CURRENT DINARY:Custom
SYSTEM STATUS:Custom
KNOX WARRANTY VOID:0*0
QUALCOMM SECUREBOOT:Enable <CSD>
RP SWREV: S2, T2,R2,A2,P2
SECURE DOWNLOAD:ENABLE
UDC START
AFTER A BIG GREEN ANDROID LOGO
Downloading...
Do not turn off target!!
Has anyone found solution yet? I'm having same problem with my Grand 2 Duos.
only download mode is working. Can't boot to recovery or normal.
After leaving in charging for 15-20 mins, I got white flash-logo( something new then ever).
So keeping it in charging for more time. let's see...!
PS: phone starts with grand 2 logo and then samsung comes up with audio. that's it ! after 3-4 mins later reboots and so on.
in recovery mode it shows android symbal and loading bar.. then it reboots in normal mode. and so on.
I guess you guys have downloaded a wrong firmware. I mean, sure it says it's for Grand 2 but the "Region" is different. Try downloading the one for your region like if you are from India, you gotta need indian version that is INS.
Sent from my SM-G7102 using Tapatalk
My SM G7102 does not go to download mode or recovery mode! It keeps restarting automatically after inserting battery! If i somehow go to recovery mode or download mode i would repair this . Please anyone help about this
oodjacid said:
My SM G7102 does not go to download mode or recovery mode! It keeps restarting automatically after inserting battery! If i somehow go to recovery mode or download mode i would repair this . Please anyone help about this
Click to expand...
Click to collapse
take the battery out and try go in to download mode
SoUnd001 said:
take the battery out and try go in to download mode
Click to expand...
Click to collapse
It doesn't go to recovery/download mode without battery
Hello all,
Problem: my S5 SM-G900F has ''Reactivation Lock'' enabled.
ROM: XtreStoLite 2.2 (touchwiz based)
I tried to get into my recovery and it gave me Custom binary blocked by Reactivation Lock instead. It seems Reactivation Lock is enabled. This happened to me after (not directly) I had flashed XtreStoLite 2.2 ROM. The thing is that I don't remember enabling anything, and I can't find the option to disable it in this ROM either. Also I never made a Samsung account in order to enable this lock. And it looks like I need a Samsung account to disable it again. So how can I disable it if I don't have a Samsung account in the first place?
I tried to flash recovery via Odin, but that just failed. I also tried to do a factory reset from the settings menu but then settings app just crashed and nothing happens.
I really hope someone can help me... Thanks in advance!
Flash a stock Kitkat ROM with ODIN from sammobile dot com, instructions under the download
Log into all accounts you have, disable reactivation lock
--
Can a mod make these instructions a MASSIVE red sticky? The number of people not reading threads and asking the same question day after day is ridiculous
Flash a stock Kitkat ROM with ODIN from sammobile dot com, instructions under the download
Log into all accounts you have, disable reactivation lock
Click to expand...
Click to collapse
Thanks for your reply!
I had already flashed a lollipop version via the same way. But I see you say KitKat, and probably for a reason...
Now with the Stock Lollipop ROM which I flashed:
-In download mode I can see Reactivation Lock is ON.
-It shows a Samsung icon to add an account in account settings. But selecting it results in nothing.
-Factory reset doesn't work. Results in endless loop <next> <next>....
-In settings>security Reactivation Lock can't be disabled. It just turns itself on automatically.
I'm downloading a KitKat version now. Hope that solves the problem.
Lollipop doesn't work, needs to be KitKat
*Detection* said:
Lollipop doesn't work, needs to be KitKat
Click to expand...
Click to collapse
Downloading took forever (200kb/s)... But I've the file now. Tried to flash it via Odin. All great, but near the end it fails to complete...
I tried twice. This phone is from Germany, but I live in the Netherlands. I bought it with Lollipop on it, didn't need to update from KitKat first. Is there any problem in that when going to a KitKat firmware? The firmware I downloaded is one for the Netherlands, not Germany.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANH6_G900FPHN1ANH1_G900FXXU1ANG8_HOME.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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
-edit-
Seems I need a PIT file or something (for re-partitioning phone). Will try finding one...
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Disabling reactivation lock - another solution
Darkmond said:
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Click to expand...
Click to collapse
I encountered the same problem with the reactivation lock after flashing xtresolite (lollipop) onto my g900f. I followed the steps to download the stock KK rom, flash from Odin and reboot. At this point I got stuck on the boot screen (not boot-loop) indefinitely (until 2% battery). After flashing KK, removing battery and reinserting it I was then able to boot into the stock recovery. I did a factory reset and wiped the cache and rebooted. The phone now boots normally into stock KK rom and I was able to deactivate the reactivation lock using my samsung account. Hope this helps anyone with a similar issue.
please help me with my s6 g920a, I can't find any kitkat firmware.
/
Darkmond said:
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Click to expand...
Click to collapse
Another easy solution can be found here:
[Guide] Unlock FRP / Deactivate Reactivation lock, Root and recovery for Samsung
Hi,
I managed to be brick free since I started reading XDA Developers & modifying my devices starting with my XDA Mini in 2008. Now 6 devices later I finally managed to - hopefully just soft - brick my Note 3 (hlte)
I bet if I search long enough I could try to recover it on my own, and i did so the lasst 15 years, but I am a bit scared now, I really fear to loose the last thread this phone is hanging on, so please hear me out and maybe its an easy problem for the more expiereinced users out there.
Situation before the update:
* rooted
* cwm recovery - latest version
* cm11 latest snapshot
* Encryption enabled
The update:
- Used adb sideload method to load cm12.1 latest nightly
- Phone booted fine, just was completely misconfigured (Xposed not working, root apps lost root access, etc.)
- Wanted to go to recovery, but recovery stopped working. Phone just showed shortly it goes to recovery, then black screen
- So I factory resetted the phone via normal CM settings.
- Everything was fine, I started to install apps and was happy.
- Phone is currenlty NOT encrypted anymore
- I totally forgot to fix the not working recovery mode *DOUH*
- Then I changed the DPI settings in build.prop to 320 as it was under cm11
- Phone never rebooted.
The situation now:
- Phone does not boot normally, shows black screen right after boot mode details in top left corner. No boot logo and such
- Phone can't enter recovery, same as with normal boot
- ADB can not see the device in either normal boot/recovery/download mode
- Download mode seems to be still working *HOPE*
So what to do now?
Can I somehow just fix the build.props?
Can I flash a new recovery using ODIN, and then format/wipe/reinstall?
Can I simply reflash CM12.1 using ODIN?
Or do I have to, as some howto suggested, flash a stock samsung rom? And which one for that matter?
Hope someone can help me,
CySlider
Update: Solved by pushing the right stock rom to the device using ODIN.
Interesting part I learned: You can flash multiple times with ODIN without rebooting the device if flashing fails. You just have to unplug and replug the cable (quickly if Battery is nearly dead). Messages on Screen might get messy with errors that the loading bar got wrong values, but it works.
Flash stock Samsung rom via Odin .
Can I somehow just fix the build.props? YES if you can see it on your phone.
JJEgan said:
Flash stock Samsung rom via Odin .
Can I somehow just fix the build.props? YES if you can see it on your phone.
Click to expand...
Click to collapse
Ok, which one, Lolipop? or Kitkat? Last stock that was installed before going to Cyanogenmod was Kitkat or even older.
Also will I loose root access this way?
Cy_the_Slider said:
Ok, which one, Lolipop? or Kitkat? Last stock that was installed before going to Cyanogenmod was Kitkat or even older.
Also will I loose root access this way?
Click to expand...
Click to collapse
If you just want a cm rom just flash a kit kat official rom.
Anyway try to go into download mode. When it asks to cancel or continue choose cancel. I saw several members mentioned the phone managed to boot that way.
And off course no root.
Sent from my SM-N920C
Rosli59564 said:
If you just want a cm rom just flash a kit kat official rom.
Anyway try to go into download mode. When it asks to cancel or continue choose cancel. I saw several members mentioned the phone managed to boot that way.
And off course no root.
Sent from my SM-N920C
Click to expand...
Click to collapse
Ok, thank you. About the tip with Cancel. unfortunately it did not help. I geuss the problem is an invalid DPI setting in the build.props and it will not changed by going to download mode first :/
Ok I will try to locate a stock rom with Kitkat.
Thank you.
No success it seams:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/012> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:1/012> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:1/012> File analysis..
<ID:0/007> SetupConnection..
<ID:1/012> SetupConnection..
<ID:1/012> Initialzation..
<ID:1/012> Get PIT for mapping..
<ID:1/012> Firmware update start..
<ID:1/012> SingleDownload.
<ID:1/012> sbl1.mbn
<ID:1/012> NAND Write Start!!
<ID:1/012> aboot.mbn
<ID:1/012> rpm.mbn
<ID:1/012> tz.mbn
<ID:1/012> sdi.mbn
<ID:1/012> NON-HLOS.bin
<ID:1/012> boot.img
<ID:1/012> recovery.img
<ID:1/012> system.img.ext4
<ID:0/007> Can't open the serial(COM) port.
<ID:1/012> modem.bin
<ID:1/012> cache.img.ext4
<ID:1/012> hidden.img.ext4
<ID:1/012> FAIL! (Size)
<ID:1/012>
<ID:1/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 2)
I used: N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_HOME.tar.md5 and set it to AP setting in ODIN 3.10.7
CAN I leave Download mode to test, if something changed? Or should I better stay in download mode to try again?
Ok, after realizing that I can not flash again without reentering the doanload mode anyway, I restarted.
It showed a new download mode with the message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I searched and found that I should use the right PIT file. I found a combination that seemed to match my device here: (german)
http://www.pocketpc.ch/samsung-gala...1800-anleitung-flashen-dbt-fw-eu-geraete.html
I did hold my breath, and...: Failed again:
<ID:0/012> Added!!
<ID:0/012> Removed!!
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOE9_N9005DBTGBOF1_N9005XXUGBOD3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<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> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> boot.img
<ID:0/012> cache.img.ext4
<ID:0/012> hidden.img.ext4
<ID:0/012> FAIL! (Size)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So, did I finally manage to hard brick? ((
I'm still in this special mode scraed frozen about powering off as I saw messages saying this is the last shot I had. COME ON!!
What I don't get is. After updating to CM12.1 didn't I got Lolipop bootloader with it? Maybe trying to put on 4.4.2 was wrong after all, b/c of downgrade?
Rop left in download mode is this info:
Product Name: SM-N9005
Current Binary: Custom
System Status: Custom
Reactivation Lock(KK): Off
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enabled
UDC START
anyone?
Cy_the_Slider said:
What I don't get is. After updating to CM12.1 didn't I got Lolipop bootloader with it? Maybe trying to put on 4.4.2 was wrong after all, b/c of downgrade?
Rop left in download mode is this info:
Product Name: SM-N9005
Current Binary: Custom
System Status: Custom
Reactivation Lock(KK): Off
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enabled
UDC START
anyone?
Click to expand...
Click to collapse
Try non DBT firmware. So you can still enter download mod?.
Sent from my SM-N920C
Rosli59564 said:
Try non DBT firmware. So you can still enter download mod?.
Click to expand...
Click to collapse
I don't know. Luckily, if I unplug and replug the USB Cable quickly, I seem to be able to flash again without the need to find out, if it will boot again.
I am currently downloading the UK version as I think to remember it was an english phone. (Got it as a present)
I just don't understand why the PIT did not fix this issue. it should have resizeed the partition anyway...
Damn I feel stressed...
Cy_the_Slider said:
I don't know. Luckily, if I unplug and replug the USB Cable quickly, I seem to be able to flash again without the need to find out, if it will boot again.
I am currently downloading the UK version as I think to remember it was an english phone. (Got it as a present)
I just don't understand why the PIT did not fix this issue. it should have resizeed the partition anyway...
Damn I feel stressed...
Click to expand...
Click to collapse
Can't you just flash a twrp and flash a CM from there?
Sent from my SM-N920C
If you tell me how to flash a twrp via odin. Sure I would try. Is this possible?
The UK Rom download finished. Lets see if htis works.
Ok, Flashing the UK BTU rom worked in the sense that ODIN did not show any errors.
When I try to start it, it starts until it asks for a password?!? then it crashes.
I can enter recovery, but when I factory reset, it does not start at all and recovery is also gone again. Only Downloadmode is luckily still available.
Have I messed up the factory reset feature by applying the PIT file for the german rom maybe?
Update: Seems I made it. The last problem now was the Batery being completely dead as it seems to not be loading while in this broken state. And the USB PC connection was not delivering enough power to survive the phone fully booting. Now its on the loginscreen and charging.
Hopefully I can put a Solved behind this topic soon. Thanks for all input!