White lock in google boot image - Samsung Galaxy Nexus

Hi, sorry for the crappy english but i want to know if the "white lock" image in the google boot screen of the galaxy nexus is like the yellow triangle in the galaxy s2 when u changed the kernel...if thats the case theres any way u can change it and just leave the google word when u reboot the phone??
thx
pd: i already unlocked the device but i dont like that white lock pricture i would love the just have the google word.

The lock means your phone is unlocked. The only way to remove the lock is to re-lock your phone.

hi, tnx for answer, so theres no way to change that image??? there isnt like the bootanimation or something??

Nope. I'm pretty sure there is no way to change it.
Sent from my Galaxy Nexus using xda premium

El Daddy said:
Nope. I'm pretty sure there is no way to change it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
what he said.
the lock shouldn't bother you anyway. it only appears for 1-2 seconds.

question
El Daddy said:
The lock means your phone is unlocked. The only way to remove the lock is to re-lock your phone.
Click to expand...
Click to collapse
Hey I was wondering what you mean by the phone is unlocked does the lock have to do anything with the phone being rooted, or the clockworkmod? Sorry im new to android

k.daya96 said:
Hey I was wondering what you mean by the phone is unlocked does the lock have to do anything with the phone being rooted, or the clockworkmod? Sorry im new to android
Click to expand...
Click to collapse
When you add su.zip for short of superuser.zip then you have root. The unlocking of the bootloader allows you the ability to install custom recovery and get root access after flashing superuser.

The only way would be if someone hacked and created a custom bootloader, in the process hiding the lock symbol, similar to what was done with BlackRose on the Nexus One.
That was done to change the NAND partition sizes, and since the Galaxy Nexus doesn't face the issue of small internal storage nobody is likely to be working on a custom bootloader for the GNex...

You can do this, actually.
LogoMe.
And yes, I use it, it works.

Jubakuba said:
You can do this, actually.
LogoMe.
And yes, I use it, it works.
Click to expand...
Click to collapse
Is that the only way? I wish they had a free version.
#Sent From md-. - bm and d,"b

phreshy said:
Is that the only way? I wish they had a free version.
#Sent From md-. - bm and d,"b
Click to expand...
Click to collapse
I've never tried it, but ROM Toolbox may be able to do it. (Maybe other free apps as well.)
The image is stored in the sbl partition on a GNex (see here) and although I haven't looked into it, but you should be able to do it just by editing that partition. Maybe segv11 can help out if you can't do it with ROM Toolbox or any other utility.

You can most likely change it with a file manager as stated before me but just make sure you have a correct size image check the logo me thread they have a bunch of icons already made and a transparent icon for the lock which will make it look like its not there
Sent from my Galaxy Nexus using xda app-developers app

efrant said:
I've never tried it, but ROM Toolbox may be able to do it. (Maybe other free apps as well.)
The image is stored in the sbl partition on a GNex (see here) and although I haven't looked into it, but you should be able to do it just by editing that partition. Maybe segv11 can help out if you can't do it with ROM Toolbox or any other utility.
Click to expand...
Click to collapse
I have rom toolbox, but the nexus isn't a supported device and I'm not brave enough to try it.lol Now, there's this app called "Flash Image GUI", which stated that it worked with the nexus, but it didn't when I chose an image to flash, so I don't know.
#Sent From md-. - bm and d,"b
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Alex1123 said:
You can most likely change it with a file manager as stated before me but just make sure you have a correct size image check the logo me thread they have a bunch of icons already made and a transparent icon for the lock which will make it look like its not there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Where is the logo located exactly?
#Sent From md-. - bm and d,"b

Alex1123 said:
You can most likely change it with a file manager as stated before me but just make sure you have a correct size image check the logo me thread they have a bunch of icons already made and a transparent icon for the lock which will make it look like its not there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I don't think you can change it with a file manager. You need to edit the sbl partition with a hex editor, and reflash it, or just echo the changed bytes to it.
Sent from my Galaxy Nexus using Tapatalk 2

phreshy said:
Is that the only way? I wish they had a free version.
#Sent From md-. - bm and d,"b
Click to expand...
Click to collapse
logo me is the only way right now, unless you compile a kernel and remove it yourself(fanger of bricking your device this way, if done wrong). but, logo me is worth it https://play.google.com/store/apps/details?id=aperture.ezekeel.logome

http://forum.xda-developers.com/showthread.php?t=1699657 for logo me icons i recommend you just buy logo me its much simpler to use that and its nice what you can do with it but honestly ive only used it a few times lol still i like supporting the developer and dont even think about cracking it lol

Off topic remark, but come on. You have a $300 phone. You can't spare 2.50?

If I could, I would, which is why I asked. At the moment I am not able to purchase anything from the market. I know many others in the same situation. So, yes, it does kind of suck, that it can't be changed for free, like the rest of the other android devices, but whatever.
#Sent From md-. - bm and d,"b

phreshy said:
If I could, I would, which is why I asked. At the moment I am not able to purchase anything from the market. I know many others in the same situation. So, yes, it does kind of suck, that it can't be changed for free, like the rest of the other android devices, but whatever.
#Sent From md-. - bm and d,"b
Click to expand...
Click to collapse
ezekeel spent a lot of time figuring out how to do it on the gnex with ics and jelly bean, it appears that its not so easy to do like in earlier android versions. with a higher chance of bricking your device. i spent a few weeks testing this mod/app for him before its initial release. for the effort and time that he put into it, he deserves to charge for it. even though i had free access to it, i bought it anyways to support his work. now the other android devices its free because there is little work that goes into it(and a completely different way then on the gnex), unlike on the gnex which is a bit more difficult to do.so far, only ezekeel has figured out how to do it.

simms22 said:
logo me is the only way right now, unless you compile a kernel and remove it yourself(fanger of bricking your device this way, if done wrong). but, logo me is worth it https://play.google.com/store/apps/details?id=aperture.ezekeel.logome
Click to expand...
Click to collapse
It's not part of the kernel though...
OP: If I get a chance tomorrow I'll see what I can find out as far as doing it without an app.
Sent from my Galaxy Nexus using Tapatalk 2

Related

[Q] Can you root without doing the CWM recovery?

All I want to be able to do is install and use Titanium Backup. Can this be done without the whole bootloader unlock / install CWM recovery / Flash SU method?
This is for a GSM GN from the Google Play store.
No. Not that know of exploits like that don't work anymore. But you can just unlock, flash a recovery, flash superuser. Then flash the stock recovery and relock the boot loader.
Sent from my sprint galaxy nexus
the only way you can do that is if you're on 4.0.2, but i would bet you are on 4.0.4
ÜBER™ said:
No. Not that know of exploits like that don't work anymore. But you can just unlock, flash a recovery, flash superuser. Then flash the stock recovery and relock the boot loader.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
Just 'fastboot boot cwm.img', flash "su.zip", reboot, done.
Sent from my i9250
ÜBER™ said:
No. Not that know of exploits like that don't work anymore. But you can just unlock, flash a recovery, flash superuser. Then flash the stock recovery and relock the boot loader.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
Wouldn't recommend relocking the bootloader. He'll just have to wipe again next time he needs to unlock.
martonikaj said:
Wouldn't recommend relocking the bootloader. He'll just have to wipe again next time he needs to unlock.
Click to expand...
Click to collapse
I would NOT recommend it either.
However, if he feels like he really has to re-lock, we now have a method that can unlock the bootloader without wiping, assuming you have root of course. (But if you ever lose root... you are screwed!
EDIT: I didn't realize that the OP had a Play Store device. Although I don't have one, the Play Store devices are said to NOT wipe when the bootloader is unlocked.
efrant said:
I would NOT recommend it either.
However, if he feels like he really has to re-lock, we now have a method that can unlock the bootloader without wiping, assuming you have root of course. (But if you ever lose root... you are screwed!
EDIT: I didn't realize that the OP had a Play Store device. Although I don't have one, the Play Store devices are said to NOT wipe when the bootloader is unlocked.
Click to expand...
Click to collapse
Thanks for the info. And just an FYI, my Play Store device does wipe data when I unlock the bootloader. Not a huge deal, but it does reset it to factory state.
dmarmstr said:
Thanks for the info. And just an FYI, my Play Store device does wipe data when I unlock the bootloader. Not a huge deal, but it does reset it to factory state.
Click to expand...
Click to collapse
some people have said it didnt wipe when they unlocked the bootloader when they got theirs from the playstore.
i always assume its going to wipe everything.
I had no idea that unlocking the bootloader would wipe everything, but I knew I had to unlock it first in order to root it so I could backup all my apps with Titanium Backup, so guess what happened..
The thing is, if I hadn't done that, I would have waited for the official Jelly Bean from Samsung for quite a while, for my yakjuxw variant...
Pfff. Everything about this whole affair with ROMs, rooting, backing up, seems so weird and counter-intuitive to me. I just don't understand it!
teomor said:
[snip]
Pfff. Everything about this whole affair with ROMs, rooting, backing up, seems so weird and counter-intuitive to me. I just don't understand it!
Click to expand...
Click to collapse
That just means you haven't done enough reading. It is actually quite simple and logical once you read and understand how things work.
efrant said:
I would NOT recommend it either.
However, if he feels like he really has to re-lock, we now have a method that can unlock the bootloader without wiping, assuming you have root of course. (But if you ever lose root... you are screwed!
Click to expand...
Click to collapse
I just dont like seeing the opened lock icon below the google logo when the phone boots up, But i just want root, and the stock recovery for future ota
So Rooting it and re-locking the bootloader doesn't limit the root functionality right?
and is there a possibility of having root + CWM + Locked bootloader ?
will CWM work that way ?
Plus whats the procedure to unlock bootloader without wiping device if your device has root + locked bootloader?
chandradithya said:
So Rooting it and re-locking the bootloader doesn't limit the root functionality right?
and is there a possibility of having root + CWM + Locked bootloader ?
will CWM work that way ?
Click to expand...
Click to collapse
No.
Sent from my i9250
chandradithya said:
I just dont like seeing the opened lock icon below the google logo when the phone boots up
Click to expand...
Click to collapse
Seriously? How often do you see the boot screen?
chandradithya said:
So Rooting it and re-locking the bootloader doesn't limit the root functionality right?
Click to expand...
Click to collapse
No.
chandradithya said:
and is there a possibility of having root + CWM + Locked bootloader ?
Click to expand...
Click to collapse
Yes.
chandradithya said:
will CWM work that way ?
Click to expand...
Click to collapse
Yes.
chandradithya said:
Plus whats the procedure to unlock bootloader without wiping device if your device has root + locked bootloader?
Click to expand...
Click to collapse
Use segv11's app. It is linked in the "Unlock bootldr w/o wipe" link in my signature.
chandradithya said:
I just dont like seeing the opened lock icon below the google logo when the phone boots up, But i just want root, and the stock recovery for future ota
There is a app to change those splash screen images. (logo me) My kids didn't like seeing the lock either. Used app to change lock icon to black image.
Click to expand...
Click to collapse
Just FYI
I have a Google Play GN and my phone did NOT wipe upon unlocking the bootloader
jerrycycle said:
chandradithya said:
I just dont like seeing the opened lock icon below the google logo when the phone boots up, But i just want root, and the stock recovery for future ota
There is a app to change those splash screen images. (logo me) My kids didn't like seeing the lock either. Used app to change lock icon to black image.
Click to expand...
Click to collapse
Man, I just don't get how that is that big of a deal.. I think the unlock logo at the bottom is actually cool. My friend said one of his friends didn't want to root his Nexus 7 because he didn't like the unlock symbol on the boot up screen too... I was soo confused. How can it bother you that much?
Click to expand...
Click to collapse
No issue for me personally. I change the splash logo on all my oem devices with my personnel symbol. Kids device their name in place of the Google.
efrant said:
Seriously? How often do you see the boot screen?
Click to expand...
Click to collapse
Well my previous phone was an android which was never updated officially after eclair. Running Cm7 ports kinda lagged the phone which was pretty noticeable after 24 hours or so,
So i used to reboot it everyday to clear memory. and yeah, I guess old habits die hard and i just love the jellybean boot up animation, so no reason not to reboot it, and thanks a lot for your replies
---------- Post added at 02:09 PM ---------- Previous post was at 02:01 PM ----------
jerrycycle said:
There is a app to change those splash screen images. (logo me) My kids didn't like seeing the lock either. Used app to change lock icon to black image.
Click to expand...
Click to collapse
Cool Ill give it a try soon.
gregs1213 said:
Man, I just don't get how that is that big of a deal.. I think the unlock logo at the bottom is actually cool. My friend said one of his friends didn't want to root his Nexus 7 because he didn't like the unlock symbol on the boot up screen too... I was soo confused. How can it bother you that much?
Click to expand...
Click to collapse
Yeah, i felt it was cool too for the first 3 months of having the Gnex but recently, Every friends non-google device i see (specifically the s2 or the s3) has the triangle on the splash screen, When they see my phone start up without the unlock symbol, they're all like "whoa dude, you still haven't modded your phone?"
then i'll go like "Nah, Why should i do that when i have the purest android ever and there's no need to mod this fast beast"
Long story cut short, i just wanna show off how awesome pure android is
No
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

No lockscreen or Market/Google Play

Hey there,
So I just got my GSM Galaxy Nexus in the mail today and found a couple things to be a bit odd. You see, my package came with 2 Galaxy Nexuses (or nexi?) and my brother's phone seemed completely normal. It had Android 4.0.4 which he instantly got an update for Jellybean. My phone on the other hand was a bit off, as stated previously. My Galaxy Nexus shipped with Android 4.0.1, when i went to the "about phone" tab, there was no option to even check for a system update, my lock screen doesn't work (security settings are on slide yet the power button just wakes my screen and no sliding to unlock required), I have no market or google play store, I can't add a Gmail account under the "accounts and sync" tab, and my home button wasn't working (factory resetting fixed this).
I'm honestly just stuck on what to do about this device. I've factory reset this device 5 times already and nothing else has worked except for fixing the home button which wasn't working on my initial boot up.
Is there any solution to this Nexus or do I just have a defective one?
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
netbuzz said:
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
Click to expand...
Click to collapse
Build Number: full_maguro-eng 4.0.1 ICL23D 347 test-keys
And why couldn't I have picked my brother's? Haha I don't know!
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
airkenada said:
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The problem is that my settings are set to slide yet my phone is acting as if it's set to none
El Daddy said:
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Does this void any warranty?
BrokeEven said:
Does this void any warranty?
Click to expand...
Click to collapse
You won't have a problem with warranty if you are running a stock build.
http://www.blogcdn.com/www.engadget.com/media/2011/11/nexnex20111117103746mat400mat400.jpg
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
Ha yeah! The not-so-normal apps that I have on my phone include "Angry GPS", "Dev Tools", and "SUB PBA Test". I checked with my Brother's Nexus running JB and he's got none of those. I called into Google's hotline for Nexus support and was able to get in touch with one of the supervisors. I was told that the device I received was a Developer's Model and that it was the "strangest thing ever".
El Daddy said:
You won't have a problem with warranty if you are running a stock build.
Click to expand...
Click to collapse
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
BrokeEven said:
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
Click to expand...
Click to collapse
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step. Flashing with fastboot is the safest way to do things and there is a very small chance of you bricking your phone.
Also what did google tell you to do when you called them?
Development Tools
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
I just got another Nexus from Play Store.
It's in developer mode, without Google apps and filled with a bunch of testing tools, like AngryGPS and Screen Test, the same menu in this image from maschiosoosa.
I tried to call Google Support and they give me two options.. One is doing exactly what everybody does.. Flash a stock Google image (but they said: "it's a very difficult way" lol) or the second, they will call Samsung for a replacement.
It's not a defective device, but it's kind of getting a Windows 8 Consumer Preview. A thing that it's not finished yet. Shame on Goole. lol
I'll flash of course.. It seems the bootloader is unlocked and its probably easy to do the flash thing.
Hey BrokeEven, if you got your device from Play Store you can ask for a replacement (if you are not sure of the flash image).
And probably your bootloader is already unlocked (at least if you received this same dev tool device).
El Daddy said:
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step.
Also what did google tell you to do when you called them?
Click to expand...
Click to collapse
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Yep... The same case... The guys on Google are very funny. lol
Reboot your device and check if theres a unlocked locker at the bottom of the Google logo screen.
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Reboot the phone, when it's rebooting (showing google logo) if there's unlocked sign (lock that is unlocked) under the google logo, then it's unlocked Nexus. If you only see Google logo, then it's just locked Nexus
I don't know whether this is a curse or a blessing... I remembered when i ordered this phone I said "meh, I'm not gonna bother with rooting and flashing ROMs. I'll just stick to stock. And so Google sends me a Nexus with an unlocked bootloader and now force me to flash back to stock (or root) in order to get my phone fully functional
One pic is my unlocked bootloader, the other is a picture of my ALL the apps on my phone
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
El Daddy said:
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
BrokeEven said:
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
Click to expand...
Click to collapse
On windows just hold down shift while you right click in the folder. You will see open command prompt here or similar.
Sent from my Nexus 7 using Tapatalk 2

Acer A110... Anyone?

Any of the A100 talent, have the A110?
It's a decent machine for the price. It goes for around 150, comes with 8gb internal, expandable to 32g via micro SDHC, 1gig of RAM, Tegra 3 quad core @ 1.2ghz.
Only current issue, no recovery (I believe the recovery and kernel are combined), root method or ROMs available for this beast. There was a root tool for 4.1.1, but some have updated (for better ui enhancements) to 4.1.2, and there's no root option for it.
Just wondering if any of the A100 talent have this, it would be great to see this thing unleashed!
Sorry if anyone is upset about this being the wrong category/thread... Unfortunately, XDA has no dedicated thread for the A110, at this time.
heX79 said:
Any of the A100 talent, have the A110?
It's a decent machine for the price. It goes for around 150, comes with 8gb internal, expandable to 32g via micro SDHC, 1gig of RAM, Tegra 3 quad core @ 1.2ghz.
Only current issue, no recovery (I believe the recovery and kernel are combined), root method or ROMs available for this beast. There was a root tool for 4.1.1, but some have updated (for better ui enhancements) to 4.1.2, and there's no root option for it.
Just wondering if any of the A100 talent have this, it would be great to see this thing unleashed!
Sorry if anyone is upset about this being the wrong category/thread... Unfortunately, XDA has no dedicated thread for the A110, at this time.
Click to expand...
Click to collapse
No I went with a nexus 7, no unlocking is a deal breaker right off the bat with me. Plus I heard they didn't upgrade the screen or battery in it, two things I hated about the a100, and were also deal breakers for me.
Sent from my Galaxy Nexus using Tapatalk 2
Unlocking the BL is easy on the A110. I did it with adb.
heX79 said:
Unlocking the BL is easy on the A110. I did it with adb.
Click to expand...
Click to collapse
Then why no root? If its unlocked just flash a rooted stock ROM or something.
Sent from my Nexus 7 using Tapatalk 2
Nothing seems to be available, at the moment. I wouldn't know where to begin, compiling from source.
heX79 said:
Nothing seems to be available, at the moment. I wouldn't know where to begin, compiling from source.
Click to expand...
Click to collapse
Will it use an update.zip that's been changed if its unlocked?
Sent from my Thrive - Kuroikaze B19
Wouldn't know, there is an os upgrade file on acers page, the same image name as my current version (after updating to 4.1.2), can that be renamed to update.zip, modded and flashed? I've not used a stock recovery before lol.
Sent from the Tab
heX79 said:
Wouldn't know, there is an os upgrade file on acers page, the same image name as my current version (after updating to 4.1.2), can that be renamed to update.zip, modded and flashed? I've not used a stock recovery before lol.
Sent from the Tab
Click to expand...
Click to collapse
If its a zip file maybe if not its anyone's guess how to mess with it.
Sent from my Galaxy Nexus using Tapatalk 2
Yes it's a zip, 54MB in size, just an update from 4.1.1 to 4.1.2.
Name: OS_Acer_AV051.A110.RV00RC09.WW.CUS1_A41J_A.zip
File/Folder layout:
/firmware
/META-INF
/patch
/recovery
/system
blob
Download link, for anyone interested.
heX79 said:
Yes it's a zip, 54MB in size, just an update from 4.1.1 to 4.1.2.
Name: OS_Acer_AV051.A110.RV00RC09.WW.CUS1_A41J_A.zip
File/Folder layout:
/firmware
/META-INF
/patch
/recovery
/system
blob
Download link, for anyone interested.
Click to expand...
Click to collapse
Then do a quick signature test, add a random file into it then see if it flashes or not. Doesn't matter how big or what it is.
Sent from my Galaxy Nexus using Tapatalk 2
Need to add a new source for the A110 to get developers. Its still a new tab but the down side is the battery sucks and they never change the screen angle. I guess to keep it in the $200 mark. Then again the nexus 7 has no micro sd port, hdmi port, but the screen is so clear and it support otg.
Sent from my A100 using xda premium
pio_masaki said:
Then do a quick signature test, add a random file into it then see if it flashes or not. Doesn't matter how big or what it is.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried to add the Superuser.apk to the /system/app and SU to the /system/bin, but it gives a corruption error. I'll have to completely unzip it, add the files and re-zip in order to add them.
But to work in the stock recovery, I assume it would need to be renamed to update.zip, and placed on the internal /sdcard?
heX79 said:
I tried to add the Superuser.apk to the /system/app and SU to the /system/bin, but it gives a corruption error. I'll have to completely unzip it, add the files and re-zip in order to add them.
But to work in the stock recovery, I assume it would need to be renamed to update.zip, and placed on the internal /sdcard?
Click to expand...
Click to collapse
Probably external SD.
Sent from my Galaxy Nexus using Tapatalk 2
heX79 said:
I tried to add the Superuser.apk to the /system/app and SU to the /system/bin, but it gives a corruption error. I'll have to completely unzip it, add the files and re-zip in order to add them.
But to work in the stock recovery, I assume it would need to be renamed to update.zip, and placed on the internal /sdcard?
Click to expand...
Click to collapse
Did you make it? I am waiting to root my A110 as well.
OK well let's see. Is there a twrp or something for a510? I can see about making a twrp but its extremely risky without some precise information since I don't have one to even look at for information. I'll be somewhat willing to work a little to get it opened up but you'll all need to do the homework and be willing to test it. Recoveries are very dangerous potential brickers.
Or someone that owns one can do it.
Or someone can send me one. I'm not willing to sell my n7 for what I consider a downgrade (battery and screen), especially when I just started working on deving on it lol
Sent from my Nexus 7 - JBSourcery 4.1
sky007 said:
Did you make it? I am waiting to root my A110 as well.
Click to expand...
Click to collapse
I did make it, haven't used a auto-signer on the zip yet. Got a bit busy with family being over, for new years. So no I haven't attempted a flash yet; not that I believe this will actually root the device, as the updater-script/binary won't have been updated.
pio_masaki said:
OK well let's see. Is there a twrp or something for a510? I can see about making a twrp but its extremely risky without some precise information since I don't have one to even look at for information. I'll be somewhat willing to work a little to get it opened up but you'll all need to do the homework and be willing to test it. Recoveries are very dangerous potential brickers.
Or someone that owns one can do it.
Or someone can send me one. I'm not willing to sell my n7 for what I consider a downgrade (battery and screen), especially when I just started working on deving on it lol
Sent from my Nexus 7 - JBSourcery 4.1
Click to expand...
Click to collapse
I'm willing to test/give any and all info you may need. I figured a decent starting point might be from the download on Acers page, but I could be wong. I'm completely ignorant on porting a recovery. There is a dev that wrote a tool kit for the a110, but it only rooted 4.1.1. On 4.1.2 all it's capable of (at this time) is unlocking the BL. Some method of rooting was patched (from what I've gathered so far) in 4.1.2, so the tool kit was using some form of (now patched) exploit.
Update: Some better support in this thread: http://forum.xda-developers.com/showthread.php?t=1915459
For anyone with the A110 who's interested, and stumbled here. Feel free to give support, it will show XDA how many of us own the A110, with the hopes of a dedicated thread for us to collaborate our efforts.
heX79 said:
Update: Some better support in this thread: http://forum.xda-developers.com/showthread.php?t=1915459
For anyone with the A110 who's interested, and stumbled here. Feel free to give support, it will show XDA how many of us own the A110, with the hopes of a dedicated thread for us to collaborate our efforts.
Click to expand...
Click to collapse
OK good luck guys
Sent from my Thrive - Kuroikaze B19
pio_masaki said:
OK good luck guys
Sent from my Thrive - Kuroikaze B19
Click to expand...
Click to collapse
pio_masaki,
Did you run into "loop" files in the /dev/block when using a custom recovery, during early builds for the A100?
Something is changing the devices when the custom recovery is loading, preventing us from even mounting /cache. The devices are listed as loop1, loop2, loop3 etc. Seem familier at all?
heX79 said:
pio_masaki,
Did you run into "loop" files in the /dev/block when using a custom recovery, during early builds for the A100?
Something is changing the devices when the custom recovery is loading, preventing us from even mounting /cache. The devices are listed as loop1, loop2, loop3 etc. Seem familier at all?
Click to expand...
Click to collapse
Yeah, just get ignored so they don't show up in recovery, you'll see them in android, though.
Iirc I saw its using initramfs or wtf ever Sammy uses, which will require more work on recovery inits.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] May have bricked my N7 (deb)

So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
jahames said:
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
Click to expand...
Click to collapse
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
StuMcBill said:
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
Click to expand...
Click to collapse
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
jahames said:
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
Click to expand...
Click to collapse
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
StuMcBill said:
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
Click to expand...
Click to collapse
Was working with the 4.4.2 image. Going to give the 4.4 a shot now
Same thing with 4.4...still stuck with the flo bootloader
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
jahames said:
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
Click to expand...
Click to collapse
You flashed a recovery for flo. Flash one for deb.
Edit:
http://techerrata.com/browse/twrp2/deb
Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!
if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
same issue
Richieboy67 said:
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
It is here
http://www.wugfresh.com/
It is a toolkit that makes these things very easy. I have used this many times and have never had any issues with it.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
LinearEquation said:
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Richieboy67 said:
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Click to expand...
Click to collapse
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
LinearEquation said:
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
Click to expand...
Click to collapse
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Richieboy67 said:
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Click to expand...
Click to collapse
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
LinearEquation said:
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
Click to expand...
Click to collapse
While not disastrous, I kind of know what you mean, I started with Wug's (and it is a great toolkit), but once I flashed my own kernel (I used francos app to autoflash so did not have to use recovery or fastboot), I did not realize that by using Wug's a week later that it would flash over that kernel to run those commands and NOT replace francos (I found I was back on stock), lucky by then I had learned enough to recover and no damage was done, but it does point out that my reliance had caused me more work and a bit of worry in the long run.
Still Wug's NRT is a great toolkit...but it should be used as a tool, not a replacement for knowing what to do without it.

New Root Method?

Has anyone read about Dirty Cow yet?
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
I read over on the V20 forums that one developer was able to get it to root his Note 7 that he refused to return. Surely it can work on the Note 5!?
jellybear456 said:
Has anyone read about Dirty Cow yet?
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
I read over on the V20 forums that one developer was able to get it to root his Note 7 that he refused to return. Surely it can work on the Note 5!?
Click to expand...
Click to collapse
I've said earlier if someone could compile it for me I would give it a try, I am no developer so I really don't know what I'm doing when I comes to that but I know enough to find my way through cmd an adb
Surely since no one has written a reply someone must be working on this, I'm pretty techy but I am in no way shape or form a dev but I am down to help, test or give input where I can.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
dpwguenther said:
I've said earlier if someone could compile it for me I would give it a try, I am no developer so I really don't know what I'm doing when I comes to that but I know enough to find my way through cmd an adb
Click to expand...
Click to collapse
Message me good sir.
Also the biggest problem is SELINUX is set in bootloader.
Now that it's been proven drammer can flip the memory on the note 5 (tested myself with their test app) we should be able to set SELinux to passive with the right knowhow and then root with dirty cow.
Unfortunately I am not a dev nor do I know how to code android but this all looks promising. Hopefully all the devs haven't moved on from this device (like I'm sure most of us will when our contracts are up).
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Jspex said:
Now that it's been proven drammer can flip the memory on the note 5 (tested myself with their test app) we should be able to set SELinux to passive with the right knowhow and then root with dirty cow.
Unfortunately I am not a dev nor do I know how to code android but this all looks promising. Hopefully all the devs haven't moved on from this device (like I'm sure most of us will when our contracts are up).
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
We can already set SELINUX to permissive. The problem is the bootloader sets the kernel to enforcing on everyboot.
TechNyne66 said:
We can already set SELINUX to permissive. The problem is the bootloader sets the kernel to enforcing on everyboot.
Click to expand...
Click to collapse
We cannot set SELINUX in MM..? All the dirtyc0w scripts work fine to get run-as or farm on system of the phone as long as you compile with arm64-v8a. But SELINUX makes dirtyc0w completely useless when trying to drop to root shell...
straby187 said:
We cannot set SELINUX in MM..? All the dirtyc0w scripts work fine to get run-as or farm on system of the phone as long as you compile with arm64-v8a. But SELINUX makes dirtyc0w completely useless when trying to drop to root shell...
Click to expand...
Click to collapse
We can't do anything with MM. I can try to compile whatever if you can get me the files.
If you are still on lollipop with eng kernel tether root. Can you try to pull boot pull boot and recovery
http://forum.xda-developers.com/general/security/farm-root-recovery-image-pulling-t3490089
I can already flash boot and recovery but the att crap that no one seams to understand WILL lock the phone out untill you do a full odin. However maybe some way can work as we haven't tried all but a simple flash of custom recovery to the recovery portion will not work.
What about rowhammer
TechNyne66 said:
I can already flash boot and recovery but the att crap that no one seams to understand WILL lock the phone out untill you do a full odin. However maybe some way can work as we haven't tried all but a simple flash of custom recovery to the recovery portion will not work.
Click to expand...
Click to collapse
i was asking if you could pull the original recovery from the phone, not flash it. I just wanted to get a look at it...
straby187 said:
i was asking if you could pull the original recovery from the phone, not flash it. I just wanted to get a look at it...
Click to expand...
Click to collapse
Yes we already have stock recovery. If you want to message me in the morning I can send it to you.
how is it looking for this new method, I feel like we are really close.
killernos said:
how is it looking for this new method, I feel like we are really close.
Click to expand...
Click to collapse
I can't get a single thing to work. Seams like KEXEC is out best bet and we need to focus all efforts on this. All we need is a custom kernel with kexec support and I can test to see if it will load. I have tried and tried for hours on hours to get a kernel to compile with no success.
I'm new here. Some may know who I am some may not. I just got my note 5 last week after my v10 took a ****......what's kexec and what's the error when compiling
Sent from my SAMSUNG-SM-N920A using Tapatalk
MysteryEmotionz said:
I'm new here. Some may know who I am some may not. I just got my note 5 last week after my v10 took a ****......what's kexec and what's the error when compiling
Click to expand...
Click to collapse
If you have to ask then compiling a kernel is probably beyond your experience (it's well beyond mine and I work in I T )
dezborders said:
If you have to ask then compiling a kernel is probably beyond your experience (it's well beyond mine and I work in I T )
Click to expand...
Click to collapse
You know what your right. I'm just go back into the shadows and continue boot to help. A quick search on xda would have shown you in plenty capable.
PS...When compiling a kernel it normally gives you some kinds of error message so you know where to start lookin
Sent from my SAMSUNG-SM-N920A using Tapatalk
MysteryEmotionz said:
You know what your right. I'm just go back into the shadows and continue boot to help. A quick search on xda would have shown you in plenty capable.
PS...When compiling a kernel it normally gives you some kinds of error message so you know where to start lookin
Click to expand...
Click to collapse
My bad lol no offence intended

Categories

Resources