hi people. I love my nexus 4 but lets face it they was pretty stingy on the memory side of things. does anyone have the schematics of the nexus 4? im thinking of the idea to take the phone apart and replace the internal memory with a bigger memory. or if that's not possible then maybe branching another memory to it? need some tech minds behind this so love to hear peoples input
mikeinessex said:
hi people. I love my nexus 4 but lets face it they was pretty stingy on the memory side of things. does anyone have the schematics of the nexus 4? im thinking of the idea to take the phone apart and replace the internal memory with a bigger memory. or if that's not possible then maybe branching another memory to it? need some tech minds behind this so love to hear peoples input
Click to expand...
Click to collapse
Use cloud storage. Clean up junk files and apps you don't use.
If you really want to mess with your phone that's your business. But it's not simply a matter of actually having a removable flash memory chip in your phone that you can replace.
You can easily Google the parts of your phone. There's a nice breakdown with pictures of the internals on ifixit.com
I have a crap tonne of stuff on my phone like roms, mods, themes, fonts etc etc. A whole bunch of stuff and still don't come close to filling my 16 gigs.
I have about 120 gigs of free cloud storage that I use
sent from my Nexus 4®
Of course
Enviado desde mi SGH-I997 usando Tapatalk
eminembdg said:
Use cloud storage. Clean up junk files and apps you don't use.
If you really want to mess with your phone that's your business. But it's not simply a matter of actually having a removable flash memory chip in your phone that you can replace.
You can easily Google the parts of your phone. There's a nice breakdown with pictures of the internals on ifixit.com
I have a crap tonne of stuff on my phone like roms, mods, themes, fonts etc etc. A whole bunch of stuff and still don't come close to filling my 16 gigs.
I have about 120 gigs of free cloud storage that I use
sent from my Nexus 4®
Click to expand...
Click to collapse
cloud isn't a option. its based on data transfer and it cost to have it aswell. I understand it wil have to be desoldered and new one soldered on. that's not the problem an engineer. what I need to know is if I did do that then would the phone still function after installing a new rom. or even function to install a new rom. when Samsung started with smartphones they advertised as internal sd. not internal memory. which made me believe that we have infact got a memory on the board plus a soldered on type sd card inside in which case it shouldn't have any effect being changed?
mikeinessex said:
if u aint got anything useful to say then don't say anything at all
Click to expand...
Click to collapse
Challenge accepted Mr.Engineer.
Your first step is understanding flashing a new ROM has nothing to do with installed internal storage. This happens at a much lower level, you'd need a flash programmer that can read and write our specific N4 storage chip to pull the firmware off the old storage chip and write it to the new one...or know someone at LG with all of the hardware and software to program it. So your first bit of work would be finding the chip part number and finding its data sheets.
Also assuming you have the equipment to even desolder and solder a chip at that level.
Or you could just wait a month for a 32gb N4.
Sent from my Nexus 4 using xda premium
I am not a tech so don't judge, but if you want to do something like this first find the most similar device and in this case I would suggest the opt us g e975 (it has 32 GB storage)
Sent from my Nexus 4 using xda app-developers app
I'm a big fan of the S5 because it is the only phone I'm aware of with both a removable battery and wireless charging (with Samsung's back cover accessory), but it seems like its greatest weakness is the lack of RAM compared to newer phones. I've read that the RAM is soldered to the motherboard, but I'm curious if there are any "hardcore" users out there that have successfully upgraded the RAM chip in their phone?
Nerva said:
I'm a big fan of the S5 because it is the only phone I'm aware of with both.........
Click to expand...
Click to collapse
This is not possible...
The Internal Memory is Micro-Soldered but, the Android Software is specially designed for the Memory it currently has.
The software specific to the Internal Memory will always remain as part of the hardware within the system itself.
Even Custom Firmware doesn't touch this. The Firmware ROM just reads/detects what's hard coded for its installation to proceed.
It's hard to explain but, I had done my best... LMAO!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
There was this case of some chinese guy who managed to increase his nexus 5X ram by making some serious modifications
https://www.xda-developers.com/nexus-5x-hardware-modded-to-upgrade-ram-from-2gb-to-4gb/
As you may have noticed, its a fairly difficult process which requires profesional help in order to sucess.
If you're on a roadtrip to China maybe you could find someone capable of such a feat, if that's so, please post the results!
It had been done ages ago and with hardware with much courser structures, like the original Apple Mac with standard DIL DRAMS. Basically a second dram must be soldered upon another plus a few wire wrap wires across the pcb. Atari used this method in the 520 STplus to double the original 520 ST's RAM. Not totally impossible on the S5, this.
Hi all,
If you want to greatly improve the way your head unit works, sounds and looks like - you've come to the right place!
Why install this?
With this package you will greatly improve:
Stability
Speed
User Interface
Sound tweaking options
Customization options
Following our previous Super MOD guide, we have now completed a new project, this time on a newer YT9216BJ head unit running the Android 6 API23 operating system (fake Android 8.1, 9.0 and 9.1).
If your head unit is Android 8 API 27 (fake Android 10 or 11), proceed to this guide instead.
This guide is for YT9216BJ units with 1 Gb RAM and 16Gb flash with no physical buttons*.
ON PHYSICAL BUTTONS: this software has only been tested on head units with no physical buttons (like volume) | Before making any changes, access the CAR SETTINGS -> FACTORY SETTINGS -> ENCODER SETTINGS on your head unit and take a screenshot of the current settings (see example below). After installing the package, go back to these settings and adjust them if needed. If that doesn't help and if you can't successfully re-calibrate the buttons after installing the firmware, restore your backup
{
"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"
}
Do not use this package if your unit is "HIFI" or has a separate radio chip installed (A or NXP series)
!! TAKE A PICTURE OF YOUR SYSTEM INFO AND KERNEL VERSION BEFORE DOING ANYTHING TO YOUR HEAD UNIT !!
Disclaimer
I do not create the software itself but rather use research and put together different mods and hacks into one package that includes very user-friendly step-by-step instructions on how to install it all. You will find the links to original posts in the instructions pdf's if credit is due. The software might include smaller changes made by me and has been fully tested in real units.
>>>This mod only works on units with screen resolution of 1024x600 px. It will not work on Tesla-style units<<<
The Software Package contains:
Custom Android 6 firmware for YT9216BJ
ROOT (SuperSU)
TWRP Recovery
Viper4Android / Viper4A / ViperFX
Custom UI (Car Launcher)
Custom Boot Animation
. . .
!! ALWAYS BACKUP YOUR UNIT BEFORE MAKING ANY CHANGES TO IT!!
DOWNLOAD #4
ExtremeMOD Software Package & Drivers - YT9216BJ
STEP-BY-STEP GUIDE (upgrading from working stock firmware):
DO NOT SKIP ANY STEPS, AND INSTALL EVERYTHING IN THE CORRECT ORDER. STEPS 5 AND 6 ARE MOST CRITICAL.
Proceed to download the software package for your unit and the drivers package in the same folder
It's highly recommended to do these upgrades with your unit connected on your desktop, rather than in the car. Video Guide
Install the Mediatek & ADB drivers on your Windows computer. Video Guide - use the same principle for ADB drivers.
Backup your current system by exporting a full memory dump. Video Guide
Import back your memory dump from step-5 to ensure it fully works. This is how.
Install the package. Separate instructions are included in every folder of the downloaded zip file. Follow them by the order.
IF THIS SOFTWARE PACKAGE HAS BRICKED YOUR HEAD UNIT AND YOU HAVE YOUR BACKUP AVAILABLE, follow the steps below:
DO NOT SKIP ANY STEPS, AND INSTALL EVERYTHING IN THE CORRECT ORDER.
It's highly recommended to do these upgrades with your unit connected on your desktop, rather than in the car. Follow this post on how to do that.
Install the Mediatek & ADB drivers on your Windows computer. Video Guide - use the same principle for ADB drivers - (download link is in the video description)
Watch this video on Test Point recovery
Import back your memory dump. This is how.
If successful - try to install the software package again or stay with your original one
IF THIS SOFTWARE PACKAGE HAS BRICKED YOUR HEAD UNIT AND YOU HAVE NO BACKUP AVAILABLE, follow the steps below:
Share the pictures of your System Info and Kernel in this thread and I'll try to help you
** IF YOU ARE UNABLE TO RESTORE YOUR UNIT, PLEASE CONSIDER DONATING IT TO US @ ExtremeMOD, SO WE CAN BUILD MORE MODS AND TUTORIALS---------------------------------------------------------
This post is being frequently updated and you'll find more guides and mods our forum signature---------------------------------------------------------
Thanks! And if this post is helpful to you please don't forget to "like" it.
Enjoy!
[V4A][VIPER4ANDROID][ViperFX][ROOT][TWRP][8227L][YT9216BJ]
Hello,
I want to use this guide for my head unit. But it says YT9216CJ, I have included pictures.
Also how do you connect this to a PC/laptop?
Highlites said:
Hello,
I want to use this guide for my head unit. But it says YT9216CJ, I have included pictures.
Also how do you connect this to a PC/laptop?
Click to expand...
Click to collapse
The easiest way is to buy a 12v 5A power adapter. Something like this. Then connect the RED (acc) and the YELLOW (B) cable to + (plus) and the black (ground) cable to - (minus).
That's good idea. I have many 12 volts adapters that I can use and strip them. I know that's unsafe and could potentially fry the unit.
I'm assuming a type a to type a cable is needed to connect it to a computer?
Highlites said:
That's good idea. I have many 12 volts adapters that I can use and strip them. I know that's unsafe and could potentially fry the unit.
I'm assuming a type a to type a cable is needed to connect it to a computer?
Click to expand...
Click to collapse
You will not fry the unit if you use at least 12V and max 14V adapter with a minimum amperage of 5A.
When you connect the cables, just put some electrical tape around the connections so they don't touch each other.
Yes you'll need a USB-A cable of maximum 90 cm long.
The next step would be to read the guides on how to install drivers in order to access the unit.
Highlites said:
Hello,
I want to use this guide for my head unit. But it says YT9216CJ, I have included pictures.
Also how do you connect this to a PC/laptop?
Click to expand...
Click to collapse
I would advise against using this mod on your unit as it does not support "HIFI" models. I am currently working on an Android 8 super mod and that includes everything. Stay tuned.
The new guide for Android 8 units is now available. It covers all Android 10 and 11 fakes.
Can my unit follow this guide or should I follow another One?
madsurfer1 said:
Can my unit follow this guide or should I follow another One?View attachment 5389371
Click to expand...
Click to collapse
I would probably recommend the Android 8 software package instead.
iceblue1980 said:
I would probably recommend the Android 8 software package instead.
Click to expand...
Click to collapse
thank you so much for your anwser
I only want root so I can enable multi-window, is it an easier to get root?
Thank you
madsurfer1 said:
thank you so much for your anwser
I only want root so I can enable multi-window, is it an easier to get root?
Thank you
Click to expand...
Click to collapse
The proper root for this unit requires modified firmware. You can of course try without it but chances are you'll either brick your unit or in "best" case get unstable root.
Just gotta say I urgently wave anyone off of this project as it is.
Most importantly this line of tablets sucks. The screen sucks, the specs suck, the performance sucks, it's max 2g crap that'll still suck after it's hacked, the screen glare is laughable/day-unusable, it crashes, stops responding to physical buttons randomly, and it has no amp which will throw unsuspecting people. The audio it does provide is a total diarrhea blast through a cheap rca canbus adapter with ground interference for miles so again, you better have a rated amp and isolater for your speakers and know audio wiring. Also hey the software is clearly disingenuous chinese spycrap that would probably try to kindnap your child if it could, to the point that I don't know if I'd even trust root hunting to find all the lies.
Past that I can't endorse this tutorial either I'm afraid. Look at the failure/success ratio in this thread already and add mine to the failure pile.
Modders are going to get into this and dl a folder sequence that looks step by step for each but then opens up into different subinstructions requiring knowledge bases you didn't know you needed until you're in it. You're gonna be messing with device manager and secure boot modes in windows and custom power wiring outside the car just to get going. To deal with that you're going to go down more forum nightmares mid way, stuff that should all be on a unified 1,2,3,4 instruction set in the main post imo. I'm capable and I'd call this written procedure luring unsuspecting people into bad times.
I had to bail on this project some weeks ago after that "boot into secure mode in windows to install temporary unsigned USB drivers (which can revert and fail while you're working on the project with so much as a windows update) just to get it to communicate" process. Then of course it never did communicate, step by step trying across 3 devices in specifiied acc wiring positions and every other attempt under the sun. This is of course after you've and soldered up this failure of a unit to a power source to hack it outside the car which is ridiculous to need to do in itself, and a dozen more things most people wouldn't sign up for if it were made a bit more clear.
I'd be willing factory reboot and get that guy from the android 8 thread the clean yt9216bj image except I don't want to waste day 4 screwing with the non working ass-up usb/windows head unit software.
The product itself is obviously not worth it and...rant but yeah this tutorial suffers from the super common XDA problem where the author is super tech skilled!...but just too in their own head to relate 1:1 what regular people need to know as if visitors were working along side them all year. I respect all the work that went in but imo this as presented seems to be tanking people's efforts and stress them out. It'd be more worth it to risk the brick if this were a hack that you shove in the usb and it goes. It's very not that.
At the time of writing I suggest saving yourself xda therapy costs, spend on a cruthfield screen that actually works, is nice, you can see in the daytime, you can mod into an enclosure yourself, and will probably have a way easier hack with much better function before and very much after a hack. I'm probably going to shove an m80 into this aptly named BJ unit and explode it like the chinese firework trash it is.
sylcat said:
Just gotta say I urgently wave anyone off of this project as it is.
Most importantly this line of tablets sucks. The screen sucks, the specs suck, the performance sucks, it's max 2g crap that'll still suck after it's hacked, the screen glare is laughable/day-unusable, it crashes, stops responding to physical buttons randomly, and it has no amp which will throw unsuspecting people. The audio it does provide is a total diarrhea blast through a cheap rca canbus adapter with ground interference for miles so again, you better have a rated amp and isolater for your speakers and know audio wiring. Also hey the software is clearly disingenuous chinese spycrap that would probably try to kindnap your child if it could, to the point that I don't know if I'd even trust root hunting to find all the lies.
Past that I can't endorse this tutorial either I'm afraid. Look at the failure/success ratio in this thread already and add mine to the failure pile.
Modders are going to get into this and dl a folder sequence that looks step by step for each but then opens up into different subinstructions requiring knowledge bases you didn't know you needed until you're in it. You're gonna be messing with device manager and secure boot modes in windows and custom power wiring outside the car just to get going. To deal with that you're going to go down more forum nightmares mid way, stuff that should all be on a unified 1,2,3,4 instruction set in the main post imo. I'm capable and I'd call this written procedure luring unsuspecting people into bad times.
I had to bail on this project some weeks ago after that "boot into secure mode in windows to install temporary unsigned USB drivers (which can revert and fail while you're working on the project with so much as a windows update) just to get it to communicate" process. Then of course it never did communicate, step by step trying across 3 devices in specifiied acc wiring positions and every other attempt under the sun. This is of course after you've and soldered up this failure of a unit to a power source to hack it outside the car which is ridiculous to need to do in itself, and a dozen more things most people wouldn't sign up for if it were made a bit more clear.
I'd be willing factory reboot and get that guy from the android 8 thread the clean yt9216bj image except I don't want to waste day 4 screwing with the non working ass-up usb/windows head unit software.
The product itself is obviously not worth it and...rant but yeah this tutorial suffers from the super common XDA problem where the author is super tech skilled!...but just too in their own head to relate 1:1 what regular people need to know as if visitors were working along side them all year. I respect all the work that went in but imo this as presented seems to be tanking people's efforts and stress them out. It'd be more worth it to risk the brick if this were a hack that you shove in the usb and it goes. It's very not that.
At the time of writing I suggest saving yourself xda therapy costs, spend on a cruthfield screen that actually works, is nice, you can see in the daytime, you can mod into an enclosure yourself, and will probably have a way easier hack with much better function before and very much after a hack. I'm probably going to shove an m80 into this aptly named BJ unit and explode it like the chinese firework trash it is.
Click to expand...
Click to collapse
First of all, really sorry to hear you had such an unfortunate experience.
Now let me add a few points to your feedback.
1. You need an understanding of both PC computers and Android devices to attempt this. Would you try to repair your car with zero knowledge or experience?
It's also a good practice to look through all the steps and tutorials before deciding whether this is something you wish to attempt.
2. The reason I create these guides is to give the users one-stop software solution in one thread. I couldn't find similar guides here.
3. Software packages are cleaned from the bugs and issues you would normally experience in these units and overall improvements are considerable. If you check the video in my signature, tell me - does this seem like a slow unit? And it's only 1Gb RAM one.
4. These software packages perform even better with appropriate hardware mods. Especially the sound quality. You can check out this website for more info.
5. Users who experience issues post here. But this package alone has over 300 downloads. This indicates high success ratio.
I also help individual users by PM.
Thanks again for your feedback
iceblue1980 said:
First of all, really sorry to hear you had such an unfortunate experience.
Now let me add a few points to your feedback.
1. You need an understanding of both PC computers and Android devices to attempt this. Would you try to repair your car with zero knowledge or experience?
It's also a good practice to look through all the steps and tutorials before deciding whether this is something you wish to attempt.
2. The reason I create these guides is to give the users one-stop software solution in one thread. I couldn't find similar guides here.
3. Software packages are cleaned from the bugs and issues you would normally experience in these units and overall improvements are considerable. If you check the video in my signature, tell me - does this seem like a slow unit? And it's only 1Gb RAM one.
4. These software packages perform even better with appropriate hardware mods. Especially the sound quality. You can check out this website for more info.
5. Users who experience issues post here. But this package alone has over 300 downloads. This indicates high success ratio.
I also help individual users by PM.
Thanks again for your feedback
Click to expand...
Click to collapse
Well, let's go point for point a little bit.
1.) Yeah but when was that in question unless you're mayyybe trying to sass a bit? My personal experience is plenty for this, enough to multimeter my harness pin by pin, design a custom wire harness with 3d printed parts, run debugs with my obd, reconnect lane cams, write my own android apps if I feel like and on and on. My point is to warn to readers that these instructions are pretty deceptive about how involved it is skillwise and just needs a simplification redo. My problems might have been isolated hardware failure, I still don't know after tons of debugging.
2.) Cool, noble, etc etc, you're very nice for doing it. I just want people here to write clearer I guess. Sorry I landed on your project to express it. Years of XDA and it's so much life lost to information gaps / gotcha tutorials. That gets pointed out and it's usually ego mania. Take some crit, XDA posters could really learn what a tutorial format that communicates to most everyone should look like instead of assuming their skill at that is also great thus providing good intented tuts that cause uh....pain.
3.) It'd be fun to test myself but it doesn't work. Looks functional sure. Speedy compared to current gen anything after esp hacks? Nawwww. If you're cool with it chugging after one or two background process I get it. Waze eats enough. While it won't be everyone, if you use a screen with more expectation I again advise against this hardware.
4.) Again for people considering this, how much extra hardware and wiring do you want to buy and staple to a piece of crap and shove behind the head unit to make it almost not suck? How many 3rd party peripherals do you want back there doing one job? Are the manhours you'll spend trying to reign this unpolishable turd in monetarily marginally close to worth it? Appreciative to the hack effort if you're stuck with this screen. If you haven't bought it friggen doooon't.
5.) I argue since silence is not success confirmation it could just as easily indicate people downloading it, the process failing, them not wanting to continue with a newly recognized tragedy of a device, and possibly just dying of dysentary right there while reading the instructions which are in 8 different folders
sylcat said:
Well, let's go point for point a little bit.
1.) Yeah but when was that in question unless you're mayyybe trying to sass a bit? My personal experience is plenty for this, enough to multimeter my harness pin by pin, design a custom wire harness with 3d printed parts, run debugs with my obd, reconnect lane cams, write my own android apps if I feel like and on and on. My point is to warn to readers that these instructions are pretty deceptive about how involved it is skillwise and just needs a simplification redo. My problems might have been isolated hardware failure, I still don't know after tons of debugging.
2.) Cool, noble, etc etc, you're very nice for doing it. I just want people here to write clearer I guess. Sorry I landed on your project to express it. Years of XDA and it's so much life lost to information gaps / gotcha tutorials. That gets pointed out and it's usually ego mania. Take some crit, XDA posters could really learn what a tutorial format that communicates to most everyone should look like instead of assuming their skill at that is also great thus providing good intented tuts that cause uh....pain.
3.) It'd be fun to test myself but it doesn't work. Looks functional sure. Speedy compared to current gen anything after esp hacks? Nawwww. If you're cool with it chugging after one or two background process I get it. Waze eats enough. While it won't be everyone, if you use a screen with more expectation I again advise against this hardware.
4.) Again for people considering this, how much extra hardware and wiring do you want to buy and staple to a piece of crap and shove behind the head unit to make it almost not suck? How many 3rd party peripherals do you want back there doing one job? Are the manhours you'll spend trying to reign this unpolishable turd in monetarily marginally close to worth it? Appreciative to the hack effort if you're stuck with this screen. If you haven't bought it friggen doooon't.
5.) I argue since silence is not success confirmation it could just as easily indicate people downloading it, the process failing, them not wanting to continue with a newly recognized tragedy of a device, and possibly just dying of dysentary right there while reading the instructions which are in 8 different folders
Click to expand...
Click to collapse
1. Why not explain what were the issues you encountered?
2. It has taken me a couple of years to learn how to properly work with these units. I tried my best to write as easy to follow guide as I can. I'm grateful for feedback as it helps me improve these guides. They are continously revised. I'm not paid to do this and it is a fairly time consuming undertaking.
3. Current gen Androids are an unfair competition to hacked and re-hacked Android 6 or 8. On the other hand, you can't do much with anything above API 27. Forget about rooting, Viper and TWRP. Also be prepared to pay hundreds of dollars for these units. People who buy Mediatek head units, normally can't spend such money but still deserve great results. This is why I share these mods packages. And it's completely free. All it takes is time and patience.
4. People here and on similar forums are many times interested in making improvements without spending loads of cash and might already have some basic equipment and skills. I haven't posted any hardware mods guides yet but I'm going to.
There are no 3rd party peripherals required. Most of the spare parts can be found in old computers. We at Extrememod.co.uk use premium spare parts as we sell these units fully modified (for charity, no profits) but it's not a requirement.
5. All I can do is to encourage users to post here so I can help if needed.
Cheers
I spent a few days as I said fighting it after it all fell down during the USB unsigned driver portion of the project. Across 3 pcs, driver reinstalls, pin verifications, living in device manager, 12 tech forums tabs open and everything else under the sun the software just refuses to communicate with the screen in any way.
I don't remember everything, I'll get you verbose logs if I ever touch this project again but don't hold your breath. I'm surely bitter over wasted time but in general the nature of in car entertainment cheapouts that need these hacks to even start limping have caused me to reevaluate life itself and what not to waste it on so I'm just pulling the trigger on a Model 3 finally. Screen problem solved for me I guess
My suggestion for readers considering buying remains to run far away if you're not already stuck with the hardware. But if you are and you have infinite patience trying to buff it up then I guess keep harassing poor iceblue here until your hack works and weeew I do wish you all luck!
sylcat said:
I spent a few days as I said fighting it after it all fell down during the USB unsigned driver portion of the project. Across 3 pcs, driver reinstalls, pin verifications, living in device manager, 12 tech forums tabs open and everything else under the sun the software just refuses to communicate with the screen in any way.
I don't remember everything, I'll get you verbose logs if I ever touch this project again but don't hold your breath. I'm surely bitter over wasted time but in general the nature of in car entertainment cheapouts that need these hacks to even start limping have caused me to reevaluate life itself and what not to waste it on so I'm just pulling the trigger on a Model 3 finally. Screen problem solved for me I guess
My suggestion for readers considering buying remains to run far away if you're not already stuck with the hardware. But if you are and you have infinite patience trying to buff it up then I guess keep harassing poor iceblue here until your hack works and weeew I do wish you all luck!
Click to expand...
Click to collapse
If you are unable to restore your unit, I can have a look at it if you can post me the motherboard. I live in UK. If that's not an option, why not donate it rather than throwing it in the bin? I can arrange pickup if it's within reasonable postage fees.
I'd donate but the math will never work out. It's installed in the honda which I'm selling already, so it'd take pulling it out which us my time+shipping hassle from the states. If I pull it out it's easily worth the $250 cost of the unit in therapy to see it *explode* and I'm not joking so I doubt you're gonna front that too. :v I mean also I don't really want anything about these boards perpetuated. If the next buyer doesn't want it in there it's getting smashed. These kinds of posts I make again to save people time on caaaancerous base products.
sylcat said:
I'd donate but the math will never work out. It's installed in the honda which I'm selling already, so it'd take pulling it out which us my time+shipping hassle from the states. If I pull it out it's easily worth the $250 cost of the unit in therapy to see it *explode* and I'm not joking so I doubt you're gonna front that too. :v I mean also I don't really want anything about these boards perpetuated. If the next buyer doesn't want it in there it's getting smashed. These kinds of posts I make again to save people time on caaaancerous base products.
Click to expand...
Click to collapse
I understand. I actually care about people succeeding with these mods. You can clearly see how much time I'm putting into these guides and helping people with any issues that come up.
I even offer repairing boards, for free. Donation is a last resort if someone wants to throw their head unit into the bin.
Any modification, as it's essentially a hack - means you're taking a risk. But with proper backup, the risk of ruining your head unit is minimal, as you can always restore it back to what it was.
Again, I'm sorry it didn't work out for you but the issue isn't with the software nor the guides as the success rates are overwhelmingly high, judging from the feedback I receive here and on my website.
@iceblue1980
Do you know of a way to get live wallpapers working?