Develop Bugs

Cannot downgrade to 4.2.2 (gt p5210), what should I do?

Hi,
After upgrading OTA to kitkat (australia version) one of my favourite apps stopped working and caused constant reboots to my tab3.
I tried to downgrade with odin to the stock 4.2.2 (auatralia, from sammobile) but I could not. After flshing, the "samsung galaxy tab 3" logo appeared but the tab never turned on, it kept rebooting and rebooting from ours. I tried the same with other 4.2.2 roms with the same results. However I was able to flash any 4.4.2 rom from sammobile.
After that I tried to flash some 4.2.2 roms using twrp and bindroid, I had the same rebooting problems. However, with twrp I can flash 4.4.2 based roms as pimpdroid.
So, I do not why, apparently my tab only accepts 4.4.2 roms... Any suggestions about what should I do to go back to 4.2.2?
Thanks for your time,
A.

Bootloop in P5210
Hi I'm trying to get back to 4.4.2 to 4.2.2 works because although there are excellent applications like Facebook that are causing me problems. But in trying to make the retoroceso as I usually do with ODIN stock form and I was left in a permanent reboot and does not pass the SAMSUNG logo .... solution? Thank you!:crying:

@planinsky, Have you tried a firmware for another region in the world? I live in the United States but have found firmware for the United Kingdom or Canada works best when I flash. There should not be any difference in the firmwares except for regionalization, but it seems some work and some don't work for me. Regional settings can always be tweaked in the Settings panel after install. Do you have a nandroid backup made in TWRP? Those usually always recover a device. I too had a problem having anything flash when I first started making my rom. 3 weeks I had a device that would not boot. So it is recoverable. Odin will save your device.
@planinsky and @MDCB try to download this firmware from Sammobile. This is for the UK 4.2.2 version. http://www.sammobile.com/firmwares/download/28243/P5210XXUANB4_P5210BTUANB1_BTU.zip/
I usually use ODIN 3.07. I assume you know the following but just in case. Remember to flash it in the PDA slot. Only have "Auto reboot" and "F. Reset time" checked.
Using Odin will reset anything the 4.4.2 builds have done to the partitions. If it doesn't work, I can only suggest to try again. When it comes to flashing, sometimes the TWRP builds for our device can be a little goofy in writing. I have not investigated completely. In the 4.2.2 roms I have flashed pimpdroid and cagrom, they seem to flash good with Moonbutt77's philz recovery with very little problems. I however cannot get 4.4 roms to flash in philz but only in TWRP. So sometimes the recovery itself seems to have a problem with the android version, or so it seems.
The above is only written from my experience on this device and cannot predict every situation.
Good luck.

Hi! Thanks for the tips.
Ufortunately, I have already tried 4.2.2 ROMS from different countries (from Sammobile): Australia (the original country of my Tab), UK, New Zealand, Belgium and US. None of them worked. I'm still downloading other ROMS but I'm startin to lose the faith... The custom ROMS I have tried, neither work and get into the bootloop.
The backup I have from TWRP is from a 4.4.2 so it's not a solution.
On the other hand, I can flash almost any 4.4.2 ROM with odin and/or TWRP. So I'm afraid I'll soon give up and I will accept that my Tab will not longer run the app I loved (Movistar TV)... Hopefully with the arrival of lollypop the developers will update the app and the bug which causes the crash will disappear.

No baseband- no IMEI not sure of anything at this point

I started with a fresh non altered I747m. The first thing I had to do was carrier unlock (PetroCAN sim) and then rooted the phone.
I pretty sure i did a cfroot and installed the newest pacman rom and all worked- just no internet ( the phone and texting worked) so I played with the APN for a while then decided to try a couple of MODEM zips (Rogers and AT&T) and flashed those in CWM.
Downhill fro there- No more SIM, no baseband- no IMEI no APN- could not even create an APN.
Tried diferent 511 ROMS (DU).
so then I did the even more stupid thing and retored the original NANDroid backup and now it is really bad- stuck on the samsung logo.
I did write down the IEMI number and I did check the baseband version (i did the check in like a dos screen on the phone) I747mluf0b1
What should I do now>?? i would be happy to return it all back to stock I really screwed this phone up bad
note: I did do a full nandroid backup before updated to 511 but i saw that there was no EFS folder (an this was when everything was working correctly)
So i think i the phone is toast..

Are you running the latest modem and bootloader?
I suggest you use Odin to flash the latest stock rom for your phone from sammobile.com to see of them either comes back.

I downloaded the correct i747m bell stock version that matches the buildprop I747MVLUFOB1
It is now in a softloop 'SAMSUNG' and sits.
it just came back up

Did you get the phone working?

That got it!!! YEAH!! I been working on this phone for days. All of a sudden the STOCK ROM is the best rom ever!!! hehe

If you have to restore to stock in the future, it is best to uncheck auto reboot in Odin. When you see the word reset in the status window, remove the usb cable, remove battery, replace batter, boot into stock recovery, and perform a full wipe. This helps to prevent the boot loop.

Camera frozen on black screen no matter what I do

I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!

Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.

You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck

Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.

Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.

sim card not working oreo/noughat

hi i have had the pleasure of using the developer oreo img and enjoyed it,but decided to reflash stock noughat img
until the official oreo comes out.heres where my issue started,after a successful flash and start up,my sim no
longer shows as inserted,i even tried a restore of my noughat back up.the only way my sim will work nowis with the
oreo stock img reflashed..anyone else have this isssue

Are you sure you flashed all the files included in the Nougat fastboot package zip? There must be an image called 'modem' and anoter 'dsp' which should take care of that.
Try reflashing the Nougat image once again.

I will try again

Having the same exact issue
Flashing the MR3 factory image results in no SIM card, same with fkashing MR1 @TheCrazyLex
EDIT: reflashed again the next day and it's now working....ugh annoying

Had exactly the same issue. Although on initial boot back to Nougat, everything worked fine.
It was only after a restart or two the SIM was then undetected.
I'm flashing stock Nougat again just now, hopefully that resolves it for me too.
EDIT. Ok I've now tried flashing multiple images, they all flash successfully and boot successfully, but none of them are detecting a SIM card.... any ideas anyone?
EDITS AGAIN: It would appear now working after flashing Oreo again, then back to Nougat. Very odd....
I want to lock the bootloader again, which is how I ended up in this mess, so I'm now flashing latest Global ROM again, rebooting and then attempting to lock the bootloader again.
I shall update with results.

any update in the same boat

I'm still having same issues,I'm just using Oreo which is working really well.only downfall I noticed is tethering doesn't seem to be working on it

Are you running the right image as Razer and Three have their own build so wanted to point this out as ThreeUK may not work right with the Razer build. i Remeber them saying something about making sure you use the right build

UPDATE - if anyone is having this issue.
--Take the Oreo preview and flash_all.bat via bootloader
--Let it boot and get in to Android just so you can enable debugging via dev options
--reboot to bootloader and flash_all.bat with the latest Three or Global image
--Again let it boot and enable debugging again
--Now reboot to bootloader, and do BOTH the following in fastboot:
---- fastboot flashing lock_critical
---- let it reboot and go back to bootloader again and perform the next lock
---- fastboot flashing lock
Once finally back in, only then did I have a locked bootloader + working SIM card.
Hope this helps someone.

Locking the bootloader doesn't fix things lol. I was on Oreo yesterday and flashed back to nougat and had signal and relocked the bootloader then 10 minutes later .y phone rebooted and lost sim. Only was to get it back was flashing Oreo then booting then flashing nougat mr1 and got my sim back. Then I locked bootloader and took the ota and now I'm back to normal and can take otas again

This is such a weird issue. like for instance I went back to MR1 from Oreo and had signal but when I picked the bootloader and ota to MR3 it was gone.then just unlocked bootloader flashed MR3 still nothing. So went back to Oreo and it worked and then flashed MR1 again and randomly worked even after the ota to MR3
So absolutely random.

hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too

SIM card issue
Hey @parky169, @Roxas598, @linuxct, @kickassdave, @joemossjr
Thanks for posting about this issue that you saw about the SIM not being detected. Our engineers would like to learn more about this and EXACTLY what happened. Can you please PM me with the details:
What carrier you guys are on?
What was the previous build you were on before you flashed the Oreo developer build?
Can you please walk me through EXACTLY what happened that caused the SIM to go undetected
Were any APNs changed prior/after?
Were any changes made to the files or phone (rooted, custom ROM, etc.) prior to flashing the O build?
How did you resolve this situation? Is this repeatable?
Thanks again for testing the developer build! Please PM me if you run into any more issues!
Best,
Khanger

parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Same issue as the rest. I wonder if this will work with the Oreo OTA modem img, I'm gonna give it a shot. I will report back
EDIT: Well there is probably no reason it shouldn't have worked I would assume the modem images are identical in 8.1 Dev and 8.1 OTA, but it does work by putting the 8.1 MR0 OTA modem img in the 7.1 MR3 and flashing. Honestly i ws too lazy and didn't want to wait for the Dev image to download and I already had a copy of the 8.1 OTA ON MY pc.

Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!

​
Jonlines94 said:
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Click to expand...
Click to collapse
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?

NoXXX said:
​I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
Click to expand...
Click to collapse
Any update on this? I am in the same boat after standard OTA update. Can not save apns either. (at&t)

Thanks!!!
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Thanks for finding a fix. I was worried my phone was jacked up. I was having the same issue. I wanted to downgrade from Oreo since there is an issue with HDMI not having audio. I got signal now whoooo

Empty IMEI

Hi
Hoping someone here might be able to help as somehow I’ve messed up my IMEI.
I flashed alexndr stock rom over my stock rom with the force XEU option enabled as my default CSC is H3G. Everything worked fine but was failing safety net so decided to flash back to my stock rom with odin but now my IMEI is empty.
I have the EFS backup that Alexandra rom installer created but flashing this doesn’t seem to solve the problem and what’s strange is if I flash alexndr rom back onto my phone my IMEI comes back and everything works normally but with the stock rom its blank.
Anyone know how to fix it?
Thanks

andrewtjb said:
Hi
Hoping someone here might be able to help as somehow I’ve messed up my IMEI.
I flashed alexndr stock rom over my stock rom with the force XEU option enabled as my default CSC is H3G. Everything worked fine but was failing safety net so decided to flash back to my stock rom with odin but now my IMEI is empty.
I have the EFS backup that Alexandra rom installer created but flashing this doesn’t seem to solve the problem and what’s strange is if I flash alexndr rom back onto my phone my IMEI comes back and everything works normally but with the stock rom its blank.
Anyone know how to fix it?
Thanks
Click to expand...
Click to collapse
In the past is was mismatched baseband. But I've never had the issue so I dont know for sure

TheMadScientist said:
In the past is was mismatched baseband. But I've never had the issue so I dont know for sure
Click to expand...
Click to collapse
Thanks
I managed to solve it was definitely a baseband issue. It looks like when I flashed the alexandr rom it updated the baseband to DTD7 where as my my carrier firmware I was trying to flash back to was still DTC5.
I've flashed DTD7 firmware now and everything's back to working normally.