Related
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Have you tried flashing different radios (baseband)?
http://forum.xda-developers.com/showthread.php?t=1785999
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Take a look at this thread, it may help. http://forum.xda-developers.com/showthread.php?p=25172599#post25172599
thanks for the replies...
I've flashed UCM1 and UCLL3 radios, they flash fine but no change...still can't flash to stock and no imei/baseband/service.
That fix thread was one of the first I found, but as I still have my keystr file in the efs folder, I didn't think it would apply to me...I suppose I could make an external backup of my efs, delete it and try one of those methods from scratch.
read through the restore to stock sticky http://forum.xda-developers.com/showthread.php?t=1652398 and go through the trouble shooting sections, if that doesn't help u could have bad hw
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
Just factory reset when it boot loops
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
causticfix said:
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
Click to expand...
Click to collapse
Yes I have two files in my imei folder i,e keystr and mps_code.dat!
I tired changing them from root explorer! pasted someones else's efs folder! but still I cant fix my imei is stays 0.
i donno how to get to diag mode with this rom, otherwise i could have tried my luck with QPTS.
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
lingowistico said:
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
Click to expand...
Click to collapse
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
causticfix said:
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
Click to expand...
Click to collapse
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
lingowistico said:
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
Click to expand...
Click to collapse
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Vgkiller said:
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Click to expand...
Click to collapse
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
lingowistico said:
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
Click to expand...
Click to collapse
This totally defeats the purpose of this forum then. Its sad.
Vgkiller said:
This totally defeats the purpose of this forum then. Its sad.
Click to expand...
Click to collapse
People want money for it because it's mostly used for making stolen phones work again.
That means real life risks like fines, jail etc.
Of course there are lots of examples when people experiment with this or that and delete their imei accidentally, or want to change the imei for some other reason. But these are more rare.
An update...
I managed to finally get flashed to stock...still null/null imei & baseband unknown. Efs folder is still there with files, keystr file is on...not sure what else I can do myself at this point so, I guess its time for the Polish dude or mobiletechvideos.
Hi People,
Did any1 found any solution?
talk2sharn said:
Hi People,
Did any1 found any solution?
Click to expand...
Click to collapse
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
causticfix said:
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
Click to expand...
Click to collapse
Ohkies.
Did you ask the polish guy about the reason why he was not able to fix your mobile. Coz, I'm just having similar problem like yours. I tried working with all the local samsung service centre guys, nothing worked. One guy said that my mobile IMEI is locked in some database, so it is not picking or detecting my SIM, hence locked. I know that my mobile is unlocked and is valid, I ignored his comments.
I assume you changed your MotherBoard of the mobile with the new cracked SR's, so that it could take new IMEI instilled in new board. Is it so?
Also, please suggest me about any alternatives on how to fix this problem.:crying:
Hi Everyone,
I'm new here and fairly new to android too but have a rough understanding as I would see it compared to most of you.
I have 2 phones here that I have acquired cheaply due to issues (not questionable backgrounds) and done extensive research here and across the net on each of their problems but come to no real conclusions with either one.
Phone 1: Galaxy S2 16gb GT-I9100
Phone operates perfectly... as a mini wifi tablet. Doesn't seem to recognize any kind of SIM I put into it, just gets no signal at all. Baseband, IMEI, IMEI SV, IP Address, etc are all unknown. Signal says 0dBm 99 asu. As far as I can tell from what I have read this is an EFS file problem.
I have tried swapping EFS file with one from another S2 I have, start up with a jig, new rom flashing x2, and have recently got a program call EFS Professional 2.0.70 but have no idea how to use it. I believe you can write an efs file but needs to be in Linux? I have also been told this is most likely a motherboard problem. What is the way to fix this myself if possible or possibly with someones assistance if you feel generous?
Phone 2: Galaxy S3 4G 16gb GT-I9305
One day the phone restarted itself and without showing any boot screen just showed a white screen with coloured dots shaded through it. This screen also happens when attempting recovery mode. I can access download mode. Phone appears in Odin.
I have tried try to flash official samsung release 4.1.2 BLL3 rom I get the error message that: 'There is no PIT partition'.
When flashing just cwm recovery or a kernal with no rom I get the same message. When trying to flash m3xx_i9305.pit I get: 'Get pit for mapping' and it just hangs on that. is this something that would take hours to do or is it just frozen? I also have PIT magic but not too sure how to mess around with that... Should I just get the text readout of the pit file from another i9305 and compare the 2 to make sure it's right? I have been told this will need a JTAG repair but then others have had success. The only thing I haven't been able to try yet is flashing a pit file with the rom as a 3 part file.
A repairer has told me that the S2 EFS problem is a maybe fix and could be the motherboard so not to get my hopes up and has also told me the the PIT problem is a fried flash chip and isn't really fixable.
Another offers JTAG for $60 and a $45 refund if it doesn't work and also an EFS repair service but is on holidays for another month.
Any help or advice would be greatly appreciated but I have researched this to the best of my ability so please only comment if you really know what you are talking about and have encountered (and fixed) either of these problems.
Thanks,
Regards Evcat
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
If you can't get into download mode then you don't have much to lose by trying what the other thread suggested.
@sacnotsack, thanks for the response, and that is my intention, however I am missing 1 crucial part to that thread and that is the debrick.img
Can someone with the PIA (G930TUVU4APIA) rom please post a dump of a partial system img for me? If I'm not mistaken, you can dump it with these commands in ADB.
adb shell
dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128
Just to clarify...
sda20 should be the system partition. Any way that's what it is for me.
You can check yourself by doing typing this in ADB:
ls -al /dev/block/bootdevice/by-name
You will get something like this:
lrwxrwxrwx root root 2016-01-08 10:35 system -> /dev/block/sda20
And to get the block size you would type this:
blockdev --getbsz /dev/block/sda20
So the command
"dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128"
If I get this working, I'll compile a nice tut for S7 users and post all the results with files in case anyone else runs into this issue.
Thank you in advance
I don't mean to be an annoyance, but does anyone have any thoughts or could point me to some direction? I know there are a lot of you that are much more knowledgable in this than I am, and all I'm hoping I can get assistance for is if someone can just make a dump of the debrick.img file so I can try to load it on my SD card.
Thanks
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
MetalPhoenix45 said:
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
Click to expand...
Click to collapse
MetalPhoenix45, thanks for your response. I have a Windows computer as well and I am very familiar with ODIN. The issue is, that in your explanation my guess is you are thinking the phone is in a "soft bricked" mode. The difference between a hard brick phone and a soft brick phone is that in a hard brick phone nothing is recognized when plugged in, it doesn't power on and it also doesn't show any sign of charge when it's plugged into the power.
In a soft brick mode, your phone can be stuck in a boot loop, or at the very least it still shows signs of it getting power. In which case I can just force into download mode and do what you stated above. I don't think that the things you mentioned above would work for me because when I have my phone plugged in to my computer, in device manager it doesn't detect anything. It doesn't even say unknown device or unrecognized hardware. It doesn't see it at all, and I have loaded the Samsung drivers on my pc because ODIN recognized the device prior to my issue.
I do have the stock firmware and everything on my machine, but I just can't get my phone to power or on into download boot even with a JIG.
m0d hipp¥ said:
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
crazynate121 said:
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
Click to expand...
Click to collapse
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
bah double post, sorry I can't delete this
Funny you said nexus just ordered 2 two days ago older 7 but 4g and and what not strictly for experimental and ethical purposes of course was actually shocked at the still high priced note 5 Screen tbh but we live and learn!! SOMETIMES? LOL
m0d hipp¥ said:
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
Click to expand...
Click to collapse
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
PadsPCB said:
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
Click to expand...
Click to collapse
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
m0d hipp¥ said:
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
Click to expand...
Click to collapse
Then i think got stuck, beacause in these forums there is no one willing/able/interested in helping anyone.
I said i'm in the SAME boat == I got an SM-G930T (from T-Mobile) that has a SnapDragon cpu but HERE in my country THERE ARE NO Snapdragons only Equinoxes. If we had such phones here surely i would have done this already, but G930F's won't do, as i have already tried.
So, as you know how i feel about a brand new SM-G930T Bricked, you wold be my last hope. There is no way to send it back to Samsung beacause it was bought from a friend and surely no warranty.
Anyway, best regards and rest in peace
Oh sorry, I misunderstood you. I'd like to think that it's not so much people don't want to try to help out, it's just that there is nothing that can be done for users on the snapdragon device so no one bothers unfortunately. Sorry to hear about this, and it really is unfortunate that you had to go through the same thing I went through with no help. Trust me, if I was able to do anything to provide any guidance I would.
Good luck!
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
UPDATE: found a stock system image dump, thank you to @lopestom for directing me to this. This guy's been the MediaTek king for as long as I can remember.
It appears to be a dtbo and system partition dump. It also has the vendor partition and a (partial?) boot image dump. Not sure if things like the full boot and recovery images are stored somewhere in here, I didn't look too deeply into it yet. I have no idea how whoever this is managed to pull these partitions... they either got root access somehow, or they found a proper Download Agent and Auth file to pull it all. Either one of these would be awesome. I reached out to the user to ask them how they did it, we will see what they say if they want to share how they did it.
https://git.rip/dumps/att/u304aa
jasonmerc said:
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
Click to expand...
Click to collapse
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
sjjtnj said:
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
Click to expand...
Click to collapse
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
jasonmerc said:
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
Click to expand...
Click to collapse
Right, I'm considering giving him my current phone when I get a new one. It doesn't seem like I'm going to be able to unlock and root it so I want a phone I can. Mainly for space personally. He's young so he doesn't need it rooted, but I'm thinking if I can root it then I might be able to use it to root my phone. Speaking of rooting I think I found a way to root this phone. It took me a couple days to get the phone since he said he couldn't find it, but I have it now. It just needs to charge, but the battery sucks so it takes forever. I did find out that it does have a decent recovery. I had booted it into recovery and then I was messing around with the keys after the little passed out green guy popped up and suddenly it loaded stock recovery. It had an option to mount the system and flash with adb and everything. The only problem is I kept booting it by messing with keys. So I honestly don't know which ones worked. I kept booting into it last night by messing with them, but now I can't seem to get it to boot into the right recovery now that I'm trying to figure out the right key combination. I will figure it out though (eventually) and let you know what you have to click, but if you get the chance just mess with it and hopefully you'll find it like I did.
Also I was looking up the phones variants and downloaded a couple stock roms that I felt had all the right specs I'm going to try to flash one if I can get it plugged in. I downloaded custom twrp image's for them as well, and even found one twrp that I was able to download in the app. If you used it then you know that it takes you to a download page if you are downloading the wrong twrp.img. So the fact it let me download it in the app meant it tricked twrp into thinking it was that phone. So I'm going to try that stock rom first. Maybe we'll be able to change it to another model. It really needs something flashed, because it's a mess. I thought he messed it up, but after reading what you said maybe it's just the phone. He's young so it doesn't matter as much to him, but I feel bad for my niece. I really need to look into at least getting her another phone. I'm going to work on it later today and see what I can do. First I got to get it to work on the computer, but I may be able to root it without the computer. I'll keep you updated with my progress.
any luck with this?
Yeh, is there a status update?
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
sjjtnj said:
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
Click to expand...
Click to collapse
I need to unlock my phone U304AA
Ok boys and girls, in case anyone is still wondering here is how to root this sucker.
https://drive.google.com/file/d/1--Ul1ae73zcejNuJ1a7ftq5sTo2VP8Ya/view?usp=drivesdk
Comes with two files. Mtksu amd magisk be sure to use the magisk version included in the zip. Install mtksu then wmagisk, open mtksu and install the top magisk option. Reboot then open magisk hit install when it asks. Now open mtksu scroll to the bottom and hit activate and reboot again. Should be good too go at this point. Oh yeah be sure to click apply at boot in mtksu. Not sure if this had been posted before or not. Now, to find a way to unlock bootloader and install twrp.
Thank you, I tried Mtksu on mine and it didn't work, but it might've been the phone. I don't have one of these anymore, but I hope you all the best of luck. For the bootloader and Twrp try Flashfire or flashify.
MTK bypass method released by some smart dudes out there. I will test if we can use SPFT on this phone now. Stay tuned. This could mean root & recovery in a matter of minutes.
EDIT: It ALMOST works. Technically it bypassed the auth file as advertised. The only thing left now is finding a compatible preloader/scatter file to use.
Used a modified Moto E6 Play scatter file to pull images from the device. Tried flashing over stuff and got an error. Long story short my U304AA is now permanently bricked, so I'm tapping out of this project here
I do have recovery and boot images that (supposedly) work if anyone else wants to try and take over Keep in mind these were pulled with a scatter file from a DIFFERENT phone that's of the same chipset, so not everything is guaranteed to work. For example, the preloader was pulled with the specified parameters but I do NOT know if it's functional
Because I'm tapping out, and because nobody else seems to have anything on this, I'm uploading everything I can. Some pulls are too big to upload and some just won't work for some reason, but use whatever you'd like for anything you can. Hope I did something helpful
I have searched in Google Search and the tutorials forum but not found a tutorial
_____________
Sent from my website: https://topsanphamhay.com/kem-chong-nang-danh-cho-da-dau-mun.html - https://topsanphamhay.com/kem-chong-nang-innisfree-perfect-uv-protection-cream-co-tot-khong.html - https://topsanphamhay.com/kem-chong...ifying-face-fluid-dry-touch-co-tot-khong.html using Iphone X
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
My wife and I just got one, so now I have two of these but I'm not sure I trust AT&T enough to use the "free" phone that they sent.
It would be great if someone can pickup this project, especially since so many phones are now flooding the market.
I just got 3 of these "free" from AT&T. In fact I don't really need them, I just happen to have phones with an IMEI number that AT&T cannot decipher, so they sent me new phones just in case I can't use 4G.
Anyway, I'm trying to use mine as spare Google assistants scattered around the house, but because they run that crappy Android Go, the Go version of Assistant won't listen to me until I long-press the home button. I would also like to use them when I travel as a spare.
These things are essentially throw-away, so I'm OK to risk bricking one of them.
What I really want to do is install a real version of Android on here, has anyone managed to crack this yet?
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
kayshinonome said:
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
Click to expand...
Click to collapse
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
luridphantom said:
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
Click to expand...
Click to collapse
Not possible to do, already tried before when I didn't brick it
KJ7LNW said:
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
Click to expand...
Click to collapse
Just got mine from this. I'd like to install something like NixOS mobile, but I've never used an android phone before. Will that be possible on this phone? If so, is there a good guide for newbs like myself?
As the title says no input or output possible on the phone only through cable in download mode or recovery but bootloader is locked and recovery is factory so not possible to execute commands to do data backup and also developer mode is not enabled. Only thing I see maybe possible is to flash the boot.img with devepolper mode and usb debuging enabled through Odin but not sure how to make the corrections in boot.img if even possible. I think that the android version is 11.
freextr said:
As the title says no input or output possible on the phone only through cable in download mode or recovery but bootloader is locked and recovery is factory so not possible to execute commands to do data backup and also developer mode is not enabled. Only thing I see maybe possible is to flash the boot.img with devepolper mode and usb debuging enabled through Odin but not sure how to make the corrections in boot.img if even possible. I think that the android version is 11.
Click to expand...
Click to collapse
If your bootloader is locked, you will not be able to flash a modified boot.img via Odin, it won't accept it.
If you did not have USB debugging enabled before this happened and if you don't have root or custom recovery, you will not be able to do anything to recover your data unless you find a professional shop that has the tools and ability to disassemble your device and pull your data directly from the hardware chip itself. Or you can get the screen replaced, if the screen is a verified exact match for your specific model number. Don't get a generic replacement screen that claims to be compatible, sometimes these require modifying your software to get them to work correctly, you do not want this.
Droidriven said:
If your bootloader is locked, you will not be able to flash a modified boot.img via Odin, it won't accept it.
If you did not have USB debugging enabled before this happened and if you don't have root or custom recovery, you will not be able to do anything to recover your data unless you find a professional shop that has the tools and ability to disassemble your device and pull your data directly from the hardware chip itself. Or you can get the screen replaced, if the screen is a verified exact match for your specific model number. Don't get a generic replacement screen that claims to be compatible, sometimes these require modifying your software to get them to work correctly, you do not want this.
Click to expand...
Click to collapse
Id like to learn how to do the data extraction from hardware. I already looked around a bit and if I understand correctly it should be something like a JTAG box ? Can you give me some direction where to start?
freextr said:
Id like to learn how to do the data extraction from hardware. I already looked around a bit and if I understand correctly it should be something like a JTAG box ? Can you give me some direction where to start?
Click to expand...
Click to collapse
I wouldn't know where to start. If I knew, I would have explained it instead of telling you to find a shop that can do it. If the data is important to you, I wouldn't risk trying to learn because you'll more than likely danage the device or destroy your data before you figure it out.
Droidriven said:
I wouldn't know where to start. If I knew, I would have explained it instead of telling you to find a shop that can do it. If the data is important to you, I wouldn't risk trying to learn because you'll more than likely danage the device or destroy your data before you figure it out.
Click to expand...
Click to collapse
Ok thanks
You might be able to use Find My Mobile or Smart Switch to back up your device, use a mouse or keyboard on your device, or connect to a PC monitor.