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.
Related
Hi there,
I'll try to make this brief. My touch screen has a 1/2" slice that is unresponsive (middle of the default google bar and down) and I am under warranty so I figured hey, let's call and get the phone warrantied.
Motorola is sending me a new phone when should be at my apartment when I arrive back from my travels.
My bootloader is unlocked. I understand there is no physical or theoretical way to relock thee bootloader; I get that. I am on 4.5.91. I never did the OTA updates; every update or ROM or anything since 1.26 has been from here. I've read a LOT in the last 24 hours.. and I'm concerned that trying to SBF anything over 4.5.91 will end up bricking the phone that I'm slated to return for a faulty screen. So, I was then thinking about moto-fastboot. That works for system and boot, but not bootloader, right?
My main concern is this: I don't want them to turn my phone on and see "UNLOCKED" in the top left and immediately charge me $499 for voiding the warranty. I DO understand this is a risk I took, and I am willing to eat the charge should it happen; but that withstanding my screen is legitimately borked. I'd be willing to try something to overwrite this bootloader if there were a tangible means to do it without like >80% chance of bricking it. Every SBF I've flashed on here has been pudding.
Is there anything that can be done to get rid of "UNLOCKED" up there? I know it won't relock the bootloader; but I want the techs to see that the screen is broke before they start snooping through system settings. I may get lucky, I don't know.
Also, anyone with experience warrantying a phone with an unlocked bootloader? How did it work out for you?
As it stands now I'm downloading the stock 1.8.3 system and boot images. But they won't overwrite the bootloader. I have about 4 days to figure this out before I fly home.
Thoughts?
I'm pretty sure you're stuck man.
Sent from my MB860 using Tapatalk
Hey I would play it safe and just buy another ATRIX off craigslist. I picked up an ATRIX in my area for 200 that is in mint condition. That sure beats the 499 they are going to charge you when they power on the device to check for user related problems before they slap a new screen on it and put it their refurbish phones inventory.
Sent from my MB860 using XDA App
I'd need somebody else to confirm this:
I thought that when you installed 4.5.91 through the safe .zip files, you were able to flash back to a previous SBF safely. I remember people in the IRC doing just that, and reporting that once they had done so, the "UNLOCKED" message on startup disappeared until they reflashed pudding. I'm pretty sure that it didn't actually relock the bootloader, just somehow get rid of the "UNLOCKED", but again I'm not entirely sure.
tl;dr I think you are safe to flash an SBF if you got GB from a .zip and that way you won't show "UNLOCKED".
I thought about that but I'd rather just get one from them if I'll be spending any money period.
I read a few posts that stated that there was a way to remove the "UNLOCKED" on the bootloader by flashing stock SBF's but I'm not sure if that would result in a brick at this point.. which is why I haven't tried it.
Either way.. I was also thinking: when they were troubleshooting me on the phone, they had me do a factory reset. This was yesterday. So, if it does brick I may have a "I did a system update and something went wrong" way out.
Would love to hear from someone who has experience with warranty services.
Thanks to both of you for your replies. I am also slightly inclined to believe I am boned. :[
KF as soon as someone verifies that I'll be happy to. I still have the 1.2.6 and 1.5.7 stock SBF's. To the best of my knowledge, I never let the OTA update happen. On my XOOM yes but not on the Atrix. Just unlocked, flashed what ever rom/zip I wanted, and went to town. Sucks that my screen blew I just had it where I wanted it with 2.3.4 :[
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
lauterm said:
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
Click to expand...
Click to collapse
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
deziguy420 said:
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
Click to expand...
Click to collapse
I love you both. It worked and I'm on the stock stuff now.
Everything else is up to the fate of the universe. At least they'll see that my screen is messed up before they start prodding around.
What happened?
Can you let us know if this was successful? I'd really like to do the same thing if it was...
I would like to shade some light to current situation regarding unlocking bootloader, custom roms, and using clockworkmod recovery on MOTO RAZR.
First of all to answer few common questions here.
1) Does Motorola Razr have locked bootloader?
Yes.
2) Is it possible to install ClockWorkMod?
Yes but with some caveats.
3) Is it possible to install custom ROM's?
Yes but there is several different methods of doing this (safestrap and bootstrap)
4) What is the difference between safestrap and bootstrap?
Bootstrap method works on the following way, it's basicly hijack of boot process
and running CWM instead of some other regular process, in RAZR method bootstrap process is hijacking logcat and running cwm. Current bootstrap method
works on all RAZR models from different carriers. J.Y.Daddy made his bootstrap method and compiled CWM for RAZR, more info can be found at original post
here.
Originally Posted by [TSON]
JYDADDY DID NOT MAKE CWM OR BOOTSTRAPPER. He kanged Nitroglycerin33 and got credit on a bunch of major websites for no reason
Click to expand...
Click to collapse
With bootstrap method we are overwriting original /system partition which may be a problem if something goes wrong because there is no way to do proper recovery (we have locked bootloader), also every time when phone reboots it goes first to recovery and then from recovery You need to select reboot in order
to boot normal system.
Safestrap works on opposite way by installing separate ROM in /preinstall folder
in order to avoid problems and have safe fallback in case that something goes wrong with custom ROM. On this way we always have safe fallback method and we can run original ROM. More info can be found here
Please be aware that safestrap works only on CDMA version of RAZR, at least for now.
Conclusion for now is that we have way to install and run CWM by using bootstrap/safestrap but only proper solution is to have unlocked bootloader,
according to some inside info which I got Motorola decided not to unlock bootloaders generally with full understanding pros and cons of this approach.
Since we had similar situation with Atrix couple of months ago and we manage
to overcome it with extracting bootloader from engineering version of sbf ROM and flashing it with RSD and after that doing normal fastboot oem unlock.
I think that this is only clean way to do the unlocking bootloader and have full
access to our phones.
I would like to invite people who participated in wide community effort to unlock
bootloader on Atrix to provide their support to do the same thing for RAZR.
In order to do this I believe that first step should be get access to engineering
and beta versions of ROM, since ICS beta firmwares should hit beta testers very soon I think that maybe good path to our final goal.
I will update this post regularly as soon as we have some development related to unlocked bootloader or some other method to achieve full access to our phones.
Press the thanks button.
Reserved..
Good brother, thanks for initiating to take the development forward.. I almost thought development is dead for RAZR except few developers like "Shady/Kholk etc..", did not see anyone digging in (especially GSM version)... Appreciate your initiation and hope to see some light on RAZR....
I'm sure that we will have soon some development going on, it's really shame that company such is Motorola which produces very innovative and high end products always needs to put some obstacles on our way to fully enjoy our devices.
As we saw already Motorola is doing some really cool things such is webtop, full phone encryption, fingerprint sensor on atrix which are not available on phones from other vendors and this is showing their R&D strength but marketing is other story and relationship to community is also something that they should work on.
P.S. nagnrik I see that You also have quite some history with Motorola
Yeah, That is really a sad part. It makes little sense(ignorable though) having been told from Verizon/AT&T, and locking boot-loaders. But, how about GSM? GSM mobiles too come with locked boot-loaders.
Motorola is very unique in whatever they present, from HW Finger print scanners to Software Smart Actions. The tech team did really excel in their work. RAZR is just an example of the way It has integrated all top notch technologies and super build quality framed into one single beautiful piece(I hate it is a bit wide thought, LoL). But true, their marketing strategy sucks..
Yeah, I have had a long Motorola history except for few HTC phones. And, MMI has quoted on its G+ status that something mind blowing on the way for CES'12.. LoL.. Let's hope not very tightly locked boot-loaders.. :-D
<https://plus.google.com/113884566566424587799/posts>
JYDADDY DID NOT MAKE CWM OR BOOTSTRAPPER. He kanged Nitroglycerin33 and got credit on a bunch of major websites for no reason
[TSON] said:
JYDADDY DID NOT MAKE CWM OR BOOTSTRAPPER. He kanged Nitroglycerin33 and got credit on a bunch of major websites for no reason
Click to expand...
Click to collapse
I strongly agree with Tson. I did testing with Nitroglycerin33 to get the Razr Bootstrap working. Check your facts.
*MOD. please move thread*
Sent from my DROID RAZR using XDA App
I had Atrix before my new Razr, i'm not a professional developer, but i will do what can i do, i'm who solved "sms delivery report" on Atrix,
i love moto brand, i think moto is the best & despite of this issues you said, i prefer to have a moto mobile phone forever,
These can not change my opinion about moto, i have a Samsung Juicer in my home and itz enough for me from Sami,
Count on me brother
Sent from my XT910 using Tapatalk
do you still need to do the safestrap/bootstrap method since the fastboot files are out.
Unless you really really like RSDLite, I'd still use safestrap. RAZRX and IC3 don't seem to like bootstrap
TSON I will update original post with informations which You provided.
[TSON] said:
JYDADDY DID NOT MAKE CWM OR BOOTSTRAPPER. He kanged Nitroglycerin33 and got credit on a bunch of major websites for no reason
Click to expand...
Click to collapse
Great news see here :
http://androidroot.mobi/t3_nvflash/
Preferable to go on dedicated thread here:
http://forum.xda-developers.com/showthread.php?t=1774352
Great news!
Now let's discuss advantages and opportunities that this will open up besides access to repair bricks. I gotta do some research I don't know nearly enough about nvflash.
Sent from my ADR6425LVW using xda premium
I can vouch that it *shouldn't* brick your device.
(Well at least it didn't for mine)
So which of you brave souls will try this first?
Striatum_bdr said:
Great news see here :
http://androidroot.mobi/t3_nvflash/
Click to expand...
Click to collapse
Our "official" xda post is here: http://forum.xda-developers.com/showthread.php?t=1774352
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
williemeiser said:
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
Click to expand...
Click to collapse
From my understanding, if you can flash the bootloader to their custom build one and get hold of someone else's files then it should work...
The thing is,i already flash the custom bootloader n its fine but i cant proceed after that since i dnt hv the files.
Yea I can confirm too it works fine.
If you are unlocked you don't have any disadvantages with this, you only get a very tight security net which recovers you from almost anything you can do to your prime
Apart from that you get some more (dev orientated) new features. Read more on the AndroidRoot site
This is great news.
williemeiser said:
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
Click to expand...
Click to collapse
You need files off your own device. You can't use someone else's files.
However, if you can fast boot flash our bootloader successfully, it's definitely recoverable!
If not, then sorry, it won't work.
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
demandarin said:
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
Click to expand...
Click to collapse
+ 1. I don't normally sound all this nooby dooby, I do a lot of mess on my Dinc2, but this is a pretty costly piece of equipment and is renowned to get bricked with the slightest provocation, SOoooooo.... An automated fool-proof and newb proof procedure is much required, for me and definitely for the many here...
litetaker said:
+ 1. I don't normally sound all this nooby dooby, I do a lot of mess on my Dinc2, but this is a pretty costly piece of equipment and is renowned to get bricked with the slightest provocation, SOoooooo.... An automated fool-proof and newb proof procedure is much required, for me and definitely for the many here...
Click to expand...
Click to collapse
You're right. It is a costly piece of equipment so it NEEDS people thoroughly reading OUR guides, our warnings, our information to fully grasp what they are about to do.
It does NOT need someone just loading a utility and pressing a button labelled: "GIMME NVFLASH ZOMG!".
Also, when it comes to hacking any device - there is no such thing as foolproof.
kmdm said:
You're right. It is a costly piece of equipment so it NEEDS people thoroughly reading OUR guides, our warnings, our information to fully grasp what they are about to do.
It does NOT need someone just loading a utility and pressing a button labelled: "GIMME NVFLASH ZOMG!".
Also, when it comes to hacking any device - there is no such thing as foolproof.
Click to expand...
Click to collapse
Yeah, I just read a similar post on the other thread and it makes sense.. Well, I need to find a day I am willing to spend unlocking my prime and doing stuff on it.. So far, couldn't convince myself to even unlock. Now, that time is probably coming close...
There are at least 2 threads about NVFlash already, people should follow the rules
thread 1 here
thread 2 here
bk201doesntexist said:
There are at least 2 threads about NVFlash already, people should follow the rules
thread 1 here
thread 2 here
Click to expand...
Click to collapse
Those threads are *****ing about there not being nvflash, this one is unrelated to your two examples, if you read the thread you may have seen that, however there is a thread in the dev section for the same thing.
It's Tapatalk's app fault, stickies are not displayed on the same page than regular posts... So didn't see the thread.
Reason to unlock
At last a real reason to unlock. I held off when the first roms appears due to the risk of full brick. Now there is no real risk, unless you brick while backing up your NVFlash files.
Now is the real time to experiment with roms and different device settings. Let the good times roll
I experienced issue when using Rom Manager Premium 1.0.7. In fact, when I want to go to recovery mode from the application to backup my current rom, the app automatically asks me to make a title for the backup. After that I continue, it shuts my device and restarts it and it says Failed to Boot 2 and Starting RSD Mode... and it stays there for few minutes and I assume that it is frozen then I pulled the battery out and restart the phone. It boots normally, so I try it again but every time when I give a try it does the same thing. What can I do?
I am using a rooted Atrix 4G with stock Gingerbread ROM 2.3.4 and the CWM recovery is already flashed before attempting to do the above procedures.
There's also a thing that bothers me, my Atrix is an unlocked phone (it is not those that is on contracted, "locked', with the carrier) and rooted, but I've hear some people saying that even your device is unlocked and rooted, that does not guarantee that the bootloader is also unlocked, especially with the Motorola devices. Am I corrected or is this the case?
Some other information about my device:
System version:
45.0.23.ME860.Retail.en.05
Model number:
ME860
Android version:
2.3.4
Baseband version:
N_01.100.00R
Webtop version:
WT-1.2.0-133_21
Kernel version:
2.6.32.9
[email protected] #2
APflex version:
GAS_ASIA_OLPSGBAPHKTWN_P011
GAS_ASIA_OLPSGBAPHKTWN_A001
GAS_ASIA_OLPSGBAPHKTWN_M001
Build number:
4.5.2A-74_OLH-25
PLEASE HELP!!!
Don't bother with rom manager. Its a crappy app that most times doesn't work. Besides which, it sounds like you are bootloader locked, which means you can't use a custom recovery until you unlock it. Best place to start is searching for the unlock thread, then you can begin to utilize fastboot to get a proper recovery and ultimately a custom rom if you choose.
I saw online that many people unlock their bootloader by using Command Prompt on their computer which I do not like since I am not good in computer language and entering codes. Any suggestion for a easy way to unlock the bootloader such as an application similar to Superoneclick for rooting [slightly complicated one is also accepted as long as no command prompt or computer language are involved]? Thanks.
The unlock method by using what you call "computer codes" is as simple as it gets. It's just a few commands. I don't think anybody is going to bother making a clickable GUI frontend for such a trivial task. I think your best bet is to just follow the procedure and quit being scared of "computer codes".
ravilov said:
The unlock method by using what you call "computer codes" is as simple as it gets. It's just a few commands. I don't think anybody is going to bother making a clickable GUI frontend for such a trivial task. I think your best bet is to just follow the procedure and quit being scared of "computer codes".
Click to expand...
Click to collapse
What he says is true. Until my atrix (had backflip and flipside previously) I only used one click root. Once I got the atrix, one clicks didn't work, so I just CAREFULLY followed instructions to root and eventually unlock 2 atrixes and I dislike codes as much as you. Its all in how much you read read read. Its well worth it to do so.
pre4speed said:
What he says is true. Until my atrix (had backflip and flipside previously) I only used one click root. Once I got the atrix, one clicks didn't work, so I just CAREFULLY followed instructions to root and eventually unlock 2 atrixes and I dislike codes as much as you. Its all in how much you read read read. Its well worth it to do so.
Click to expand...
Click to collapse
I also hear people say that Motorola put a code on Droid X that when you want to unlock your bootloader it will "permanently" brick your phone and you can not turn it on again. But I am not sure that if they do the same on Atrix or maybe some guys already crack it since this is not a news. Do anyone here has the same experience like this?
Hm. Seems to me you developed an irrational fear of all this due to an information overload, even though much of that information doesn't even apply here.
Do you think there would be a clear and detailed tutorial (which countless people followed successfully already) if this was really so risky?
Put some trust into our devs here, will ya? Nothing can go wrong so long as you follow the instructions PRECISELY and take necessary precautions (if a tutorial says to do a backup, you do it).
ravilov said:
Hm. Seems to me you developed an irrational fear of all this due to an information overload, even though much of that information doesn't even apply here.
Do you think there would be a clear and detailed tutorial (which countless people followed successfully already) if this was really so risky?
Put some trust into our devs here, will ya? Nothing can go wrong so long as you follow the instructions PRECISELY and take necessary precautions (if a tutorial says to do a backup, you do it).
Click to expand...
Click to collapse
Sorry about that, but unlike those of you who are in the game for years, right now I just got ONE (1) Android phone (and I just got XDA last night) so I can not get any error when doing these tweaks. Maybe I should slow myself down a bit and wait until Christmas after I got my Huawei Ascend D1 Quad to hack my Atrix. You know, it's like playing poker.
Oh yes. You should definitely not jump the gun and do something before you're ready. Do read and learn and educate yourself before you take any actions. Just keep in mind that this is not as complicated as it may seem.
ravilov said:
Oh yes. You should definitely not jump the gun and do something before you're ready. Do read and learn and educate yourself before you take any actions. Just keep in mind that this is not as complicated as it may seem.
Click to expand...
Click to collapse
So so true. So many people automatically panic at one minor thing (anyone who has unlocked their bootloader knows what I mean ) but if the tutorial is followed TO THE LETTER that minor thing is not an issue. Good luck and yes educate yourself.
OK I have question for developing if possible or someone more qualified than myself it's about the bootloader on verizon s4 I know it's locked down but I wondering if there is a way to go back to a previous version and unlock the bootloader
OK so here is what I did I tried unlocking bootloader with ez unlock for the s3 by the way this was my s4 i545 I tried this on .OK so I installed gave superuser permissions it said wasn't sure if my bootloader was unlocked but had a button to unlock it so I pressed it and it did something not sure what then it said it was successful. OK I then backed out and all my apps still worked phone still working until I powered down to try and get into download mode then phone bricked and yes hard bricked I know I can probably use jtag service for phone but my question is. If somehow it did unlock my bootloader can we use this and flashfire to maybe flash an older firmware like say the one that has an unlock able bootloader maybe
brandon79 said:
OK so here is what I did I tried unlocking bootloader with ez unlock for the s3 by the way this was my s4 i545 I tried this on .OK so I installed gave superuser permissions it said wasn't sure if my bootloader was unlocked but had a button to unlock it so I pressed it and it did something not sure what then it said it was successful. OK I then backed out and all my apps still worked phone still working until I powered down to try and get into download mode then phone bricked and yes hard bricked I know I can probably use jtag service for phone but my question is. If somehow it did unlock my bootloader can we use this and flashfire to maybe flash an older firmware like say the one that has an unlock able bootloader maybe
Click to expand...
Click to collapse
so your phone is bricked. is there anyway to get back the phone to usual or just throw it into the ocean? i think i have the same problem as you and my phone is "bricked". does it fixable?
Booboobanget said:
so your phone is bricked. is there anyway to get back the phone to usual or just throw it into the ocean? i think i have the same problem as you and my phone is "bricked". does it fixable?
Click to expand...
Click to collapse
If you are unable to get into dl mode, JTAG is required. Stop messing with the bootloader when you have no clue how it works
Matthew M. said:
If you are unable to get into dl mode, JTAG is required. Stop messing with the bootloader when you have no clue how it works
Click to expand...
Click to collapse
no by all means let him mess with it all he wants one less noob in this sub
Legitsu said:
no by all means let him mess with it all he wants one less noob in this sub
Click to expand...
Click to collapse
That's the stupidest thing i've seen on this board yet. But i haven't been here long. Samsung is a team full of selfish bastards for boobytrapping these things and trying to pawn them off as Look-see this here is android it's customizeable all you want, then they screw you into taking their lollipop crapware, and then they screw you into not being able to flash your way out of it.l And here you are saying crap like this. This place i thought was here for people to learn, but i've seen quite a few pricks here already in my short time. A lot of really smart helpful people. Two types that should be kicked off this place- idiots like you and people who talk too much like me.
Legitsu said:
no by all means let him mess with it all he wants one less noob in this sub
Click to expand...
Click to collapse
I always love coming here and reading your opinions. It gives me the greatest joy in life.
OK I have question for developing if possible or someone more qualified than myself it's about the bootloader on verizon s4 I know it's locked down but I wondering if there is a way to go back to a previous version and unlock the bootloader
Short answer: no, probably not.
Longer answer: if you want an unlocked bootloader, get a Nexus. I know that sucks, but I'm tired of messing with all this locked down.... stuff. I'll get my Nexus 6 in the mail tomorrow.
Long answer: sometimes, but it's a long, dangerous trip. (Not noob friendly at all-trust me, I've been there over and over)
If you remain undaunted, figure out what exactly which bootloader you have, and do some googling.
Matthew M. said:
If you are unable to get into dl mode, JTAG is required. Stop messing with the bootloader when you have no clue how it works
Click to expand...
Click to collapse
fortunately for everyone reading this, youre wrong. this brick is fixable with the boot.img file for the bootloader you were on when ya bricked it mounted to a sd card of equal size to the internal (if the phone came with a 16 but there was a 32 option, you can also use a 32). The hardware will look for the bootloader on the internal, and if it fails, it moved to internal sd, and if THAT fails, it looks finally on usb. There are many threads about this, and i personally fixed an sch-i535 in the EXACT same way.
also, not nice to chastise people when youre as wrong as they are...... so be nice......
---------- Post added at 02:31 PM ---------- Previous post was at 02:19 PM ----------
Airsoftjunky said:
Short answer: no, probably not.
Longer answer: if you want an unlocked bootloader, get a Nexus. I know that sucks, but I'm tired of messing with all this locked down.... stuff. I'll get my Nexus 6 in the mail tomorrow.
Long answer: sometimes, but it's a long, dangerous trip. (Not noob friendly at all-trust me, I've been there over and over)
If you remain undaunted, figure out what exactly which bootloader you have, and do some googling.
Click to expand...
Click to collapse
now this guy is on the right path. If you have a locked bootloader, the only ways to unlock it is if the carrier decides that its ok for samsung to issue a tar.md5 that can do it, a dev figures out a way around the security or if you were to connect the motherboard to a JTAG to force a previous firmware onto it that already has an unlocked bootloader. So if yours is locked, youll need to wait for an unlock or be clever enough to dink around with the coding and get it done yourself. That last option is not likely, not that im doubting your knowledge, its just that its nearly impossible to do so.
youdoofus said:
fortunately for everyone reading this, youre wrong. this brick is fixable with the boot.img file for the bootloader you were on when ya bricked it mounted to a sd card of equal size to the internal (if the phone came with a 16 but there was a 32 option, you can also use a 32). The hardware will look for the bootloader on the internal, and if it fails, it moved to internal sd, and if THAT fails, it looks finally on usb. There are many threads about this, and i personally fixed an sch-i535 in the EXACT same way.
also, not nice to chastise people when youre as wrong as they are...... so be nice......
---------- Post added at 02:31 PM ---------- Previous post was at 02:19 PM ----------
now this guy is on the right path. If you have a locked bootloader, the only ways to unlock it is if the carrier decides that its ok for samsung to issue a tar.md5 that can do it, a dev figures out a way around the security or if you were to connect the motherboard to a JTAG to force a previous firmware onto it that already has an unlocked bootloader. So if yours is locked, youll need to wait for an unlock or be clever enough to dink around with the coding and get it done yourself. That last option is not likely, not that im doubting your knowledge, its just that its nearly impossible to do so.
Click to expand...
Click to collapse
might wanna fact check before you got calling others out the sd recovery boot.img has not worked on the i545 since *NC5 it was removed for whatever reason (likeky to hamper attempts at unlocking it)
this has been confirmed by multipl devs
vzw s4 bootloader unlocking is completely dead stop giving false hope
btw good thread necro bro
Legitsu said:
might wanna fact check before you got calling others out the sd recovery boot.img has not worked on the i545 since *NC5 it was removed for whatever reason (likeky to hamper attempts at unlocking it)
this has been confirmed by multipl devs
vzw s4 bootloader unlocking is completely dead stop giving false hope
btw good thread necro bro
Click to expand...
Click to collapse
this is fact "bro". Ive walked a few people thru this process and helped them revive their "hardbricked" phones. Is it guaranteed to work on every baseband? No, there arent any guarantees in any of this stuff. And there wasnt any mention as to what baseband he was on.....
I never said that its unlockable, i was suggesting how one could go about unbricking their phone as opposed to throwing in the ocean.
and for your trolling, get a day job... youre terrible at it "bro"....
youdoofus said:
this is fact "bro". Ive walked a few people thru this process and helped them revive their "hardbricked" phones. Is it guaranteed to work on every baseband? No, there arent any guarantees in any of this stuff. And there wasnt any mention as to what baseband he was on.....
I never said that its unlockable, i was suggesting how one could go about unbricking their phone as opposed to throwing in the ocean.
and for your trolling, get a day job... youre terrible at it "bro"....
Click to expand...
Click to collapse
verizon section version phone verizon problems ONLY
bro
check your ignorance at the door please I don't need to be nice to wrong.ppl especially when they walk around acting like they know stuff and don't have a clue
Legitsu said:
verizon section version phone verizon problems ONLY
bro
check your ignorance at the door please I don't need to be nice to wrong.ppl especially when they walk around acting like they know stuff and don't have a clue
Click to expand...
Click to collapse
youre kidding right? i said BASEBAND!!! as in VERIZON BASEBANDS for the VERIZON S4....
bro....
im not gonna go thru my PMs to find the messages that i have from people who have had success fixing their phones with boot.imgs... even if i did, youre likely the type to say im faking it anyways... so just keep up the troll attitude, dont offer any help to anyone with your wrong info and just offer dead ends and "youre screwed" answers when there is an alternative...
bro... gawd, do you think this is jersey shore? who says bro anymore to people they dont know? is your chest all stuck out too? pffft...