Develop Bugs

[23/Jan/2012][NST][1.1] Current book cover screensaver + custom shutdown image

UPDATE 23/01/2012:
Added support for content on sd-card (BETA). Further details on this post.
UPDATE 03/01/2012:
WARNING: some users reported troubles starting custom launcher and application after installation of this mod; a full backup before installation of this mod is strongly suggested!
UPDATE 27/12/2011:
Added custom shutdwown image mod.
UPDATE 18/12/2011:
Complete refactoring of Hack; now it's based on firmware 1.1.
Older firmware (1.0 and 1.0.1 no more supported).
Hi all,
i made a modification on Nook Simple Touch to use, as screensaver, the cover of the current reading book (i.e. the last book opened in the stock reader application).
Of course, it's necessary that the book has a cover (i.e. the cover is shown in the library application); on contrary, the default screensaver will be displayed (i.e. "authors").
Usage:
to activate the "current reading book cover screensaver: go to settings / screen / screensaver and select the new option, called "Current reading book image";
to set the custom shutdown image: copy an image called "shutdown.png" inside folder "screensavers" of Nook internal drive, when the Nook is connected with USB; the image "shutdownLowBattery.png" is displayed in case the Nook turns off due to low battery.
If the images are not found, the default ones are used.
Thanks to:
XorZone for it's really useful modification "Edit n/reading now/side btns/RecentApps+ActivityPicker+ForceOrient";
WARNING: as usual, modifying system files you may risk to brick your Nook, unless you know what you are doing. You are strongly advised to make a full backup before proceeding. I don't take any responsibility if you decide to apply this mod.
WARNING-2: this modification could only be appied on firmware 1.1 .
Installation:
download and unpack one of the attached files:
screensaver-hack-110-xor.zip in case you are using XorZone mod to improve button mappings etc..;
screensaver-hack-110.zip otherwise (i.e.: you are just using plain firmware from B&N);
verify that the archive you downloaded contains these 4 files:
android.policy.jar [needed only for "current book cover screensaver"];
services.jar [needed only for "current book cover screensaver"];
Settings.apk [needed only for "current book cover screensaver"];
framework.jar [needed only for "custom shutdown image"];
please consider that if you want to apply just one of the 2 modification included, you may limit the execution of next steps just to the relevant files as listed above;
(optional) make backup of original files, in case of problems with the modded ones (in case you revert to original files, remember to set the permissions of the original files, and delete the dalvik-cache)
remount system partition r/w
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
copy the downloaded files to Nook
Code:
adb push android.policy.jar /system/framework
adb push services.jar /system/framework
adb push framework.jar /system/framework
adb push Settings.apk /system/app
change the permission
Code:
adb shell chmod 644 /system/framework/android.policy.jar
adb shell chmod 644 /system/framework/services.jar
adb shell chmod 644 /system/framework/framework.jar
adb shell chmod 644 /system/app/Settings.apk
delete dalvik-cache
Code:
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
adb shell rm /data/dalvik-cache/[email protected]@[email protected]
delete packages.xml [needed only for "current book cover screensaver"] (it will be regenerated at next boot; optionally make a backup also of this file, in case of troubles)
Code:
adb shell rm /data/system/packages.xml
(optional) due to packages.xml regeneration, it's possible (in my case it occurred) that now when you turn on the NST, the demo mode starts automatically; in any case, it's turned off as soon as you click any button, so it doesn't make any harm; but, if you want, you can simply delete the apk to get rid of it:
Code:
adb shell rm /system/app/DemoMode.apk
reboot your Nook
Code:
adb reboot
Thanks to user persichini, it's also available an alternative installation guide using RootExplorer directly from Nook (i.e. no need of ADB commands): in any case, please take into account that the same considerations about the relevance of modified files (in case you only want to install either "current book cover screensaver" or "custom shutdown image").
In case of issue, please provide the logcat log. You can redirect the log to a file (logcat.log) with the ADB command (launch it when Nook is booting to have all useful info):
Code:
adb logcat > logcat.log
Hit Ctrl+C to stop logging.
Hope you will enjoy it!
PS: as soon as i will have time, i will post sources, so you can build the mod by yourself (meanwhile, if you need them, just decompile and compare to original files of firmware 1.1 )
PS2: attached to this message you can also find 2 nice possible shutdown / lowBattery images.

I know you said that it's not compatible with v1.0.1, but is there a reason why you don't have v1.0.1 firmware on your nook? It's been out since July/August and works just as (un)well with the rooting scripts out there.

nickveldrin said:
I know you said that it's not compatible with v1.0.1, but is there a reason why you don't have v1.0.1 firmware on your nook? It's been out since July/August and works just as (un)well with the rooting scripts out there.
Click to expand...
Click to collapse
mostly, just because i'm lazy! and on changelog it's just mentioned that 1.0.1 hav some improvement on wifi, that i don't use at all.
In any case, this doesn't matter for my mod, since i downloaded the manual upgrade file from B&N, so that it would be easy to apply the mod to 1.0.1. I just need to find some time. I hope i will do it during the week-end.
Regards

traycold said:
mostly, just because i'm lazy! and on changelog it's just mentioned that 1.0.1 hav some improvement on wifi, that i don't use at all.
In any case, this doesn't matter for my mod, since i downloaded the manual upgrade file from B&N, so that it would be easy to apply the mod to 1.0.1. I just need to find some time. I hope i will do it during the week-end.
Regards
Click to expand...
Click to collapse
Okay thank you! I will look forward to the 1.0.1 release.

Another option is to use Cool Reader 3. It has Nook Simple Touch features (e.g.: type of refresh - full, fast; you can map the physical buttons) and, starting with cr3.0.51-20, it automatically creates one folder (currentbook) in screensavers and saves the current book's cover in that directory (deleting all others when the current book is changing). You can then choose that directory in the standard screensaver option of your Nook.
Not to mention other nice touches not present in the standard reader (showing the clock and the battery percentage or bars while reading a book, very customizable).

Yeah, problem encountered when I try reading or going into settings.. here's the log:
http://pastebin.com/fGGJVnGQ
I'm using 1.0.0
EDIT: Restored the backuped files, reader's back online, settings still not working :[
This particular error appears when I'm trying to launch the settings panel:
Code:
No Activity found to handle Intent { act=android.settings.SETTINGS flg=0x14400000 }
Touching the wifi icon doesn't open up any popup, it just fast reboots the nook

koltzu said:
Yeah, problem encountered when I try reading or going into settings.. here's the log:
http://pastebin.com/fGGJVnGQ
I'm using 1.0.0
EDIT: Restored the backuped files, reader's back online, settings still not working :[
Touching the wifi icon doesn't open up any popup, it just fast reboots the nook
Click to expand...
Click to collapse
hi,
sorry for your issue.
Actually, i also had some issue just opening the wifi-tab of the settings. I didn't found it before simply because i don't use wifi at all, so normally i don't have any reason to open it!
To solve this issue, you just need to update the file settings.apk, following the instruction on post 1. I updated the file "Settings.apk" in the firtst post.
In your case, if you reverted to original file, then there is no trace left of my modification, so i really don't understand what may occur. It could be useful to get a complete logcat trace since boot. To do so, launch the logcat command, as soon as the Nook is booting (tipically, as soon as the Nook drive appears on Windows): this way, you don't miss the first log lines that could help understanding your issue.
Additional advices: check that, after reverting to original files, you set the right permissions; wipe dalvik-cache:
Code:
adb shell rm /data/dalvik-cache/*.*

Thanks for the answer, I did as you told and the settings started working [by using your apk] but the reader died again. Replaced it again by using my files and the reader started working while the settings menu stopped working.
I seem to be unable to do a logcat while booting [can't connect through cable for some reason].
I blame all of these problems on my own previous tinkering with my nook.
Luckily I have a backup that I've done before rooting the nook. I'll just restore it and try again on a 'clean' and newly rooted Android system as soon as I get my hand on a microSD card.
If I bang into any more problems after restoring, I'll let you know

Any update on this? Possibly getting it to work on the (yes just released) v1.1 update?

I'm interested to see if this has been worked on anymore? Is there any plans for bring this to V1.1? I would love to use this on my nook.

persichini said:
I'm interested to see if this has been worked on anymore? Is there any plans for bring this to V1.1? I would love to use this on my nook.
Click to expand...
Click to collapse
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards

traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
Hey tray - thanks a lot!
But many of us here have already installed modified versions of android.policy.jar and services.jar...it's not possible to release a patcher, right? Can't ask for too much, and don't mean to be belittling your contributions...
And, btw, I'm seeing all these different patches here...does anybody have a primer on patching these jars? Or at least some intro? I'd google it but I'm not quite sure what to search for...

traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
That would be awesome if you did bring it to 1.1. I under stand developers have lives outside of development thank you for your time.

traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
Since you are going to patch Reader.apk, how hard would it be to modify it so that it can be launched from standard drawer as any other app?
It would be great to be able to add a big icon (e.g. with Desktop VisualizeR) to the home page that opens the book your currently reading...

traycold said:
hi, i will try and find the time to make the updates for firmware 1.1 as soon as possible (possible, this week-end).
Regards
Click to expand...
Click to collapse
Hey trey- instead of releasing a jar file, which many of us have modified, what about just giving us whatever you modify in the smalis, and then we go ahead and apply the patch ourselves?

You could also take the stock 1.0.0 files and make the patches yourself.

LOL, right, if I knew just what the heck I was looking for...

LastSilmaril said:
LOL, right, if I knew just what the heck I was looking for...
Click to expand...
Click to collapse
You don't need to know! Decompile the original files, decompile the files from this thread (apktool). Make a diff of the to decompiled folders (diff -crB folder_with_decompiled_stock_files folder_with_decompiled_files_from_this_thread > diff.patch ). Now you know what has been changed and you can try to use the patch with the 1.1 files.

mali100 said:
You don't need to know! Decompile the original files, decompile the files from this thread (apktool). Make a diff of the to decompiled folders (diff -crB folder_with_decompiled_stock_files folder_with_decompiled_files_from_this_thread > diff.patch ). Now you know what has been changed and you can try to use the patch with the 1.1 files.
Click to expand...
Click to collapse
Thanks...I've never had to really use diff for anything before so I never really thought about it. I'll try it out, but likely not today - I need a break from Nook testing/hackery already (see my dhcp thread...)

bump.........

[MOD] OLD VERSION HULU MOD Automatic Hex Editing Script

OLD VERSION
NEW VERSION FOLLOW LINK BELOW
CLICK HERE for Updated Post and Application
==========OLD INFO BELOW THIS LINE===========================
Im leaving the old info here for reference and in case anyone still wishes to continue to use this version. The new version is beter in every way IMO. But the choice is yours.
===============================
FLASHEX and FLASHMOD script INFO 0.98beta
===============================
This is a new set of scripts I created, Flashex.sh and Flashmod.sh. They take advantage of the same old AND to WIN hex edit. The big difference is Flashex.sh will hex edit the file right on any android device that has busybox installed. I have only been able to test it on my 1 Android device the A100 works perfectly on it. I'm curious if anyone can run it on current rooted ICS since it only requires WRITE to /data, I'm fairly sure it will work just fine, and/or on other devices with flash and a decent enough CPU and memory to watch hulu.
What they do
==========
Flashex.sh will look at /data/data/com.adobe.flashplayer/lib/libflashplayer.so, find its version string, then make a copy of the file and hex edit the copy. It DOESNT require root since it only needs READ access. Flashex.sh only needs to be run once unless you delete the WIN_libflashplayer.so or your Flash Player gets an update.
Flashmod.sh will look for the WIN_libflashplayer.so(hex edited file), check for write access, then copy the file to /data/data/com.adobe.flashplayer/lib/libflashplayer.so.
They can both be run from Terminal, Script Manager, etc. I suggest Setting Flashmod.sh up with a Desktop Icon via Script Manager for an easy way to apply the fix before watching Hulu.
How To Install and Use
======================
1) Create a directory you want to run the script from. I suggest
/mnt/external_sd/FLASHEX but it can be anyplace as long as you
can find, and run the scripts.
2) Download FLASHEX_098b.tar.gz and place it inside the folder
3) cd into the directory
cd /pathtofolder/foldername (note: typically /mnt/external_sd/FLASHEX or /mnt/sdcard/FLASHEX)
4) run the following commands to extract Flashex.sh and Flashmod.sh
gzip -d FLASHEX_098b.tar.gz
tar -xvf FLASHEX_098b.tar.gz
5) Now "sh Flashex.sh" this will READ the original flash file, and hex edit the file.
it will place the edited file inside the default(same folder as script) directory.
The Edited file is named "WIN_libflashplayer.so"
6) Now "su" because Flashmod.sh will need root access to overwrite
/data/data/com.adobe.flashplayer/lib/libflashplayer.so with the edited version
7) Now "sh Flashmod.sh" This script will find WIN_libflashplayer.so and copy it to
/data/data/com.adobe.flashplayer/lib/libflashplayer.so
Note: You will also see "ORIG_libflashplayer.so" that is a backup of the original
that is made before the change. It can be used to restore in the even someone
edits and decides they want to go back, or in case of an unforseen event.
8) Now just make sure your web browser is set to view as "Desktop" and enjoy watching hulu.
That's about it. IF you have run Flashex.sh once you
DON'T need to run it again UNLESS you get a Flash
update, or you delete the WIN_libflashplayer.so.
If your Adobe Flash updates on you just rerun Flashex.sh
to edit the new file. Once edited it will store a copy of
the modded file the scripts home dir.
Then use as Flashmod.sh as normal.
THANKS TO:
===========
All the other people who make GNU open source
programs, the people who figured out how to get hulu to work
by hex editing the libflashplayer.so, and all the great folks
at XDA Developers for providing so much good information,
and for all the hard work to figure out root methods,
and all the other amazing stuff that goes on.
=========================================================
TESTING INFO FOR OTHER DEVICES
This should work on most any android flash in theory but that's UN-tested.
I wrote it to try and look for the same expected pattern for 10.x 11.x and even
12.x(taking a guess). It HAS been tested with Flash 11.x and works
great. It's written in such a way it should be safe to test. Either the Flashex.sh script will give you a properly edited libflashplayer.so or it should be able to tell you it couldnt edit the file. If you end up with an edited file it should be safe to copy over and should work. If you find it DOESN'T work with your version of flash you may contact me and make the .so file available and I will see if I can add support. Eventually I would like this to be universal and easy to use.
ALSO PLEASE!
If it does work for you, especially on other devices or other flash versions please post and let me know. It will help me improve the set of scripts.

Got it working on ICS took me abit of reading on google on how to cd to the directory but alls well that ends well!

/system/bin/sh: cd: /FLASHEX - No such file or directory
1|[email protected]:/mnt/sdcard $ tar -xvf FLASHEX_098b.tar.gz
tar: can't open 'FLASHEX_098b.tar.gz': No such file or directory
1|[email protected]:/mnt/sdcard $ tar -xvf FLASHEX_098b.tar.gz
Flashex.sh
Flashmod.sh
README.txt
[email protected]:/mnt/sdcard $ sh Flashex.sh
======================================================================
Cannot locate /mnt/external_sd/FLASHEX(configured path for Flashex.sh)
The script will attempt to adapt...
Flashex.sh is running from /mnt/sdcard
Flashex.sh has write access to /mnt/sdcard
attempting to use /mnt/sdcard instead...
To avoid this message in the future read the directions better
======================================================================
Detected READ access for /data/data/com.adobe.flashplayer/lib/libflashplayer.so
USING: /data/data/com.adobe.flashplayer/lib/libflashplayer.so
Created /mnt/sdcard/cache Sucessfully...
Found /data/data/com.adobe.flashplayer/lib/libflashplayer.so...Checking
grep: 1[0-2],[0-9]*: No such file or directory
grep: 1[0-2],[0-9]*: No such file or directory
ERROR: Can't figure out what version of Flash this is so it cant be edited.
Currently only tested with v11.1.111.x. It should work with about any version.
I can't test what I dont have. If you send a copy of the libflashplayer.so I will
add it to the Flash versions that are 100% tested and supported.
Contact me(NoSudo) and/or look for updates at forum.xda-developers.com
1|[email protected]:/mnt/sdcard $ su Flashmod.sh
[email protected]:/mnt/sdcard # sh Flashmod.sh
======================================================================
Cannot locate /mnt/external_sd/FLASHEX(configured path for Flashmod.sh)
The script will attempt to adapt...
Flashmod.sh is running from /mnt/sdcard
Flashmod.sh has write access to /mnt/sdcard
attempting to use /mnt/sdcard instead...
To avoid this message in the future read the directions better
======================================================================
ERROR: /mnt/sdcard/WIN_libflashplayer.so NOT FOUND
1|[email protected]:/mnt/sdcard #
Here is my outcome from the script. Searched files and could not find flash hex version.
Running Acer a100 ICS rooted

igwtapc said:
[email protected]:/mnt/sdcard $ sh Flashex.sh
===============================================
Cannot locate /mnt/external_sd/FLASHEX(configured path for Flashex.sh)
The script will attempt to adapt...
Flashex.sh is running from /mnt/sdcard
Flashex.sh has write access to /mnt/sdcard
attempting to use /mnt/sdcard instead...
To avoid this message in the future read the directions better
===============================================
Click to expand...
Click to collapse
You need to create a folder for the script still. It looks like you currently have the scripts located in /mnt/sdcard. You would need to make a folder called FLASHEX still inside /mnt/sdcard/ or /mnt/external_sd/ so the full path would be /mnt/external_sd/FLASHEX or /mnt/sdcard/FLASHEX. If you change the folder name you "may" have to edit the script. I will be releaseing an update soon and I will include a little more testing of that. It was an afterthought and was just added to help make it easier for people. Anyway try this...
First make a folder.
"mkdir /mnt/external_sd/FLASHEX"
Now move the 2 scripts into that folder from the current location
"mv /mnt/sdcard/Flashex.sh /mnt/external_sd/FLASHEX/Flashex.sh"
"mv /mnt/sdcard/Flashex.sh /mnt/external_sd/FLASHEX/Flashmod.sh"
Now you can run them
This will run the script once moved
"sh /mnt/external_sd/FLASHEX/Flashex.sh"
Now you should have WIN_libflashplayer.so inside the FLASHEX folder.
Next run
"su"
"sh /mnt/external_sd/FLASHEX/Flashmod.sh"
I suggest running this via script manager once you decide you like using it. I have mine setup to run at boot. Just be sure and turn off auto update for adobe flashplayer if you run Flashmod.sh at boot. The next version Im thinking about adding the ability to have it run the hex edit each time it detects an updated version. We will see. My main concern with that would be the amount of time the hex edit takes.
Anyway that should get you going on the Hulu. Remember to set your browser to "Desktop" too or it still wont work. I suggest Dolphin HD for a browser.
Let me know if you have any more issues and check back for an updated version in the next few days.

by igwtapc
Created /mnt/sdcard/cache Sucessfully...
Found /data/data/com.adobe.flashplayer/lib/libflashplayer.so...Checking
grep: 1[0-2],[0-9]*: No such file or directory
grep: 1[0-2],[0-9]*: No such file or directory
ERROR: Can't figure out what version of Flash this is so it cant be edited.
Currently only tested with v11.1.111.x. It should work with about any version.
I can't test what I dont have. If you send a copy of the libflashplayer.so I will
add it to the Flash versions that are 100% tested and supported.
Click to expand...
Click to collapse
After looking at your output a little closer. I noticed it did seem to create a cache folder inside your /mnt/sdcard. Can you confirm the existence of a cache folder at /mnt/sdcard/cache? Also did you edit the script or did you change the type of quotes around the strings used by grep? I'm going to do some testing and it would speed things up if I knew those two things.
The above(previous post) directions still apply and should work. However if the script has been edited even just a change from " to ' could break it so be careful.
If your not used to scripting I would not advise you change anything other then the HEXHOME="/mnt/external_sd/FLASHEX" inside the script, and don't change anything left of the = or change the " type. Only edit the directory path/name.

I just tried this and got the same error as above. I did notice that it created the cache folder in the same directory though. It just can't determined what the library file is.
Current flash player version is: 11.1.115.7 March 5, 2012
Edit: Here is the libflashplayer.so file:
http://dl.dropbox.com/u/24495685/libflashplayer.so
Sent from my A500 using XDA Premium HD app

does this works in ICS?
Update:
Yes it does.
But,,, the script gave me an error about "uncommon string' on line 228,, any ways what I did was just to open adb and run all commands in the script one by one. I copy the edited lib.so to the flash folder , restarted, watching hulu now.
Thanks for this.

Cool. Not sure what the error was(without a way to recreate it) but, I have a new version coming out in a few days that will work better. I will post it over in the app section so I can get more feedback posts and just link it back to here.
It's a single script solution that will do the hex edit when it detects an upgrade or downgrade of Flash to update the edited copy and write it over each boot. That way people don't have to worry about updates and such.
If I can find the time I'm going to upgrade to ICS this weekend. I haven't had time to do much the last few weeks and need my tablet so I have been waiting. I need to read up on the latest. It looks like we even have CWM now OMG! Nice work!
Once I'm running ICS I can test on it and make sure it's working on both.

Joecascio2000 said:
I just tried this and got the same error as above. I did notice that it created the cache folder in the same directory though. It just can't determined what the library file is.
Current flash player version is: 11.1.115.7 March 5, 2012
Edit: Here is the libflashplayer.so file:
http://dl.dropbox.com/u/24495685/libflashplayer.so
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse
That's very odd. My current version is 11.1.111.7. I will take a look at it in a few. For me so far I have seen 11.1.111.5-11.1.111.7 and all worked fine on my acer. I'm posting a new version that may already address the issue you are having. I will do some tests with the file you attached to see this evening.
Also might not be a bad idea to confirm the path for the libflashplayer.so is the same as the script is expecting. I havnt added anything in to search the system for alternate flash locations yet. It can be configured at the top of the script though.
I have also found some people are using an older BusyBox that seems to be mission a feature. Im using busybox v1.19.3 latest is 1.19.4 the installer I use is the one from JRummy. It's not a bad idea to confirm which Busybox you have if you run into issues with odd errors.

Looking at this right now. I will need to modify the pattern a little to make it work on this lib version. Thanks for bringing it to my attention. I'll PM you when I update with support for that version.
EDIT: New improved version here
Joecascio2000 said:
I just tried this and got the same error as above. I did notice that it created the cache folder in the same directory though. It just can't determined what the library file is.
Current flash player version is: 11.1.115.7 March 5, 2012
Edit: Here is the libflashplayer.so file:
http://dl.dropbox.com/u/24495685/libflashplayer.so
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse

[GUIDE][All-In-One]LG Optimus Me P350

So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide​
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit

great guide good job

Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!

to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy

antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...

Updated adding unyaffsmbn tool... Thanks antdking!

Added Volume tweak for speaker to sound harder.

Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me

dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:

Guys We have got Official Support From XDA Please Move This Thread To Our Device Section

Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183

Great Guide Man! Thanks a lot.

Collection of Guides and Tutorials for G9(Also, how to root and get custom rom)

Welcome
I wrote this post to help people get their Archos g9 tablet running custom roms. If you have any improvement ideas, please post them so I can make this better source of information.
List of content:
Post 1
What is recovery
What is SDE and how to install it
-Also SDE for 4.0.25
List of most commonly used roms
How to install custom roms
How to install offical rom
How to multiboot android 4.0 based roms
Installing 3G stick and Huawei modems support.
Post 2
Change symlinks/binds.
Installing ADB
Installing SuperCharger
Installing Chainfire3D
But why?
FAQ
Useful links
What is recovery​You can boot to recovery menu by holding volume- while booting your device. From recovery meny you can calibrate your touchscreen, wipe data and do this kind of stuff. Installing SDE creates new entry to recovery menu, called Special Developers Edition. There you can remove android kernel, flash new, export hdd and data. In recovery move up and down with volume + and -. Select by pressing power button
What is SDE and how to install it​SDE is shortened word from Special Developers Edition. After SDE is installed, your tablet is able to boot to official rom, recovery, and SDE rom. Most of the roms advice you to use "Remove android kernel" from SDE before you install kernel. When you remove your android kernel from there and install kernel from custom rom, your archos boots directly to custom rom. If you don't delete it, your device boots to official, but keeping volume - while booting gives you change to boot to SDE.
There are 3 guides how to install SDE. Official SDE watermarks your device for archos (there is no watermark on screen ), so they can detect you have installed SDE in some point. It stays even if you remove SDE. Official way is more safe. Also, it removes "only" software warranty. If your devices powerbutton, Usb-port or etc brokes, you can still send it to warranty. Link to official SDE install guide. Big thanks for Shano56.
Then there is unofficial, a bit more dangerous method. It doesn't watermark your device, but is more complicated. Guide tells that it's outdated, but it worked for me. I used official 4.0.4 version while installing. Link to the guide. Big thanks to Shano56.
4.0.25 Guide, by surdu_petru
surdu_petru said:
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
On your tablet :
check on Settings-> Developer options -> USB debugging on !
connect USB cable ( PC to tablet )
On your PC :
> adb push 1 /data/local
> adb push 2 /data/local
> adb shell
$ chmod 0755 /data/local/*
$ ./data/local/1
$ exit
> adb reboot
> adb shell
$ ./data/local/2
$ exit
> adb reboot
> adb push zimage /data/local/tmp
> adb push initrd.cpio.lzma /data/local/tmp
> adb push abcbox /data/local/tmp
> adb shell chmod 755 /data/local/tmp/abcbox
> adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
( now you have installed unofficially SDE ! )
Flash Root version or other Custom Rom :
> adb reboot
> adb shell rm /data/local.prop
> adb push archos.ext4(.update) /mnt/storage
Go to SDE -> ( check "Reboot" on power off menu , and after a while press & keep volume down until you see SDE menu !)
Go to Recovery System -> Developer Edition Menu -> Remove Android Kernel -> I Undestand -> OK -> Developer Edition Menu -> Flash Kernel & Initramfs -> copy here zImage and initramfs.cpio.lzo appropriate archos.ext4(.update) -> OK -> wait to boot !
Now you have Rot version installed !
Here you will find the necessary files : Enable_SDE.zip
Click to expand...
Click to collapse
List of most commonly used roms​These roms are most commonly used. Most of them are still being developed. I also included link to rooted official honeycomb, because some people have better touchscreen responsibility with it.
ParanoidAndroid 3
Cyanogenmod 10, 4.2 mockup
Cyanogenmod 10
AOKP ROM
[email protected]
Clean_Slim&Fast(Based on official 4.0.25!)
Ubuntu. This requires special kernel, which is compatible with official android 4.0.4Overclockable stock rom
Early CM9
Stock ICS rom with root & busybox
Stock honeycomb with root. (FYI, kernel requires renaming while installing)
How to install custom roms​Custom roms have different installing methods, but basic idea is same. You move image file with specified name to specified location.
When coming from stock rom or whengoing to stock rom:
CyanogenMod 10, AOKP, CyanogenMod 9
surdu_petru said:
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /mnt/storage ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
[email protected], Ubuntu, Root 4.0.7 Clean_Slim&Fast
surdu_petru said:
Install :
- copy archos.ext4.update(archos.ext4 in case of Clean_Slim&Fast) in /mnt/storage/ , you can use this command > adb push archos.ext4.update(remove .update if Clean_Slim&Fast) /mnt/storage/
- go to SDE -> Developer Edition Menu -> ( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- after everything was installed - please reboot your device !
Click to expand...
Click to collapse
Honeycomb
Install like Cyanogenmod and AOKP and others, but rename initramfs.cpio.gz to initramfs.cpio.lzo
How to install official rom​Download official 4.0.7 rom from here.
Now boot to recovery (hold volume- while booting) and choose update firmware.
Now there should be noew drive in your pc. Drop the downloaded firmware_archos_it4.aos to there and press ok in recovery. Keep usb plugged in while installing. It should take around 30 seconds to 2 minutes. Now choose ok again. your tablet should now reboot to stock rom.
4.0.24 Official is owrking on some devices, but because it won't work on all, i won't cover it here(yet)
How to multiboot android 4.0 based roms​Install modified initfram from this topic. Use the zimage from the rom you want to multiboot. AFAIK you can multiboot with following combos:
[email protected], Ubuntu (download newer kernel from later pages.), Root 4.0.7
and
AOKP, CyanogenMod 9.
You cant use [email protected] and AOKP because they do not use same kind of data. That means that after you have run first rom, the second will bootloop. That is also why it requires wiping data when changing from stock to aokp and vise versa.
Detailed:
Download dmenu-0.3a.zip, and extract initframfs to desktop. Then download [email protected] and stock 4.0.7 rooted. Extract Image files and zimage from either one of the roms. Now just instal like described in earlier section, while using initframfs from multiboot and kernel from other rom.
Installing 3G stick and Huawei modems support. ​
Trevd made a package to add 3G stick and extra Huawei modems work for AOKP and generally all ICS ROMs. This guy is awesome because he also made some Huawei modems work.
trevd said:
Hi surdu_petru and AOKP fans.
Great work as always, It's not a rom i'll ever use but It's the first time I've loaded an AOKP Rom, I like notification layout, I'll be having that away for my own personal rom Anyway I was more just passing through and noticed 3G was not working yet. As seen as though that seems to be my speciality and preoccupation/addiction for the last 9 months I thought I do something to remedy that situation for you.
Here's an hotfile link to download the update [ 3g-archos-aopk.7z ] this should contain everything you need to get the Archos 3G Dongle, just for ****s and giggles as a extra bonus i've also included the huawei support file as well :good:
Installation:
From a command prompt / bash terminal
Code:
7z x 3g-archos-aopk.7z
adb push 3g /
adb shell reboot_into sde
extracting the 3g-archos-aopk.7z will give youu a 3g directory in you current directory, we then push the contents of the 3g directory to the root direcotry on the device. This operation is recursive.
Have Fun!
What follows is a detailed explanation of what files and modifications are required to add 3G support.
Archos 3G Stick
The changes / additions to add this functionality breaks down like this ; The following required binary's were on the device already:
** /lib/modules/hso.ko is insmod'd by the device specific init file /etc/init/init..rc
Code:
/lib/modules/hso.ko[B]**[/B]
/usr/bin/usb_modeswitch
/system/lib/libtcl-ril.so
/system/bin/rild
/system/bin/pppd
/system/xbin/chat
/etc/ppp/init_pppd_datakey
/etc/ppp/ip-up-datakey
/etc/ppp/ip-down-datakey
/etc/ppp/peers/datakey
/etc/chatscripts/datakey_start
/etc/chatscripts/datakey_stop
/etc/usb_modeswitch/1bbb_f000
The following required services were already defined in the device specific init.rc's located in /etc/init/init..rc ,
*** switch_ms_3g defined by /etc/init/init.archos.rc
Code:
service service switch_ms_to_3g[B]***[/B]
service pppd_secrets
service pppd_datakey
service ril-daemon
So what's missing? you may ask as this pretty much is everything that is needed by the Archos 3G Stick.
Standard Archos Roms use the UsbKeyManager.apk system service to start the switch_ms_to_3g and ril-daemon service's. I replace that with my own ueventd handling native service and add an additional to configuration file keep everything clean
Code:
/system/bin/hotplugd
/init.dongle.rc
I've added the following line to the top of the /init.rc
Code:
import init.dongle.rc
All that is left to do now is enable mobile networks on the rom. I used apktool to decompile the /system/framework/framework-res.apk and change the following values
res/values/bools.xml
Code:
true
true
res/values/arrays.xml
Code:
wifi,1,1,1,-1,true
mobile,0,0,0,-1,true
mobile_mms,2,0,2,60000,true
mobile_supl,3,0,2,60000,true
mobile_hipri,5,0,3,60000,true
mobile_fota,10,0,2,60000,true
mobile_ims,11,0,2,60000,true
mobile_cbs,12,0,2,60000,true
wifi_p2p,13,1,0,-1,true
"1,1"
"0,1"
"7,1"
"9,1"
res/values/strings.xml
Code:
ppp1
Huawei Support
The extend this functionality further I added the following files
Code:
/etc/ppp/init_pppd_gprs
/etc/ppp/ip-up-gprs
/etc/ppp/ip-down-gprs
/etc/ppp/peers/gprs
/etc/chatscripts/gprs_start
/etc/chatscripts/gprs_stop
/etc/usb_modeswitch/ [ numerous configurations files ]
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
We also need to chmod 6755 /system/bin/pppd but that is handled/checked in the /init.dongle.rc so there is no need to do that manually
Click to expand...
Click to collapse

Change symlinks/binds​Trevd wrote guide to let people know how to change binds. That way you can move large folders, like Gameloft games and navigator files to ExternalSD, saving InternalSD space.
trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
Installing ADB​ADB comes from word android development bridge, and it allows you to debug, move files and get shell access to your tablet.
Archos said:
First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:
Go to the Android SDK page and download the latest SDK for your operating system.
For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
Click to expand...
Click to collapse
Running adb from anywhere
steviewevie said:
We need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Click to expand...
Click to collapse
sources:Archos, steviewevie
Installing Supercharger​Supercharger is a multiscript which makes the tablet work much better. Its created by Zeppelinrox, and its official topic is here. We are using also script manager in this guide. That way we can make MinFrees and OOM apply.
In this guide we'll use Apex launcher which is moved to /system/app for our default launcher.
We are also using adb to configure and run Supercharger.
Because stock launcher is odexed and i am not writing how to deodex, we are not using it.
First make sure apex is your default launcher. This can be tested by pressing home button in homescreen.
If it show mini previews of your homescreens, apex is your default launcher.
Now lets begin:
go to here and download newest file. At
the time of writing, it is Update 9_RC11_test6. Move it to your adb folder.
Then open commandline. This can be opened with windowskey + R and writing cmd. Navigate
to adb folder using cd command. I have made adb to run from anywhere, so i just navigate to the downloaded file.
Now use command "adb push v6* /mnt/sdcard" then use command "adb shell". Now you should have
shell access to your tablet. Now do following
su
cd /mnt/sdcard
sh V6* /remember capital V)
Supercharger script should open now. After presentation, script should print after telling your busybox version
"com.anddoes.launcher is the home launcher!" Now continue install. Supercharger will tell you everything you need to know.
So just follow the instructions. After choosing kernel tweak, you get bunch of permission denieds.
We can't help them, so lets just continue.I recommend on using all the tweaks that you can,
but it is your choise do you want to use or not. After all the selections are selected and your in
driver panel, choose number 32. It'll reboot your tablet and wipe dalvik. When the tablet has booted, lets run supercharger script again.
So write these again:
su
cd /mnt/sdcard
sh V6_Super*
After getting to drivers panel, you notice that minfrees are not in effect, and neither is OOM Grouping Fix BUT if they are, you can ignore this step..
Install script manager from market and open it. Give it root permissions and navigate to /system/etc/init.d
press SS99SuperCharger to open its settings. Now press the Su button and then Boot button.
Now press save, and then click it's name which appers to right. Then press back button and reboot.
Now Minfrees should work, and OOM too.
Now you can run 22 if you want to try it. Supercharger is now fully working.
Installing Chainfire3D​
Chainfire said:
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Click to expand...
Click to collapse
It is very useful for running gameloft games and other games too. I recommend buying it. There are some plugin for it, but i'm not going to tell you about it now.Play store link.
After downloading it, open it and choose "Chainfire3D Driver" and from there "install". Then confirm it and tablet should reboot. Now reopen it and choose "Default opengl setting". From there you can tweak 3D performance if some games lag. Also, if you install plugin, there you can apply them. I personally use "reduce texture quality".
But why?​
This section is to point few reason why to follow these guides. Lets begin:
SDE
Well, you should install this if you want to customize your tablet. If your happy with your tablet running stock, you don't need this, or any other guides.
Custom roms/kernels
Custom roms allow you to use root, they make your tablet faster and add extra functionality. This "functionality" includes: Overclock, run init.d scripts, enable both cores with all governors, root and themes. The benefits are not limited to these, but I could name this quickly. If you wan't to try something which is close to stock, but still has root and some custom functionalities, i would recommend deodexed 4.0.7, or [email protected]
Install official roms
These roms do not require SDE, but will not include root or anything fun . Updating your official rom has many benefits. They include fixes and boost your tablets performance.
Multiboot
Multibooting allows you to have 2 or more roms, which you can choose which to boot on startup. I would recommend this if you want to test functions with root, but still have "backup plan" if testing rom renders unbootable.
3G support
Basicly this allowes some extra huawei 3G sticks to work. There is no list of working stick, you just have to try and hope.
Change symlinks/binds
These allow you to "move" eg. gameloft games to external sd, and allow you to acces your externalsd via internalsd folder.. That way your gamedata does not eat the valuable internalsd space.
ADB
You need this to transfer rom to your tablet. It is also required when you sent logcat reports to help remove bugs.
SuperCharger
This makes your tablet work more fluid. I personally install supercharger to all my android devices. It removes need for task killer, and makes the device work better. Everyone has different results, and it costs only time to install, so i would recommend installing it.
Chainfire3D
This tool allows you to play games made for other GPUs and it can tweak application graphics. You can make the game look worse, but run better or adjust the grphics for a bit higher, so the game looks nicer.
FAQ[/CENTER]
These questions and answers are collected from various sources.
surdu_petru said:
How to activate second core for all govenors in surdu_petrus roms?
To activate the second core, you need the following steps :
- copy /system/S1tweak in /system/etc/init.d/ or ( > adb shell ; # cp /system/S1tweak /system/etc/init.d ; # exit )
- open No-frills CPU Control :
- choose the desired Governor ( but not hotplug ) !
- choose the desired frequency , but not overclocked ! ( when the device will boot - will open with the selected frequency , so please choose max. frequency = your max. stock frequency )
- check "Apply on boot"
- check "Applay"
- check allow if superuser asked permission
- reboot your device !
- Now , both core will be used in any selected Governor ( other than hotplug ! ).
Click to expand...
Click to collapse
What modems does Trevds mod support?
trevd said:
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
Click to expand...
Click to collapse
Shano56 said:
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
Click to expand...
Click to collapse
[/quote]
Useful links​Some link i consider useful are here:
G9 101 16GB 1.5GHz Teardown! (Lots of Images)
XBMC for android
Want faster GPS? Follow this guide

3th just i remember something to add. Comment and give me some feedback. It helps me to make this topic useful for beginners, and for those who seek info.

I meant to edit first post... well, this works as 4th reserved then.

Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:

trevd said:
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
Click to expand...
Click to collapse
Thanks for the feedback.
I removed the part which had github link, and modified the AOKP section to tell it works with all ICS ROMs.
I'll included your mini guide. I might even have some use for it myself...
Sent from my GT-I9100 using xda app-developers app

help me for multi boot ubuntu ics bleuv03
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.

muti642 said:
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
Click to expand...
Click to collapse
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app

julle131 said:
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?

muti642 said:
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
Click to expand...
Click to collapse
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit

THX
julle131 said:
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
Click to expand...
Click to collapse
Thank you thanks you it works well, I do not use the right kernel or the good image of ubuntu. ps: the touchscreen does not work but using the OTG is perfect.
thank you again julie :good:

sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!

solrakk6 said:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
Click to expand...
Click to collapse
Yes, you must use adb. I assume your "untoot" means unrooted. You use cd command to navigate to your adb folder and from there to platform-tools. Also drop archos.ext4.update to there. Then use the adb command to move the file. Moving file to that location does not require root.
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.

hondacity said:
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
Click to expand...
Click to collapse
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
julle131 said:
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.

hondacity said:
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
Click to expand...
Click to collapse
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
http://update.archos.com/9/gen9/gen9_4.0.26/firmware_archos_it4.aos
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
julle131 said:
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,

hondacity said:
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
Click to expand...
Click to collapse
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
julle131 said:
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks again Dear,
I applied same as you say but ending on same 221 error. Any thoughts please.
Best regards.:crying:

[ROOT]G955U/G955U1 SnapDragon SamPWND Root IS HERE!

FINALLY!
We Present To You
SamPWND!
Root for the USA Variants of the S8 & S8 Plus Devices!
(This thread will focus only on the S8+)
This thread had been closed/locked until further notice. The thread and links should remain active and the thread has served it's purpose. You will need to search the thread if you have any questions pertaining to root or any errors/issues that you are facing. The other reason I have decided to close the thread is because it has gone off topic one too many times, people like to argue and debate and MODS have had to come in here 1 too many times to clean it up so as to make life easier, I will just shut it down. Please do not bombard me with PM's for root assistance because if it has been answered in this thread already (and it most likely has) I will just direct you to search in the thread if I am able to respond at all.
ALSO, please do not utilize our firmware/root files/method without gaining permission first or I will ask for the thread to be removed/locked. Just because the thread gets closed does not mean we didn't spend a lot of time to get to this point.
Thank you and enjoy SamPWND root!​
DISCLAIMER:
We are not responsible for any damage done to your device as no one is "forcing" you to root your phone! If you are not sure of how to follow instructions or use ADB then I would suggest waiting for someone to help you or that you read up on how these things work before diving head first. The ENG system is not very stable when it comes to root as well as it has a ton of tools and binaries not available on stock devices so we are not responsible if you break something while on any firmwares but especially while on the ENG firmware.
DISCLAIMER 2:
Please do not take our work and post it elsewhere. We spent a lot of time on this for people to take it and use it as if it is their own. With that being said, if you have a better process for something or find any issues/errors, please PM myself or one of the listed contributors of this root method, do NOT post it directly in the thread because it causes confusion. We know with 100% certainty the files and method presented WORK. If it is not working for someone there are a number of possible reasons why. If users start modifying our files/scripts and posting them and you decide you are going to use someone else's files/scripts, do not post in our threads asking for us to help you because we will have no idea what was modified or changed and will just tell you to use the original files.
Returning to Stock:
- It is possible to return to 100% stock and it is very EASY to do.
- This is the reason why I provide both Normal, and Comsey ODIN's.
- All you need is a full stock 4 files firmware of your choice.
- Extract those files. Open ODIN and select the 4 files in their respective slots.
* IF YOU GET ERRORS such as model mismatch, start with 1 partition at a time to find out which one is throwing the error. (In my experience, it is the BL file that causes the error.) Once you find the culprit, throw that partition into the other ODIN. (For example, the BL file is giving an error in Comsey ODIN, throw the BL file in NORMAL ODIN and flash it by itself.)
* Typically you might have to throw individual partitions into either of the ODIN's but in the end you will be back on full stock firmware.
What doesn't work while rooted?
- On ANY ROOTED device, anything that utilizes "SafetyNet" will NOT work.
- Magisk and/or SuHide will NOT work. Our bootloader is still locked and these two modify the boot.img which would cause our devices to not boot up and having to start the root process over again, you have been warned!
- Systemless root also does NOT work. Again, this patched the boot.img which we cannot do because of our locked bootloader.
- Battery currently only charges to 80%. There are a few that feel it legit doesn't charge fully but others are claiming they get the same amount of life as they did with a 100% battery so the 80% might just be a visual issue or "fake" when it is really at 100%. Either way, we are still looking into this.
Main Contributors:
@elliwigy
@Harry44
@akiraO1
@BotsOne
@GSMCHEN
@jrkruse (for uploading system.img.ext4 and his root zip for the part 2 instructions)
@V0idst4r (for help in creating a "1 click" method for part 1!)
Initial Description on the process:
We are essentially flashing a modified 4 file firmware package in ODIN and then utilizing a few binaries in conjunction with SU binary and a permissive kernel. We will then be running some ADB commands and in order to have a fully working, amazing root with all things working we will be utilizing a stock system.img & a root script in conjunction with Flashfire. If you want to know all the technical details, you can take apart the files if you would like. It is released, so it is no longer a secret!
PART 1 Instructions: NEW
Flashing SamPWND 4 Files Firmware:
1) Download the PART 1 FILES Listed Below (this includes SamPWND_Root.zip and Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them.)
2) Extract the 4 Files ODIN Firmware Package (also extract the ODIN's if you do not have them already.)
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the NEW Root Process:
1) Once the phone is booted up, make sure you have ADB Enabled and connected to your PC. It should have prompted you to accept USB debugging as soon as it booted up.
2) Unzip the SamPWND_Root.zip
3) Double click "step1"
4) Wait for it to finish and once it reboots and comes back on you will be rooted with SuperSU!
5) Continue to PART 2 for "EVEN BETTER ROOT"
* It is a Windows bat file so not sure if it works on MAC. If you can't run bat files, use the OLD instructions.
* The bat will take about 30 seconds to run it's course. This is due to giving enough time for the remount script to mount the system as RW.
PART 1 Instructions: OLD
1) Download the PART 1 FILES Listed Below (this includes Systemroot + ADB zip, Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them)
2) Extract the 4 Files ODIN Firmware Package, Also extract the ODIN's if you don't have them already.
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the ADB Process to actually Root:
1) Extract the Systemroot + ADB zip listed below in an easy to find directory.
2) Make sure phone is connected to PC and ensure USB Debugging is enabled.
3) In the folder you extracted, you should see a "cmd-here" file. Double click it and it should open up an ADB cmd window.
4) Now we will start with the ADB commands:
- Type
Code:
adb push systemroot /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb push systemroot /data/local/tmp
/data/local/tmp/systemroot/: 8 files pushed. 0 files skipped. 10.0 MB/s (7072263 bytes in 0.673s)
- Type
Code:
adb shell chmod -R 7777 /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell chmod -R 7777 /data/local/tmp
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>
- Type
Code:
adb shell setsid su
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell setsid su
(It will be blank with the blinking cursor, move to next step)
- Type
Code:
id
(you should at this point see that your are in a root shell!)
What it will look like:
id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
- Type
Code:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
What it will look like:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
(Again, it will be blank with a blinking cursor after you type the command in, move to next step)
- WAIT ABOUT 30 SECONDS BEFORE MOVING TO THE NEXT COMMAND
- Type "
Code:
mount
" (you should now see rw next to rootfs and system partitions)
What it will look like:
mount
(After we type in mount, we are looking for the below two items to say rw like they do in the next two lines)
rootfs on / type rootfs (rw,seclabel,size=1586716k,nr_inodes=396679)
/dev/block/sda19 on /system type ext4 (rw,seclabel,relatime)
- Type
Code:
sh /data/local/tmp/systemroot/root.sh
What it will look like:
sh /data/local/tmp/systemroot/root.sh
rm: /system/bin/install-recovery.sh: No such file or directory
cp: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
chcon: /system/bin/.ext/.su: No such file or directory
touch: '/data/.supersu': Permission denied
/data/local/tmp/systemroot/root.sh[55]: can't create /data/.supersu: Permission denied
chmod: /data/.supersu: No such file or directory
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot\NEWSAMPWNDFILES>
5) If you followed all of the above commands to the T, your device will reboot and you will have SuperSU installed.
6) Install Flashfire from the Play Store.
7) Up to this point, you are on an ENG system.img with root that doesn't function the way we would like it to. This means you will feel a vibrate every time you try to gain SU access as well as it will take quite a while for an SU prompt. You can stay on this root if you would like to experiment with the ENG system, but outside of that I would HIGHLY recommend you proceed to the STEP 2 PROCESS.
PART 2 Instructions:
1) Download the PART 2 FILES listed below (this includes the system.img.ext4 and the add CSC Systemroot zip both provided courtesy of @jrkruse , view post #195 for specifics on what these are but essentially they are stock QD2 system.img and the zip has multi CSC, root, and a bunch of other goodies!)
2) Extract the System.img.ext4 zip and place that actual "system.img.ext4" onto the Internal SD Card (might work from external but some users have reported issues with chainfires root.zip and FF with external sd cards, this is not a fault of the SamPWND files/process.)
3) Place the entire Add CSC Systemroot zip onto Internal or Externdal SD Card (THIS FILE DOES NOT NEED TO BE UNZIPPED, THROW THE WHOLE ZIP FILE ONTO SD CARD OR INTERNAL)
4) Open Flashfire and grant it root when it prompts you. IF FLASHFIRE IS NOT LOADING FILES AND YOU JUST SEE A CIRCLE OR LIKE ITS CONSTANTLY LOADING, PUT THE PHONE IN AIRPLANE MODE AND THEN GO BACK INTO FLASHFIRE AND THE FILES SHOULD NOW APPEAR.
5) Press the + sign and select "Flash Firmware Package" & navigate to where you placed the system.img.ext4 and select it
6) Press the + sign and select "Flash ZIP or OTA" & navigate to where you placed the Add CSC Systemroot zip and select it, select Mount System as r/w
7) Press the + sign and select "Wipe" and select System data, 3rd party apps, Dalvik cache, Cache partiton, Cache Partiton format
8) Now, long press on "Wipe" and make sure it is on the top by dragging it. The order should be Wipe, Flash Firmware Package & finally Flash ZIP or OTA
9) Make sure the "Everoot" is disabled!
10) Flash away!
If you followed all of PART 1, then followed all of PART 2, then you will be updated to QD2, rooted with busybox (and have some other goodies) and the phone will be running great! Root will be stable and snappy as ever. Adaway, Root Checker, V4A etc. etc. are now all possible.
XDA:DevDB Information
S8 Plus SamPWND ROOT, ROM for the Samsung Galaxy S8+
Contributors
elliwigy
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 7.0, Any Current Firmware
Based On: Stock Touchwiz
Version Information
Status: Beta
Current Stable Version: 1
Stable Release Date: 2017-08-19
Current Beta Version: 1
Beta Release Date: 2017-08-19
Created 2017-08-19
Last Updated 2017-08-19

DOWNLOADS SECTION:
PART 1 FILES:
SamPWND_Root.zip
https://mega.nz/#!8YcgTSwI!hIfbdJZ466sr1AyfiHLdtr1p-To0QdthTPDmVwtv0dc
Initial ODIN 4 Files FIRMWARE
https://mega.nz/#!5cUjnCwK!Zgw5_CaINbES08gwDzl7yMN0N4nzm56Fa12ow-gppKA
Mirror: https://www.androidfilehost.com/?fid=961840155545589828
AFH MD5: 73720c409782b751355b9443a003a6e8
Normal + Comsey ODIN
https://mega.nz/#!cFN2DD4C!I7AT4TgNSzBp7Py0UhC7pHZ0M4WDQhEC5qj2xD_qluM
Systemroot + ADB zip - OLD
https://mega.nz/#!1MVDhZxQ!Wd4Umvju1sS1DAe-jBcTue9NKSJ4co0I2gwiyC3c2pE
PART 2 FILES: (Potentially will be providing a rom.zip soon that will have latest updated U1 with multi CSC pre-rooted with other goodies)
system.img.ext4
https://www.androidfilehost.com/?fid=817550096634794132
Add CSC Systemroot
https://www.androidfilehost.com/?fid=745425885120757028
For more info on these files please see @jrkruse post located here:
https://forum.xda-developers.com/showpost.php?p=73489978&postcount=925
THANK HIM WHILE YOU'RE AT IT!

@elliwigy @Harry44 @akiraO1 @BotsOne
These months these four people are very hard, and I very relaxed!! lol

Cool Job!

GSM CHEN said:
@[email protected]@[email protected]
These months these four people are very hard, and I very relaxed!! lol
Click to expand...
Click to collapse
haha but we know it wouldnt be possible without you man

Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......

theboz1419 said:
Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......
Click to expand...
Click to collapse
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol

Awesome can't wait to try this out soon!

elliwigy said:
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol
Click to expand...
Click to collapse
You are forgiven, lol. I figured it would be out in the morning, just not this early in the morning.
You guys should have gotten some sleep you may need it after this weekend.

What a nice thing to wake up to when I'm getting ready to head to work at 530 in the morning lol. Can't wait to give this a shot once I get off work 12 hours later. Thanks for everything devs.

S8 thread will be posted tomorrow, too late to do it tonight

You guys are the ****. Thanks for all of your hard work.

Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]

Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.

Wow,. I honestly didn't think it was possible. Amazing accomplishment ellwigy.
Sent from my SM-G955W using XDA-Developers Legacy app

powerstroke said:
Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.
Click to expand...
Click to collapse
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Also do we need to back up our EFS/Imei stuff? I know its recommended when flashing roms in recovery but our bootloader is locked.... Is there a way to back up without root?
Edit* I asked about the backup before in a previous thread but didn't get an answer.... Sorry to ask again

Techvir said:
Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]
Click to expand...
Click to collapse
Knox is not triggered

Kjc99 said:
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol

powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
If you have the system.img for the latest update then correct, if not and you want those features with root you will have to download the AP and CSC from thw firmware you want

powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
I have the U1 model so I'm not sure...
Edit* Deleted