So I just Odin Stock 4.3 and then I applied the update.zip to get it to 4.4.2. After that I tried flashing a ROM and eventually I just stupidly wiped my phone and I have no firmware on it. I went to Odin to get it back to stock 4.3 but due to Knox, I was not able to and now I'm stuck on the "Connect to kies" message. What do I do? I'm at loss here ;(. Please help. And the phone is not showing up on Odin...do I wait for Samsung to release a 4.4.2 tar?
nivekx9 said:
So I just Odin Stock 4.3 and then I applied the update.zip to get it to 4.4.2. After that I tried flashing a ROM and eventually I just stupidly wiped my phone and I have no firmware on it. I went to Odin to get it back to stock 4.3 but due to Knox, I was not able to and now I'm stuck on the "Connect to kies" message. What do I do? I'm at loss here ;(. Please help. And the phone is not showing up on Odin...do I wait for Samsung to release a 4.4.2 tar?
Click to expand...
Click to collapse
Do you have custom recovery installed?
If so just put any ROM on your SD Card, and flash that in recovery. The phone will boot right up and will be working again. From there you can do whatever you want.
Skipjacks said:
Do you have custom recovery installed?
If so just put any ROM on your SD Card, and flash that in recovery. The phone will boot right up and will be working again. From there you can do whatever you want.
Click to expand...
Click to collapse
Nope, otherwise I wouldn't be here . Stuck on that "Connect to Kies" message :/
Related
So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.
Thanks for reading.
I was on stock rooted 4.3. I went back to complete stock 4.1 using odin in order to update to 4.4. i started with the first update and installed fine but wouldnt boot past the first samsung note screen. I tried to get into recovery but no success. I can get into download mode. What else can I do to get the phone booted.
thanks!
koarthur84 said:
Thanks for reading.
I was on stock rooted 4.3. I went back to complete stock 4.1 using odin in order to update to 4.4. i started with the first update and installed fine but wouldnt boot past the first samsung note screen. I tried to get into recovery but no success. I can get into download mode. What else can I do to get the phone booted.
thanks!
Click to expand...
Click to collapse
Download this and flash in odin in the ap or pda slot
http://d-h.st/iVH
terpin32 said:
Download this and flash in odin in the ap or pda slot
http://d-h.st/iVH
Click to expand...
Click to collapse
Thank You
similar
i was running slimrom 6.8 and it was working just fine. then my work email required that i encrypt the phone. phone would not encrypt. went back to stock 4.1.2 and encrypted and was running successfully. decided to OTA update and back stuck to bootscreen.
i tried other bootloaders, but this is the only that has worked. will repeat going to stock, encrypt. no more ota for me!
unless someone knows if there is an encryption friendly rom out there?
miserly said:
i was running slimrom 6.8 and it was working just fine. then my work email required that i encrypt the phone. phone would not encrypt. went back to stock 4.1.2 and encrypted and was running successfully. decided to OTA update and back stuck to bootscreen.
i tried other bootloaders, but this is the only that has worked. will repeat going to stock, encrypt. no more ota for me!
unless someone knows if there is an encryption friendly rom out there?
Click to expand...
Click to collapse
Just do the 4.4.2 updated rom like a stock touchwiz or maybe a cm rom would be able to
my work requires encryption. i was on slimkatv22 at the time and had to encrypt. as encryption kept failing, i went back to stock. way back to stock.
so i'm running
JZO54K.I317UCAMH3 ROM
TEAMWIN Recovery
I317UCUCNE5 Bootloader
with Root and Busybox installed.
everytime i try to update via device update, it downloads, reboots and runs TWRP, I decrypt using password, reboots and the update fails with "Update Interrupted" message.
Is there a way to update ROM and keep encryption?
You can't OTA stock ROMs without stock recovery.
xBkKx said:
You can't OTA stock ROMs without stock recovery.
Click to expand...
Click to collapse
Thanks for your response. I tried updating ROM via ODIN and was not successful. Always got stuck in boot logo after i flashed new ROM.
Is there a stock recovery I should flash over TWRP to try?
Thanks for your help.
I have never used encryption so I can't really help if there are specifics around that. What exactly are you trying to install through Odin? If it's the firmware such as THIS it should overwrite the custom recovery with the stock one. If the stock ROM isn't booting you might have to boot into recovery and factory reset/wipe dalvik cache. This is my first Samsung phone so if nothing helps someone else who'd like to offer their assistance would probably be more knowledgeable.
I was going back to stock, which I guess, was mostly successful. however, I've not been able to install new ROM, namely 4.4.2 I317UCUCNE5. so if I install from your link, that should overwrite custom recovery and allow me to upgrade to 4.4.2 ROM either OTA or via Odin?
Maybe? Using the OTA always tells me there isn't an update (cause I'm on T-Mobile I guess?) and I haven't seen any files to update to Kitkat firmware through Odin
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
miserly said:
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
Click to expand...
Click to collapse
haven't had time to try. tbutbut i noticed that foxfi doesn't work even though i'm rooted. i searched for tether and doesn't seem to be a working solution for a free app.
SOLVED
finally got around to following the directions from dicksteele and voila! i'm on 4.4.2!
thanks all!
m
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip
First off, if I did this wrong(posting in this) then I'm sorry but I need some serious help.
lets begin, I flashed a rom (5.1.1) and then I used Odin to restore to (4.1.1) it worked but then I flashed a newer rom (7.0.1) and it wasn't working so I tried to flash again but in twrp custom recovery, I wiped everything off my phone accidentally, including system. My phone then wouldn't turn on, it was bricked. so after hours I created a debrick sd card and used a usb jig to get into download mode, then when I flash a recovery with Odin, before the phone completely boots, I hold volume up and menu to get access to recovery mode.
Now I cant flash, wipe or even replace twrp recovery with stock recovery on Odin. Even tho Odin says it "passed". When the phone boots up in recovery, its still twrp. When I try to flash anything I get error that unable to mout '/system', '/data' and '/cache'. Internal storage is shown to be 0mb.
when I run the android toolkit, in the information for the phone it shows that my android version is 5.1.1 but my bootloader is I747UCUFNJ2 which is android 4.4.2 and build description is I747UCUFNE4 which is 4.3
I can provide information to anyone with knowledge of how to help. Thank you in advance if anyone can assist.
Was the phone running a 4.3 or 4.4.2 bootloader when you used Odin to flash a stock 4.1.1 ROM?
not sure
audit13 said:
Was the phone running a 4.3 or 4.4.2 bootloader when you used Odin to flash a stock 4.1.1 ROM?
Click to expand...
Click to collapse
I think it was 4.3
The bootloader in the s3 cannot be downgraded to 4.1.1 if it was running 4.3 or 4.4.2. If the 4.1.1 rom you flashed using Odin included a 4.1.1 bootloader, this could be the cause of the problem as an invalid bootloder/modem combination will brick the phone.
Where are you getting the stock recovery? Are you flashing just recovery?
audit13 said:
The bootloader in the s3 cannot be downgraded to 4.1.1 if it was running 4.3 or 4.4.2. If the 4.1.1 rom you flashed using Odin included a 4.1.1 bootloader, this could be the cause of the problem as an invalid bootloder/modem combination will brick the phone.
Where are you getting the stock recovery? Are you flashing just recovery?
Click to expand...
Click to collapse
Yeah I knew that part after, I was able to create a debrick sd card with a 16 gb memory card and used to a usn jig to get it into download mode. I got the stock recovery from one of the posts here I think, yes I just flash the recovery with the sd card still in the phone.
but it doesn't replace the twrp that was installed prior to the brick, when I get it into recovery mode, there is no internal storage, cant mount or change file or anything.
Maybe a pit file is required? I'm guessing here as I don't experience with de-bricking.
audit13 said:
Maybe a pit file is required? I'm guessing here as I don't experience with de-bricking.
Click to expand...
Click to collapse
i have all the files I suppose to have. even the pit file but when I odin the pit file, I get an error. I cant even flash the stock recovery. when I am in twrp, I cant mount anything, system shows 0 mb.
I'm curious as to which 5.1.1 rom you flashed.
audit13 said:
I'm curious as to which 5.1.1 rom you flashed.
Click to expand...
Click to collapse
it was the dirty unicorns 5.1.1 unofficial rom
The phone may to be force flashed with something like an octopus box.