Question SIM/Baseband/IMEI errors since Tuesday 17th - Samsung Galaxy A12

I'm getting a problem where everytime I try to call someone or I receive a call, my SIM cards become undetected, the phone crashes after a short time and then doesn't detect SIM cards again, and Samsung or Google backups stop working, and all Samsung account related apps refuse to work. Only fixable after multiple factory resets.
After some investigation, I found that the Baseband and IMEI of the phone seem to be "unknown" whenever this occurs.
Is there a reason to this, or even a fix?

ZaneJulien said:
I'm getting a problem where everytime I try to call someone or I receive a call, my SIM cards become undetected, the phone crashes after a short time and then doesn't detect SIM cards again, and Samsung or Google backups stop working, and all Samsung account related apps refuse to work. Only fixable after multiple factory resets.
After some investigation, I found that the Baseband and IMEI of the phone seem to be "unknown" whenever this occurs.
Is there a reason to this, or even a fix?
Click to expand...
Click to collapse
same with my A125F variant, try to reset your device and it will fix the problem
and don't update your device with the build number of A125FXXU1BUG6, i think there's is a bug with that update..

You were completely right! It WAS the new update. I flashed the previous firmware and my SIMs work perfectly now! I've turned off auto-update in the normal area and developer settings too, hopefully can avoid it till it's fixed sometime. Thanks again!

I found a way how to fix it... try to flash the A125FXXU1BUG6 firmware version together with the pit file and it will fixed the problem

Hi all,
That sounds exactly like the problem I have
When I ROOT, I unblock BOOTLOADER, the connection to the network is blocked.
When I ROOT, I unblock BOOTLOADER, the connection to the network is blocked: / Bootloader unlocked = connection blocking
forum.xda-developers.com
(I was assuming it was due to the unlocking)
I was using Frija to get the latest (bugged?!) version - I was unable to find the previous one
Baseband A125FXXU1BUE1 / Build A125FXXU1BUE3 (XSA)
Could anyone please describe where to get an older version / the pit file?
Thanks a lot for that!

is your device is A125F?

A125F pit file i used this pit to fix the problem
A12_EUR_OPEN
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

Jayke770 said:
A125F pit file i used this pit to fix the problem
A12_EUR_OPEN
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thanks a lot, if I cannot find the lower firmware (it's on Samfrew, but downloading will take ages...), I'll give it a try. And good to have it if I get a bootloop!

Whoooo? said:
Thanks a lot, if I cannot find the lower firmware (it's on Samfrew, but downloading will take ages...), I'll give it a try. And good to have it if I get a bootloop!
Click to expand...
Click to collapse
i have an app that can download latest firmware for Samsung

or just try this website https://www.google.com/url?sa=t&sou...0QFnoECEIQAQ&usg=AOvVaw0neIA-O_nYmWom070upF4v

Just as a note for everyone who has the same problem -
I could fix this without the pit file, all that was required was flashing the complete (previous) firmware with Odin.
So not just the AP file but all the other ones as well (AP, BL, CP, CSC). Maybe a modem issue?

Hey guys, i tried everything, but have not been able to fix it.
I have the SM-A125W
and I tried flashing:
Samfw.com_SM-A125W_RWC_A125WVLU2AUFA_fac
Samfw.com_SM-A125W_RWC_A125WVLU2AUG5_fac
Samfw.com_SM-A125W_XAC_A125WVLU2AUFA_fac
Samfw.com_SM-A125W_XAC_A125WVLU2AUG5_fac
and used the pit file:
from: https://www.full-repair-firmware.com/p/galaxy-a12.html
and also, checked repartition option in odin,
When i make a phone call, and hang up, the sim card and phone number shows UNKNOWN
and when i perform a factory reset, it comes back and then goes again when i make a phone call.
Are we able to use the SP flash tool on this phone?
What seems to be the problem here?

I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!

andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Does it also work with the new update A125FXXU1BUI3?

andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Allehandro said:
Does it also work with the new update A125FXXU1BUI3?
Click to expand...
Click to collapse
THANKS SOOOO MUCH. IT WORKED. IT WORKED WITH THE NEW UPDATE AND IMEI AND BASEBAND ARE BOTH WORKING. LIFESAVER!!!

andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Allehandro said:
Does it also work with the new update A125FXXU1BUI3?
Click to expand...
Click to collapse
I've flashed the new A125FXXU1BUJ4 November security update and the bug is still there but I was able to flash the same IMEI/Baseband repair file and it worked. THANKS FOR THAT.

andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
However, this file according to your link now becomes paid, please re-upload into XDA

i already fix my a12

I am using a125n. On Android 11, Clearing /mnt/vendor/nvdata, flashing with pit, re-locking does not work. But flashing android 10 CP makes the phone work well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you're not sure it a software fail, "Unknown" Baseband probably cause by faulty MT6177mv chip on mainboard. Usually damage by warter or falling, and it just need to reflow or replace a new one.both imei will re-apear when the baseband chip working.
Talking from personnal experient

Related

S6 Bootloader and Modem Odin Flash Failed Red

Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
agentdangermouse said:
Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
Click to expand...
Click to collapse
you phone g920i?
agentdangermouse said:
Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
Click to expand...
Click to collapse
If you previously firmware (OI9 and new) had it, you can return to the boot loader only to release OI9.
Older bootloader cause an error.
furkanndk said:
you phone g920i?
Click to expand...
Click to collapse
Yeah sorry i mentioned its Samsung SM-G920i
bininga59 said:
If you previously firmware (OI9 and new) had it, you can return to the boot loader only to release OI9.
Older bootloader cause an error.
Click to expand...
Click to collapse
I never had I09, pretty sure previous to this i had one B0F or something like that. What is the latest for Samsung 920i that i can try ?
agentdangermouse said:
I never had I09, pretty sure previous to this i had one B0F or something like that. What is the latest for Samsung 920i that i can try ?
Click to expand...
Click to collapse
Actually issue is resolved, i installed Samsung Phone Info from app store and i double checked my bootloader and modem installed i am already running latest bootloader from here http://forum.xda-developers.com/galaxy-s6/development/g920i-bootloader-modem-updated-10-10-t3221796
So i guess the fact is i cannot downgrade maybe thats why this is the issue. So i think all is ok
Thanks for the assistance

I give up.

I've got a Galaxy S5 that I purchased from someone earlier today and it worked well until I did some type of software update, it went well but then restarted and it's been messed up since. Now, whenever I boot up the phone it boots fine all the way too the Sprint Spark screen and it just hangs, and hangs and then restarts again, and goes through the same process. I've tried reflashing the device using Odin but I keep getting an error "SW REV CHECK FAIL" with some other stuff. I've tired to do so much, I tried resetting the device and the cache using the options. Please, can someone offer me some help. It's a 900P and it's a Sprint device. I just got back from a funeral a little bit ago so I'd love to get this thing working finally, I've been working on it all night.
Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.
tys0n said:
Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.
Click to expand...
Click to collapse
Yes, that's correct my bad. It's the 900P. I'll correct the thread.
nulledbyme said:
Yes, that's correct my bad. It's the 900P. I'll correct the thread.
Click to expand...
Click to collapse
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.
nulledbyme said:
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.
Click to expand...
Click to collapse
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.
tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
tys0n said:
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.
Click to expand...
Click to collapse
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..
nulledbyme said:
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..
Click to expand...
Click to collapse
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.
tys0n said:
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.
Click to expand...
Click to collapse
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?
nulledbyme said:
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?
Click to expand...
Click to collapse
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.
tys0n said:
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.
Click to expand...
Click to collapse
I'll try that so, with those files I just put them all into Odin?
nulledbyme said:
I'll try that so, with those files I just put them all into Odin?
Click to expand...
Click to collapse
Yes exactly. This is what you'll find once it's unzipped.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.
tys0n said:
Yes exactly. This is what you'll find once it's unzipped.
View attachment 4098803
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.
Click to expand...
Click to collapse
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?
nulledbyme said:
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?
Click to expand...
Click to collapse
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.
tys0n said:
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.
Click to expand...
Click to collapse
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.
nulledbyme said:
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.
Click to expand...
Click to collapse
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.
tys0n said:
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.
Click to expand...
Click to collapse
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..
nulledbyme said:
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..
Click to expand...
Click to collapse
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't
tys0n said:
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't
Click to expand...
Click to collapse
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!
nulledbyme said:
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!
Click to expand...
Click to collapse
That's awesome! Glad I could help.

[Rom][Unbrick] Bootloader Recover Huawei Watch 2 LTE LEO-L09S

I have downloaded the LTE full factory recovery firmware, I will be providing a package that will bring the watch and will not flash system, userdata, nvram (imei) and will require you to flash the global firmware afterward.
Recovery firmware:
Here
sorayahya said:
So after downloading the above files extract the files. After that, we will need to get QPST which has the program called QFIL which we will be used to unbrick the watch.
Download “QPST 2.7 (QFIL)” from HERE and extract it to an empty folder. Install QPST by double-clicking setup.exe.
Now you want to plug in your Huawei Watch 2 to the PC using the charging cable that came with the watch.
At first, you might get a notification from the PC that the USB device is unknown, if that happens you will need to hold down on your watch's right top button for around 30 seconds. After that, you should get a notification from your PC that a new device was plugged in and it will start to install a new driver. Once that's done you should have a "Qualcomm HS-USB QDLoader 9008" device show up in your device manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We won't be needing the storage device to show up so if it doesn't for you that's alright.
Next, we will open QFIL from the start menu, if it's not in the start menu you can locate it by going to Program Files\Qualcomm\bin\. You should see "Qualcomm HS-USB QDLoader 9008" written on the top if it's not then click on the "SelectPort" button and then select "Qualcomm HS-USB QDLoader 9008". After that Insert all the necessary file needed by QFIL:
(1)The programmer will be prog_emmc_firehose.mbn;
(2)Use the rawprogram_unsparse.xml;
(3)Use the patch0.xml;
(4)Hit “Download” button.
If the process you did with QFIL finished successfully, the watch will boot again. If not then try to restart the program and repeat the same process again until you succeed.
Click to expand...
Click to collapse
At this point, your watch is alive again but without a way to boot to android so you will need to flash the stock rom here
Mine just in case
Is the latest version of the firmware?
OWDE.180707.001.E1 ?
Cao Aobo said:
Is the latest version of the firmware?
OWDE.180707.001.E1 ?
Click to expand...
Click to collapse
No this is just 7.1.1 recovery firmware in case your watch is bricked, then from there you can flash whatever newer firmware you want
Today I restored my watch by this manual. Model LEO-DLXX (LTE). It is 100% works. Thanks again)
Now, can you help me find the latest firmware for flashing with adb/fastboot? I have only old version (android wear 2.0.) And I can't flash ROM from TWRP, it shows the file format has problem and fail to install.
My watch has been updated to the latest firmware. But I had a problem that I did not notice before. When I restored the watch, IMEI was erased. Now any SIM does not work. Please help me.
y-type said:
My watch has been updated to the latest firmware. But I had a problem that I did not notice before. When I restored the watch, IMEI was erased. Now any SIM does not work. Please help me.
Click to expand...
Click to collapse
I have revised the flash package so it doesn't flash the nvram partition and the system, cache, userdata partitions so you need to flash the global rom. I am sorry that your imei was lost, unless you have a backup you would need to get it flashed at a repair store.
I have the same watch as in some of these pics (LEO-DLXX), but am getting the same error of sahara protocol fail. The bootloader recovery link above brings me to Leo-B09S _Recovery. Should it be this folder or something like LTE LEO-L09S? When I load the files in QFIL, it looks a bit different. I don't have rawprogram0.xml, but a file called rawprogram_unsparse.xml. Any help is greatly appreciated. It looks like others have successfully recovered their bootloader on the exact same watch that I have.
stephen1981 said:
I have the same watch as in some of these pics (LEO-DLXX), but am getting the same error of sahara protocol fail. The bootloader recovery link above brings me to Leo-B09S _Recovery. Should it be this folder or something like LTE LEO-L09S? When I load the files in QFIL, it looks a bit different. I don't have rawprogram0.xml, but a file called rawprogram_unsparse.xml. Any help is greatly appreciated. It looks like others have successfully recovered their bootloader on the exact same watch that I have.
Click to expand...
Click to collapse
I reuploaded the file with the proper name, they were the right files just with the wrong zip/folder name and updated the instructions to say rawprogram_unsparse.xml
deadman96385 said:
I reuploaded the file with the proper name, they were the right files just with the wrong zip/folder name and updated the instructions to say rawprogram_unsparse.xml
Click to expand...
Click to collapse
Thanks for your help! I still get the same error over and over again, "Download fail: Sahara fail: QSaharaServer failrocess fail". How many attempts does it usually take?
stephen1981 said:
Thanks for your help! I still get the same error over and over again, "Download fail: Sahara fail: QSaharaServer failrocess fail". How many attempts does it usually take?
Click to expand...
Click to collapse
me also have same watch leo-dlxx and have same error please help.
stephen1981 said:
Thanks for your help! I still get the same error over and over again, "Download fail: Sahara fail: QSaharaServer failrocess fail". How many attempts does it usually take?
Click to expand...
Click to collapse
deadman96385 said:
No this is just 7.1.1 recovery firmware in case your watch is bricked, then from there you can flash whatever newer firmware you want
Click to expand...
Click to collapse
Hi @stephen1981 there is one missing file which is tz.mbn I got it from another recovery and it works fine I put the file in attachments just extract it to the main recovery folder and it will work now my watch started and connected to phone and now it is searching for update
abo3bdo said:
Hi @stephen1981 there is one missing file which is tz.mbn I got it from another recovery and it works fine I put the file in attachments just extract it to the main recovery folder and it will work now my watch started and connected to phone and now it is searching for update
Click to expand...
Click to collapse
Thank you so much! Everyone on XDA has been so helpful. I am glad to have the watch working again!
Now can any one please put a working link for a working stock orio rom for the LEO-DLXX model
---------- Post added at 04:30 AM ---------- Previous post was at 04:19 AM ----------
stephen1981 said:
Thank you so much! Everyone on XDA has been so helpful. I am glad to have the watch working again!
Click to expand...
Click to collapse
You are welcome my friend I'm happy for you too that you got your watch working again
Thanks to everyone who contributed to this thread! Finally my watch has been unbricked!
It's being recognized as BX09 instead of DLXX though, and my sim functionality appears to have disappeared. Still, this is better than being completely useless...
EDIT: Flashed the Sawshark ROM. It's back to DLXX now. IMEI is missing though. Still, it's not the end of the world.
I have hw2 chenesee version. I flashed it with eu firmware and its work fine till i make update (after update my wathes dont have sound). I tried to flash it one more time with eu firmware and now they stop on logo.
savteam said:
I have hw2 chenesee version. I flashed it with eu firmware and its work fine till i make update (after update my wathes dont have sound). I tried to flash it one more time with eu firmware and now they stop on logo.
Click to expand...
Click to collapse
Very interesting.
savteam said:
I have hw2 chenesee version. I flashed it with eu firmware and its work fine till i make update (after update my wathes dont have sound). I tried to flash it one more time with eu firmware and now they stop on logo.
Click to expand...
Click to collapse
please use this :
https://forum.xda-developers.com/showpost.php?p=77935791&postcount=646
and flash it to the watch only that 3 files and it will work again
use adb to reboot to fastboot and then flash the files in the zip file which you will download from the link.
---------- Post added at 11:40 PM ---------- Previous post was at 11:36 PM ----------
ilitirit said:
Thanks to everyone who contributed to this thread! Finally my watch has been unbricked!
It's being recognized as BX09 instead of DLXX though, and my sim functionality appears to have disappeared. Still, this is better than being completely useless...
EDIT: Flashed the Sawshark ROM. It's back to DLXX now. IMEI is missing though. Still, it's not the end of the world.
Click to expand...
Click to collapse
I have also same problem IMEI is 0 and also when connect the watch to PC it shows that the LEO-DLXX driver is missing and can not open its internal memory but still can communicate with the watch using adb
A WARNING: new users, don't flash this as it will erase your IMEI.
old users whose imeis have been erased, take the watch to a service center, along with the original box it came in, and ask them nicely to fix it.
There are several instructions for restoring IMEI. But for this we need to enable diag mode. Who knows how to do this? I've got ROOT. But
this instruction does not work https://www.youtube.com/watch?v=AiOcfvyQf-4 It only finds a new device, but not one com port.

Soft bricked?

Okay, guys...
I've been flashing since the Touch Pro 2 days, but haven't much since bootloader tend to be locked down these days. That said, I know my way around Odin and such, so I don't need anyone to hold my hand. Anyways...
A friend brought me her N970U (ATT) with a no charge issues. Resolved that, but all it would do was boot loop. Her goal was simply to get pictures off of the device, so I was trying to retain data. Wiped cache and repaired apps to no avail, figured next step would be to dirty flash via Odin. I used the firmwares provided by @iBowToAndroid, but I couldn't get anything to flash except the most recent BL. Now I can't even get boot loop. Goes straight to the bootloader with the error:
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot): 5C45D4E6BB, (VEMETA): 4514875C6A
SAMSUNG boot, N970USQU4DTH7, 33954676R
VBMETA N970USQU5ETLL, 36955741R
Not sure why it's failing to flash anything besides that one BL, any help is appreciated.
flatlander_2k5 said:
Okay, guys...
I've been flashing since the Touch Pro 2 days, but haven't much since bootloader tend to be locked down these days. That said, I know my way around Odin and such, so I don't need anyone to hold my hand. Anyways...
A friend brought me her N970U (ATT) with a no charge issues. Resolved that, but all it would do was boot loop. Her goal was simply to get pictures off of the device, so I was trying to retain data. Wiped cache and repaired apps to no avail, figured next step would be to dirty flash via Odin. I used the firmwares provided by @iBowToAndroid, but I couldn't get anything to flash except the most recent BL. Now I can't even get boot loop. Goes straight to the bootloader with the error:
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot): 5C45D4E6BB, (VEMETA): 4514875C6A
SAMSUNG boot, N970USQU4DTH7, 33954676R
VBMETA N970USQU5ETLL, 36955741R
Not sure why it's failing to flash anything besides that one BL, any help is appreciated.
Click to expand...
Click to collapse
It won't boot unless the full firmware matches the BL. So you need to flash the full TLL package, sans USERDATA and using HOME CSC
iBowToAndroid said:
It won't boot unless the full firmware matches the BL. So you need to flash the full TLL package, sans USERDATA and using HOME CSC
Click to expand...
Click to collapse
That's the issue, though. It fails trying to flash anything besides the BL. I've tried doing them all together and each individually. Re-downloaded a time or two in case of a bad file, but no dice
flatlander_2k5 said:
That's the issue, though. It fails trying to flash anything besides the BL. I've tried doing them all together and each individually. Re-downloaded a time or two in case of a bad file, but no dice
Click to expand...
Click to collapse
Can you be more specific? Any specific error messages etc?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flatlander_2k5 said:
.
Click to expand...
Click to collapse
Try a different port, different cable, different computer, and also try Odin 3.14.1
Update: finally got all of the files to unzip correctly after using Frija to download them. Everything installed successfully via Odin, but it's giving a modem error on the device, saying it was flashed with unauthorised software.
flatlander_2k5 said:
Update: finally got all of the files to unzip correctly after using Frija to download them. Everything installed successfully via Odin, but it's giving a modem error on the device, saying it was flashed with unauthorised software.
Click to expand...
Click to collapse
Post a pic or screenshot of the error
I used the USC download since ATT isn't available, then used the home CSC for ATT provided from @iBowToAndroid
flatlander_2k5 said:
I used the USC download since ATT isn't available, then used the home CSC for ATT provided from @iBowToAndroid
Click to expand...
Click to collapse
How is ATT not available, if you used the CSC from the ATT package that I uploaded......?
(Not like it matters anyway, because all firmware is universal)
What I mean is that Frija says that ATT isn't a supported CSC, so I had to choose another one. I used all of the files from that download (BL, AP, CP) except the home CSC, for which I used your most recent one.
Flashed the home CSC that downloaded with the USC package and it's back to bootloop. If I go to the BL and repair apps, it gets to like 338 of 4xx and reboots. This phone is giving me a headache.
flatlander_2k5 said:
What I mean is that Frija says that ATT isn't a supported CSC, so I had to choose another one. I used all of the files from that download (BL, AP, CP) except the home CSC, for which I used your most recent one.
Click to expand...
Click to collapse
You can't get "my most recent" CSC without downloading the full firmware, because it's all one zip file. So obviously you downloaded the full firmware. So why didn't you just flash my whole firmware?
flatlander_2k5 said:
Flashed the home CSC that downloaded with the USC package and it's back to bootloop. If I go to the BL and repair apps, it gets to like 338 of 4xx and reboots. This phone is giving me a headache.
Click to expand...
Click to collapse
You need to flash the full TLL package. Doesn't matter if it's USC from Frija or ATT from me. Choose one package and flash all 4 files from it - AP, BL, CP, and HOME CSC
iBowToAndroid said:
You can't get "my most recent" CSC without downloading the full firmware, because it's all one zip file. So obviously you downloaded the full firmware. So why didn't you just flash my whole firmware?
Click to expand...
Click to collapse
The AP wouldn't unzip correctly, regardless of which mirror I used. Tried 7-zip and WinRar multiple days/times, got two errors unzipping every single time. Frija's download was the first one that I could unzip the whole package and it pass in Odin.
I am currently using every part of that download, which is how I got from the bootloader error back to the original boot loop issue.
flatlander_2k5 said:
The AP wouldn't unzip correctly, regardless of which mirror I used. Tried 7-zip and WinRar multiple days/times, got two errors unzipping every single time. Frija's download was the first one that I could unzip the whole package and it pass in Odin.
I am currently using every part of that download, which is how I got from the bootloader error back to the original boot loop issue.
Click to expand...
Click to collapse
If you're referring to my package, the AP is zipped up in the entire firmware package. So are you saying the entire package wouldn't unzip correctly?
iBowToAndroid said:
If you're referring to my package, the AP is zipped up in the entire firmware package. So are you saying the entire package wouldn't unzip correctly?
Click to expand...
Click to collapse
When I unzip your download, it gives two errors and Odin won't accept the AP. Per the pictures, I've tried using two different decompression tools.
flatlander_2k5 said:
When I unzip your download, it gives two errors and Odin won't accept the AP. Per the pictures, I've tried using two different decompression tools.
Click to expand...
Click to collapse
I still have the zip itself on hand (the same one that I uploaded), and it passes the 7-Zip archive test and also extracts without errors. You might have gotten a bad download - that can happen with AFH, if it gives you a janky mirror. Try downloading again, and try a different mirror if it gives you a slow one
EDIT: I just re-downloaded it from AFH, in case it was a bad upload. Tested fine and extracted fine, so it appears to have been a bad download
iBowToAndroid said:
I still have the zip itself on hand (the same one that I uploaded), and it passes the 7-Zip archive test and also extracts without errors. You might have gotten a bad download - that can happen with AFH, if it gives you a janky mirror. Try downloading again, and try a different mirror if it gives you a slow one
EDIT: I just re-downloaded it from AFH, in case it was a bad upload. Tested fine and extracted fine, so it appears to have been a bad download
Click to expand...
Click to collapse
I've downloaded it various times from different mirrors, thinking exactly that. I get the same error every time. Downloads from frija extracted without issue.
I'll note that this computer is a fresh OS install with no third-party virus protection or anything installed that might normally cause issues.
flatlander_2k5 said:
I've downloaded it various times from different mirrors, thinking exactly that. I get the same error every time. Downloads from frija extracted without issue.
I'll note that this computer is a fresh OS install with no third-party virus protection or anything installed that might normally cause issues.
Click to expand...
Click to collapse
Antivirus wouldn't cause zip errors like that. That can only be caused by a broken archive.
Here's my Google Drive mirror - try that
N970U_TLL_5.zip
drive.google.com

Found my Galaxy Tab 2 - doesn't boot!

I haven't used my Tab 2 (P5110) in a long time. I rely on my phone quite a bit instead.
Recently, I've been doing a bit of IoT stuff and though the Tab would make an excellent remote controller.
When I boot it, it shows the Samsung logo and goes no further.
Is there anything I can do to recover it, please?
I can get it into Odin mode, but I can't remember what can be done from there.
Can someone just steer me to a refresher, please?
Use recovery and do factory reset
KDMcM said:
I haven't used my Tab 2 (P5110) in a long time. I rely on my phone quite a bit instead.
Recently, I've been doing a bit of IoT stuff and though the Tab would make an excellent remote controller.
When I boot it, it shows the Samsung logo and goes no further.
Is there anything I can do to recover it, please?
I can get it into Odin mode, but I can't remember what can be done from there.
Can someone just steer me to a refresher, please?
Click to expand...
Click to collapse
You can flash TWRP from Odin and flash Custom Rom
drnightshadow said:
Use recovery and do factory reset
Click to expand...
Click to collapse
With apologies, if I knew what "use recovery" meant, I probably would have already done it.
Can you help, please?
hmd_msrf_k said:
You can flash TWRP from Odin and flash Custom Rom
Click to expand...
Click to collapse
I've downloaded twrp-2.8.5.0-p5110.tar.
The guide on the TWRP download site says I should install Odin and look for the "PDA tab or button". I have Odin 3.14.1 and the buttons are BL, AP, CP, CSC and USERDATA.
Elsewhere, here, I'm told to use AP. Is AP the correct / safe option?
Thanks.
KDMcM said:
I've downloaded twrp-2.8.5.0-p5110.tar.
The guide on the TWRP download site says I should install Odin and look for the "PDA tab or button". I have Odin 3.14.1 and the buttons are BL, AP, CP, CSC and USERDATA.
Elsewhere, here, I'm told to use AP. Is AP the correct / safe option?
Thanks.
Click to expand...
Click to collapse
Yes you can use AP, but why are you using too old recovery?.
New Version of TWRP is available and you should use that one
hmd_msrf_k said:
Yes you can use AP, but why are you using too old recovery?.
New Version of TWRP is available and you should use that one
Click to expand...
Click to collapse
It's the most recent one I could find as a .tar file. The more recent ones seem to be .img.
Download TWRP for p5110
Download TWRP Open Recovery for p5110
eu.dl.twrp.me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's not looking good for the good guys. Is this a dead loss?
Thanks.
Try different Odin, oldest is better
KDMcM said:
View attachment 5805273
Click to expand...
Click to collapse
Try Odin 3.07, it has PDA option, it may work
KDMcM said:
I haven't used my Tab 2 (P5110) in a long time. I rely on my phone quite a bit instead.
Recently, I've been doing a bit of IoT stuff and though the Tab would make an excellent remote controller.
When I boot it, it shows the Samsung logo and goes no further.
Is there anything I can do to recover it, please?
I can get it into Odin mode, but I can't remember what can be done from there.
Can someone just steer me to a refresher, please?
Click to expand...
Click to collapse
use old odin/heimdall and flash stock firmware
$cronos_ said:
use old odin/heimdall and flash stock firmware
Click to expand...
Click to collapse
Where can I get a heimdall Windows Binary, please?
Also, not sure where I can get stock firmware!
Thanks!
hmd_msrf_k said:
Try Odin 3.07, it has PDA option, it may work
Click to expand...
Click to collapse
Interesting. First try the progress bar went to about 80% and I thought it was working. Then it failed.
Second try ... waited for ages then failed outright.
Any other thoughts, please?
i
KDMcM said:
Interesting. First try the progress bar went to about 80% and I thought it was working. Then it failed.
Second try ... waited for ages then failed outright.
Any other thoughts, please?
View attachment 5807221
Click to expand...
Click to collapse
Interesting.
I have a couple of suggestions
1) Try to place the tar file in a folder without any spaces in the name in it and try to flash it again
2) Try to download the latest TWRP tar file from here https://dl.twrp.me/espressowifi/ and flash it with Odin 3.14.1
If none of this work, then I have no idea
KDMcM said:
Interesting. First try the progress bar went to about 80% and I thought it was working. Then it failed.
Second try ... waited for ages then failed outright.
Any other thoughts, please?
View attachment 5807221
Click to expand...
Click to collapse
use the latest odin, (in the latest it is called ap instead of pda partition)

Categories

Resources