Related
EDIT: Let's keep this thread focused on how we can move past old methods, and make some progress towards modding. Thanks, and any relevant input is welcome.
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
lkrasner said:
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
Click to expand...
Click to collapse
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
scott14719 said:
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
Click to expand...
Click to collapse
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it. I am trying to learn quickly, and as you all know, devices are very different.
From what I understand, LOKI allows recovery to be overwritten, or is at least more permanent. What happens if you were to totally kill your system, could you still get into recovery with loki?
I understand that this is not motorola, and I am not trying to be stubborn here, but I fell like the same basic boot hijack that a ton of locked devices use should work.
lkrasner said:
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it.
Click to expand...
Click to collapse
http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html
and http://forum.xda-developers.com/showthread.php?t=2292157
lkrasner said:
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Click to expand...
Click to collapse
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
scott14719 said:
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
Click to expand...
Click to collapse
Thanks, It still looks to me like loki is a bit more advanced than what I am talking about, though the underlying principle is the same. LOKI allows the phone to actually boot a kernel (or recovery kernel) a boot hijack just loads some files on top of what is already running.
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
ashaton said:
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
Click to expand...
Click to collapse
Thanks, I am sure that will prove helpful.
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
The entire thread is very interesting. Starting around "Post# 115" and beyond there is talk about (what i believe) you are trying to do with the bootstrap idea. Maybe it will help you.
scott14719 said:
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
Click to expand...
Click to collapse
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
lkrasner said:
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
Click to expand...
Click to collapse
I edited my above post. I believe around post 115 and beyond of the above linked thread there is some information about the bootstrap idea you have.
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
scott14719 said:
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
Click to expand...
Click to collapse
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I'm just theorizing there from what I "think" I know. It still might be worth a try. The resulting TAR could:
1. Work, and if so we will have an ODIN flashable firmware for MF3. It doesn't matter if it is 'Frankenstein'd" or not...if it works it works!
2. Not work, but only fail in ODIN not causing anything to change or brick.
3. Not work and cause a soft or hard brick that can not be recovered from because it didn't work.
So, once again, finding someone to test the finished product out would be an issue. I'm guessing someone that is already hard bricked and already previously on MF3 could test because they already have nothing to lose (with JTAG not working for MF3).
I think Aou has deconstructed the MF3 OTA and pulled the bootloader(s) out of it. If someone can pull an MF3 image from their device and the bootloader can be added to it...and it can be made into a flashable TAR, maybe it would work. I don't think it will because of the reasons I listed in my last post...but it might.
Anyone willing to put it together and try it?
I think the problem is that it won't be signed. That is how it was with the a2. We just used fastboot but it would not flash an unsigned image
Sent from my Nexus 7 using xda premium
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
Click to expand...
Click to collapse
ashaton said:
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Click to expand...
Click to collapse
Yup, that's what I was saying. I can try to port a bootstrap cwm, but I really do not want to be the one to test it
Sent from my Nexus 7 using xda premium
Alright, Im going to be completely honest. I am a complete and total noob to the tech behind smartphones. As Ive been learning, I tried rooting my Samsung Galaxy SII SCH-R760X, and after I attempted to flash a kernel that was suggested by this guide: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-galaxy-sii-sch-r760-generic-t1928566, my phone is now stuck at the logo with a warning sign at the bottom. After all this, I realized I made the worst possible mistake anyone could ever make: I didnt backup my system. Luckily, I didnt have much data on it anyway. At this point I am aware it has become a softbrick, and Ive looked at guides such as this one:http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571, but it still tells me to "put the recovery file in its place". Im assuming he's talking about the backup... which i dont have. If anyone could point me to where I can find a backup for it, or upload one for me, I would be incredibly in debt to you. Thank you for reading, I know how most people feel about noobs, but I dont know where else to go.
Please, if I am doing something wrong with this post, please tell me. I dont want to be an annoyance. In fact, this is my first time ever posting to a forum! Id love to get into smartphone tech, however, since I couldnt find a place to start, I made the foolish choice of simply diving in and ruining my phone (hopefully not permanently). Anyway, thank you for reading! Even if you cant help, I really appreciate the attention. Thanks!
RikkyRoe said:
Alright, Im going to be completely honest. I am a complete and total noob to the tech behind smartphones. As Ive been learning, I tried rooting my Samsung Galaxy SII SCH-R760X, and after I attempted to flash a kernel that was suggested by this guide: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-galaxy-sii-sch-r760-generic-t1928566, my phone is now stuck at the logo with a warning sign at the bottom. After all this, I realized I made the worst possible mistake anyone could ever make: I didnt backup my system. Luckily, I didnt have much data on it anyway. At this point I am aware it has become a softbrick, and Ive looked at guides such as this one:http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571, but it still tells me to "put the recovery file in its place". Im assuming he's talking about the backup... which i dont have. If anyone could point me to where I can find a backup for it, or upload one for me, I would be incredibly in debt to you. Thank you for reading, I know how most people feel about noobs, but I dont know where else to go.
Please, if I am doing something wrong with this post, please tell me. I dont want to be an annoyance. In fact, this is my first time ever posting to a forum! Id love to get into smartphone tech, however, since I couldnt find a place to start, I made the foolish choice of simply diving in and ruining my phone (hopefully not permanently). Anyway, thank you for reading! Even if you cant help, I really appreciate the attention. Thanks!
Click to expand...
Click to collapse
You have already found good threads.
To recover a soft-bricked device, you basically have to flash back an official firmware for your device.
The guide you found was for the GT-I9100G, which is a little bit different from your exact device model.
Here is another guide for other variants of the S2: [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED) by Phistachio.
As there is no "ready-to-go" recovery package available for your device model, you have to get an official/stock firmware for your device.
A link to possible firmware sources is in the first post of the guide you posted.
Flashing the stock firmware with Odin should fix the soft-brick.
If not, maybe a wipe data (= factory reset) in recovery mode (long press Volume UP + HOME + POWER) is needed additionally.
And rooting your device seems to be working with this too: [ROOT] Framaroot, a one-click apk to root some devices by alephzain ... I found some users confirming it working fine to root your device model.
If you still have issues and need further help, please ask in the [Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread by It_ler thread.
There we try to give detailed help for all variants of the S2.
Good luck !
Thanks for responding man! I didnt think anyone would reply.
I really appreciate the help. However, I downloaded and flashed the droiddroidz kernel turner78 said to flash, and that was what made my phone go softbricked in the first place... I tried flashing the other two kernels instead, and they proceeded to put my phone in bootloop... So, I tried flashing the "Siyah" stock kernel everyone was talking about, and it made this weird eye thing with a yin-yang flash on my phone... And Im sorry Im a total noob, I just recently learned what flashing and kernels were from the help of google :/... Im still a little lost on what Roms are. But reguardless, Im assuming the kernels I tried flashing were incompatible or corrupted, and thats whats making my phone not work. If Im wrong, correct me please. I know my phone is version 1.4.1, but thats about it. I dont know if its "Gingerbread" or "jellybean" or whatnot. Im sure Ive just made a stupid mistake and Im too dumb to know how to fix it.
RikkyRoe said:
Thanks for responding man! I didnt think anyone would reply.
I really appreciate the help. However, I downloaded and flashed the droiddroidz kernel turner78 said to flash, and that was what made my phone go softbricked in the first place... I tried flashing the other two kernels instead, and they proceeded to put my phone in bootloop... So, I tried flashing the "Siyah" stock kernel everyone was talking about, and it made this weird eye thing with a yin-yang flash on my phone... And Im sorry Im a total noob, I just recently learned what flashing and kernels were from the help of google :/... Im still a little lost on what Roms are. But reguardless, Im assuming the kernels I tried flashing were incompatible or corrupted, and thats whats making my phone not work. If Im wrong, correct me please. I know my phone is version 1.4.1, but thats about it. I dont know if its "Gingerbread" or "jellybean" or whatnot. Im sure Ive just made a stupid mistake and Im too dumb to know how to fix it.
Click to expand...
Click to collapse
As you have already posted in the help thread, this thread can be closed now.
Let's continue in the S2 help thread.
Thanks for your understanding!
Signature:
Device: SGS5 (SM-G900F)
ROM: AllianceROM v9.1
Kernel: Stock XXU1BOE6 kernel
Recovery: TWRP recovery by Ktoonsez
Modem: XXU1POG1
I really have no clue what I'm doing or where to look, and I have no choice but to register here and ask a question that's probably already been answered. Sorry for creating a new thread, but there's just too many to sort through. I just wanted to try asking if anyone has a working download link for Odin that's not malware. All of the links I keep finding are either fake or have been removed by a mod, or are just flat out dead links. Whenever I search online for odin, I just keep finding mostly harmful links. I simply want to get rid of the bloatware on my phone that Sprint's been installing as of late. While I'm at it, I might as well ask if this guide's legit as well: https://theunlockr.com/2016/12/11/how-to-root-the-samsung-galaxy-s5-all-variantscf-root/ ? This is what I've been using for reference. I've rooted an HTC-Evo phone in the past and flashed a cyanogenmod rom over the stock one, so this isn't a completely foreign concept to me. However, I haven't messed with this stuff for a long time, and I just wanted to know if I'm looking in the right place, and I figured I should come to a trustworthy site like this one to ask about it.
heres a link, ill get back on the other stuff in a bit, but ther eisnt a one-and-done method for all firmwares available for this phone
https://www.androidfilehost.com/?fid=23269279319197444
sorry, i got tied up at work, what firmware are you on? settings/about phone/baseband
I really appreciate your response. I managed to root my device through Odin, and proceeded with installing TWRP and a LineageOS rom for my device.
Please suggest somekind of guide or tool that makes easier to change 1+8t bootsplash..theres only up to 5t tool but it aint work for me, or i just cant.
Would really appreciated if some guru could help
Thx in advance
You talking about the unlocked bootloader warning?
If that's what you're talking about that,then I'm sorry you're out of luck. Google has hardware baked that into android from my understanding.
Good question but it might be difficult to convince some developers to build this patch.
It has something to do with logo and display time which can replaced but I am completely unsure about this.
I am waiting for proper TWRP and pretty bored to keep manually flashing everything.
I'm searching these forums, the web, every single website, and I still haven't came across a solution. Cyanogen, clockworkmod, they don't want to cooperate. I really am desperate now.
I'm trying to find a way to easily run a ROM on my phone, or maybe just install it. I'm aiming for Kitkat, but I have no idea how, as almost all of the posts on this forum contain broken links. Please, someone help!!!
Alex
Tell me about your fone.
Whats your skill set, as in do you KNOW how to unlock bootloader? Do you know how to root?
Firmware creators are too busy creating firmware. And fixing Bugs.
If your a noob, I can handle that, in effect, I need more information, because all those broken links are irelevant when what you actually need is found in millions of posts here..
The very reason developers dont answer
Pachacouti said:
Tell me about your fone.
Whats your skill set, as in do you KNOW how to unlock bootloader? Do you know how to root?
Firmware creators are too busy creating firmware. And fixing Bugs.
If your a noob, I can handle that, in effect, I need more information, because all those broken links are irelevant when what you actually need is found in millions of posts here..
The very reason developers dont answer
Click to expand...
Click to collapse
Okay.
My phone is a Samsung Galaxy W. It's model number is SGH-T679M and it is currently running Gingerbread.
And so I wanted to change that version because... Gingerbread is unsupported, right? So I landed on this forum first, trying out all the ways that I could, and most of them lead me to dead links as I said.
So I went on different web pages, the Android subreddit, all that. Ended up finding this zip file supposedly containing KitKat or something earlier.
I tried to install it how they told me. Already knew how to go into recovery mode, then it told me to go to the apply update from sd card (used the internal storage instead because i could) and it said the MODEL NUMBER WAS WRONG.
It was for the Samsung Exhibit II, model I8150, and that makes no sense. Because they are LITERALLY THE SAME PHONE.
Thought this was gonna be simple but it was being rough on me. This is why I need help, because I honestly don't know what to do anymore. It is so confusing.
Look at this:
h**ps://www.youtube.com/watch?v=et0AnYkBlc4
correct the link above copy n paste in your browser
Then say if you can handle the work, nothing more. If you are up for it, your best here
Pachacouti said:
Look at this:
h**ps://www.you tube.com/watch?v=et0AnYkBlc4
Then say if you can handle the work, nothing more. If you are up for it, your best here
Click to expand...
Click to collapse
Thank you, I will try it. I'll keep you updated if i didn't mess something up lol
Sincerely, Alex