Develop Bugs

[Q] Help with KIES emergency recovery

Hey guys,
I've been working on rooting the new Captivate Glide, and unfortunately my kernel flash with ODIN failed (inexplicably). Now the device is complaining I need to perform an emergency recovery, but of course the device isn't listed in the KIES panel.
Apologies if this is covered elsewhere, but I searched and didn't find anything.
Can anyone explain how KIES works? What is a recovery code? Do I need to get one from Samsung? Is there any other way to force it to perform the recovery on my semi-bricked phone?

Wrong forum ...

There isn't a forum for him yet, so this is the best he could do.
Try going to download mode and flashing again! Try again, until it works, redownload the kernel.
Sent from my SGH-I897 using xda premium

Actually, strangely enough ... I entered 3e recovery (out of desperation) and rebooted, and it cleared the flag, allowing it to boot up normally.
I checked the kernel timestamp (cat /proc/version) and it appears to still be the stock kernel, so the NAND update completely failed.
I still would like to figure out how to force a KIES recovery, but at least for the moment I'm back up and running (till I take my next shot ).

Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.

studacris said:
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
Click to expand...
Click to collapse
Frustrating. The n900 flashing tool was so excellent (and cross-platform). Wonder why Samsung would release such a piece of junk.
Anyway, I'm back in business now and still working on it.
I'd love to try one of the other kernels, but since I don't have any recovery path (stock kernel / image / firmware), I'm really nervous now.

[Q] help, s3 t999 4.3 can't flash, missing root access problem

So I rooted my s3 t999 so I could get cyaneginemod. I used the flashing rom way, and it didn't work,(i used twerp recovery) it kept saying failed, and then I went to the easier way of installing the rom with, the new cyaneinge mod app, (I'm still rooted). Then after waiting for it too finish my phone rebooted, but cyaneinge was not on it, instead it came with a page that said root missing I clicked on yes fix the missing root, n well nothing happens I was back on touchwiz, superuser was their but Samsung Knox kept it from doing anything but I used supersu to disable it. I thought that knox was keeping the cyaneinge mod app from working, so I decided to downgrade to 4.1 when knox didn't exist, bless that time, but I couldn't since odin kept failing at flashing a stock rom, I did this soo msoon times I went through every firm ware n back to 4.3, it kept failing, im pretty sure its boot locked, but the root is also limited, every time I reboot n go to recovery n leave it asked me if it should fix the missing root, but yes or no, it wont change, n every time I reboot it says optimizing apps 0 of 48, it takes at least 5 min to go through. N after going through every forum, YouTube video, asking friends, I still can't find a solution, n im stuck on a screwd up root version of 4.3 plz help

You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?

serio22 said:
You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?
Click to expand...
Click to collapse
i don't remember but I used twrp n as I Was flashing through rom it said failed, same thing when I flashed 4.3 stock firmware on odin later

If you have Kies that will give you problems with Odin. And make sure you have latest twrp

Reflash your current firmware with Odin. Then flash recovery, then the rom. No need to root first.
If the rom flash fails, you need to post the exact error it gives, and attach the recovery.log or theres little we can do to help.
We could start throwing out guesses, but there could be dozens of things potentiality causing your problem.

Softbrick cause buy Bootloader

Hello Everyone,
I've been up literally all night (I know, that old line) trying to fix what happened. I bought this phone last year. It was unlocked and rooted. I never updated because it was never giving me issues. But the lagging and battery has finally got to me. So I decided to upgrade to this new rom(http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423).
It looked clean and minimal bloat, just the way I like it. However, I didn't get past updating the Bootloader. As soon as I did in Odin it went into a bootloop. Try as I might I couldn't get into recovery. Luckily I can still get into download mode. So I read up and found that I should flash the original firmware. Unfortunately it failed because I tried to upload an older version. Is there anyway I can flash this rom via odin? Sorry for the noobish questions here but it's past 8am and I've just about given up. If I see recovery is not seandroid enforcing or rev check fail s6 device 3 binary 2 I'm going to lose my mind lol. I did have TWRP installed if that makes a difference. Just can't access it. Any help would be greatly appreciated. Thanks guys
P.S. I know I used buy instead of buy but can't fix it. It was really early in the morning haha

Ok I managed to download the stock MM version for my phone. I still have bootloop issues but I'm in recovery mode at least. However not TWRP though, if I try downloading a custom recovery it says the dreaded "recovery is not seandroid enforcing" also it says Device does not have DRK. Any guesses here?

Well, I've just about given up. I've searched extensively and it appears that the fix is to download a different kernel. However, the G925T has no support yet for any custom MM kernels. I made a backup of my phone via TWRP before this whole mess but the problem is I can't get to it. And to be honest I'm not entirely sure if it's still there. Here are the steps I have taken thus far.
1. Downloaded MM Bootloader: this was the start of my issues. Started bootloop, couldn't get into recovery.
2: Attempted to download original LP firmware: Odin denied it, there was another version I download from zidroid called "downgradeable". Obviously did nothing because I was still running MM bootloader and was effectively the same thing.
3. Downloaded stock MM firmware: Finally was able to boot into recovery but it was useless as it was the stock one. Also wouldn't boot up due to "Device does not have DRK" and boots straight into download mode. Tried to download recovery but none of them worked. Kicked me back to "Recovery not Seandroid enforcing".
So this is where I'm at, I just want to get back to my old device I honestly would rather have a clunky phone than one that doesn't work at all. Is it possible to downgrade back to LP and get back into TWRP and flash my backup? Do I still have root after taking all those steps? Any help would be greatly appreciated because this has officially ruined my weekend?

I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.

try dd the mm firmware

Nickle60 said:
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
Click to expand...
Click to collapse
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.

Docmjldds said:
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Click to expand...
Click to collapse
Thanks for the reply, I don't have the box for the phone and couldn't boot it up so that was a no go. But luckily for me I decided to give that rom one more go. I flashed bootloader and modem again, then flashed TWRP, and finally installed the rom. And boom! It worked, and it's better and faster than ever. I'm not sure what all that other mess was but I am going to say I have everything I need at the moment and won't be flashing anything anytime soon. I've learned a great deal through this process though. Thanks for everyone's help.

[SOLVED] S3 T999 "No SIM card" beyond Andorid 4.x.x (Lineage, OctOS)

Hello.
The short story is I found one s3 t999 in the drawer and it had 4.x.x ROM. Without paying much attention I flashed the latest TWRP and installed Lineage 7.1.2, but I get "No SIM card" error and am essentially without a network. I'm using a non-tmobile SIM card.
The problem synopsis:
The S3 T999 yields "no SIM card" error with anything beyond Android 4.x.x.
- Tried with Lineage 14.1
- Tried with the latest 7.1.2 OCtOS
- Tried with a LP 5.1.1 OCtOS rom
they all say NO SIM CARD and subsequently "No Service".
Once I restore my touchwiz 4.1 ROM via TWRP - I get network reception and I can make and receive calls.
Can anyone walk me through the problem? I work with linux and flash my other phones with ease, which means I can execute any suggestions momentarily.
THANKS

You need to flash the latest stock ROM, then twrp, then custom ROM.

audit13 said:
You need to flash the latest stock ROM, then twrp, then custom ROM.
Click to expand...
Click to collapse
If I understand correctly, I need to Odin-flash the latest stock rom, which I found it to be JB 4.3. Will this affect my SIM lock situation, seeing as I don't use a tmobile SIM.
Also, Odin requires that I enter "download mode", which TWRP (currently installed) does not seem to have. Odin does not 'see' the s3 connected (whilst in recov. mod).
Does that mean I need to flash a stock recovery first, and if yes, where do I get it and does it matter which stock recovery is being installed?

Flashing the latest stock rom should not affect the sim lock.
You can boot to the bootloader from twrp.
Just flash the stock with Odin, no need to flash anything before hand.

audit13 said:
Flashing the latest stock rom should not affect the sim lock.
You can boot to the bootloader from twrp.
Just flash the stock with Odin, no need to flash anything before hand.
Click to expand...
Click to collapse
Quite right, I was about to sideload-flash a stock recovery I unearthed here, before I noticed in TWRP in the Advanced menu having the "Download" option right next to sideload, so I booted directly into download mode Odin'd the latest stock rom I found (JB 4.3) and I do still have cell reception.
Does that mean I go into DL mode now, sideload TWRP and proceed to install Nougat (and hoping to have network access)
THANKS A BUNCH

You can flash the tar version of twrp from Odin. Then flash custom ROM, and enjoy

audit13 said:
You can flash the tar version of twrp from Odin. Then flash custom ROM, and enjoy
Click to expand...
Click to collapse
ALL DONE.
I Odin'd TWRP 2.8.6, from there I sideloaded TWRP 3.1.1 then upgraded via IMG install from within and installed OctOS 7.1.2 nightly.
Would you recommend Lineage over OctOS?
Thanks for the tips!

You could have install twrp 2.8.6 and flash the 3.1.1 zip from recovery.
Sorry, I can't make any rom because I haven't owned an s3 for a few years.
Glad you got it all sorted

audit13 said:
You could have install twrp 2.8.6 and flash the 3.1.1 zip from recovery.
Sorry, I can't make any rom because I haven't owned an s3 for a few years.
Glad you got it all sorted
Click to expand...
Click to collapse
Unfortunately, right off the bat, LED notification isn't working when a call is missed. I tried to call my number to inspect reception and when the call was registered as missed - no notification light is present - at all. Despite being enabled in settings.

Some custom ROMs have bugs so I recommend trying others until you find one you like. I used to flash my s3, s4, Nexus 5, LG g2 all the time and would come across minor bugs. At least your sim works with newer custom ROMs.
I'm now using an iPhone but still get the urge to hop back to android.

audit13 said:
Some custom ROMs have bugs so I recommend trying others until you find one you like. I used to flash my s3, s4, Nexus 5, LG g2 all the time and would come across minor bugs. At least your sim works with newer custom ROMs.
I'm now using an iPhone but still get the urge to hop back to android.
Click to expand...
Click to collapse
Quite right. I nandroid all of my ROMs so I can give few a spin and return to the one I fancy the most.
And yes, my SIM is now recognized and communications flowing . All I needed was the latest stock rom requirement tip and I was done.
Thanks for that.

audit13 said:
Some custom ROMs have bugs so I recommend trying others until you find one you like. I used to flash my s3, s4, Nexus 5, LG g2 all the time and would come across minor bugs. At least your sim works with newer custom ROMs.
I'm now using an iPhone but still get the urge to hop back to android.
Click to expand...
Click to collapse
Fux's sake! I spoke too soon.
Overnight, the phone (with Nougat) lost network again and in the morning showed "no SIM card". A restart remedies the problem for about 10 minutes before it completely refuses to acknowledge its SIM .
I downgraded with Odin to JB 4.3 and it appears to have network coverage for about two hours now. I'm about toss this piece of garbage 'fone' in the bin.
Is there any reasonable explanation as to why this idiot of phone of mine looses connection, just willy-nilly?

Maybe these nougat roms are too buggy. How about some older cm roms?

Freakin' antique isn't holding service more than few hours (at best) regardless of ROM installed. Even if there is a sequence of actions that can make this piece of garbage 'fone' work well - I'm no longer interested in investing a single minute further. Goes in the bin, end of.
Life's too short.

Just to update those who'll likely one day google and find this.
After going back and forth for as many days... my personal reason for losing connectivity on the s3 was because of a FAULTY SIM CARD. Had it replaced and network coverage came flowing.
As for those wishing to upgrade to Nougat or MM as I have, YOU NEED TO UPGRADE TO THE LATEST STOCK ROM, BEFORE MOVING ONTO NOUGAT.
Matter is now closed.

SM-N910P bootloop after OTA upgrade...

Hello guys!
I've buyed 910P, which was camuflated to 910F (i checked under battery - sticker there says SM-N910F, but in Odin download I see 910P). There was Lineage OS, celluar part works good, but there was some freezes (with camera/gallery), and pulse/UV sensor on back panel of phone isn't work. So after couple of days I've decided to return it to stock firmware - I wanted that sensor, and fast camera.
So. I maded backup with TWRP, found stock FW with 6.0.1 (N910PVPS4DQH1 if I remember correctly), loaded it with Odin - it works, but only english language (not a big problem), and no celluar networks at all. While I was on stock 6.0.1, it pulls update through OTA, and phone was updated. Nothing seems changed after OTA, celluar part don't works, all other good... I've decided to restore backup from my initial Lineage OS - and I don't maked backup of stock FW - I thinked like "I have firmware for Odin, I can re-flash it, if I'll need it...". But this seems to be critical mistake...
I've recovered Lineage OS backup, but phone don't see celluar network, all other was like before. I've tried several custom ROMs - and there was similar picture everywhere - all good, but no network. I decided that this probably caused by "bad" modem, and I just need to load some other modem firmware... I loaded it - and I've found that any custom ROM rebooting after 35-45 seconds from powering phone up. It can be on load animation on that moment, of If I install fresh lineage OS - it can ever show me a desktop - but it WILL vibrate and reboot after some time from powering up. Looks like watchdog...
I've tried to re-load stock ROM - but Odin fails - aboot in my phone has version 5, and in stock rom there is version 4. So I can't go back to stock state, and every ROM that I tried rebooting shortly after powering phone on.
Today I tried to load all parts of that stock rom, just without aboot - I unpacked tar, and maded tar without aboot (I changed system.ext4 with winhex, altered there version from 0004 to 0003 - there was same version mismatch like with aboot) - but it not helps, phone still reboots...
I think, this is because "new" aboot wants "new" modem...
So, I stuck here. Can't go back to stock, can't make phone just work without reboots...
Did somebody tries to load aboot from stock tar with TWRP? I mean copy aboot to SD, go to TWRP->terminal and try something like dd if=/sdcard/aboot.img of=/dev/block/... ?
I tried KIES, but it don't recognize phone - so I can't do "emergency recovery" there...
Did somebody have phone in stock after last OTA update? If yes - can you please share modem image for TWRP?
Sorry for really long post... I just need an advice, because I totally stucked now...

Dmitry_Sysoletin said:
Hello guys!
I've buyed 910P, which was camuflated to 910F (i checked under battery - sticker there says SM-N910F, but in Odin download I see 910P). There was Lineage OS, celluar part works good, but there was some freezes (with camera/gallery), and pulse/UV sensor on back panel of phone isn't work. So after couple of days I've decided to return it to stock firmware - I wanted that sensor, and fast camera.
So. I maded backup with TWRP, found stock FW with 6.0.1 (N910PVPS4DQH1 if I remember correctly), loaded it with Odin - it works, but only english language (not a big problem), and no celluar networks at all. While I was on stock 6.0.1, it pulls update through OTA, and phone was updated. Nothing seems changed after OTA, celluar part don't works, all other good... I've decided to restore backup from my initial Lineage OS - and I don't maked backup of stock FW - I thinked like "I have firmware for Odin, I can re-flash it, if I'll need it...". But this seems to be critical mistake...
I've recovered Lineage OS backup, but phone don't see celluar network, all other was like before. I've tried several custom ROMs - and there was similar picture everywhere - all good, but no network. I decided that this probably caused by "bad" modem, and I just need to load some other modem firmware... I loaded it - and I've found that any custom ROM rebooting after 35-45 seconds from powering phone up. It can be on load animation on that moment, of If I install fresh lineage OS - it can ever show me a desktop - but it WILL vibrate and reboot after some time from powering up. Looks like watchdog...
I've tried to re-load stock ROM - but Odin fails - aboot in my phone has version 5, and in stock rom there is version 4. So I can't go back to stock state, and every ROM that I tried rebooting shortly after powering phone on.
Today I tried to load all parts of that stock rom, just without aboot - I unpacked tar, and maded tar without aboot (I changed system.ext4 with winhex, altered there version from 0004 to 0003 - there was same version mismatch like with aboot) - but it not helps, phone still reboots...
I think, this is because "new" aboot wants "new" modem...
So, I stuck here. Can't go back to stock, can't make phone just work without reboots...
Did somebody tries to load aboot from stock tar with TWRP? I mean copy aboot to SD, go to TWRP->terminal and try something like dd if=/sdcard/aboot.img of=/dev/block/... ?
I tried KIES, but it don't recognize phone - so I can't do "emergency recovery" there...
Did somebody have phone in stock after last OTA update? If yes - can you please share modem image for TWRP?
Sorry for really long post... I just need an advice, because I totally stucked now...
Click to expand...
Click to collapse
Check this post, at the end you'll find link for the latest QI5 build, try to flash your phone by using odin, it may fix it.
https://drive.google.com/open?...d=0B1blPsoKK5taRk5SZ3NwdmUtTzA
Sent from my SM-N910P using Tapatalk

jam97 said:
Check this post, at the end you'll find link for the latest QI5 build, try to flash your phone by using odin, it may fix it.
https://drive.google.com/open?...d=0B1blPsoKK5taRk5SZ3NwdmUtTzA
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Actually, that post is mine too
But thanks anyway!