Speak up to Asus! - Eee Pad Transformer General

Don't know if this would actually work but it's better trying than doing nothing.
ReTweet this or create your own tweet asking Asus to unlock their boot loader and give us better root access to their transformer:
Edited tweet: https://twitter.com/#!/stevegaron/status/76007197145960448
We may want to speak up on their facebook page too... http://www.facebook.com/ASUS?sk=wall

It worked for HTC...

Tenny said:
It worked for HTC...
(FYI: Easier not easyier)
Click to expand...
Click to collapse
Damn! I think I made it obvious that english is not my first language... I changed the tweet...

steve.garon said:
Damn! I think I made it obvious that english is not my first language... I changed the tweet...
Click to expand...
Click to collapse
Wait so we aren't going to resort to kidnappings and firebombs....man, hate this place.

I'm confused.
I thought the bootloader was unlocked...
Or are you talking about APX mode being locked? If that's the case, then I'm with you on that one. Without a functioning APX mode, I am scared to do anything to my Eee Pad. I couldn't count how many times I've soft bricked my GTab and APX saved my bum!

and why should this thread be in the development section?

rj3005 said:
and why should this thread be in the development section?
Click to expand...
Click to collapse
Just because it would help make dev easier. So I thought it belong here.
Sent from my Transformer TF101 using Tapatalk

KnightCrusader said:
I thought the bootloader was unlocked...
Or are you talking about APX mode being locked? If that's the case, then I'm with you on that one. Without a functioning APX mode, I am scared to do anything to my Eee Pad. I couldn't count how many times I've soft bricked my GTab and APX saved my bum!
Click to expand...
Click to collapse
Unless I misunderstood what lock bootloader are, I beleive its locked. It requires root to flash another recovery/rom and requires an exploit to get root. That pretty locked for me
I would be much more fun if you could just do a fasboot flash recovery like the Nexus phones ;-)
Sent from my Transformer TF101 using Tapatalk

Did my part on facebook....

I posted on their wall too
hope they follow like HTC did

steve.garon said:
Unless I misunderstood what lock bootloader are, I beleive its locked. It requires root to flash another recovery/rom and requires an exploit to get root. That pretty locked for me
Click to expand...
Click to collapse
Go to the Acer Iconia A500 forums, and then you'll find out what a "locked bootloader" really is.
What you should really be asking for is simply official root access, without having to find an exploit. Note that HTC have only said they are ending their policy of locking the bootloaders on their phones - as far as I'm aware they've said nothing about giving official root access.
Regards,
Dave

The never ending discussion about what a locked bootloader is, is useless because it depends on your definition on "locked". If "locked" means that it checks signatures before flashing or booting, then yes, the Eee Pad bootloader is unlocked. If however "locked" means that you have no way of recovering from a system/recovery fail, then the ASUS EeePad is very well locked down. The only way around this would be fastboot and/or nvflash access which we don't have.
So as opposed to the Xoom or other Tegra devices like the G2x etc, the ASUS bootloader is locked, and the only way of flashing boot/recovery is through a (admittedly simple) reverse engineering process. That is a shame, and also could be locked down anytime by ASUS if they were sigchecking those updates in the bootloader (though I think that's unlikely to happen).
So in my opinion ASUS shouldn't announce that the bootloader is open etc, when at the same time they do not provide a documented flashing method.
Equally though, I agree that there is no practical sense in complaining or doing further work on this, because all people care about is flashing boot/recovery (unless they are bricked of course...).

stridger said:
The never ending discussion about what a locked bootloader is, is useless because it depends on your definition on "locked". If "locked" means that it checks signatures before flashing or booting, then yes, the Eee Pad bootloader is unlocked. If however "locked" means that you have no way of recovering from a system/recovery fail, then the ASUS EeePad is very well locked down. The only way around this would be fastboot and/or nvflash access which we don't have.
So as opposed to the Xoom or other Tegra devices like the G2x etc, the ASUS bootloader is locked, and the only way of flashing boot/recovery is through a (admittedly simple) reverse engineering process. That is a shame, and also could be locked down anytime by ASUS if they were sigchecking those updates in the bootloader (though I think that's unlikely to happen).
So in my opinion ASUS shouldn't announce that the bootloader is open etc, when at the same time they do not provide a documented flashing method.
Equally though, I agree that there is no practical sense in complaining or doing further work on this, because all people care about is flashing boot/recovery (unless they are bricked of course...).
Click to expand...
Click to collapse
Well put. We need either fastboot or Nvflash access.. just eliminates any sort of risk we have while messing with our TFs

r34p3rex said:
Well put. We need either fastboot or Nvflash access.. just eliminates any sort of risk we have while messing with our TFs
Click to expand...
Click to collapse
Then that's what should be asked of Asus, rather than "unlocked bootloader" which is open to interpretation!
Regards,
Dave

I don't think that downgrading is a viable option for installing a custom Rom. Just because we can downgrade now, doesn't mean we will be able to in the future. Beside, having to rely on an exploit is also to me not a viable option. I'd rather have the exploits fixed! It's safer that way.
The fact that the boot loader is not signed, NAND locked or encrypted is a big plus and I congratulate Asus for this. It's a good design decision. But the missing ingredient for the completely unlock bootloader is the tool the allows us to flash anything from the bootloader...
If in the end Asus give us fastboot/nvflash access to the bootloader well to me its a win for all Transformer's owners. This is even a win for Asus because most devs would go for hardware that they can easily modify which would increase sales. (Not that sales are a problem right now.. )

How's this then?
Please @Asus give us a fastboot/nvflash and official root access - like the Google Nexus phones - for your amazing #eeepadtransformer!

jerdog said:
How's this then?
Please @Asus give us a fastboot/nvflash and official root access - like the Google Nexus phones - for your amazing #eeepadtransformer!
Click to expand...
Click to collapse
Works for me... Tweet it!

steve.garon said:
Works for me... Tweet it!
Click to expand...
Click to collapse
http://twitter.com/#!/jerdog76/status/76296399330873346
done.

foxmeister said:
Then that's what should be asked of Asus, rather than "unlocked bootloader" which is open to interpretation!
Regards,
Dave
Click to expand...
Click to collapse
Yeah, thats what I asked them for when I posted a message on their Facebook wall.

I just posted on their FB page

Related

Might be able to root through galaxy s method?

Since the galaxy s and nexus s have the same specs and both made by samsung the method of a flashable.zip to root and install busybox might new possible what are your thoughts?
Sent from my Samsung Nexus S
Maybe you could unlock the bootloader as well?
Sent from my Samsung Vibrant
Yup, I'd suggest fastboot oem unlock and then go ahead and flash whatever you like...
i like that idea ^^
Yea its gotta be the same one as the nexus one same kind of software
Sent from my Samsung Vibrant
No the Galaxy S 2.1 .zip method will not work. It doesn't work on 2.2 Vibrant leaks. SuperOneClick / rageagainstthecage does, however.
Either way, thanks to this not being HTC, we will have it rooted the day it comes out (or sooner).
You realize that the n1, an HTC phone, has a neat fastboot command to unlock the bootloader out of box, yeah? Funnily enough that tiny convenient feature is present in the ns.
Bad HTC for making it easy at the request of Google. And bad Samsung for doing the same!!
Anderdroid said:
No the Galaxy S 2.1 .zip method will not work. It doesn't work on 2.2 Vibrant leaks. SuperOneClick / rageagainstthecage does, however.
Either way, thanks to this not being HTC, we will have it rooted the day it comes out (or sooner).
Click to expand...
Click to collapse
Sent from my Nexus One
swetland said:
Yup, I'd suggest fastboot oem unlock and then go ahead and flash whatever you like...
Click to expand...
Click to collapse
quick question idk if you can answer it or if you know the answer to it but will this void the warranty like it did on the N1 and will it make a lock appear on splash1 like on the N1?
I wonder if the new method to root the nexus one without unlocking the bootloader would be able to work on the nexus S..
godsfilth said:
quick question idk if you can answer it or if you know the answer to it but will this void the warranty like it did on the N1 and will it make a lock appear on splash1 like on the N1?
Click to expand...
Click to collapse
The warranty language is slightly different this time around (uses "may" instead of "will"). The unlocked icon displays when you have it unlocked. It goes away when you run fastboot oem lock -- at which point it is not flashable until you unlock it again.
I have high hopes that Samsung will be reasonable about hardware warranty service.
swetland said:
The warranty language is slightly different this time around (uses "may" instead of "will"). The unlocked icon displays when you have it unlocked. It goes away when you run fastboot oem lock -- at which point it is not flashable until you unlock it again.
I have high hopes that Samsung will be reasonable about hardware warranty service.
Click to expand...
Click to collapse
So the fastboot oem lock command is available on retail Nexus S devices but not on the N1? Interesting... or did I misunderstand you? Also, what partitions do you mean are not flashable after locking it again? Just like it was before unlocking or even more locked?
swetland said:
The warranty language is slightly different this time around (uses "may" instead of "will"). The unlocked icon displays when you have it unlocked. It goes away when you run fastboot oem lock -- at which point it is not flashable until you unlock it again.
I have high hopes that Samsung will be reasonable about hardware warranty service.
Click to expand...
Click to collapse
thanks thats good news i dont OC my phone or anything but i was hit by the dust under the screen issue on the N1 (resolved eventually) and am paranoid about it now
I have one more question will retail phone be lockable or is that only for you special google people with a s-off spl like the N1
@blunden the N1 had oem unlock as well but it said it WILL void your warranty which HTC used that wording a number of times to decline replacing peoples phones, though i know google folks tried to and mostly succeeded in getting HTC to reverse the decision on most phones
and yes he ment when re-locked you cant flash anything because you lose root privlages to flash through fastboot (i.e. fastboot flash clockwork-recovery.img to get a custom recovery and flash update.zip ROMs)
Picking up my nexus s tomorrow will report back
Sent from my SGH-T959 using XDA App
HTC fixed my phone three times with an unlocked bootloader. I hope Samsung is as generous.
swetland said:
The warranty language is slightly different this time around (uses "may" instead of "will"). The unlocked icon displays when you have it unlocked. It goes away when you run fastboot oem lock -- at which point it is not flashable until you unlock it again.
I have high hopes that Samsung will be reasonable about hardware warranty service.
Click to expand...
Click to collapse
You can confirm that fastboot oem lock works on retail Nexus S units? I know Google's internal Nexus Ones had that capability, but it was removed from the SPL in retail models.
Using SuperOneClick won't void your warranty (rageagainstthecage method). I heard it works. Confirm/Deny anybody?
mortzz said:
You can confirm that fastboot oem lock works on retail Nexus S units? I know Google's internal Nexus Ones had that capability, but it was removed from the SPL in retail models.
Click to expand...
Click to collapse
Yes that is correct it does have that capability.
Hook it up to your PC then:
adb reboot-bootloader
Your bootloader will be unlocked.
mortzz said:
You can confirm that fastboot oem lock works on retail Nexus S units? I know Google's internal Nexus Ones had that capability, but it was removed from the SPL in retail models.
Click to expand...
Click to collapse
i can confirm fastboot oem LOCK does work and it does say locked in the spl again yay
ignore....
*EDIT* NVM

Do not flash ota!!!!!!11 it's got a bootloader in there

Do not flash ota!!!!!!11 it's got a bootloader in there
I'll have something flashable shortly!!
you've been warned.
Are you saying that they are trying to lock us down now?
Do we have any info on the bootloader changes?
with fastboot ala oem unlock how can they lock us down?
Thanks for the heads up
Is this a headsup for what will happen, or did you actually get your hands on the 3.1? Got me excited!
Awesome! You are the best! Long live XDA!!!
Hopefully you'll have something flashable for us wifi users???
kewl, can't wait to see the changes on the WIFI-only one.
guessing this'll be a rooted update.zip we flash via CWM BRD you rock!
Pretty sure he's saying it'll overwrite any bootloader you've already installed, IE Clockwork Recovery.
Could you upload the update for those of us that don't care about the bootloader?
Sent from my PC36100 using XDA Premium App
So much Fear Uncertainty and Derp
Elysian893 said:
Pretty sure he's saying it'll overwrite any bootloader you've already installed, IE Clockwork Recovery.
Click to expand...
Click to collapse
Clockwork recovery is not the bootloader, it's a recovery. I would expect Moto to push out new stock recoveries (hopefully that support the sdcard).
But really I don't expect this to screw up anyone's root or bootloader. Proof or GTFO.
Im upping it now. I have not flashed yet. Working on modified safe version. Honestly, I don't know what that bootloader binary does. And I personally don't wanna find out. I've been in this game to long to mess with all that. However, if anybody want's to play guinea pig, go for it.
dimitri407 said:
Are you saying that they are trying to lock us down now?
Click to expand...
Click to collapse
No, he is making huge assumptions without anything to back it up. I HIGHLY doubt this will lock down your device.
bigrushdog said:
Im upping it now. I have not flashed yet. Working on modified safe version. Honestly, I don't know what that bootloader binary does. And I personally don't wanna find out. I've been in this game to long to mess with all that. However, if anybody want's to play guinea pig, go for it.
Click to expand...
Click to collapse
I'll load it tonight, really REALLY REALLY highly doubt this has any adverse affects and is probably just a bug fix anyway.
Seriously you guys are sometimes way to paranoid.
Got a link to the OTA?
nemith said:
Clockwork recovery is not the bootloader, it's a recovery. I would expect Moto to push out new stock recoveries (hopefully that support the sdcard).
But really I don't expect this to screw up anyone's root or bootloader. Proof or GTFO.
Click to expand...
Click to collapse
Just open up zip and look at that bootloader.bin staring at you. I'm not being alarmist. Well, actually, yes I am. So I'll have the link in a quick second here. Please flash and get back to me.
UPDATE DOWNLOAD VERIZON 3G ONLY!!!!!!!!!1
http://www.multiupload.com/MAW2MD8GJQ
bigrushdog said:
Just open up zip and look at that bootloader.bin staring at you. I'm not being alarmist. Well, actually, yes I am. So I'll have the link in a quick second here. Please flash and get back to me.
UPDATE DOWNLOAD
http://www.multiupload.com/MAW2MD8GJQ
Click to expand...
Click to collapse
Any chance this will work with the WiFi Xoom?
nemith said:
I'll load it tonight, really REALLY REALLY highly doubt this has any adverse affects and is probably just a bug fix anyway.
Seriously you guys are sometimes way to paranoid.
Got a link to the OTA?
Click to expand...
Click to collapse
I hope I'm wrong and everything is just fine. However, as a developer, I have an ethical obligation to protect users. Period. If I see something that don't look right, you're damn right I'm gonna be paranoid. What would you guys be saying if it does lock down the system? "Oh, how did BRD miss that!?" You don't know if Motorola changed their mind about OEM unlock. But please flash and let us know.
How would we go about flashing this. I'm backing up my xoom now and am willing to try if I knew how to install it.
bigrushdog said:
I hope I'm wrong and everything is just fine. However, as a developer, I have an ethical obligation to protect users. Period. If I see something that don't look right, you're damn right I'm gonna be paranoid. What would you guys be saying if it does lock down the system? "Oh, how did BRD miss that!?" You don't know if Motorola changed their mind about OEM unlock. But please flash and let us know.
Click to expand...
Click to collapse
I understand trying to educate and warn users, but this is neither. This is just FUD spreading.
A more appropriate post would be "Warning: there is an updated bootloader binary in the motorola update. It is probably nothing, but you may want to hold of on updating until we find out more"
As a developer you shouldn't be participating in just FUD spreading (and generation) and get to the bottom of it. Claiming otherwise just makes that large "Donate link" at the bottom of your posts even more ironic and annoying.

Bootloader unlock for motorola devices!!!!

Motorola today launched the program to unlock bootloader on moto devices.
Only 4 models are supported atm, but we can hope for the future (for milestone 2 too)
Look here:
hXXps://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215/session/L3RpbWUvMTM0NTI1MzIxMS9zaWQvRTJUbk1ZM2w%3D]
I saw it ont he portal. Hope we don't have to wait too long in order to have it.
fugitifduck said:
I saw it ont he portal. Hope we don't have to wait too long in order to have it.
Click to expand...
Click to collapse
Fingers crossed
So if they do unlock the M2's bootloader, what can we expect? Still running Endless GB & I don't know how much more an unlocked bootloader can improve the situation...
terayder said:
Fingers crossed
So if they do unlock the M2's bootloader, what can we expect? Still running Endless GB & I don't know how much more an unlocked bootloader can improve the situation...
Click to expand...
Click to collapse
Tezet posted in his CM10 thread about what it brings to unlock the bootloader, and from memory it's :
- newer custom kernels
- no need for boostrap anymore, we could use more "regular" recovery (like all other phones)
- easier hardware support
- possibility probably to reformat the phone partitions
- more and easier customization instead of "fiddling" with the phone;
But he said too to not expect that for the MS2, and that he thought that the only chance for something "like" that for the MS2 was probably Kexec (a bootloader hijacker which would allow quite some things).
Ashareth said:
But he said too to not expect that for the MS2, and that he thought that the only chance for something "like" that for the MS2 was probably Kexec (a bootloader hijacker which would allow quite some things).
Click to expand...
Click to collapse
To confirm that and not to burst anyone's bubble
http://androidcommunity.com/motorola-has-no-plans-to-unlock-older-devices-20120822/
Not gonna happen for older devices i.e. for MS2 as well

Why one should never unlock the Motorola Razr HD bootloader (xt925) !

The pro & cons of unlocking the bootloader:
Pro: Install customs ROMS with custom kernels (basically that's it)
Cons: - Loosing warranty from Motorola & your carrier
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
If someone can add some Pro's to an unlock bootloader please do it..
Are you sure about the firmware upgrades? I read somewhere that's not the case.
I wish I had known all this before I unlocked my phone.
Are you sure about the firmware upgrades? I read somewhere that's not the case.
Click to expand...
Click to collapse
I spoke to Motorola & my carrier services, also read the warning details before the unlock process begins.
I wish I had known all this before I unlocked my phone
Click to expand...
Click to collapse
Same here..(I learned all that after the fact)
I'd add this to Pro:
If you're stuck on Rogers 49003 ICS because you flashed the ROM trying to get root, your best option to get anything above 4.0.4 is to unlock bootloader?
Perhaps a CWM install will be possible for those with unlocked bootloaders when updates come.
It seems that in one form or another an unlocked bootloader means being able to push all the new files in doesn't it? Is there any limitation on this phone, for example flashing a new modem or kernel?
Cons one by one:
itzik_man said:
- Loosing warranty from Motorola & your carrier
Click to expand...
Click to collapse
True, but obvious.
itzik_man said:
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
Click to expand...
Click to collapse
Nope. Even if you were not to receive OTA, which by the way is not true as I've observed on my Photon Q, you can still freely flash the new firmwares yourself ^^
itzik_man said:
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
Click to expand...
Click to collapse
Depends on ones point of view. Usually a CM port means you get newer Android sooner.
itzik_man said:
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
Click to expand...
Click to collapse
Why it wouldn't? Unlocking BLs has no impact on upgrade schedule.
itzik_man said:
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
Click to expand...
Click to collapse
No. That's solely on Moto / Google decision. They don't have to update it at all. (See Droid 3, Milestone 3, Motorola XT720 etc.)
itzik_man said:
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
Click to expand...
Click to collapse
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
itzik_man said:
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
Click to expand...
Click to collapse
You can sue Moto for breaking laws. They can't forbid you doing that (don't know honestly how is that in US / Canada, but I doubt that seeing how it works with computer games).
So please, while for normal user not willing to flash custom ROMs it's true that they should not unlock the bootloader, don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
Click to expand...
Click to collapse
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
itzik_man said:
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
Click to expand...
Click to collapse
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.
We should be promoting "unlock the world"
This is not to imply everything should be free, however if I own something it should be mine in every regard, that includes breaking it.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
@skrilax thanks for you work on the a500.
Sent from my Galaxy Nexus using Tapatalk 2
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
Click to expand...
Click to collapse
To end my part in this discussion: The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Darbness said:
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Click to expand...
Click to collapse
Have you tried out lte tethering? It doesn't work on Rogers.
To epinter -
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.http://www.linuxmobile
Click to expand...
Click to collapse
I did not notice your response at first, now to the point -
Without any disrespect to the work, time & effort invested, the main point is being ignored by the developers: All comments I got on this OP didn't touched the number one reason of my suggestion to not unlock the bootloader: There in not really enough of a variety of development options today to justification the bootloader unlocked of the xt925.
Skrilax_CZ said:
Cons one by one:
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
Click to expand...
Click to collapse
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Tombs1234 said:
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
Click to expand...
Click to collapse
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
itzik_man said:
The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Click to expand...
Click to collapse
It's your decision whether to unlock the bootloader or not. I'm just saying (for other users) that many of the cons you wrote were absolutely incorrect.
PantsDownJedi said:
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Click to expand...
Click to collapse
I believe there is something stored in the pds partition. Or at least it is that way on Droid RAZR XT912 and you had to fix it to remove the remaining traces. Flashing FXZ is also a way how to get a clean stock firmware, but pds partition is not affected that way.
PantsDownJedi said:
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
Click to expand...
Click to collapse
I think he meant "stock firmware" instead of "stock bootloader"
So if that were the case on this phone, I wonder if doing a dd backup of the pds partition before rooting at ICS, for restoring after downgrade, would be the way to go. Assuming it restores properly, it would be a good thing to add to the sticky thread about rooting. I did a dd of all my partitions except for /data last night, but I'm already rooted.
hmm... I'm wondering if there's something inaccessable in /system or even the sdcard since they get mounted with fuse. My only other Android phone was the Galaxy S II which was pretty straightforward and dead simple to root and unroot. I was surprised to see the fuse module being used to mount anything when I got this one.
The original topic is here: http://forum.xda-developers.com/showthread.php?t=1857558
I don't know if there was a proper fix developed (haven't checked) on the RAZR.

[Request] Root for Z3C (D5803) -> Solved

HI @all,
now that we have a FW for the device - is root possible?
All known root methods are not working.
BR
UserX10
Edit:
Solved -> Thanks you DooMLoRD
http://forum.xda-developers.com/z3-...58xx-cwm-based-recovery-6-0-4-7-root-t2890231
Delete.
Jeez.
People haven't even got their hands on the phone yet...
Be patient
Anyone wanna try Framaroot?
http://framaroot.net/index.html
framaroot does not work ...
Ok because I saw it posted on this blog and thought it would work. Strange!
plisk3n said:
Ok because I saw it posted on this blog and thought it would work. Strange!
Click to expand...
Click to collapse
Well, it says "tested on device" and is from 9/4, before the device was even unavailable. I'd be careful that apk isn't something more.
CollinsJ said:
Well, it says "tested on device" and is from 9/4, before the device was even unavailable. I'd be careful that apk isn't something more.
Click to expand...
Click to collapse
Yeah that's also the reason why I decided not to download it, I'll just wait till someone @ XDA finds a way to root the device. It's not like we'll die because our device isn't rooted for x weeks/months.
Weeks/months?! I would die! It's been a day and the amount of things I can't do is driving me nuts!
If you have an unlocked boot loader see what I say at http://forum.xda-developers.com/showthread.php?p=55709585. If you don't I think you'll be waiting for a while - someone needs to find an exploit and write the app/code needed to exploit it. This has become increasingly hard as Android has become more secure - before Towelroot AFAIK the Z1/Z2 was not rootable for a long time. You'd probably be waiting a similar length of time for the next big root exploit.
tilal6991 said:
If you have an unlocked boot loader see what I say at http://forum.xda-developers.com/showthread.php?p=55709585. If you don't I think you'll be waiting for a while - someone needs to find an exploit and write the app/code needed to exploit it. This has become increasingly hard as Android has become more secure - before Towelroot AFAIK the Z1/Z2 was not rootable for a long time. You'd probably be waiting a similar length of time for the next big root exploit.
Click to expand...
Click to collapse
Would it not be helpful to contact Sony themselves? They're increasingly developer friendly, these days. Maybe they'd be willing to offer pointers to root app developers?
mudnightoil said:
Would it not be helpful to contact Sony themselves? They're increasingly developer friendly, these days. Maybe they'd be willing to offer pointers to root app developers?
Click to expand...
Click to collapse
Well I know people at Sony and long story short: if you want root unlock the boot loader. Its as simple as that. You have to understand that while a root exploit looks nice to tinkerers its also a serious security issue which must be fixed - that is why many root solutions also patch the exploit they use after using it.
Does unlocking the bootloader require wiping the phone? I know this is required on the nexus phones. If it requires wipe then its the very first thing I'm doing once I get the phone out of the box.
Sent from my Nexus 5 using Tapatalk
tilal6991 said:
Well I know people at Sony and long story short: if you want root unlock the boot loader. Its as simple as that. You have to understand that while a root exploit looks nice to tinkerers its also a serious security issue which must be fixed - that is why many root solutions also patch the exploit they use after using it.
Click to expand...
Click to collapse
I'm aware of this ... but on the one hand being one of the few if only manufacturers to provide official unlocking for the bootloaders (with the obvious intention of spurring development etc), but on the other actively closing non-simple (i.e. ones requiring a dedicated program) root 'exploits' would seem a little at odds. Is it really that black and white? You'd think it might be in their interests to provide an official complex / secure rooting method.
sublimnl said:
Does unlocking the bootloader require wiping the phone? I know this is required on the nexus phones. If it requires wipe then its the very first thing I'm doing once I get the phone out of the box.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes. It will wipe everything AFAIK - double check with the website.
mudnightoil said:
I'm aware of this ... but on the one hand being one of the few if only manufacturers to provide official unlocking for the bootloaders (with the obvious intention of spurring development etc), but on the other actively closing non-simple (i.e. ones requiring a dedicated program) root 'exploits' would seem a little at odds. Is it really that black and white? You'd think it might be in their interests to provide an official complex / secure rooting method.
Click to expand...
Click to collapse
Your statements contradict themselves. Rooting without unlocking the bootloader needs a security flaw. How can any method which leaves a security hole be secure?
Bootloader unlocking gets around this by letting you control the boot partition of the device so you can disable the "security barrier" that android provides. This is a choice you are explicitly making which is why it is the only "secure" way to root.
Does towelroot work?
MrOeyta said:
Does towelroot work?
Click to expand...
Click to collapse
Unfortunately Towelroot does not work.
I've read some people saying that unlocking the bootloader causes you to lose your DRM keys which apparently would affect software/ camera issues?
Can anyone verify this?
tacocats said:
I've read some people saying that unlocking the bootloader causes you to lose your DRM keys which apparently would affect software/ camera issues?
Can anyone verify this?
Click to expand...
Click to collapse
This is very true. On the z1c I neglected to back up the TA partition. And apparently lost native mirror cast and some camera features when I rolled the device back to stock.
Back up your TA partition before unlocking BL.
dillalade said:
This is very true. On the z1c I neglected to back up the TA partition. And apparently lost native mirror cast and some camera features when I rolled the device back to stock.
Back up your TA partition before unlocking BL.
Click to expand...
Click to collapse
Any idea how this could be done?

Categories

Resources