Continue reading at your own risk - I'm a noob
-------------------
I'm almost entirely a noob when it comes to phone development. But I've done a bit of research recently, and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1136261
Now that we too are running 4.5.91, would this method actually work?
If I were a rich dude I'd just go ahead and attempt it, but I have no where near the funds to be able to get myself a new phone if this bricks it. (I'm not even 18 yet, heh)
Don't bash me if this is a stupidly stupid idea that has no potential for success
I'm just trying to see if maybe this gives one of you super smart people an idea or two.
--------------------
So I unpacked the SBF from the aforementioned thread (the one that was supposed to prep bootloader for unlock) and loaded the code groups with HxD (hex editor)
Using this http://forum.xda-developers.com/showthread.php?t=1205527 the CG3 indeed has the values for Atrix, but also using that table i wonder if the sbf file can be modified to include the X2 values instead?
Again I'm a noob and just throwing ideas out there
Maybe ill try it when I get to my computer. I have a spare dx2 i could try it on fortunately!
Sent from my DROID X2
uhh186 said:
I'm almost entirely a noob when it comes to phone development. But I've done a bit of research recently, and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1136261
Now that we too are running 4.5.91, would this method actually work?
If I were a rich dude I'd just go ahead and attempt it, but I have no where near the funds to be able to get myself a new phone if this bricks it. (I'm not even 18 yet, heh)
Don't bash me if this is a stupidly stupid idea that has no potential for success
I'm just trying to see if maybe this gives one of you super smart people an idea or two.
Click to expand...
Click to collapse
Probably Not, Different signatures (and the risk of hard bricks), The2dcour is working tireless to bring the bootloader unlock to us, and don't feel bad we were all new once
ericerk said:
Probably Not, Different signatures (and the risk of hard bricks), The2dcour is working tireless to bring the bootloader unlock to us, and don't feel bad we were all new once
Click to expand...
Click to collapse
Probably not, but if IDMA.DROID.X2 is willing to risk hard bricking that spare x2, it might be worth a shot!
He might just get the worlds first unlocked Droid X2.
I'm willing to test anything on my X2 as well. I'm switching phones soon so unless my dad wants it, I'll either sell it or keep it for any future developments here..
uhh186 said:
Probably not, but if IDMA.DROID.X2 is willing to risk hard bricking that spare x2, it might be worth a shot!
He might just get the worlds first unlocked Droid X2.
Click to expand...
Click to collapse
All in the name of gloating haha
Ill try it tonight if time permits. I'm hoping that the signatures are the same!
The atrix is pretty much thr same spec wise right?
Sent from my DROID X2
Yes, besides the HSPA+ radio in the Atrix.
EDIT: Can I ask, what you are planning on doing? Just my curiosity.
So I unpacked the SBF from the aforementioned thread (the one that was supposed to prep bootloader for unlock) and loaded the code groups with HxD (hex editor)
Using this http://forum.xda-developers.com/showthread.php?t=1205527 the CG3 indeed has the values for Atrix, but also using that table i wonder if the sbf file can be modified to include the X2 values instead, and whether this might yield better/safer results?
Again I'm a noob and just throwing ideas out there
Less of a noob then me! Haha, I got lost reading that! I think we should mod it, seems like itmakes sense too.
I was going to try threw atrix unlock in the link in OP.
Sent from my DROID X2
The problem with modding it is that I don't know how the sbf file works... any modification with the files to make it reflect the x2 would require the insertion of bytes, I think... maybe not... either way we need multiple DROID x2s available for testing...
Sent from my DROID X2
uhh186 said:
The problem with modding it is that I don't know how the sbf file works... any modification with the files to make it reflect the x2 would require the insertion of bytes, I think... maybe not... either way we need multiple DROID x2s available for testing...
Sent from my DROID X2
Click to expand...
Click to collapse
This is a reply to most of the above posts as well as the quoted text.
The Pudding SBFs are signed by two or more source to specifically work with your phone / manufacturer / provider. There is basically no way to get around this besides getting the private signing keys from each source (and you think getting an sbf with unlockable bootloader is hard?)
I could make an sbf with the RDLs etc from the X2 and jsut the BL from Atrix, but the BL is still going to be signed for our(Atrix) phone. If someone seriously wants to brick their phone I'll do it for the lulz. You can probably even recover by stock sbf flashing (no guarantees, kiss your phone goodbye imho).
If you really want to give it a shot shoot me a PM, first come first brick. And please, don't give the file to anyone else, I don't want even more than one intentional brick.
the2dcour said:
This is a reply to most of the above posts as well as the quoted text.
The Pudding SBFs are signed by two or more source to specifically work with your phone / manufacturer / provider. There is basically no way to get around this besides getting the private signing keys from each source (and you think getting an sbf with unlockable bootloader is hard?)
I could make an sbf with the RDLs etc from the X2 and jsut the BL from Atrix, but the BL is still going to be signed for our(Atrix) phone. If someone seriously wants to brick their phone I'll do it for the lulz. You can probably even recover by stock sbf flashing (no guarantees, kiss your phone goodbye imho).
If you really want to give it a shot shoot me a PM, first come first brick. And please, don't give the file to anyone else, I don't want even more than one intentional brick.
Click to expand...
Click to collapse
Yeah that's basically it.
If you want to try to for the lulz, you would only want to flash the bootloader partition and not with the RDL partitions for the Atrix radio. Flashing the radio would instantly fail. You may need a more direct method in flashing like (dd if= of= ).
I wouldn't stop you from trying it. But you are messing with the bootloader and there's no guarantee that when you boot, you can get into a state where you can SBF again.
the2dcour said:
This is a reply to most of the above posts as well as the quoted text.
The Pudding SBFs are signed by two or more source to specifically work with your phone / manufacturer / provider. There is basically no way to get around this besides getting the private signing keys from each source (and you think getting an sbf with unlockable bootloader is hard?)
I could make an sbf with the RDLs etc from the X2 and jsut the BL from Atrix, but the BL is still going to be signed for our(Atrix) phone. If someone seriously wants to brick their phone I'll do it for the lulz. You can probably even recover by stock sbf flashing (no guarantees, kiss your phone goodbye imho).
If you really want to give it a shot shoot me a PM, first come first brick. And please, don't give the file to anyone else, I don't want even more than one intentional brick.
Click to expand...
Click to collapse
Ok, thanks for clearing that up.
I made it clear of my noobiness exactly for this reason. I don't know these things yet.
This thread should be deleted.
Sent from my DROID X2
uhh186 said:
So I unpacked the SBF from the aforementioned thread (the one that was supposed to prep bootloader for unlock) and loaded the code groups with HxD (hex editor)
Using this http://forum.xda-developers.com/showthread.php?t=1205527 the CG3 indeed has the values for Atrix, but also using that table i wonder if the sbf file can be modified to include the X2 values instead, and whether this might yield better/safer results?
Again I'm a noob and just throwing ideas out there
Click to expand...
Click to collapse
Yeah. We have the same partition table for the most part with the Atrix. The problem is that the at the bottom of the CG3 file is the signature and the signature is definitely NOT the same with the Atrix. Same goes for the bootloader, recovery and boot partitions.
Now we may be able to flash the Atrix bootloader since technically they have the same CPU and the the bootloader is nothing more than a BIOS. But there is no guarantee that the Atrix bootloader on the DX2 will work enough to the point where you can SBF out of it. Hopefully, you just fail the signature check and the phone allows you to SBF. We'll see if someone wants to try. And if you error, I want to know what the error says.
mostKnownUnknown said:
Yeah. We have the same partition table for the most part with the Atrix. The problem is that the at the bottom of the CG3 file is the signature and the signature is definitely NOT the same with the Atrix. Same goes for the bootloader, recovery and boot partitions.
Now we may be able to flash the Atrix bootloader since technically they have the same CPU and the the bootloader is nothing more than a BIOS. But there is no guarantee that the Atrix bootloader on the DX2 will work enough to the point where you can SBF out of it. Hopefully, you just fail the signature check and the phone allows you to SBF. We'll see if someone wants to try. And if you error, I want to know what the error says.
Click to expand...
Click to collapse
You are right on with everything you've been saying. I've in fact flashed unsigned / signed for other phone BLs on my Atrix. The result is a febe error (Failed to boot 4 or something). Basically it rejected the BL coz it wasn't signed properly but I could still recover.
That being said, what I did was idiotic and could have easily resulted in a hard brick.
@Uhh186 please msg a Moderator with a link to this post if you want it deleted. Honestly the best outcome of this would be a soft brick.
SwiftLegend said:
I'm willing to test anything on my X2 as well. I'm switching phones soon so unless my dad wants it, I'll either sell it or keep it for any future developments here..
Click to expand...
Click to collapse
Really!
PLEASE consider donating it to navenedrob.
Thanks
uhh186 said:
I have no where near the funds to be able to get myself a new phone if this bricks it.
Click to expand...
Click to collapse
No insurance?
If it in fact did flash, even if it soft/hard bricked the phone, would it be at all useful knowing that it actually passed the bootloaders sig check?
Edit: and what are the pros and cons of flashing, I'm thinking this(but could be way off base):
cons:
1. it doesnt pass sig check and fails but is more than likely recoverable
2. It passes sig check but the bootloader is incompatible with our phone( which from my perspective is unlikely because the hardware the bootloader depends on is similar/the same?) and is more than likely hard bricked
now for pro's:
1. It passes sig check, so now we know a little more about how the sign works if even a little?
2. It passes sig check and the bootloader is intact with the ability to unlock(score)
again I might be way off base, but only one out of four results in a hard brick(maybe) and thats only if the sig passes.
Am I close?
I also have another unrelated question. idk enough about the hardware, but would one be capable of physically flashing/backing up something from these partitions?
And by physically, I mean taking the phone apart and flashing straight to whatever memory our phone uses, effectively bypassing any soft/firmware on the phone. Basically, reflashing the "firmware" of our phone with an external NAND backup/restore which would mean no permanent brick and room to experiment.
the2dcour said:
@Uhh186 please msg a Moderator with a link to this post if you want it deleted. Honestly the best outcome of this would be a soft brick.
Click to expand...
Click to collapse
My main goal with this post was to spark some kind of a conversation between developers. I seem to have done that (woo) and because I'm still learning about all this stuff I'm going to leave it open so I get the chance to learn from all of you guys' smart posts.
While searching for a way to do what it says in the title of this thread, I ended up bumping into this app called Flash Gordon. It allows you to flash anything (Except for a custom rom) through the app itself and DOES NOT require a custom recovery. This is perfect for those that got their tabs RMA'd like myself and anybody else with a locked bootloader. I'm not really sure if this will actually work with us though, so I was wondering if anybody is willing to test it out. I would love to try it out myself, but I wouldn't want to end up with an unrecoverable tablet yet again, IF something happens that is. The link for it can be found right here: http://forum.xda-developers.com/showthread.php?t=2250555
UndeadKonvict said:
I would love to try it out myself, but I wouldn't want to end up with an unrecoverable tablet yet again, IF something happens that is.
Click to expand...
Click to collapse
Can anyone help me out i tried to restore my One via ADB but i failed so if anyone out there can help me ill glady appreciate it and i'm willing to donate some money in return, serious people only
thecityboy781 said:
Can anyone help me out i tried to restore my One via ADB but i failed so if anyone out there can help me ill glady appreciate it and i'm willing to donate some money in return, serious people only
Click to expand...
Click to collapse
Well, serious people that would like to help you would need way more information than you've provided. All you said was you tried to restore by ADB and failed.
Well, that says little to nothing about the situation you're facing. We need to know:
what is the actual problem you're seeing?
will the Rom simply not install?
will the Rom not boot?
are you unlocked? (Assume you are, but never know around here)
are you soff?
what bootloader are you running?
what ROM were you running before?
what Rom did you try to flash?
do you have the correct version of your custom recovery installed?
can you boot into it?
i fixed it it took me a while to restore my phone since no one here apparently saw my post and didn't ask like you did (kinda late tho) but it's w/e kinda disappointed but who cares now lol
so i had this thought. we talk alot in the "rom's" thread about the progression of the custom recovery.
although my phone is on servide and i cant do much ar this point but i hope i get it back in a couple of weeks.
but my thought was this.. everyone here should post all files they can to make this work.
what they have tried and what did not work so people dont have to try it again.
whos working hard on this and what theire progression is, or if anyone can post files that could work and perhaps some tutorials for it.
i think that would be better then to update this OP and write everything down that have been tried and so on.
it was just a thought to make this work out its best way. ive been sending PM's to som developers and asked if they could give me some tutorials on this but non has answeres yet. ive been trying alot of different adb reboot commands, nothing work. i also was that stupid and tried autorec for lg g2 and that bricked my phone HARD so dont ever try that.
Loki is the key for this phone, I don't think that anything else works.
Garcia98 said:
Loki is the key for this phone, I don't think that anything else works.
Click to expand...
Click to collapse
okej then. loki it is. now how do we go about to port this to our device?
found this, my phone like i said is on service so yeah, take a look
http://androidforums.com/motion-4g-all-things-root/733454-tried-port-loki-failed.html
and have a look at this http://forum.xda-developers.com/showpost.php?p=43480931&postcount=11
perhaps if we give djrbliss this info he can help us out?
Warning: Theoretical and last ditch effort to save a bricked unlocked device only.
I'm curious... I found a thread that some have hacked the MSM Download tool to allow flashing of any ops file. So if it's possible, could This Tool used with the Tmobile MSM Download unzipped get those who are unlocked unbricked to the Tmobile setup, then use the other thread Here to switch back to Unlocked? I do not have an unlocked phone, but I'm curious if someone is willing to give this a try on their bricked phone that can't return it now.
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
I take no responsibility for anyone flashing anything to anything. This is just a friendly sharing of information, and you do what you do at your own risk. I will not be held responsible for the apocalypse.
Older tools simply don't work, already tried during my earlier attempts of conversion.
I do believe that unlocked can be "full-converted" with MSMDT to TMo, but as you already said, that might end up with a deadlocked BL.
AndyYan said:
Older tools simply don't work, already tried during my earlier attempts of conversion.
I do believe that unlocked can be "full-converted" with MSMDT to TMo, but as you already said, that might end up with a deadlocked BL.
Click to expand...
Click to collapse
I figured if someone has missed their return deadline, it's something that could be used to get their "Brick" up and running, and hope that OP finally releases the MSMDT for unlocked someday.
mthous01 said:
Warning: Theoretical and last ditch effort to save a bricked unlocked device only.
I'm curious... I found a thread that some have hacked the MSM Download tool to allow flashing of any ops file. So if it's possible, could This Tool used with the Tmobile MSM Download unzipped get those who are unlocked unbricked to the Tmobile setup, then use the other thread Here to switch back to Unlocked? I do not have an unlocked phone, but I'm curious if someone is willing to give this a try on their bricked phone that can't return it now.
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
I take no responsibility for anyone flashing anything to anything. This is just a friendly sharing of information, and you do what you do at your own risk. I will not be held responsible for the apocalypse.
Click to expand...
Click to collapse
I have an unlocked phone bought from their website only .. i am going to try this and see if it works .. thanks
Dimitrimem said:
I have an unlocked phone bought from their website only .. i am going to try this and see if it works .. thanks
Click to expand...
Click to collapse
Note, this is only for terminally bricked phones. Do not use it phone is working.
mthous01 said:
Note, this is only for terminally bricked phones. Do not use it phone is working.
Click to expand...
Click to collapse
my phone got the Your device is corrupt my friend with the little link thingy at the bottom .. because i had it bricked for so long ( since august) now i cant even get the battery to charge so i can try this little hack .. but this gives me a little hope .. i will let the phone on the charger for few days see if it will work ..
Dimitrimem said:
my phone got the Your device is corrupt my friend with the little link thingy at the bottom .. because i had it bricked for so long ( since august) now i cant even get the battery to charge so i can try this little hack .. but this gives me a little hope .. i will let the phone on the charger for few days see if it will work ..
Click to expand...
Click to collapse
Let us know if it worked.