different image version - Acer Iconia Tab A100

I sent my tablet off to get repaired after it was bricked. My new version is different when it boots than it used to be. the new build version number on my tablet is " Acer_AV041_A100_1.015.00_PA_CUS1 " and it is on kernel 2.6.39.4+. is this what others have? When i boot it now comes up with 2 acer logos one in the upper right and left. than changes to the normal center acer then android .

max69power said:
I sent my tablet off to get repaired after it was bricked. My new version is different when it boots than it used to be. the new build version number on my tablet is " Acer_AV041_A100_1.015.00_PA_CUS1 " and it is on kernel 2.6.39.4+. is this what others have? When i boot it now comes up with 2 acer logos one in the upper right and left. than changes to the normal center acer then android .
Click to expand...
Click to collapse
This is exactly what I've been waiting to see. If you can get adb up can you paste the output of adb shell cat /proc/cmdline ? The boot loader change may hint at Acer doing some work on the cause of the brick.
Tapatalked from my Galaxy S II.

pio_masaki said:
This is exactly what I've been waiting to see. If you can get adb up can you paste the output of adb shell cat /proc/cmdline ? The boot loader change may hint at Acer doing some work on the cause of the brick.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I will get it up in about 45 min when I can get back to my PC.

do i need it rooted ? I got permission denied

max69power said:
do i need it rooted ? I got permission denied
Click to expand...
Click to collapse
Probably do accessing that file to output. You could try adb root then try again but it'll probably deny that too. If you don't want to root that's cool I'll wait to see if I can pay for mine to get fixed then do it when I get it back.
Tapatalked from my Galaxy S II.

i rooted and unlocked it is still says access is denied. i am willing to try something else.

pio_masaki said:
Probably do accessing that file to output. You could try adb root then try again but it'll probably deny that too. If you don't want to root that's cool I'll wait to see if I can pay for mine to get fixed then do it when I get it back.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
if there is a way just to copy the os and boot loader i will put it up

max69power said:
i rooted and unlocked it is still says access is denied. i am willing to try something else.
Click to expand...
Click to collapse
try:
Code:
adb kill-server; adb root; adb wait-for-device; adb shell cat /proc/cmdline
If you are rooted and adb starts as root you shouldn't get permission denied. If you still do get permission denied give output of :
Code:
adb shell ls -l /proc
This will be quiet large, but we really only need to know the specific line like this:
-r--r----- root radio 0 2012-08-12 02:44 cmdline
And make sure that you aren't getting any messages like "Root isn't available in Production builds"
Thanks.

i got unknown option '-1' aborting. I will have to pick this up tomorrow afternoon.

Copy your SDK platform tools to the desktop and try again. From there.
Check android debugging
Sent from my A500 using xda app-developers app

Oh its L not 1, lowercase.
If he isn't rooted he doesn't have busy box. Just saying.
Tapatalked from my Galaxy S II.

i am charging it i will start trying in a few min. I am rooted and unlocked.

I have seen the .015 pa cus, its nothing unusual. It was one of the first ics ota's.

Romman0 said:
I have seen the .015 pa cus, its nothing unusual. It was one of the first ics ota's.
Click to expand...
Click to collapse
have you seen it start out with 2 acer logos when you are not rooted or unlocked? That was the first thing i noticed that was different.
I did the comand i got a ton of lines saying root and the one line you asked about is the same except for a different time.

Romman0 said:
I have seen the .015 pa cus, its nothing unusual. It was one of the first ics ota's.
Click to expand...
Click to collapse
Its the boot loader change that I'm interested in, not really the system image.
Tapatalked from my Galaxy S II.

linuxsociety said:
try:
Code:
adb kill-server; adb root; adb wait-for-device; adb shell cat /proc/cmdline
If you are rooted and adb starts as root you shouldn't get permission denied. If you still do get permission denied give output of :
Code:
adb shell ls -l /proc
This will be quiet large, but we really only need to know the specific line like this:
-r--r----- root radio 0 2012-08-12 02:44 cmdline
And make sure that you aren't getting any messages like "Root isn't available in Production builds"
Thanks.
Click to expand...
Click to collapse
ok i have done these and tried the first line again also but the first line is still denied. I will keep an eye on this thread if you want me to try anything else.

max69power said:
have you seen it start out with 2 acer logos when you are not rooted or unlocked? That was the first thing i noticed that was different.
Click to expand...
Click to collapse
I have not seen the dual logos. It is very interesting.
But didn't you just overwrite the new bootloader you had by installing the unlocked a200 bootloader?
i rooted and unlocked it is still says access is denied. i am willing to try something else
Click to expand...
Click to collapse

true i guess i did

Related

Help Pls

Does anyone know when I'm trying to Flash the Eng-Release to the Slide why on step 6 I get permission denied or cdmod not found?
I don't know specifically to this but yesterday while I was rooting I had that happen. I was pushing some files through adb and told me no permissions. I did reboot on phone and computer and it worked the next time. Weird. You may have already tried that but that's all I got and like I said it was not for this specific step. mine was during the root process.
khtims said:
I don't know specifically to this but yesterday while I was rooting I had that happen. I was pushing some files through adb and told me no permissions. I did reboot on phone and computer and it worked the next time. Weird. You may have already tried that but that's all I got and like I said it was not for this specific step. mine was during the root process.
Click to expand...
Click to collapse
Yea I already have root and superuser working so I don't know what's wrong.
ImABoss said:
Does anyone know when I'm trying to Flash the Eng-Release to the Slide why on step 6 I get permission denied or cdmod not found?
Click to expand...
Click to collapse
If you are actually typing "cdmod" that is why, the command is "chmod".
falken98 said:
If you are actually typing "cdmod" that is why, the command is "chmod".
Click to expand...
Click to collapse
Wow thanks for pointing that out. I can't believe I was typing it wrong.

Need Xoom WiFi boot.img

Looks like the boot.img on the WiFi only model is slightly different. Flashed the rooted boot.img file and now I'm stuck at the Dual Core technology screen. Anyone have this available. All help greatly appreciated!
UPDATE
See thread -> http://forum.xda-developers.com/showthread.php?p=12432218
Can someone post the stock xoom wifi dump of the boot.img, recovery.img, system.img, and userdata.img in case something happens?
Apparently it looks like its slightly different than the wifi+3g version. Also is the overclocked kernel file working posted by coolbho3000?
i need the answer too... i m comfused.
Alright I have a stock Xoom tablet now Just gotta figure out how to pull the boot.img file off. Any ideas and I'll do it ASAP.
No clue mate. From my knowledge you have to be rooted, or have the SDK on your pc. I think. Neither which are available as of now
So is the wifi only version able to be rooted as of now?
currently, yes. We need a new root method. Well I would not say a new "method" but their need to be some modifications done to the original rootboot img file. Shouldnt be hard for devs
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Issue 1: Don't currently have root
Issue 2: No SD card access
But I did try it and got an access denied.
onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App
B Dizzle said:
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
It's actually a Permission issue.
/dev/block/platform/sdhci-tegra.3/by-name/boot: Permission denied
So someone with root needs to run it. Anyone wanna help out? Im not getting mine till tomorrow but by then I suppose you would have yours exchanged
Sent from my Nexus One using XDA Premium App
B Dizzle said:
So someone with root needs to run it.
Click to expand...
Click to collapse
That's actually the catch-22... can't get root because we don't have the right boot.img file. I think it's going to boil down to Motorola releasing a stock one.
If anyone is up for IRC chat - hop onto Freenode and room #Xoom
I can try if someone tells me what needs to be done. I tried copying it over to another folder in root explorer but no luck.
Update: Ran through the fastboot oem unlock in hopes that it would resolve the Permission Denied. It did not.
http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154
destroyerbmx said:
http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154
Click to expand...
Click to collapse
You'll end up with a (soft)brick
No luck
I also booted into fast boot, tried and still got no permission sometimes and no such directory some times... If some one will walk me through getting the img file I will gladly do so
how can I remove the softbrick, I saw this AFTER I tried to root and now I cannot even turn it off, just sitting on the Motorola Dual Core Technology screen.
ok I also now need to the stock boot.img from a wifi xoom. Can anyone help? I can flash it if someone can provide it please, if not I guess I will go exchange my xoom in the morning.

anyone started to root the device?

has anyone started to root this device?
i need to gain access to the root folder
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Lol what a way to put it
Sent from my LT15i using Tapatalk
vegetaleb said:
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Click to expand...
Click to collapse
+1
hahah this made my day
I will try tomorrow. Will have to get testers as I can only test on DHD.
vegetaleb said:
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Click to expand...
Click to collapse
Good 1 :-D
lollylost100 said:
I will try tomorrow. Will have to get testers as I can only test on DHD.
Click to expand...
Click to collapse
I would like to help testing. just pm me when you need a tester
vegetaleb said:
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Click to expand...
Click to collapse
Whaha really Genius!
But rooting can't be far away now..... Because I don't think the Durex is sold out in the super market. I actually think they have a special offer...
It's precisely because of the lack of root access that I've held of unlocking my bootloader; I don't see any point of having to erase all my data and setting up my device when there's no pay-off in the form of root and custom ROMs
Yeah well you never know if SE change their minds and cancel the unlocking website
Better get your gift before Santa takes it back
I will try to convince Marc from MIUI to think about the Arc...
I don't think SE will change it's mind, but the longer you wait, the more adjustments you make on your device (well at least I do..). So that's why I unlocked the bootloader as soon as I had my Arc. Even though I had allready played with it. But what the h*ll, now I had to play a bit longer with it. I don't see the problem
They wont change their mind but the downside of unlocking is that you cannot update using SEUS
Hopefully SE will change that if you use stock firmware but have the bootloader unlocked
Sent from my LT15i using XDA App
Blomkungen said:
They wont change their mind but the downside of unlocking is that you cannot update using SEUS
Hopefully SE will change that if you use stock firmware but have the bootloader unlocked
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
I don't see where that's a problem : if you unlock your bootloader, it's because you want to flash custom roms, isn't it ?
Who care about stock update when we get better functionnalities and often faster updates with all the leaks with custom roms ?
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
lollylost100 said:
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
Click to expand...
Click to collapse
permission denied
lollylost100 said:
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
Click to expand...
Click to collapse
su: permission denied
lollylost100 said:
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
Click to expand...
Click to collapse
I try to test when I reach home. Don't I need to push the su to the phone first?
Sent from my Xperia Arc
I don't have my PC with working ADB drivers here, try this:
adb remount
adb shell
su
Sometimes it need the adb remount to access system files
vegetaleb said:
I don't have my PC with working ADB drivers here, try this:
adb remount
adb shell
su
Sometimes it need the adb remount to access system files
Click to expand...
Click to collapse
remount failed: operation not permitted
We definitely need a custom Boot image flashed then!
If only I took Linux courses...

Phone app requesting superuser

This just started today. Anyone else having the Phone app request superuser?
I just had "reset notify" request superuser, and I'm at work so I haven't had a chance to figure out what it exactly is yet.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Phone asked again today. Only one it seems. Tempted to let it go haha.
I have it also.
GrayTheWolf said:
I have it also.
Click to expand...
Click to collapse
At least I'm not going crazy. I managed to catch the command and it's trying to chmod 666 a modem file. I'm going to turn on full logging in su to see exactly what file.
isdnmatt said:
At least I'm not going crazy. I managed to catch the command and it's trying to chmod 666 a modem file. I'm going to turn on full logging in su to see exactly what file.
Click to expand...
Click to collapse
If the stock phone app is being granted root, might there be a possible root exploit somewhere depending on the command?
firepacket said:
If the stock phone app is being granted root, might there be a possible root exploit somewhere depending on the command?
Click to expand...
Click to collapse
I doubt it. I would be more interested to see if it's checking for root to change or disable something.
It only does it about once every other day though.
isdnmatt said:
I doubt it. I would be more interested to see if it's checking for root to change or disable something.
It only does it about once every other day though.
Click to expand...
Click to collapse
It happens to me too. Running BoneStock 1a. I have it set to deny and not prompt me and haven't noticed any difference whatsoever.
The phone app asking for root randomly seems like a dirty hack someone made and those tend to be sloppy. What if you could symlink the chmod target, or adjust the path variable to have it execute something else?
I am now pretty interested to see the command it's trying to run, lets turn on logging and see if it happens.
I have gotten it a few times, not since v1.0f but nothing I changed would make it stop, not sure what the hell it wants permission for and wy it's asking for it, but I also denied it.
I've also been getting it several times in the last few days.
I get it on my stock rom just after unlocking bootloader and installing supersu on launch day. Like others I just denied it. Haven't seen any side effects yet since then.
Sent from my HTC6500LVW using xda app-developers app
Zynesterysdan said:
I get it on my stock rom just after unlocking bootloader and installing supersu on launch day. Like others I just denied it. Haven't seen any side effects yet since then.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
HTC Service Accessory or something similar to that requests root every few days on mine. Is that what you guys are asking about? Haven't had the phone app request access yet.
karn101 said:
HTC Service Accessory or something similar to that requests root every few days on mine. Is that what you guys are asking about? Haven't had the phone app request access yet.
Click to expand...
Click to collapse
No... the Phone app. I haven't had any other system app request root access on any of my devices, it completely undermines the security platform.
If the Phone app is being granted root on a stock phone, that means that app is whitelisted for root access somehow. And wasn't there a recent Android vulnerability that allows you to alter the code of a signed APK without affecting the signature?
---------- Post added at 04:15 AM ---------- Previous post was at 03:54 AM ----------
This is the command it is trying to run: chmod 666 /sys/devices/platform/mdm2_modem/msr_info
The mdm2_modem is public rx only, but would it be possible to change the app's PATH variable maybe and have it execute a different chmod since I can't tell if it is using the full file path to execute it.
Well my little newb investigation turned up nothing.
The Phone app is run as user "radio" uid 1001 which, unlike root, does have a PATH set to outside /system. Write access to /data/local/ would almost certainly give root but I'm sure that's probably known already.
Android bug 8219321 would have given root to original versions of The One running 4.1, but the Verizon version runs 4.2.2.
Oh well, obviously couldn't have been that easy.
firepacket said:
No... the Phone app. I haven't had any other system app request root access on any of my devices, it completely undermines the security platform.
If the Phone app is being granted root on a stock phone, that means that app is whitelisted for root access somehow. And wasn't there a recent Android vulnerability that allows you to alter the code of a signed APK without affecting the signature?
---------- Post added at 04:15 AM ---------- Previous post was at 03:54 AM ----------
This is the command it is trying to run: chmod 666 /sys/devices/platform/mdm2_modem/msr_info
The mdm2_modem is public rx only, but would it be possible to change the app's PATH variable maybe and have it execute a different chmod since I can't tell if it is using the full file path to execute it.
Click to expand...
Click to collapse
Wouldn't chmod 666 make it writeable? That would be a sneaky trick is they put that request in there to check for root and change something. I feel like root = free tethering to Verizon lol.
I would think that there is a root exploit available for the one, but there is no point in using it right now because system is protected and the phone resets whenever you try to change system.
isdnmatt said:
Wouldn't chmod 666 make it writeable? That would be a sneaky trick is they put that request in there to check for root and change something. I feel like root = free tethering to Verizon lol.
I would think that there is a root exploit available for the one, but there is no point in using it right now because system is protected and the phone resets whenever you try to change system.
Click to expand...
Click to collapse
Yeah it makes it world writable which could be relevant depending on how that file is used by other processes. I'm sure there are others who have been at this longer so I won't waste my time looking for a unicorn.
And I think people would still like root even if they lose it on restart.
I'm getting this issue on a stock Rogers HTC One with root. Has anybody been able to gather the SU logs?
going into recovery and fixing permissions worked for me.
wiredout46 said:
going into recovery and fixing permissions worked for me.
Click to expand...
Click to collapse
are you sure? I get it only every few days so hard to nail down a fix.
firepacket said:
[/COLOR]This is the command it is trying to run: chmod 666 /sys/devices/platform/mdm2_modem/msr_info
The mdm2_modem is public rx only, but would it be possible to change the app's PATH variable maybe and have it execute a different chmod since I can't tell if it is using the full file path to execute it.
Click to expand...
Click to collapse
As was posted, it's trying to make a modem file writable. Fixing permissions might make sense. It also probably means that this is no big deal.

Changing dpi and warranty

I'm tempted to change dpi to take advantage of 4k screen but wanted confirmation if doing so would void warranty. Also how do you change dpi and do you need to be rooted?
Thanks
Any modifacation voids your warrenty
And to edit your DPI you need to edit /system/build.prop and look for a line that says
"ro.sf.lcd_density=480"
(480 part may differ per user or device)
( i believe 4k dpi is 820)
Hi, how you can do that if there is no rooting for that device?
sev7en said:
Hi, how you can do that if there is no rooting for that device?
Click to expand...
Click to collapse
Flash recovery
Flash su binary
Rooted
Alternatively you can push it through adb
Envious_Data said:
Flash recovery
Flash su binary
Rooted
Alternatively you can push it through adb
Click to expand...
Click to collapse
how can I push it through adb?
Envious_Data said:
Flash recovery
Flash su binary
Rooted
Alternatively you can push it through adb
Click to expand...
Click to collapse
As first thanks for your reply, where did you get the Recovery? Did you the same of Z5?
Thanks,
tonylcc said:
how can I push it through adb?
Click to expand...
Click to collapse
sev7en said:
As first thanks for your reply, where did you get the Recovery? Did you the same of Z5?
Thanks,
Click to expand...
Click to collapse
I dont have a Z5 but Sony Xperia devices typically get a working Recovery shortly after release
I have tried pushing superUser through ADB many times logged in as sudo or root and it has been fine.
You can look up guides on "how to install ADB" and how to push "superSu through Adb"
It may be that my Z2's bootloader is unlocked hence why im able to root it so easily but i havent the time to test the fact.
Envious_Data said:
I dont have a Z5 but Sony Xperia devices typically get a working Recovery shortly after release
I have tried pushing superUser through ADB many times logged in as sudo or root and it has been fine.
You can look up guides on "how to install ADB" and how to push "superSu through Adb"
It may be that my Z2's bootloader is unlocked hence why im able to root it so easily but i havent the time to test the fact.
Click to expand...
Click to collapse
Thanks but you are reporting that without to have checked it with the device? I am curious to try the 4K in the whole system...
ZohabK said:
I used this guide, and it worked perfectly!
Let me know if you have problems with it...
http://android.wonderhowto.com/how-...creen-resolution-without-root-access-0160439/
Click to expand...
Click to collapse
This guy seems to have done it without root using the linked method.
Craleb said:
This guy seems to have done it without root using the linked method.
Click to expand...
Click to collapse
And here's the proof...
http://forum.xda-developers.com/showthread.php?p=63858899
ZohabK said:
And here's the proof...
http://forum.xda-developers.com/showthread.php?p=63858899
Click to expand...
Click to collapse
Thanks for posting that. I was curious as to what DPI you went with.
Envious_Data said:
I dont have a Z5 but Sony Xperia devices typically get a working Recovery shortly after release
I have tried pushing superUser through ADB many times logged in as sudo or root and it has been fine.
You can look up guides on "how to install ADB" and how to push "superSu through Adb"
It may be that my Z2's bootloader is unlocked hence why im able to root it so easily but i havent the time to test the fact.
Click to expand...
Click to collapse
People are reporting that the camera's features stop working once you unlock the bootloader... Can you confirm this? I believe it was reported that two major camera functions stop...don't know if there is a workaround yet.
gparmar76 said:
People are reporting that the camera's features stop working once you unlock the bootloader... Can you confirm this? I believe it was reported that two major camera functions stop...don't know if there is a workaround yet.
Click to expand...
Click to collapse
Im not sure about how it is with the Z5P
But with my Z2 2 things stopped, post processing and xreality which in my opinion both are a waste of time
You can change you DPI by running
adb shell wm density 400
and reset it by running
adb shell wm density reset
You don't have to root or unlock your bootloader to change screen density.
CLShortFuse said:
You can change you DPI by running
adb shell wm density 400
and reset it by running
adb shell wm density reset
You don't have to root or unlock your bootloader to change screen density.
Click to expand...
Click to collapse
Would doing so void your warranty?
riz157 said:
Would doing so void your warranty?
Click to expand...
Click to collapse
Ask a lawyer who specialises in consumer law in the country you live in. They would definitely know.
Sent from my SGP311 using XDA Free mobile app
riz157 said:
Would doing so void your warranty?
Click to expand...
Click to collapse
Any customization voids your warranty. But you can always change back the DPI to factory...
Sorry for my weak english
I need a little help. I changed my dpi to 400 using adb and now the icons don't fill the screen
kamalaggi said:
I need a little help. I changed my dpi to 400 using adb and now the icons don't fill the screen
Click to expand...
Click to collapse
Yeah the stock launcher won't adapt to the DPI the way you'd think. You could try Nova with the 400 DPI.
what is the consensus what is the best dpi?

Categories

Resources