Related
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
From what I've heard, the "key" so to speak, in burned into the CPU itself. Its my understanding the only true way to unlock the BL is with Moto's keys, which we wont be getting any time soon. Whatever your plan is, I wish you the best. But we've had roughly 20+ of these threads come and go on here with everyone thinking they can crack it, and nothing ever pans out. Its a matter of the right people with knowledge and the right equipment to do the job, but those things have just not come together yet.
Once again, I wish you the best!
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
MrKazman said:
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
Click to expand...
Click to collapse
MrKaz,
+1 to your idea. Hey, who knows what will work.. with all that is going on, I wouldn't be surprised if the one idea that works..is some off the wall idea such as a chip flaw... Go for it man... I say take the idea and run with it.
best of luck
Your idea is one that I have been working on. All that needs to happened is find a way to dump the info to a computer and resign or make a dummy key to patch and inject back in.. unfortunately I have yet been able to inject anything because once dumped and cleared it doesn't regonize still active.. blah DX
MrKazman said:
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
Click to expand...
Click to collapse
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
gpaulu said:
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Click to expand...
Click to collapse
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
http://www.and-developers.com/boot:boot_chain
You may want to take a look at this. I think it's about the milestone, but it is similar to if not the same as the droid x
tekahuna said:
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
Click to expand...
Click to collapse
I love your honesty!
Sent from my DROIDX using Tapatalk
Syco54645 said:
I love your honesty!
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Beesley doesn't... LOL
http://twitter.com/TheRealBeesley/status/30036655129763840#
@LexusBrian400
build.prop edits vs. Droid X Froyo Overclocking & AP Mode Tethering
Maybe I should put up a donation link, huh? LOL
P.S. I can't help but think your username is a reference to B-Legit's verse on Sideways... Little known fact: The Ambassador himself gave me the handle FreeWELL.
http://www.youtube.com/watch?v=3YXGvsbSjLw
Didn't notice that you mentioned jared. I rather like him. Let's just leave it at that...
Sent from my DROIDX using Tapatalk
Update
I'm getting more and more familiar with this situation every day. I'm also starting to realize what a big problem this is. I've spent a good deal of time pouring over the work they're doing with the Milestone which is kind of the same thing but isn't. Nonetheless I applaud the work they do and donate my CPU to Androinc. After that I've been reading and collecting every Block Diagram, Datasheet, Whitepaper, and post about mbmloader, m-shield, omap, and the like. Yeah, its complicated alright. The fact is though that its just a lock. A lock is a system based on deterrent not prevention. Systems built for mass production have accepted flaws to keep costs down. Chips aren't perfect, code is not perfect. Use the weakness against the system and the lock is picked. The more complex the system the more chances to get in....
Eh, I digress...
Anyone wanting to learn more about this let me know.
The search continues....
Kaz
Motorola, I paid for the Hardware. I can handle my own software and security...
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Ubermicro13 said:
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Click to expand...
Click to collapse
Well ill drive to help out...as long as someone has some snaps on the petro!
Sent from my DROIDX using XDA App
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
As much as I want to believe that this can be done, its close to impossible and honestly not worth the persons time to try it, they did a good, well great, job of locking this thing down but ill say that liberty actually makes this feel like a new phone.
Sent from my DROIDX using XDA App
IWHBYD said:
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
Click to expand...
Click to collapse
Just take one for the team there buddy.... lol
Sent from my DROIDX using XDA App
what does the CEO of motorola look like?
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
openbox9 said:
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
Click to expand...
Click to collapse
not it *noses*
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Check out the Post Your eMMC thread in the general section, it will tell you how to check which one the phone has using terminal emulator. Phones with the "bad" eMMC cannot be rooted using the root.sh method, but can be with g-free.
King350z said:
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Click to expand...
Click to collapse
Root via gfree method...
Sent from my HTC Glacier Sense 3.0 using XDA app
King350z said:
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Click to expand...
Click to collapse
Before I learned about this website I had rooted my phone using the tutorial from the unlockr's website, gfree method.. Worked great.
saranhai said:
Root via gfree method...
Sent from my HTC Glacier Sense 3.0 using XDA app
Click to expand...
Click to collapse
you need to be careful before throwing out the idea that ./gfree is a fix all. It's not. It's a huge problem on phones that have bad eMMC chipset.
neidlinger said:
you need to be careful before throwing out the idea that ./gfree is a fix all. It's not. It's a huge problem on phones that have bad eMMC chipset.
Click to expand...
Click to collapse
Yea... That's what happened to my old MT4G
Best suggestion is to just keep stock.
Sent from my HTC Glacier Sense 3.0 using XDA app
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
U can also use launchers and home replacements if u get bored wit stock
McSurge45 said:
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
McSurge45 said:
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
Click to expand...
Click to collapse
I wouldn't say don't put roms on your phone EVER.... but before you do make sure you check what emmc chip you have. If you have the bad one you're sort of giving your phone a death sentence by rooting with gfree. It might last a good while, but most likely your phone will brick itself at some point. And considering the root.sh method doesn't work with the bad chip, gfree is your only option.
Basically, if you have the good chip feel free to flash roms to your delight, AFTER YOU INFORM YOURSELF HOW. But if you have the bad chip just know that your phone is at risk of dying if you root it.
AlanB412 said:
I wouldn't say don't put roms on your phone EVER.... but before you do make sure you check what emmc chip you have. If you have the bad one you're sort of giving your phone a death sentence by rooting with gfree. It might last a good while, but most likely your phone will brick itself at some point. And considering the root.sh method doesn't work with the bad chip, gfree is your only option.
Basically, if you have the good chip feel free to flash roms to your delight, AFTER YOU INFORM YOURSELF HOW. But if you have the bad chip just know that your phone is at risk of dying if you root it.
Click to expand...
Click to collapse
I have rooted and unrooted my phone(with the bad chip) many times, which writes to the emmc and power cycles it and flash at least 5 ROMS a week and flash back to nandroid backups as well during the week, so saying the bad chip and gfree combine is the issue is not true... There are cases of the root.sh emmc failure as well just not as many.... There is something more at bay with the bad emmc that has to be a common fail point not known yet. Cause as much as my chip has been power cycles and written to, it should be the first to fail! Just my two cents...
Sent from my HTC Glacier using XDA Premium App
irrelephant said:
I have rooted and unrooted my phone(with the bad chip) many times, which writes to the emmc and power cycles it and flash at least 5 ROMS a week and flash back to nandroid backups as well during the week, so saying the bad chip and gfree combine is the issue is not true... There are cases of the root.sh emmc failure as well just not as many.... There is something more at bay with the bad emmc that has to be a common fail point not known yet. Cause as much as my chip has been power cycles and written to, it should be the first to fail! Just my two cents...
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
+1 I have heard more horror stories about root.sh and visionary method failures then gfree method there's got to be more to the story then just the bad emmc chip and using Gfree to root. I used Greer to root as well and have bad emmc but good display and I'm a crack flasher, tho I've slowed down a bit after finding my 3 favorite roms.
Sent from my HTC Glacier using XDA Premium App
@Irrelephant & DrunkBastard
I don't intend to discount your experiences with what I said. Like I posted before, I have read about plenty of people with bad chips who have spent a long time flashing and reflashing their phones, so I can totally believe that you guys haven't had any problems with it or gfree. And considering the nature of rooting I can also believe that people have messed their phones up with the visionary method as well, especially since I actually was one of those people. However, I was fortunate enough and informed enough to fix it without any lasting damage.
As you said, the emmc chip problem is something that nobody is entirely sure about, but the general consensus seems to be that they are much more likely to fail when you have the bad model, whether or not you have rooted your phone or flashed roms or anything. I've even read some cases where people with entirely stock phones have had it fail on them.
On top of that, the gfree method, while very reliable, relies heavily on that chip. I can't honestly say that I know the exact processes that are different between the visionary method of rooting and the gfree method, but from what I've read gfree is more of a hardware oriented approach to achieving s off while visionary is more software oriented. Feel free to correct me if I'm wrong, I'm here to learn just like everyone else.
I guess it was sort of bold(and grim) for me to say that having a bad chip and then rooting it was a death sentence for your phone. What I was trying to get across was that the bad chips definitely do have a worst reputation. And while anybody who wants to root their phone should try and be as well informed of the risks and processes as possible, I think that if you have a product with a bad reputation you should read up about the problem and what extra risks it may cause.
ALL of the evidence doesn't point towards death sentences for bad chipped phones, but a lot definitely points to major problems with the bad chips, and that's something people should know about, particularly if they are one of the people who have it.
So in the end, people just need to try and make well informed decisions about what they will do with their phones(and the same can be applied to life I guess). That's what I was trying to get across. Sorry if I bothered you guys with my strongly worded post before, I just wanted to make sure people knew what they were getting into before they jumped into the pool.
____________________________________
Sent from the AFB Corporation's Main Communication Portal
AlanB412 said:
As you said, the emmc chip problem is something that nobody is entirely sure about, but the general consensus seems to be that they are much more likely to fail when you have the bad model, whether or not you have rooted your phone or flashed roms or anything. I've even read some cases where people with entirely stock phones have had it fail on them.
Click to expand...
Click to collapse
That.
Moreover, I had an experience with Desire S (HTC Saga) with the aforementioned "bad" chip, and I can confirm it's prone to failure even in completely stock form. The "bad" chip seems to have a bad production run or post-silicon verification issues, since there are many perfectly fine specimens, yet more than enough reports of failing devices, not necessarily rooted. Of course, vast majority of reports on XDA would be of rooted devices, since this is what XDA is about.
Judging by the time-to-failure reports for those chips, it's probably safe to say that 2-3 weeks of heavy use would be a good checkpoint - if a chip is prone to failure, it'll fail within 2-3 weeks of heavy use, and if it didn't fail - it'll most likely serve the regular lifetime of eMMC (which isn't eternal either).
There was an interesting hypothesis for this chip's failures in one of the threads at Desire S section, which might be worth checking. It was said that the chip is most likely to fail when it has power failure (intentional or not) during write cycle. Which means, pulling the battery while installing the app, for example, has a high chance of bricking a completely stock device.
i totally agree with both of you guys!!! and as jack stated, i think there was just a bad production run, or lot run for that matter... but all in all, rooting your phone is taking a chance since there are always unknown variables that could come to play. i have noticed that my phone with the bad chip has always been a bit more wonky that the one with the good chip, but i continue to use the bad one to flash away with because it was the one i started all the crack flashing on and if it fails, then it fails! i kinda wish it would fail so that i can start poking around at it to see what craziness i can find in there... i am all about troubleshooting things and if all else fails then i can send it in under insurance!
i think people should read and know what could happen and make a choice based on that, but i see too many ppl trying to scare off users because they have the so-called bad chip... but the bad chip has been good to me over a yr now and i continue to abuse this bad boy more than the average user!
and nothing anyone says on here is going to get me BUTT HURT, i am always open to a good debate on a controversial topic... so long as it is civil that is, cause if it gets ignorant, then i just leave it at that... to in the end, thank yall for holding open debate with me as it keeps me informed and thinking!!!
I wish you could buy the phone and pick the rom it comes with......
1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK! Also, updating to v4.5.141 and than unlocking the bootloader will also cause a hard brick!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
3.Xoom ICS release
The release of ICS for the Motorola Xoom does not help in any major way to the development of ICS on the Atrix.
Explanation/Elaboration: Yes, we do need the ICS kernel for Tegra 2. Yes, the Xoom uses Tegra 2. No, they are not the same. The atrix uses the Tegra 250 AP20H while the Xoom uses the Tegra 250 T20. Yes, the one on the Atrix is slower, but more importantly, different! (Thanks live4nyy!)
4.Carrier Unlocking the Atrix (NOT BOOTLOADER UNLOCK)
This is less of a myth, more of a guide. If you CANNOT unlock the Atrix even with the code provided (I can/will not provide), do NOT keep trying. All you are doing is wasting the number of tries you can try before the phone will not accept any more tries. What you should do is flash to an AT&T rom/radio and try again. This is assuming you want to unlock the AT&T version of the Atrix of course. Once unlocked, the Atrix can be flashed to your hearts content and will not be re-locked. (Thanks Abu-7abash!)
Any other widely mistaken facts about the atrix you want corrected?
Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head
matthew5025 said:
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.
UFOs > Bigfoot
matthew5025 said:
1.Bootloader!
When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible.
Click to expand...
Click to collapse
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?
stang5150 said:
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?
Click to expand...
Click to collapse
eFuse is an IBM invention. I posted a lengthy explanation of this a long long time ago after verifying the Atrix was using eFuse technology. When you read eval's explanation it is very accurate, except that you cannot "burn a bit". You could "set a bit" which sends the signal to overload the hardware circuit.
Carrier can specify they want a locked bootloader or not. I believe the method could be up to the manufacturer, but carrier may also specify type of bootloader lock. Of course, manufacturer may have an internal policy that all phones have a locked bootloader, but include provisions for unlocking it.
eFuse does not blow a fuse per se. This implies there is an actual fuse in the phone. eFuse (electronic fuse) is a circuit built into a chip inside the phone. When you unlock the bootloader a very small electrical charge is sent to that circuit and simply overloads it and burns it out. eFuse technology is not solely used for bootloaders. They are in many more electronic devices than you may think. eFuse is both software and hardware based. Software sends the signal, hardware circuit is blown, software checks this circuit on boot-up, when the circuit cannot be completed the software knows this, and reports, in the case of a phone, that the bootloader is unlocked.
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
---------- Post added at 12:31 PM ---------- Previous post was at 12:25 PM ----------
ifalldownalot said:
UFOs > Bigfoot
Click to expand...
Click to collapse
This ^^^^^^^! LOL
matthew5025 said:
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Well as far as I know UK version is safe to flash back to froyo. I went back from 2.3 to froyo sbf few times myself and few other people confirmed this aswell.
/edit
Never upgraded OTA so my post is useles...nice!
matthew5025 said:
1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Oem lock ******
Tried?
Sent from my MB860 using XDA App
Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL
Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk
jgc121 said:
Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head
Click to expand...
Click to collapse
Thanks! Its annoying the way they keep repeating the same stuff over and over again isn't it? Drives me up the wall!
live4nyy said:
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.
Click to expand...
Click to collapse
Thanks! Will include that point!
CaelanT said:
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
Click to expand...
Click to collapse
The reason I created this thread is so that the next time I want to correct someone, I just link them here, instead of typing out the whole thing again.
On a separate note, I see you are really active on in the Atrix community, helping others. I would like to thank you, a person who is knowledgeable, taking time to answer their questions. Can't say the some about myself.
guidoido004 said:
Oem lock ******
Tried?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
?
ssmr2t said:
Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL
Click to expand...
Click to collapse
Isn't it next Saturday? And the iPhone is the "hottest" phone here, accessories for iPhones, yes, Atrix, little.
Abu-7abash said:
Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
Thanks! Will include that!
Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there
ssmr2t said:
Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there
Click to expand...
Click to collapse
hey, hey, hey. get a room, you two. keep this thread myth related.
Now that we have smaller ASOP/AOKP ROMs, is it possible to Re-Size the System Partition to fully leverage the extra space that before was being used by the Samsung ROM?, thanks
I remember someone saying that, due to the fact the internal memory drivers are proprietary, there wouldn't be a way to resize partitions. Hopefully I'm wrong, though.
What I'm really hoping for is a well-laid-out tutorial for reallocating your external SD card as internal storage.
i'm wondering the same, recently installed SlimBean, still only have 9.7GB free of Internal Storage, my system root indicates only 2.6GB, thats 12.3GB, is that all the 16GB models have after formatting?
i think someone will have to get us to an engineering hboot of sorts
This will likely never happen, period. The eMMCs used in most Android smart phones are only set up to allow partitioning once at the factory, and then never again. It's a hardware thing. You can partition and divide up more, but you can't reclaim or change what's already been partitioned(unless you did it).
What's more likely to happen is, just like with most other Samsung phones I've owned, someone will take the Internal-External-Swap script and modify/update it to work on the Galaxy S4. Basically what this script does is change the mount locations inside the phone so Android believes the SD card is the internal storage, and the former Internal Storage is the external.
EDIT: Example of the script being modified/updated for the Galaxy Note 8.0: http://forum.xda-developers.com/showthread.php?t=2276193
We did on the Nexus One to get ICS on it. Called Blackrose. S-Off was created, not true, but enough to allow a hex editor to resize partitions. I did this many times to make System larger and Data smaller to flash the bigger rom's like ICS that needed more System size to run properly.
It was developed because of a strong need. If the need is not big enough, no dev may waste their time. The One S got that capability too--
rugmankc said:
We did on the Nexus One to get ICS on it. Called Blackrose. S-Off was created, not true, but enough to allow a hex editor to resize partitions. I did this many times to make System larger and Data smaller to flash the bigger rom's like ICS that needed more System size to run properly.
It was developed because of a strong need. If the need is not big enough, no dev may waste their time. The One S got that capability too--
Click to expand...
Click to collapse
While I acknowledge those feats, from my quick research, I'll point out that those were both done with custom HBOOTs which changed the bootloader. As the Galaxy S4's bootloader is not only locked but encrypted, I still have my doubts about this being able to be done.
Were the Nexus One or HTC One S able to reclaim internal storage space for the user in the way that the OP is asking? I'm curious because while making System larger and Data smaller is an good example of re-partitioning, weren't you simply moving around space that was already reserved to the OS area and unavailable to the user... if that statement makes any sense. This is stepping outside my realm of expertise here, and I'll admit that my technical knowledge is very limited. The last time I heard these proposals were back when the T-Mobile G2 came out and folks were asking the same questions then.
EDIT: Ultimately you're right, and demand will drive innovation either way. IF the devs find a way to do this, I'll be pleased. If they find way to swap the internal/externals, I'll be happy with that too.
It was a moving around of sizes. Make one larger and one smaller. Total size had to remain same. Not sure if anyone will do it. But, may be possible. Outside of my expertise too.
Sent From My 32gb Samsung Galaxy S4 using Tapatalk 2
Awwww crap. In that case I think I'm refusing delivery of my AT&T GS4. Sucks...
the pit file for the gegs4 would resize it
HumanXv2 said:
the pit file for the gegs4 would resize it
Click to expand...
Click to collapse
You go first trying that
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
You go first trying that
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will when my phone gets here monday and the files are available. Really no reason it shouldn't work but I may be wrong. I odin'd Tmobile files onto my S3(bootloader,csc,rom) and it worked fine.
Im on Tmobile and would prefer to rid the phone of all traces of ATT =)
HumanXv2 said:
I will when my phone gets here monday and the files are available. Really no reason it shouldn't work but I may be wrong. I odin'd Tmobile files onto my S3(bootloader,csc,rom) and it worked fine.
Im on Tmobile and would prefer to rid the phone of all traces of ATT =)
Click to expand...
Click to collapse
Odin will probably error out if you try that, due to the locked bootloader.
I thought a full odin file had the bootloader?
mattdm said:
Odin will probably error out if you try that, due to the locked bootloader.
Click to expand...
Click to collapse
If he's lucky. I predict a brick.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
If he's lucky. I predict a brick.
Click to expand...
Click to collapse
Maybe so. And if it bricks, it will be a hard brick.
HumanXv2 said:
I thought a full odin file had the bootloader?
Click to expand...
Click to collapse
Unless it is signed by Samsung with the correct authentication key, it won't matter. If you run across said key...you will be one popular individual.
Ok so there are keys on the phones non writable memory and when the phone boots up it has to match keys with the bootloader and all to boot?
Thank you. This is much better than "it wont work"
HumanXv2 said:
Ok so there are keys on the phones non writable memory and when the phone boots up it has to match keys with the bootloader and all to boot?
Thank you. This is much better than "it wont work"
Click to expand...
Click to collapse
Yea, but it runs a lot deeper than that. The "chain of trust" employed by this phone goes all the way down to the hardware not just NV. Loki sidesteps the process (again, there is more to it than that), but can be software patched by AT&T / Samsung. So far, the three best ways at getting at this bootloader seem to be:
1. Obtaining Samsung's encryption key. It would most certainly have to be released or leaked because it would be near impossible to break the encryption by other methods.
2. Somehow allow a secondary bootloader to run on the device. I think Devs are still waiting for the full release of KNOX to see if it would allow this or not.
3. Somehow disable the hardware fuses that are part of the chain of trust. This is very unlikely and would require the ability to re-press certain circuitry and develop new code. And if successful, every single phone would have to be done that way. So although I mentioned it, it's really not a viable option at all.
The bottom line is to NEVER take a software OTA from AT&T or Samsung until it is checked and cleared by Devs and (in the near future), if you need to send your phone for warranty repair or need to exchange it, you might be screwed.
This is not wise at all. We're talking hardbrick here.
Hey folks! I have an Acer A500 that I have been working on "with" dibb_nz over the past week. I have no idea what was on it originally, it came to me nearly dead. After a TON of attempts and hard work from dibb, I now have Skrilax's bootloader and recovery installed. I flashed CM10-10 Flex_V6 ROM from Civato onto the device successfully. Here is the problem: no matter how I boot up, it either goes directly into "Power off - Shutting down" then vibrates and blanks out or, after a fresh install, it will say "Android is upgrading", "Optimizing apps", "Starting Apps", then on to the Power Off-shutting down thing.
Does anyone have any clue what may be going on here? I have tried earlier ROMS, all from Civato, but with the same Power OFF result.
Any help would be MUCH appreciated!
Thanks in advance,
Sharkguy
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
dibb_nz said:
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
Click to expand...
Click to collapse
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Well, that sounds complicated. I should have the new battery by the weekend so let me at least try that before anyone gets all technical. Unfortunately I dont know anyone with another a500 to test batteries...
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Moscow Desire said:
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Click to expand...
Click to collapse
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Yeah Dib, the eec thing. Just couldn't remember. Usually we just removed that command from the install script as usually once it was flashed at the factory, rarely did you ever have to flash it again. I will have to look and see in the next couple of days. Worth a shot though. Might be able to put it in a CWM install.
Oh, forgot to add @sharkguy
As with a damaged partition, if the memory got hosed in that particular partition, whichever, there's not a whole lot that can be done. Could try running babsector, but not sure if it would fix it or not. There's been success running it before, but only about 30% as I can tell. Devblks can get physically damaged. Usually the partitions are large enough to mark the bad spots as bad, and still be able to install things. That's what babsector did I think as near as I can tell.
A faulty chip "could" cause a shutdown, especially if it couldn't create the dalvak which is kind of the next step when "starting applications" If I guess right, although I would think it would bootloop rather than shut down. As you say, I've never heard of a power off before, unless the eec was bad and it thinks the battery is dead.
I'm just curious if the OP has done a full format on internal memory via CWM? Before installing. Not the usual wipes, but going into advanced, and triggering the full format. I used it after running that CM stuff awhile back, as it messed up everything (lots of testing). Needed a clean sweep of the internal memory.
As you see, I am still around Just with being a senior mod, not a lot of time for messing with things.
I'm still leaning towards eec pwr. (I'm using beer logic at this point)
Bear with me on this. Let's say the eec got hosed somehow. It happens on occasion. And you install several custom roms, which of course don't have eec pwr in the install script as we removed it. Here's what I know.
1) Battery won't charge and is always going to shut down
2) No response on the touch screen if indeed the OS starts.
3. Tab shuts down after OS start.
So you see why I am leaning towards this.
MD
EDIT: The reason why we removed eec from the custom roms to begin with, primarily as it really wasn't needed, but it "could" cause an issue if the flash went bad. But considering the OP has UID and NVFlash, that isn't an issue now.
dibb_nz said:
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Click to expand...
Click to collapse
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Always works in recovery, as it is independent of the OS...
Righto. I figured it didnt matter in this case. But yes, the rest of the facts are as you understand them.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
The FULL wipes as stated in the guide m8 or via fastboot erase.
@Moscow Desire _bab sector was run and successfully, boot loader and recovery installed with no errors.
As far as the eec thing I do have a copy of that in my stash if that's any help, but no idea how to apply it????
Sent from my HTC_PN071 using Tapatalk
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
sharkguy said:
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Well m8 I dunno if u made the right choice there, I guess only time will tell...there is this thread http://forum.xda-developers.com/showthread.php?t=2617196. I cannot recommend it but then my tab has never been in that state...and I'm not sure I could bring myself to put it in the oven lol...u nut wanna take a look at it any way
Sent from my HTC_PN071 using Tapatalk
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Well, you'll be in your element then,lol...Yeh, your issue is rather unique...with babsector not returning any error its out of my area of expertise!!! But I do know that Acers build quality isn't the best....from power buttons falling out to the memory chip failure and their dodgy soldering techniques, i'm leaning towards a hardware fault 'somewhere'....
But then, it does seem strange the tab powers off during "updating apps" that points to software doesn't it???? Have look in the guide for fastboot commands (if you still have the unlocked bootloader on there) I'd erase all partitions, /system, /data, /cache etc....then run babsectot again to repartition -flash a rom and see what happens...or use tdv4 to do the same, but no rom flash needed for that as it comes with HC 3.2.1 rooted and cwm.
Anyways m8 keep us updated - and fingers crossed you end up with a positive resolution
rgds Donna
One of the last things I think I did was tdv4 without a rom flash. It still came up with the same issue. I did notice that when I took the battery out to charge on the equipment at work (closely monitored of course) to see if there was an issue with the charging circuit, that I could still do all of the same things as before with just the AC plugged in. No battery. This is why I bought a battery to try that out. The Galaxy 3 guy realized what a steal he was offering me and bumped up his price so it looks like I'm stuck woth the A500.
Thanks for the crossed fingers!!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
sharkguy said:
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Soz m8 been full on at work to even check emails let alone reply...phew!!!!
As MD pointed out above, the EEC file thing, devs have dealt with that particular issue, but b/c yours is a relatively unique issue I guess it can't be ruled out...
Have you managed to take a look at fastboot and using the erase command to delete EVERYTHING - at least u can be sure its as clean as can be, then using babsector with an appropriate rom and see what happens there.
In that "tab flu" thread there are links to another thread (somewhere) re: eec thing - If you find it can link it here in this thread and I'll track down the file -
Oh, just to be clear - when it boots into to the OS and powers off - is it completely shutting down i.e. power led is off or is it actually booting to apx mode, black screen power lite on...whats the chances of a vid so we can see exactly what it does???
rgds dibb
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Ok, so new development, so to speak. As you can see from the crappy video I shot just now, I can boot the tablet into the start of the OS, but it hangs at Powering Down. The new part is that I had to manually shut it off, it did not do that itself this time. I showed you the power light (orange) and when I press it again, it does power on, but is still hung up on the same screen. I don't know if that helps any, but now you can see it. By the way, sorry it is upside down, it was the only way to show you the power button after it booted.
http://youtu.be/pG_efbq6DZg