Inspectifier Wrectifier

Hey, da C-Dev site in the first post be out, for good, yo. New link: https://jenkins.adamoutler.com/job/Customize%20BSP/build?delay=0sec

Permanent

My conclusion:

 

we cannot change the filesystem with script on the 5200... even if I insert in the script, just before a "cat", this command:

mount -o remount,rw /system

I see in my output.txt:

mount: Read-only file system

my id is root, I checked:

uid=0(root) gid=0(root)

 

and here is the before first remount:

/dev/block/mmcblk0p7 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0

and after:

/dev/block/mmcblk0p7 /system ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0

 

So something (kernel?) is preventing me from modifying the /system partition.

 

Anyone with a x200 can change files in lib or etc?!?

Yo dawg, what's da Android version?

I see barrier=1, dat might be preventing write, but if dat filesystem be power-on write protected, u be in fo' problems.

 

If I wuz u, I'd remove dat sdcard and 'tempt a manual decryption, den mount an write with a *nix box. After yous got write access, further testing will be required to determine if it's just temp write protect, boot write protect or perma write protect. Could be all three, yo!

Yo dawgs, da CASUAL-Dev site keeps going down. I asked my boy Adam Outler to host it somewhere else and he just erected the web service "CustomizeBSP" over at jenkins.adamoutler.com.  Da job is right here fo shizzle: https://jenkins.adamoutler.com/job/Customize%20BSP/

It don't need to be created. A mod just needs to figure out what derailed this topic and split it into a new thread. The how-to would be a great place to split.

This don't belong here. Someone needs to start a maps thread, a mod needs to prune this one, and link it to the first post. I subscribe to this thread to find out the latest in development, not to find out the status of maps in various people's units, yo.

No progress at all, we need someone with pionee head unit on the table (preferably with UART converter connected to device's yellow connector) who can do a lot of tests.

Dawg, what we need is a way to bring these bad mamajamas back to life when they get a case of the bricks. Ya'll know what happens when you set da snapshot BSP item, yo.

I have test mode on a usb, and can see the options on boot up. Can someone lead me through the steps to see the password please.

 

Chris

yo, dat password is in da BSP yo. You can use the Customize BSP job o'er at C-Dev. https://jenkins.casual-dev.com/job/Customize%20BSP/build?delay=0sec

 

To remove the password, use test key 3. It's a bit tricky tho. Yous best burn a new SD from one of the images floating 'round, yo.

That's some whack shizzz, chmod 777 on some data files is excessive use of permissions. While it's not "important" in a closed system, as a matter of practice; Thou shall not create world writable files, yo.

Ok i'll try to upload. So i shouldn't worry about this "update failed" message?

It's all good, yo.   Bad bits from the manufacturer means variations in the size of the card.  You just lost the last few bytes or megs. 

Hmm the only volume showing under alsa-mixer is "Guide DAC Mute Set"

You rooted? If so, what brand and what ALSAMixer app?

Dat sounds like an AA device-side volume issue. The unit ain't commanding d volume to raise up and touch the roof. Whatchawanna do is, on a rooted device, use ALSAMixer, find the proper volume, and raise it. There are about 100 volumes for Android, yo.

For x000 models bypass for OK screen is much simpler: just add sys.pioneer.misc.navi_pl_cation=sys.pioneer.navi_pl_on to build.prop I think something like this is available for x100 series too.

 

I tried that, homie. It didn't work. The new value is called sys.pioneer.misc.smartphone_caution (they fixed that cation jive). I think the way forward is to snap a new snapshot, reenable Warp!, and then party on.

Waddup dawgz? I made this Xposed module for Android that allows you to bypass that stupid OK screen on 8100 units.

https://github.com/InspectifierWrectifier/AVICOkKillerXposedModule/tree/master/app

 

The installation is complicated.

Disable Warp!

Install a custom launcher like Nova Launcher into /system/app

Install the proper Android version of Xposed to /system/framework from XDA-Developers.

Activate the module.

Remove the launcher.

 

This module activates when the OK window is created. When the system commands it to show, it parses the UI for the message, finds the button, then activates the onClick() method. It effectively presses the button before the message is shown.

 

 

We need to figure out how to reactivate Warp with a custom system image, yo!

Sounds like an improperly configured watchdog in the bootloader.

New 8100/8000 firmware is available yo!

http://www.pioneerelectronics.com/PUSA/Support/Downloads

Great work guys!  This is some awesome stuff.  I'm working on some things in my spare time to contribute.