[Q] Root for acer iconia A1? - Android Q&A, Help & Troubleshooting

Does anyone know how to root acer iconia a1 tablet?
thanks for the replies

serpe18 said:
Does anyone know how to root acer iconia a1 tablet?
thanks for the replies
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=40425886
Enviado desde mi B1-A71 usando Tapatalk 2

Succesfully run root, but got permisson deny when type su on Iconia A1
Hi,
I used your 0.7.0 (and 0.6.3) root tools and tried to root my Iconia A1.
I had tried Linux (root from scratch method) and Windows root method, the results are the same. All said successfully rooted after finish execution those root tools.
But actually My Iconia A1 can not execute su when I go into shell. (I use adb shell to verify su succeed or not).
The message from shell console shows permission denied.
Is there any steps missed from me?

same here
I had the same prob with my asus.
And still get no solution.
One time the root tool v31 worked, but only Wirth the imfo su is old. Open the supersu and i get the Info that is not possible. Still no root.

Q
does anyone gonna make mods or roms for acer iconia? because im tired of my Acer Iconia A1-810 Tablet!!!!! i bought it 2 days ago!!! waste of money and no HD screen! i should read before i bought it! i could have bought a Nexus 7!
:crying:

a1 811
I have the A1 811 Version and also looking for root.
This tab has a MTK chipset, so i looked at many China Forums and get many root Tools.
But no success. I dont know why. The Ainol 828 has the same chipset. If someone had more luck than i had.

konsolen said:
I have the A1 811 Version and also looking for root.
This tab has a MTK chipset, so i looked at many China Forums and get many root Tools.
But no success. I dont know why. The Ainol 828 has the same chipset. If someone had more luck than i had.
Click to expand...
Click to collapse
If you have a MT65XX CPU then I can help you root it. Download and install the tool from first post of this link then run it, it will tell you which MT65XX CPU you have and then we can get you rooted from there. You will need ADB drivers for MTK Droid Tools to work but I have them also if you need them.
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Hope this helps!

Klown80 said:
If you have a MT65XX CPU then I can help you root it. Download and install the tool from first post of this link then run it, it will tell you which MT65XX CPU you have and then we can get you rooted from there. You will need ADB drivers for MTK Droid Tools to work but I have them also if you need them.
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Hope this helps!
Click to expand...
Click to collapse
Thank you. I hope we can root this Thing.
MKT Tool read it as MT6589 (Fake 8389)
Thats from the scatter:
ADER 0x0
{
}
MBR 0xc00000
{
}
EBR1 0xc80000
{
}
__NODL_PMT 0xd00000
{
}
__NODL_PRO_INFO 0x1100000
{
}
__NODL_NVRAM 0x1400000
{
}
__NODL_PROTECT_F 0x1900000
{
}
__NODL_PROTECT_S 0x2300000
{
}
__NODL_SECCFG 0x2d00000
{
}
UBOOT 0x2d20000
{
}
BOOTIMG 0x2d80000
{
}
RECOVERY 0x3380000
{
}
SEC_RO 0x3d80000
{
}
__NODL_MISC 0x4380000
{
}
LOGO 0x4400000
{
}
__NODL_EXPDB 0x4700000
{
}
ANDROID 0x5100000
{
}
CACHE 0x45100000
{
}
USRDATA 0x70d00000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}
---------- Post added at 03:22 AM ---------- Previous post was at 03:18 AM ----------
konsolen said:
Thank you. I hope we can root this Thing.
MKT Tool read it as MT6589 (Fake 8389)
Thats from the scatter:
ADER 0x0
{
}
MBR 0xc00000
{
}
EBR1 0xc80000
{
}
__NODL_PMT 0xd00000
{
}
__NODL_PRO_INFO 0x1100000
{
}
__NODL_NVRAM 0x1400000
{
}
__NODL_PROTECT_F 0x1900000
{
}
__NODL_PROTECT_S 0x2300000
{
}
__NODL_SECCFG 0x2d00000
{
}
UBOOT 0x2d20000
{
}
BOOTIMG 0x2d80000
{
}
RECOVERY 0x3380000
{
}
SEC_RO 0x3d80000
{
}
__NODL_MISC 0x4380000
{
}
LOGO 0x4400000
{
}
__NODL_EXPDB 0x4700000
{
}
ANDROID 0x5100000
{
}
CACHE 0x45100000
{
}
USRDATA 0x70d00000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}
Click to expand...
Click to collapse
If i push root, device reboot and i get the info Root is possible over CWM.

konsolen said:
Thank you. I hope we can root this Thing.
MKT Tool read it as MT6589 (Fake 8389)
Thats from the scatter:
ADER 0x0
{
}
MBR 0xc00000
{
}
EBR1 0xc80000
{
}
__NODL_PMT 0xd00000
{
}
__NODL_PRO_INFO 0x1100000
{
}
__NODL_NVRAM 0x1400000
{
}
__NODL_PROTECT_F 0x1900000
{
}
__NODL_PROTECT_S 0x2300000
{
}
__NODL_SECCFG 0x2d00000
{
}
UBOOT 0x2d20000
{
}
BOOTIMG 0x2d80000
{
}
RECOVERY 0x3380000
{
}
SEC_RO 0x3d80000
{
}
__NODL_MISC 0x4380000
{
}
LOGO 0x4400000
{
}
__NODL_EXPDB 0x4700000
{
}
ANDROID 0x5100000
{
}
CACHE 0x45100000
{
}
USRDATA 0x70d00000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}
---------- Post added at 03:22 AM ---------- Previous post was at 03:18 AM ----------
If i push root, device reboot and i get the info Root is possible over CWM.
Click to expand...
Click to collapse
Actually since you have a MT6589, you may be in luck and be able to root your device rather quickly. Go to this link and download Motochopper, I know it is from Galaxy S4 thread but it wrks on a number of devices. Make sure you have drivers installed and USB debugging enabled in settings. (If you need help installing drivers you can get them from here: http://www.snappea.com/ )
http://forum.xda-developers.com/showthread.php?t=2252248
If this by chance does not work on your device, let me know and there is another quick root method we can try before having to go the long route and pull the stock recovery to gain root.
Good luck!

Klown80 said:
Actually since you have a MT6589, you may be in luck and be able to root your device rather quickly. Go to this link and download Motochopper, I know it is from Galaxy S4 thread but it wrks on a number of devices. Make sure you have drivers installed and USB debugging enabled in settings. (If you need help installing drivers you can get them from here: http://www.snappea.com/ )
http://forum.xda-developers.com/showthread.php?t=2252248
If this by chance does not work on your device, let me know and there is another quick root method we can try before having to go the long route and pull the stock recovery to gain root.
Good luck!
Click to expand...
Click to collapse
Thx again. I tried snappea and moborobo. No Chance. I triedmotochopper, root with restore and doomlords v17 and eroot 1.3.4

konsolen said:
Thx again. I tried snappea and moborobo. No Chance. I triedmotochopper, root with restore and doomlords v17 and eroot 1.3.4
Click to expand...
Click to collapse
So do you have working drivers now? Also, do you have USB debugging enabled on the device? Once you get drivers working I know of a few other root program you can use.
Once drivers are working you can use this most likely:
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7&styleid=18

I loadet the last VersionVersion is tool. After the process i get the info root OK. A chinese Version of superuser is also installed but still no root.
When i install a english version i get every time no su binary installed.

konsolen said:
I loadet the last VersionVersion is tool. After the process i get the info root OK. A chinese Version of superuser is also installed but still no root.
When i install a english version i get every time no su binary installed.
Click to expand...
Click to collapse
You do not get a pop up from chinese app when you try to update binary? If so make sure you hit the right hand button. IF not pop up, go into the chinese root app and tap the last choice (I think it says root in the title) then it should show you a list of apps that asked for root access, check to make sure SuperSU did not get denied first. If that still wont work we will move on to the harder root method if you like.

Klown80 said:
You do not get a pop up from chinese app when you try to update binary? If so make sure you hit the right hand button. IF not pop up, go into the chinese root app and tap the last choice (I think it says root in the title) then it should show you a list of apps that asked for root access, check to make sure SuperSU did not get denied first. If that still wont work we will move on to the harder root method if you like.
Click to expand...
Click to collapse
I see the list of apps with a blue switch on right side.
But still no su install possible. Root tools and mobile uncle said no root.
IS this possible that this tool put the binary in a wrong place?
And yes, i want to heck this thing. So harder way are welcome. -

konsolen said:
I see the list of apps with a blue switch on right side.
But still no su install possible. Root tools and mobile uncle said no root.
IS this possible that this tool put the binary in a wrong place?
And yes, i want to heck this thing. So harder way are welcome. -
Click to expand...
Click to collapse
Try this:
http://www.cydiaimpactor.com/
Download Impactor. Extract the files then run the Impactor application. When it opens make sure device is connected to PC and USB debugging is enabled. Then just hit start button. As long as you dont get a fail message try installing SuperSU from Play Store after wards and see if it lets you update bainry now.
If that dont work either I have one more program we can try before we take the long route. Finally try the MTK root all zip I have attached. Let me know how it goes please.

Klown80 said:
Try this:
http://www.cydiaimpactor.com/
Download Impactor. Extract the files then run the Impactor application. When it opens make sure device is connected to PC and USB debugging is enabled. Then just hit start button. As long as you dont get a fail message try installing SuperSU from Play Store after wards and see if it lets you update bainry now.
If that dont work either I have one more program we can try before we take the long route. Finally try the MTK root all zip I have attached. Let me know how it goes please.
Click to expand...
Click to collapse
THe injector i tried 2 days ago. Failes. I will tray your second tool.
THx

konsolen said:
THe injector i tried 2 days ago. Failes. I will tray your second tool.
THx
Click to expand...
Click to collapse
Ok, let me know how the last tool goes. If still no luck we can just take the long route. Your device isnt making this easy is it? lol

Klown80 said:
Ok, let me know how the last tool goes. If still no luck we can just take the long route. Your device isnt making this easy is it? lol
Click to expand...
Click to collapse
OK, second tool also nothing. SH... I dont understand the chinese superuser. If i install an APP, a popup comes. But left or right button, akways the same.

konsolen said:
OK, second tool also nothing. SH... I dont understand the chinese superuser. If i install an APP, a popup comes. But left or right button, akways the same.
Click to expand...
Click to collapse
something does indeed sound messed up. If you have any free time today I will have some time if you would like to install Teamviewer on your PC, I can connect and help you get this issue solved.

Klown80 said:
something does indeed sound messed up. If you have any free time today I will have some time if you would like to install Teamviewer on your PC, I can connect and help you get this issue solved.
Click to expand...
Click to collapse
Wow, thank you. I would really thankfully for that. Because this thing buggibg me,
I rootet from rk chip devices over sony, htc every phone or tablet.
This is the first one, which is really hard to knock.
As my last chance i thinked about about a backup to implement su and write it back.
But i dont know how to open the backup.ba.
What time is ok for you? Iam from austria and here is 17:00.
What do say about 20:00 around?
My wife is looking tv , so i can concentrate me -

Related

[Q] How to disable power button in lock screen ?

Hi,
I managed to do it in SGS2 but with my tab 10.1 it didn't work ..
I edited the file sec_power_key.kl and removed the WAKE command from POWER.
the reason I want this is for security because I don't want any one to turn off the device if my tab is locked.
Thanks.
logic5 said:
Hi,
I managed to do it in SGS2 but with my tab 10.1 it didn't work ..
I edited the file sec_power_key.kl and removed the WAKE command from POWER.
the reason I want this is for security because I don't want any one to turn off the device if my tab is locked.
Thanks.
Click to expand...
Click to collapse
Without that key edit I am not sure. In source it could be done by doing something like:
Line 317:
https://github.com/CyanogenMod/andr...droid/internal/policy/impl/GlobalActions.java
That creates the list you see when its called. You could create an intent to override those default settings.
Code:
@Override
public void onReceive(Context context, Intent intent) {
if (intent.getAction().equals(Intent.ACTION_SCREEN_OFF)) {
//screen locked
} else if (intent.getAction().equals(Intent.ACTION_SCREEN_ON)) {
//screen unlocked
}
}
Then you update the code in 317 to check the variable assigned at that public void. If true it wouldn't display that list, meaning phone locked. If false it would show that list meaning phone awake.
Other then that. I am not sure. I will let you know if I come up with anything else though.

[Q] Please help dumping an MTK6575 Phone's ROM

Hi guys I could really do with some help.
I recently purchased 4 Haipai Noble i9220s. 3 of them I have 'upgraded' to the latest firmware found on this thread. However (and luckily), before flashing the last device I noticed that with the firmware from that thread, the SIM functionality is missing - pretty important for a phone! I need then to retrieve the firmware from the one un-flashed phone.
I have tried following the instructions here (I know that's for 65x3 devices, but that's all I could find) to dump the rom but I get stuck. The first file I tried to dump was DSP_BL (assuming, rightly or wrongly, this is the bootloader for the second 'core', ie the one that runs the GSM radio) however the start address is 0x04000 and end address is 0x046023. I make the length, therefore 0x042023. However when putting these figures into the flash tool I get the message "[WARNING] Read back length is adjusted to 512-Bytes alignment" and I am unable to proceed.
I would really appreciate help with this; I need to get the other three devices back into a working state!
Thanks in advance
OK... I managed to find a version of MTK Tools here, which I gather is needed to dump the ROM. I have successfully performed the dump, but when I load the scatter into Flash Tool I get the following error message on both the PRELOADER and the DSP_BL:
BROM ERROR: S_DL_PC_BL_INVALID_GFH_FILE_INFO (5066)
All the other files load fine, but after flashing the dumped firmware to another phone the radio doesn't come back (in fact the phone simply loads up on what appears to be an 'enter your recovery password' screen, but it's in chinese so I can't verify that.
Here's the scatter file, if it's any help...
PRELOADER 0x0
{
}
DSP_BL 0x40000
{
}
MBR 0x600000
{
}
EBR1 0x604000
{
}
__NODL_PMT 0x660000
{
}
__NODL_NVRAM 0xa60000
{
}
__NODL_SECCFG 0xd60000
{
}
UBOOT 0xd80000
{
}
BOOTIMG 0xde0000
{
}
RECOVERY 0x13e0000
{
}
SEC_RO 0x19e0000
{
}
__NODL_MISC 0x1fe0000
{
}
LOGO 0x2040000
{
}
__NODL_EXPDB 0x2340000
{
}
EBR2 0x23e0000
{
}
ANDROID 0x23e4000
{
}
CACHE 0x224e4000
{
}
USRDATA 0x425e4000
{
}
__NODL_FAT 0x626e4000
{
}
__NODL_BMTPOOL 0xffff0050
{
}
Click to expand...
Click to collapse
I just found out that Root & Tools has a button "To prepare blocks for flash tool". Pressing this prepares a flashable firmware which includes the Preloader and DSP_BL. However, reflashing the devices with this firmware does not re-enable the GSM Radio. I noted the following error message when attempting "To prepare blocks for flash tool"
-- preloader_and_dsp: md5 OK; ... it is copied ... cut OK- The signature isn't found! ... File Size Too Small!
-- DSP_BL: md5 OK; ... it is copied ... cut OK
-- MBR: md5 OK; ... it is copied
......
Click to expand...
Click to collapse
any ideas, anybody?
You phone is rooted?
I don't know that phone, but you can look in the build.prop. There is a line that specifies the rild module. Look that the file exists. If is there, try using the one from the original rom.
http://www.kandroid.org/online-pdk/guide/telephony.html
Hi thanks for that but it hasn't worked.
I didn't think it would have, As I say, the firmware, including system image is flash-able to the device, so all the correct files appear to be in place in the file system. I'm guessing it must be something to do with those Preloader and BL images which caused errors when backing up. I'm just at a loss as to what I can do to fix the issue :s
Try this steps to enable GSM Radio
Phone must be rooted.
1. Open Es File Explorer.
2. Go to Setting>Root Setting> and tick all.
3. Go to data/nvram/md/ and delete NVRAM folder. You must successful delete NVRAM folder.
4. Then reboot.
5. Open ZOPO_IMEI then write new imei.
6. Shutdown device, insert SIM and turn on device.
7. Done.
If not successful, repeat again but at step number 3 go to data/ and delete nvram folder.
mtk 6575 rom backup
LairdPleng said:
Hi guys I could really do with some help.
I recently purchased 4 Haipai Noble i9220s. 3 of them I have 'upgraded' to the latest firmware found on this thread. However (and luckily), before flashing the last device I noticed that with the firmware from that thread, the SIM functionality is missing - pretty important for a phone! I need then to retrieve the firmware from the one un-flashed phone.
I have tried following the instructions here (I know that's for 65x3 devices, but that's all I could find) to dump the rom but I get stuck. The first file I tried to dump was DSP_BL (assuming, rightly or wrongly, this is the bootloader for the second 'core', ie the one that runs the GSM radio) however the start address is 0x04000 and end address is 0x046023. I make the length, therefore 0x042023. However when putting these figures into the flash tool I get the message "[WARNING] Read back length is adjusted to 512-Bytes alignment" and I am unable to proceed.
I would really appreciate help with this; I need to get the other three devices back into a working state!
Thanks in advance
Click to expand...
Click to collapse
:good:
Hi,
I successfully rooted and backed up my mtk 6575 hd7 phone with mtk droid tools. Also I made another stock rom back up with rom dump2. Only you need to do the things that install adb and vcom drivers of the phone to your computer.
MT6575 custpack partition (ALCATEL One Touch 5020A/5020E)
Hi everyone!!!
I got my ALCATEL One Touch 5020A and its cool even powered of a single core cpu only. Like other android device user I'd like to use a custom ROM on it but the problem is SP Flash Tool can't Readback the custpack partition. How could I port a ROM on it if this problem occurs?
Please help me guys.... What Flash Tool version should I use to carry out custpack partition? Or any Tool you know to solve my problem.
Your help will highly appreciated.
Thanks.

[Q] [Help] s4 mini 1:1 Bootloop after root/backup with MTkdroidtools

Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
Hardware : MT6572
Model : GT-I9190
Build number : ALPS.JB3.MP.V1
Build date UTC : 20131111-114605
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1.P1, 2013/09/02 13:50
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Mon Nov 11 19:44:39 CST 2013
Uboot build v : ----- should be root shell
LCD Driver IC : 1-otm8009a_fwvga_mipi
Click to expand...
Click to collapse
-scatter
PRELOADER 0x0
{
}
__NODL_PRO_INFO 0x100000
{
}
__NODL_NVRAM 0x200000
{
}
__NODL_PROTECT_F 0x500000
{
}
__NODL_PROTECT_S 0x800000
{
}
__NODL_SECCFG 0xb00000
{
}
UBOOT 0xb40000
{
}
BOOTIMG 0xbc0000
{
}
RECOVERY 0x11c0000
{
}
SEC_RO 0x17c0000
{
}
__NODL_MISC 0x1800000
{
}
LOGO 0x18c0000
{
}
__NODL_EXPDB 0x19c0000
{
}
__NODL_FAT 0x1bc0000
{
}
ANDROID 0x2fc0000
{
}
CACHE 0x11fc0000
{
}
USRDATA 0x126c0000
{
}
__NODL_BMTPOOL 0xFFFF0050
{
}
Click to expand...
Click to collapse
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
no one can help? .. I tried to readback boot & recovery from the working phone but after prepare files with mtk droid there is a error message:
Error :No UnGZip Recovery Images
no one can help me out with this issue
hey
chillbreak said:
no one can help me out with this issue
Click to expand...
Click to collapse
another brick... ahhhh ...
can you access download mode?
backups wont help in this situation i think. you need to reflash stock firmware via oddin
I think odin ist just for original samsung. The phone i talk about is a samsung s4 mini clone
S4 mini clone
chillbreak said:
Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
-scatter
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
Click to expand...
Click to collapse
same problem here..please help us
chillbreak said:
Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
-scatter
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
Click to expand...
Click to collapse
can you post the backup files. i assume it is in zip format
chillbreak said:
Hello @all,
First sorry for my bad english. I try explain my Problem as best as i can in english.
2 Days ago i got 2 pcs from this Phone: mixeshop , Mini s4 1:1 106$
I messed around with one of these phones with mtk droid tools for root / Backup. My hand was faster then my brain.. i have bricked the first phone after the question from droid tools to make cwm and i klicked OK by thequestion of write back boot.bin or similar.. So now my phone is in Bootloop. If i start the phone with vol + and powerbutton the phone starts into 3e recovery. I tried wipe data/factory reset & wipe cache partition but phone is still in bootloop (Samsung startlogo - blackscreen - samsung startlogo - blackscreen ....)
The backup before the bootloop isnt done without errors so i think i can forget do smth with the backup (with many errors)
The 2nd Phone is exact the same phone, same software, same lcd driver and work well (rooted with ADB script)
So what can i do to get the bootloop smartphone working? I´ve tried to make a backup from the working phone and flash this to the bootlooped one but i can´t make a backup because of errors. Maybe i stuck on this becaus i´m newbie. I do not want to be responsible for the fact that my daughter got a destroyed phone by dumb daddy to christmas
Informations about the bootloop stucking phone from backup:
- phone.info
-scatter
The Backup size is 293 MB
Prepare file for flashtool gave me an error.. cant remember exactly
Information about the second working phone with pictures:
block info:
I´m really grateful for any help get the bootlooped phone working. I´m new to this stuff with all the tools but i´m ready to learnand hope anyone can help me. shpuld i contact seller to give me stock rom? i really dont know what to do
Thank you
Click to expand...
Click to collapse
We have same phone and I have bricked the phone I kinda fix the phone but it doesnt have the correct base band. Can you send me your backup files maybe I can get the baseband from it so we both will have a working phone again.

Get method which calls another method (API)

Hi,
For example, we have API: Toast.show(params). I need to hook this API and get class/method name which uses this API (who calls it). Btw, how to check if method is hooked? I dont want re-hook things many times with the same hook.
pyler said:
Hi,
For example, we have API: Toast.show(params). I need to hook this API and get class/method name which uses this API (who calls it). Btw, how to check if method is hooked? I dont want re-hook things many times with the same hook.
Click to expand...
Click to collapse
I used a code like this to hook a method in a View:
Code:
public void handleLoadPackage(LoadPackageParam lpparam) throws Throwable {
XposedHelpers.findAndHookMethod(View.class,
"onTouchEvent",
MotionEvent.class,
new XC_MethodHook() {
@Override
protected void afterHookedMethod(MethodHookParam param)
throws Throwable {
//things...
}
}
});
}
So, in your case, you may use this with Toasts, for example, and then:
- if you want to obtain information for you, use XposedBridge.log
- if you want to use the informations in your module, you can use intents and broadcast receivers
It's an idea, let me know if it was what you were looking for :fingers-crossed:
Thank you for help
But.. I need to know who (method in app's code) calls it after hooking, not before.
pyler said:
Thank you for help
But.. I need to know who (method in app's code) calls it after hooking, not before.
Click to expand...
Click to collapse
Mm..I don't understand. You want to know what method in what app cals a method in an other app. But do you want this because you want to use this information IN your module (dinamically) or to develop your app?
Sent from my Vodafone 875
In the module.
pyler said:
In the module.
Click to expand...
Click to collapse
So, you want to obtain the name of the method which called the method you are hooking... Am I right?
Is the method an instance method?
Sent from my Vodafone 875
Exactly. Yes.
pyler said:
Exactly. Yes.
Click to expand...
Click to collapse
I think this information is normally held in the call stack but I dont know how to get that information from within the hook.
Haven't used it but
StackTraceElement has getClassName(), getFileName(), getLineNumber() and getMethodName().

Reset SELinux to Enforcing after installing magisk module

I'm running lineageos 17.1 and was selinux enforcing, that is until I flashed this mod for Gcam to enable the wide lens. I'm trying to get netflix to work in widevine L1 and was seeing some promising results in enforcing mode, (the modded apk I previously used on a verizon stock rom now only plays audio, no video), but after flashing that aux camera enabler (and uninstalling it) I cant get selinux back to enforcing. I've tried "setenforce enforcing" but after reboot "getenforcing" returns "Permissive".
I did some research on selinux and I saw some concerns that, even if I did get enforcing reset, the policies changed by the aux mod might cause issues if not reversed. These are the policy statements contained in the aforementioned mod:
Code:
allow { untrusted_app } persist_camera_prop file { read open getattr map }
allow { untrusted_app } vendor_default_prop file { map }
allow { untrusted_app } priv_app_tmpfs fil { read }
allow { untrusted_app } rootfs file { read getattr open }
allow { untrusted_app } vendor_camera_prop file { read open getattr map }
allow { system_server } vendor_camera_prop file { read open getattr map }
allow { hal_camera_default } default_prop file { read open getattr map }
allow { untrusted_app_25 } vendor_camera_prop file { read open getattr map }
allow { system_server } vendor_default_prop file { read open getattr map }
allow { platform_app } vendor_default_prop file { read open getattr map }
Any ideas where I should go from here? I realize wiping and restarting is probably the simplest solution, but my dumb ass didn't make a backup before installing the aux mod, and I would really like to avoid spending another weekend setting up my phone again.
Stuckurface said:
I'm running lineageos 17.1 and was selinux enforcing, that is until I flashed this mod for Gcam to enable the wide lens. I'm trying to get netflix to work in widevine L1 and was seeing some promising results in enforcing mode, (the modded apk I previously used on a verizon stock rom now only plays audio, no video), but after flashing that aux camera enabler (and uninstalling it) I cant get selinux back to enforcing. I've tried "setenforce enforcing" but after reboot "getenforcing" returns "Permissive".
I did some research on selinux and I saw some concerns that, even if I did get enforcing reset, the policies changed by the aux mod might cause issues if not reversed. These are the policy statements contained in the aforementioned mod:
Code:
allow { untrusted_app } persist_camera_prop file { read open getattr map }
allow { untrusted_app } vendor_default_prop file { map }
allow { untrusted_app } priv_app_tmpfs fil { read }
allow { untrusted_app } rootfs file { read getattr open }
allow { untrusted_app } vendor_camera_prop file { read open getattr map }
allow { system_server } vendor_camera_prop file { read open getattr map }
allow { hal_camera_default } default_prop file { read open getattr map }
allow { untrusted_app_25 } vendor_camera_prop file { read open getattr map }
allow { system_server } vendor_default_prop file { read open getattr map }
allow { platform_app } vendor_default_prop file { read open getattr map }
Any ideas where I should go from here? I realize wiping and restarting is probably the simplest solution, but my dumb ass didn't make a backup before installing the aux mod, and I would really like to avoid spending another weekend setting up my phone again.
Click to expand...
Click to collapse
All Android 10 AOSP ROMs are supposed to be run on permissive and are permissive by default.
So you were probably never on selinux enforcing
tech_infinity said:
All Android 10 AOSP ROMs are supposed to be run on permissive and are permissive by default.
So you were probably never on selinux enforcing
Click to expand...
Click to collapse
Typically, yes, but I suppose this one (lineage 17) is enforcing by default:
https://forum.xda-developers.com/lg-v30/development/rom-lineageos-16-0-lineageos-17-0-wip-t4042333
Previously, I showed as enforcing under the "Trust" page (current picture attached for context). Furthermore, drm info and Netflix, previous to flashing that aux mod, showed my widevine status as L1, both of which now show L3.
Also, I went ahead and tried to use the kernel se policy patcher mentioned in the thread above to set to enforcing, but it just bootloops until I flash again and set back to permissive. I'm guessing that's due to the policies set by that aux mod, but idk for certain.
Oh well, even if I did get selinux enforcing again, it's unlikely that I could get Netflix to work in L1 ¯\_(ツ)_/¯
Stuckurface said:
Typically, yes, but I suppose this one (lineage 17) is enforcing by default:
https://forum.xda-developers.com/lg-v30/development/rom-lineageos-16-0-lineageos-17-0-wip-t4042333
Previously, I showed as enforcing under the "Trust" page (current picture attached for context). Furthermore, drm info and Netflix, previous to flashing that aux mod, showed my widevine status as L1, both of which now show L3.
Also, I went ahead and tried to use the kernel se policy patcher mentioned in the thread above to set to enforcing, but it just bootloops until I flash again and set back to permissive. I'm guessing that's due to the policies set by that aux mod, but idk for certain.
Oh well, even if I did get selinux enforcing again, it's unlikely that I could get Netflix to work in L1 ¯\_(ツ)_/¯
Click to expand...
Click to collapse
Nope. ALL android 10 ROMs are permissive including this one.
you're getting bootloops because the ROM isn't made to be run on enforcing.
Also the latest build had some issues with Netflix, might wanna try a different rom for netflix to work
Stuckurface said:
I'm running lineageos 17.1 and was selinux enforcing, that is until I flashed this mod for Gcam to enable the wide lens. I'm trying to get netflix to work in widevine L1 and was seeing some promising results in enforcing mode, (the modded apk I previously used on a verizon stock rom now only plays audio, no video), but after flashing that aux camera enabler (and uninstalling it) I cant get selinux back to enforcing. I've tried "setenforce enforcing" but after reboot "getenforcing" returns "Permissive".
I did some research on selinux and I saw some concerns that, even if I did get enforcing reset, the policies changed by the aux mod might cause issues if not reversed. These are the policy statements contained in the aforementioned mod:
Code:
allow { untrusted_app } persist_camera_prop file { read open getattr map }
allow { untrusted_app } vendor_default_prop file { map }
allow { untrusted_app } priv_app_tmpfs fil { read }
allow { untrusted_app } rootfs file { read getattr open }
allow { untrusted_app } vendor_camera_prop file { read open getattr map }
allow { system_server } vendor_camera_prop file { read open getattr map }
allow { hal_camera_default } default_prop file { read open getattr map }
allow { untrusted_app_25 } vendor_camera_prop file { read open getattr map }
allow { system_server } vendor_default_prop file { read open getattr map }
allow { platform_app } vendor_default_prop file { read open getattr map }
Any ideas where I should go from here? I realize wiping and restarting is probably the simplest solution, but my dumb ass didn't make a backup before installing the aux mod, and I would really like to avoid spending another weekend setting up my phone again.
Click to expand...
Click to collapse
Have you found a complete solution to the problem?
Redy321 said:
Have you found a complete solution to the problem?
Click to expand...
Click to collapse
If you're talking about "problem" of ROM being permissive then no. Because the Devs will have to make the ROMs boot with Enforcing, nothing the user can do here.
And if you're talking about Netflix, The latest build had some issues with Netflix, might wanna try a different rom or build for netflix to work
Redy321 said:
Have you found a complete solution to the problem?
Click to expand...
Click to collapse
Technically, yes. I bought a Pixel 5.
With the death of custom ROMS looming on all but at&t, and with all the time I spend trying to get pixel exclusive features working on my phone, I thought it was time to join cstark on pixel.
In unrelated news, I'm getting ready to sell a 2yo carrier and bootloader unlocked us998 (good condition, it lived its life in an OtterBox). I'll was planning on selling it on ebay after resetting to stock and re-locking the bootloader (because of the "scary" warning on boot), but if someone on the forum is interested, DM me for details.
tech_infinity said:
If you're talking about "problem" of ROM being permissive then no. Because the Devs will have to make the ROMs boot with Enforcing, nothing the user can do here.
And if you're talking about Netflix, The latest build had some issues with Netflix, might wanna try a different rom or build for netflix to work
Click to expand...
Click to collapse
Yeah, DRM content on the whole is a problem for the lineage 17.1 ROM (not just Netflix, but also HBO). Strangely, it reports itself as L1, but unless you can force widevine to drop to L3, perhaps through installing some magisk module like I did (which will result in SD quality), video playback won't work.

Categories

Resources