Related
Okay, I couldn't find an answer I was looking for anywhere else; I'll try and keep it brief:
I am new to android. I rooted my Straight talk Galaxy SII with cyanogen mod 10.1, and everything went fine with it, no problems so far.
I introduced my friends to the wonders of rooting, and feeling unconfident in his own abilities, he gave me his Verizon Galaxy SIII for the night for me to root for him.
In short, I messed it up and now every time I try to turn it on or enter recovery mode, it gives me a yellow triangle, and says "Verizon has identified software on your device that is not approved, please bring it in to your Verizon store for help." or something along those lines.
I am done trying to root it now, because I do not want to mess anything up and just want to get it back to 100% factory stock so I don't have to pay for a new $700 phone....I tried following this ( http://forum.xda-developers.com/showthread.php?t=1840030 ) guide to reset the phone, but the link to the Root66.tar is not available anymore because Mega Share is gone, and when I downloaded the torrent, and tried to extract it with 7-zip, 7zip tells me into can't enter the archive.
I was wondering if anyone knew of that file located somewhere else where I can grab it myself (I already googled it) or if anyone has a better, simpler alternative to get this phone to factory stock?
I can still get into download mode, by the way, I just can't get to the home screen, or boot into recovery mode.
ANY help is greatly appreciated, I have already chewed off all my fingernails and am quite scared I completely trashed the phone. I don't plan on messing with any of this anymore after this.
Lol you'll be fine. You're seeing this warning because you didn't unlock the bootloader depending on how you rooted the phone. Use Droidstyle's guide in the dev section and Odin flash stock image of either VRALG1 or VRBLK3. It formats /sdcard btw.
Sent from my SCH-I535 using xda app-developers app
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!
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint. It would appear that Boost and Virgin Mobile variants can be flashed as they are used on Sprint's network, but no promises will be made.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing.
In the "CSC" box, use the file beginning with "home_CSC" to retain your user data, or use the "CSC" file to completely wipe user data. If you bricked your device, you may need to resort to using the "CSC" file. If you flash with "home" and it still fails to work, use "CSC." (that's my understanding of the two files anyways)
If you are down-grading, you may have to select the "NAND erase all" check box. This will completely wipe the device and should allow a fresh install. Be careful, if the phone dies, I would worry about a hard brick, but I'm not positive about that though.
Google Drive link:
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
There have been several reports that these Odin ROMs fail to flash. If that happens to you, you may be able to try an alternate procedure here. Keep in mind this procedure will trip Knox and probably void warranty if you haven't done that already:
https://forum.xda-developers.com/general/general/rom-stock-pl1-samsung-galaxy-j3-emerge-t3689346
The newer QI1 version is posted here, and has been confirmed:
https://forum.xda-developers.com/showpost.php?p=74171277&postcount=39
and if you're more enterprising with your computer and image file skills:
https://forum.xda-developers.com/showpost.php?p=74137125&postcount=29
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
Click to expand...
Click to collapse
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Doctur said:
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Click to expand...
Click to collapse
The system ROM is actually about five and a half gigabytes based on the storage info in the device settings (on my device anyways). So here's what I'm thinking makes sense for space required. I'm just gonna round the decompiled ROM up to 6GB to allow room to play with. Here's the space you'll need at a minimum:
1. 6GB for the compiled ROM.
2. 6GB for the decompiled ROM.
3. 6GB minimum for working with the ROM, so that your source is unmodified.
4. 6GB for the recompiled ROM.
So you'd need a minimum of 24 GB to work with, but the more you have, the more breathing room you have. This is just my 2¢... As for the rest of it, I have no real clue.
I just bought the j327p last week and I am returning it today if I can't get the tethering to work.
I tried editing a lot of the easily searchable fixes which there aren't many.
Do you know if installing this might work?
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
SammaelAkuma said:
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
Click to expand...
Click to collapse
It works and it's been updated from APL1 to AQB6 .. at least mine has .. and I don't know what was updated or what's new but it's still on Android 6.0 .. I just used this to fix my Boost J3 Emerge after it got stuck installing an app from the Galaxy S8
Doctur said:
...I believe a deodexed rom to be a pre-requisite to having the xposed
This link will get xposed to work...
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
TD378
Divided we stall,
United We Install!
Click to expand...
Click to collapse
Actually Wanam got xposed working on our device. Nice tut but its really almost standard issue when dealing with samsung. Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p, there are also many tutorials on how to do so, thanks for trying to help, but you could have just linked wanams thread wich has all cautions and tuts in like 12 words a HUGE thanks to Wanam for spending countless hours making a modded version of xposed that is compatible with ours as well as many other galaxy devices!!!
Project89Odin said:
...Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p...
Click to expand...
Click to collapse
Choose to stay away from "main stream" phones for a number of reasons.
But at the request of your post, link has been updated!
TD378
DIVIDED WE STALL
UNITED WE INSTALL
Thank you, the Galaxy J3 is not a very followed device by samsung of the fact that it is not high-end
________________________________________________________________________________
http://iphon8.fr/ galaxy note 9
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
Click to expand...
Click to collapse
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Download the default firmware here...
http://updato.com/firmware-archive-select-model?record=F2F2C99C28B211E7963AFA163EE8F90B
In Odin, put each file in the correct section "ex. APxxx goes in AP section."
Use CSCxxx file NOT Home_CSCxxx in CSC section. All data will be lost.
Brick problem will be solved. Let me know if you need a tut created.
TD378
Divided we stall
United we install
If refering to me as this being my first Samsung that would be a negative....mainly all ive dealt with or care to deal with besides a few exceptions ( IOS Not EVER being one of those) After all thesr years of either referring quickly to this site or the last 2 1/2 pouring countless hours learning random device or specific ...usefull or not (* Few times have i bee let downyet its been an occurance.. worth noting) I belived it was time to throw my hat inthe ring.
So mainly besides wanting to recontribute the resources I have.....mostly my hours of studying and stuff i picked up retentetion being put work and the test and the Love of Working in A Linux Terminal
(*Flavor preference is not important.)
And the Fact that I have a Laptop that can process at about 3.7ghz with 8 threads if you include hyperthreading...along with my growing older and not wanting to Let small contributions like that and Development left saught after by the few.....and honestly which matters in some places I am only scraping by so Financially I have nothing to offer the community along with Tha Mad Love I have for everything XDA ....put that together and you got me doing what I can..Lately it hasnt been to much but wait around and other issues that have eaten away at time leaving me unable to do simple things such as deodex......tho I was looking to do it the hard way and by hand..
My apologizies if the post after mine answered or the second one did but I have yet to read link .....so besides me knowing Wanam got a way around it for most the Install and Stuff
My true and Last Attempt at my first Question
FINGERS CROSSED
LONG
Would there be any necessity in the terms of Modular Functionality either individual or a compilation of your choosing and or combination that would specifically require you to deodex the firmware of any 5.0 or Higher Samsung Based Firmware so that one might have a higher sucess rate or all around better experince?
SHORT
Should i spend my time deodexing this rom for the few who have it in attempts to better the end user experience , spend my time else ?
Id like a little bit of step i the right direction but might just do it and then move to more time , intelectually and pc resource consuming work....
---------- Post added at 01:14 PM ---------- Previous post was at 01:04 PM ----------
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Umm I know if you downloaded off a disrepputable and FREE source that it might be the CSC partiton. I ll pm you with a copy of my firmware that was Adb Pulled by my old Firmware subcription site and did in Fact come from my device.....or the file was set to reupload for seeding purposes....idk either way we will handle this as a community united.
NOTE
I have since given device up....
Havent given up on it ...
So yeah to modding out a new more flagship type model...
Building ,Porting , Deodexing this J3 ....
And just seeing a lil development o a mid to low end device * price =low specs=mid....ish
Growing as a person in both knowledge and contributionally as well. Thanks 4 time.... **Sorry if I ramble.**
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
tac0xenon said:
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
Click to expand...
Click to collapse
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Greaper88 said:
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Click to expand...
Click to collapse
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
tac0xenon said:
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
Click to expand...
Click to collapse
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Thanks for the tips I'll try it when I get home and let you know how it goes much appreciated
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Had to flash three times but your advice worked thank you very much
Frp
Hello I have a question I'm a newbie and I would like to know if when I do install the stock rom does that mean I have to put in the google account information of the person providing the stock rom
Has anyone figured out a fix for this other than changing the bootloader? Some sort of build prop edit or something?
I'm so frustrated with how locked down Samsung, or as I call them "Sampple" (Samsung apple) is becoming.
I've tried downgrading the bootloader in Odin. With phone bootloader update checked, it either fails or freezes (when I remove md5). Only other idea I had is installing the bootloader portion afterward in twrp but I'm not sure if that's ever been done (successfully) before or if it's even possible at all. I did just today try using the build prop from nougat on marshmallow, this didn't work either... Thought maybe if the bootloader thought it was 7 that would be enough, but nope.
Everything else works perfectly, this is driving me crazy! If we know what we're doing well enough, and we purposely bought the model that comes with unlocked bootloader, why not make it *truly* unlocked? Give us an extra security warning on first boot of an older OS if you have to to cover your own butts, but let us do what we want...
I want that chunky touchwiz look and feel that everyone else hates. But custom roms come with too much of this or that having bugs or being left out altogether.
I already know the s7 isn't getting pie either, cuz that actually brought on a touchwiz feel to the "naked" OS, but everyone likes it now cuz it's not Samsung. Hardware wise I like the layout of the buttons and the fact that they're not just on screen (until s8 anyway). Maybe I'm old school but I like it.
To Google this downgrade issue, so so many people for whatever reason want to downgrade, yet they're making every effort to lock up their devices even further. I don't get it. Imagine how many happy people there would be if they released an update which then let us "legally" downgrade!
(If this is in the wrong area, someone feel free to move it! )
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
Has anyone figured out a fix for this other than changing the bootloader? Some sort of build prop edit or something?
I'm so frustrated with how locked down Samsung, or as I call them "Sampple" (Samsung apple) is becoming.
I've tried downgrading the bootloader in Odin. With phone bootloader update checked, it either fails or freezes (when I remove md5). Only other idea I had is installing the bootloader portion afterward in twrp but I'm not sure if that's ever been done (successfully) before or if it's even possible at all. I did just today try using the build prop from nougat on marshmallow, this didn't work either... Thought maybe if the bootloader thought it was 7 that would be enough, but nope.
Everything else works perfectly, this is driving me crazy! If we know what we're doing well enough, and we purposely bought the model that comes with unlocked bootloader, why not make it *truly* unlocked? Give us an extra security warning on first boot of an older OS if you have to to cover your own butts, but let us do what we want...
I want that chunky touchwiz look and feel that everyone else hates. But custom roms come with too much of this or that having bugs or being left out altogether.
I already know the s7 isn't getting pie either, cuz that actually brought on a touchwiz feel to the "naked" OS, but everyone likes it now cuz it's not Samsung. Hardware wise I like the layout of the buttons and the fact that they're not just on screen (until s8 anyway). Maybe I'm old school but I like it.
To Google this downgrade issue, so so many people for whatever reason want to downgrade, yet they're making every effort to lock up their devices even further. I don't get it. Imagine how many happy people there would be if they released an update which then let us "legally" downgrade!
(If this is in the wrong area, someone feel free to move it! )
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you have one of the Samsung devices that has a bootloader that blocks downgrading the firmware, you aren't going to find a way around it, people have been trying to do that for several years with no success.
The best you might can hope for is you might be able to download a copy of the downgraded firmware and a copy of your currently installed firmware, then take parts from the downgraded firmware(system.img, zimage, etc) and replace them into the copy of your current firmware, then repackage and re-sign the firmware into a modified stock firmware, then flash that modified firmware.
***NOTE***
I'm not certain which parts you will need to switch in order to get a working firmware that will successfully flash. The currently installed bootloader might not allow the modified firmware to flash without issues or it might actually work if you get everything put together correctly with the right pieces. You'll have to do your own steadying and researching to make this work.
Sent from my LGL84VL using Tapatalk
So, nobody has found a way to trick the bootloader? Rename a certain file or files to make it think the older software is the newer software, that way the bootloader and the user can both be satisfied with a fully functioning OS? I feel like with the high demand for the ability, surely someone has come across a way? Someone who knows more of what they're doing within the file manager in twrp?
I'm not opposed to more searching, it just gets in the way that most "solutions" on YouTube especially are to give up and upgrade your software, or use a total custom firmware. But they word it to look like an actual fix, not a tutorial on giving in.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, nobody has found a way to trick the bootloader? Rename a certain file or files to make it think the older software is the newer software, that way the bootloader and the user can both be satisfied with a fully functioning OS? I feel like with the high demand for the ability, surely someone has come across a way? Someone who knows more of what they're doing within the file manager in twrp?
I'm not opposed to more searching, it just gets in the way that most "solutions" on YouTube especially are to give up and upgrade your software, or use a total custom firmware. But they word it to look like an actual fix, not a tutorial on giving in.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I say again and expound, many, many, many, very, very, very experienced people have tried finding a way for years, not even a glimmer of light at the end of the tunnel, even after all this time. There is no way to crack it. No, there are no files that can be modified. The reason is because it isn't just software, there is hardware involved such that when the bootloader is first installed or updated via stock firmware update, there is a chip in the device(Qfuse) that stores that information, it can not be accessed or modified, if the bootloader is tampered with, it triggers Knox which triggers Qfuse on some Samsung devices, Qfuse is designed to actually "burn-out" rendering the device permanently hard bricked. I'm not up to speed on just how intricate the more recent Samsung devices have gotten with the hardware related security/anti-tampering measures.
Your question about TWRP is irrelevant because you have to unlock the bootloader BEFORE you can even install TWRP. So....no, not even with the built-in TWRP file manager.
As stated, the best you can hope for is to use the older software to package the newer bootloader(and other related files based on region and android version) into the older firmware then flash the newer firmware. With the correct modifications to the firmware, you can flash the newer software without violating the bootloader because you'll be using the same bootloader.
Sent from my LGL84VL using Tapatalk
I have twrp installed, with super SU, it is rooted. That in itself isn't the issue. So it's "unlocked" to a degree. Knox is already tripped so I'm not worried about that, I didn't buy a warranty anyway cuz I knew I'd want to root and debloat.
But the older firmware being used with a newer bootloader is from my reading what is causing the beeping instead of vibrating. This was more what I was trying to address when asking is there anything able to be modified to re enable true vibration despite the bootloader version and firmware version being different. I can flash ap cp and CSC from marshmallow with no issues at all, besides the vibrate not truly working. It's when trying to flash bl too which is causing the "sw rev check". That's what I don't understand on Samsung's end. It's unlocked.... But it isn't, not *really*. Unlocked should mean able to use any firmware you want as long as it's specifically for your device and region. But that's frustratingly not the case. They should know they have advanced users who want to do these things and know how. Those who would screw it up beyond their own repair don't know what rooting is to begin with (for example my mom, she barely knows how to use it as intended, she's not about to mess with Odin let alone twrp and root). They've probably dealt with more customer service issues locking things down so hardcore and people trying to work around it, than they would just letting things be modified.
It seems the only thing I can hope for is a way to enable the vibration again with the differing bootloader and firmware versions. Or, being able to use add ons/hacks to make nougat or Oreo look the way I want while still being newer to keep the bootloader happy. From marshmallow I want the more basic menus in settings, those shortcuts at the top of settings would be handy too. And I'm also a big fan of the "chunky" look that that version of touchwiz has in the notification area. I also much prefer sliding the toggles over instead of having to pull down twice to see all toggles. They took the touchwiz out basically for nougat and Oreo, I'm only looking to put it back in one way or another. I'm a big fan of the Samsung theme store which is why I'd like to keep things Samsung based too.
I thought of trying the superman rom but since it uses Samsung components, I'd run into the exact same issues trying to use the marshmallow version of that rom.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
I have twrp installed, with super SU, it is rooted. That in itself isn't the issue. So it's "unlocked" to a degree. Knox is already tripped so I'm not worried about that, I didn't buy a warranty anyway cuz I knew I'd want to root and debloat.
But the older firmware being used with a newer bootloader is from my reading what is causing the beeping instead of vibrating. This was more what I was trying to address when asking is there anything able to be modified to re enable true vibration despite the bootloader version and firmware version being different. I can flash ap cp and CSC from marshmallow with no issues at all, besides the vibrate not truly working. It's when trying to flash bl too which is causing the "sw rev check". That's what I don't understand on Samsung's end. It's unlocked.... But it isn't, not *really*. Unlocked should mean able to use any firmware you want as long as it's specifically for your device and region. But that's frustratingly not the case. They should know they have advanced users who want to do these things and know how. Those who would screw it up beyond their own repair don't know what rooting is to begin with (for example my mom, she barely knows how to use it as intended, she's not about to mess with Odin let alone twrp and root). They've probably dealt with more customer service issues locking things down so hardcore and people trying to work around it, than they would just letting things be modified.
It seems the only thing I can hope for is a way to enable the vibration again with the differing bootloader and firmware versions. Or, being able to use add ons/hacks to make nougat or Oreo look the way I want while still being newer to keep the bootloader happy. From marshmallow I want the more basic menus in settings, those shortcuts at the top of settings would be handy too. And I'm also a big fan of the "chunky" look that that version of touchwiz has in the notification area. I also much prefer sliding the toggles over instead of having to pull down twice to see all toggles. They took the touchwiz out basically for nougat and Oreo, I'm only looking to put it back in one way or another. I'm a big fan of the Samsung theme store which is why I'd like to keep things Samsung based too.
I thought of trying the superman rom but since it uses Samsung components, I'd run into the exact same issues trying to use the marshmallow version of that rom.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What you're looking for is to use the kernel from the firmware that supported vibration, this "should" fix that. I say this because the kernel is what tells the software how to use the hardware, in a manner of speaking.
Sent from my LGL84VL using Tapatalk
Droidriven said:
What you're looking for is to use the kernel from the firmware that supported vibration, this "should" fix that. I say this because the kernel is what tells the software how to use the hardware, in a manner of speaking.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Which part of the firmware is the kernel located in? It certainly sounds worth a try... If I can find it that is.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
Which part of the firmware is the kernel located in? It certainly sounds worth a try... If I can find it that is.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Typically, in Samsung firmware, the kernel is in the "zimage", the zimage is typically located in factory.fs image.
Try doing a google search for:
"How to extract kernel from samsung firmware"
That should find more than one guide to follow.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Typically, in Samsung firmware, the kernel is in the "zimage", the zimage is typically located in factory.fs image.
Try doing a google search for:
"How to extract kernel from samsung firmware"
That should find more than one guide to follow.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Is this something I'd be able to find via twrp? I know it would be a longer way. But, install nougat. Scoot through twrp to find the files needed, copy to external sd card. Then install marshmallow, but then paste/over write the files there?
I've been browsing a little within the files on my own, just to have a look not to modify yet, but keep coming across "boot image file is corrupted" in windows, but I know they're not as I can flash those same images to my device with Odin and they flash and work no problem, if I wanted to run 7 i can, or 6 without vibration I can, everything else works just fine. So I'm getting a false error it seems. This is with using the Linux diskinternals reader too. Most tutorials I'm finding show that method. I'm hoping maybe to find some alternate way.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
Is this something I'd be able to find via twrp? I know it would be a longer way. But, install nougat. Scoot through twrp to find the files needed, copy to external sd card. Then install marshmallow, but then paste/over write the files there?
I've been browsing a little within the files on my own, just to have a look not to modify yet, but keep coming across "boot image file is corrupted" in windows, but I know they're not as I can flash those same images to my device with Odin and they flash and work no problem, if I wanted to run 7 i can, or 6 without vibration I can, everything else works just fine. So I'm getting a false error it seems. This is with using the Linux diskinternals reader too. Most tutorials I'm finding show that method. I'm hoping maybe to find some alternate way.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not really, you need to extract it from the stock firmware file itself if you want to make a flashable copy.
Sent from my LGL84VL using Tapatalk
Pawprints1986 said:
Is this something I'd be able to find via twrp? I know it would be a longer way. But, install nougat. Scoot through twrp to find the files needed, copy to external sd card. Then install marshmallow, but then paste/over write the files there?
I've been browsing a little within the files on my own, just to have a look not to modify yet, but keep coming across "boot image file is corrupted" in windows, but I know they're not as I can flash those same images to my device with Odin and they flash and work no problem, if I wanted to run 7 i can, or 6 without vibration I can, everything else works just fine. So I'm getting a false error it seems. This is with using the Linux diskinternals reader too. Most tutorials I'm finding show that method. I'm hoping maybe to find some alternate way.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Then again, you could extract the kernel .img, then use terminal emulator with dd commands to install the kernel on your device, it would require knowing the exact dd command for your device based on its partition structure to make sure the kernel gets flashed to the correct partition on your device.
You might also be able to use TWRP to flash the kernel .img, it has the ability to flash .img files if you know how to get to that feature in TWRP.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Then again, you could extract the kernel .img, then use terminal emulator with dd commands to install the kernel on your device, it would require knowing the exact dd command for your device based on its partition structure to make sure the kernel gets flashed to the correct partition on your device.
You might also be able to use TWRP to flash the kernel .img, it has the ability to flash .img files if you know how to get to that feature in TWRP.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I haven't yet been able to find a file named kernel with a .img extension. I've found a couple files named kernel, but they don't show a file type at all, in fact windows properties just say "file" under type. That was looking around in nougat, I found that somewhere within the "meta data" folder. There was a file called kernel and a folder called ramdisk in the same area in nougat. In one of the folders within that meta data folder I found those.
In the marshmallow files at least on a brief look I couldn't find anything called kernel at all on windows anyway. Maybe without that mounting error I could. There was no meta data folder in marshmallow. I believe in nougat it was in the ap md5 but there's no such folder for marshmallow that I've found as of yet. Other than that, the main components seem to be the same. Just a matter of digging further to find that file I need.
I've thought about digging out my windows 7 laptop and trying that one instead of my windows 10 desktop to see if it makes any difference at all. With computers as with android, newer isn't always better!
Luckily I have the time to dig around and am in no huge rush. Would rather spend the time and research and start out on a proper OS i fully like than be rushed and have personal things on there I'd fear losing each time I experiment with it. Right now the only backups I'm worried about are for the OS itself, but that's not nearly as scary as personal/irreplaceable files
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
I haven't yet been able to find a file named kernel with a .img extension. I've found a couple files named kernel, but they don't show a file type at all, in fact windows properties just say "file" under type. That was looking around in nougat, I found that somewhere within the "meta data" folder. There was a file called kernel and a folder called ramdisk in the same area in nougat. In one of the folders within that meta data folder I found those.
In the marshmallow files at least on a brief look I couldn't find anything called kernel at all on windows anyway. Maybe without that mounting error I could. There was no meta data folder in marshmallow. I believe in nougat it was in the ap md5 but there's no such folder for marshmallow that I've found as of yet. Other than that, the main components seem to be the same. Just a matter of digging further to find that file I need.
I've thought about digging out my windows 7 laptop and trying that one instead of my windows 10 desktop to see if it makes any difference at all. With computers as with android, newer isn't always better!
Luckily I have the time to dig around and am in no huge rush. Would rather spend the time and research and start out on a proper OS i fully like than be rushed and have personal things on there I'd fear losing each time I experiment with it. Right now the only backups I'm worried about are for the OS itself, but that's not nearly as scary as personal/irreplaceable files
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You're looking for zimage. The kernel is in there.
Do a google search for:
"How to extract kernel from Samsung Firmware"
Sent from my LGL84VL using Tapatalk
Droidriven said:
You're looking for zimage. The kernel is in there.
Do a google search for:
"How to extract kernel from Samsung Firmware"
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
If any of it worked I would. This is becoming so impossible. Windows doesn't know what to do with img files so it doesn't mount them properly and sees them as corrupted even though they're not so I can't look at diddley squat inside of them. To look up drivers for said img Linux based files for windows just brings up the actual windows system os disk image file which is not at all what I need. My idea of browsing through them in twrp failed horrifically because once you click the boot.img it only gives options to delete, chmod, copy, move.... That's where I read the kernel is in, but it's impossible to get to. I've tried disk internals and osfmount. The latter will at least mount the image but then it still doesn't open because parameters aren't proper. Odin doesn't seem to know what to do with created files either. Tried one ap with system from Marsh and boot from nougat. it does flash properly, but then That just leads to boot loop.
I then tried flashing the nougat boot file and then separately the Marsh system image. As 2 different files in Odin in 2 separate sessions manually rebooting right back into download mode in between. This failed too. Boot loop. Same as combined. I figured it would be but worth a try.
..... No wonder people give up
The only other idea I've got with the tools i have that actually work is to flash the whole nougat boot img section separately as a zip file through twrp after I've installed all the rest of Marsh in Odin but I have no idea how badly that would screw things up. Or maybe it would just lead to that same boot loop.
If anyone can direct me to some sort of img reading system for windows that truly works and let's you into the inner workings of the img files I'm all ears. My windows 7 and windows 10 systems both show the same error.
Sent from my [device_name] using XDA-Developers Legacy app
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?