Develop Bugs

[Q] Question: Supposed Quick Root Method Usning Androot/Rom Maqnager Need Help!!!

Ok so I started the method previously posted before it was linked back to nbecthers method because it supposedly works but I flashed the clockwork it wouldn't flash my custom rom (CM Mod 6.1.1) and returned me to the stock then I tried the correct method and it won't let me adb push flash_img/data/local or mtg0.img to data/local either so I can't cd, chmod the commands to then boot into the stock recovery and flash esprimg.zip followed by clockwork(update.zip cause its already applied but NAND protection stops it from working I guess) because I no longer have a stock recovery to exploit or whatever I have clockwork I have since used androot and root explorer for root used to copy flash_image and mtg0.img to data/local and exploid is in the sqlite_stmt_journals as it should be... So can I run the commands to run flash image and mtg0.img and exploid again from and android shell off my phone with su permissions from androot temp root and then flash a custom image or am a screwed? Or should I run the exploid command toggle wifi and then the flash/mtg commands from android shell or what cause I'm away from a pc and I need to do this to my phone plus it goes to the triangle screen and nothing works I gotta pull the battery...

Honestly, start from ground zero of the updated for 12/30 root method and you will be just fine. Just messing around earlier today I unrooted and rerooted my phone a few times. Stick with eugene373's method from step one on and things should work fine.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I recommend using the one involving the exploid file, it's very simple.

NVM!!! I Stumbled Upon My Own NO PC QUICK ROOT Method!
aaldiar said:
Honestly, start from ground zero of the updated for 12/30 root method and you will be just fine. Just messing around earlier today I unrooted and rerooted my phone a few times. Stick with eugene373's method from step one on and things should work fine.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Ok so in my never ending struggle against the Evil Eclair/T-Mo/HTC NAND Protection and the Futility of Trying to flash a ROM With the "Supposed AndRoot QuIck Root Method" As well as a fine point from Nbetcher that the Engineering build must be flashed because Android has NAND protection while running. I have devised my own "No PC ROOT Method!!!"
Required Files (Tested For MT3G SLIDE Latest OTA Unrooted Stock)
1.Download Androot From Location of Choosing (I'm Using Version 1.6.2)
2.Download ESPRIMG.zip (ENG build)
3.Download SlideEng-Package.zip
4.Download Custom Rom Of Your Choosing(Mine Is CM 6.1.1 Stable)
5.Download Android Terminal Emulator(From Market)
6.Download Root Explorer Android (Requires Root) (From Market Or Some Place Online)
7.Download File Explorer (Dev:Adao Team)(From Android Market)
8.Download Latest Clockwork Recovery(I Used 2.5.0.1)
Please Not I Am NOT The DEV Behind these Apps nor am I Resposible For Any Damages You May Incur To Your Device or Warranty by using this Method! Also Before anyone says I repped someone off remeber I accidentally discovered this using 2 failed methods because they essentially cancel each other out.(The Latter Nbetchers works just not after the AndRoot One)!!!
So...
1st Download/Install all needed files from market( File Manager Android Terminal Emulator)
2nd Download all zip images, Recoveries, Roms, apps from phone browser Directly To SD ROOT(Google em until I get links up on Dev Forum)
3rd. Unzip SlideEng-Package.zip To Root using File Manager or Other Zip Program for android(Andro-Zip Works Well)
4th Change Name of Clockwork to Update.zip(Case Sensative)
5th Install AndRoot And Run Root Me With Install Su & Temp Root/Unroot After Reboot Selected(Or Else You Will Boot Loop)
6th Install And Run Root Explorer then Copy and paste flash_img and mtd0.img to /data/local on android device by multi-select copy then RM R/W in program in upper left on data local folder.
7th IMPORTANT!!! Long Press and hold each copied file and set permissions to allow read and write on both user and the lowest option (I Think Dev or system)
8th Run Android Terminal Emulator and type the following commands verbatim spaces included Pressing enter after each line($ n # will be there provided you follwed all steps if not go back to androot and root again):
$ su
# cd /data/local
# chmod 04755 flash_image
# ./flash_image misc mtd0.img
Now power off and reboot using VOL-DOWN + POWER
It'll reboot into the HBoot Screen and ask if you want to Check ESPRIMG.zip after Verifying it will ask you to flash Select Yes (VOL-UP) And Wait DO NOT POWER DOWN OR TAKE OUT BATTERY!!!
Once its Completed it will ask you to Reboot select no Instead and Go To Recovery
Now Select APPLY Update.zip to flash CLOCKWORK RECOVERY YAY!!! :-D Now We Can Flash a Custom Rom With Root and Even Go As Far As S-OFF!!! But Please Be Sure Its Already On Your Micro SD...
Select Wipe Data Factory Reset by Scrolling with VOL- UP/DOWN or Track Pad and Use Power/Trackpad TO Select.
Now Use Install Zip from SD Card to Install Custom Rom(Flash GApps Second if downloaded and desired if using CM Mod 6.1.1) Now Reboot And Enjoy!!! If you Wanna Flash Anything Else Use Rom Manager From Market and Som Custom Roms to Boot into Clockwork!!! Thanks to all the Devs and their tools and immense knowledge for Making this Possible! Thanks To All The ROM Chefs Too!!!

Unroot defy superoneclick 2.1

1 Im sorry for my english,im spanish
2 ive got superuser and i dont want this ,but i know that the solution is unroot but my defy JRDNEM_U3_3.4.311_BLUR_SIGN_SIGNED in superonclik i dont see option unroot,can you help me?
Thanks

Here's a quote from another XDA thread which can help you get rid of superuser without voiding the guarantee
XDA thread said:
adb shell
su
Step 6) If you get "permission denied" or something like that from step 5a/5b,
CONGRATULATIONS! YOUR PHONE HAS BEEN SUCCESSFULLY UNROOTED!
Step 7) If you don`t want to void your warranty, you should unistall applications that require root, especially Superuser
To date, I have rooted and unrooted my phone (Backflip) 3 times without any problems. In case your phone can`t be booted up, only to the bootloader or recovery, DO NOT WORRY! You can use the adb (android debug bridge) to flash in the stock recovery, push/pull the updates and reboot the phone into recovery mode or normal mode!!!
Useful ADB commands
Reboot Phone
adb shell
reboot
Reboot Phone into recovery mode
adb shell
reboot recovery
Flash a new recovery image temporarily (resets when rebooting)
adb shell
flash_image recovery /sdcard/recovery.img
Flash a new recovery image that does not reset when rebooting
adb shell
flash_image recovery /sdcard/recovery.img
exit
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Push file to sdcard
adb push file.blah /sdcard/file.blah
Push file to sdcard
adb pull /sdcard/file.blah file.blah
Click to expand...
Click to collapse
OR try this:
* The first step is to enable USB debugging mode on your device. You can enable USB debugging on your phone by going to Menu > Settings > Applications > Development and check mark USB Debugging.
* Now Download one click root file, extract the contents and save them on your desktop [or wherever your prefer].
* Now connect your phone to the computer and double click on Galaxy S I9000 One-Click Root file.
* Now simply click One-Click Root 2.1 or 2.2 on the screen and follow the onscreen command mode instructions to complete the root process. Please note that for One-click root 2.1, your phone needs to be running Android 2.2 2.1 Eclair and for One-click Root 2.2, Android 2.2 Froyo.
* In case you are using this application to unroot your phone then simply follow the instructions above and click on One-click Unroot.

Old superoneclick versions don't have unroot option. The new versions have. If superuser is still there after unroot, you can uninstall it like uninstalling other app.

Thanks every all but i dont want of new flash a,d log time i do z4root and has unroot and superoneclick no,the version old have goot unroot but this not,and remember ive got defy im not Galaxy I9000 S

[ROOT] Rooting the Fujitsu Arrows X LTE Docomo F-05D

Thanks go to goroh_kun, ayati and DoomLord. All the usual warnings about attempting to root a phone apply. This works on a phone with build number V16R24C, which is current as of this writing. I can't speak for any later updates.
You will need the following:
Java SDK (required for android dev kit – get the JDK): http://www.oracle.com/technetwork/java/javase/downloads/index.html
ADK: http://developer.android.com/sdk/index.html
ADB driver: http://spf.fmworld.net/oss/usb_driver/f-05d/index.html
F-05D rooting files: http://ayati.cocolog-nifty.com/blog/files/F05Droot.zip
zergRush files (tested with v4): http://forum.xda-developers.com/showthread.php?t=1319653
Optional:
- a terminal application of your choice
- busybox installer from the market
- English versions of the .bat files (remove the .txt extension): http://pastebin.com/RBCWvzES and http://pastebin.com/EQfjpDAM
Part 1, installing the ADB driver:
1. Install the JDK
2. Install the ADK
3. Go to C:\Users\YourUsername\.android and edit the adb_usb.ini file.
4. Add 0x04C5 on a separate line at the bottom. Save and close the file.
5. Reboot the computer or restart adb
6. On the phone, press home, settings, applications – toggle Unknown sources to On.
7. Same place, press development and toggle USB debugging to On.
8. Connect the phone to the PC, and when prompted, navigate to the location where you extracted the ADB driver.
Part 2, rooting the phone:
1. Extract the zergRush and rooting files to the same folder. (put the English versions in the same spot if want to use them instead).
2. With the phone connected and in debug mode, run the f05dsu.bat file (DO NOT RIGHT CLICK AND SELECT RUN AS ADMIN).
3. You first will get asked to go to Settings, Setting my body, Step/activity counter app, Pedometer use, is turned On. Press space after doing that.
4. You will then get asked to toggle the same setting OFF once, then back to ON. After doing that, press space and the phone will reboot
5. Wait for the phone to reboot and connect over USB properly. Press space when ready.
6. Files will be transferred over and the phone rooted. If you don't get any errors, press space and wait for the phone to reboot again.
7. The phone should now be rebooted, and you can install Busybox and Superuser from the market.
I had trouble getting the Busybox installers to work properly at first – the stericson one would wipe su and require re-running the f05dsu.bat, and the jrummy one would simply not start properly. I suggest trying the jrummy16 installer first just to see if it runs. In the end I had to do things manually to get it installed, but once that was done both installers worked fine.
Part 3, optional, installing Busybox manually:
1. If superuser has been lost, re-root the phone.
2. Open up your favorite terminal application and enter the following manually:
Code:
su
soff
mount -o rw,remount /system /system
dd if=/data/local/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
dd if=/data/local/su of=/system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
echo insmod /data/local/lsm_disabler.ko > /system/xbin/soff
chmod 755 /system/xbin/soff
At this point you should be able to do a "which su" and get /system/xbin/su as a response. If you don't get any response, Busybox is not properly installed (start over). Doing a "ls -ls /system/xbin/su" should also NOT return a symbolic link to Busybox – if it does, you'll need to copy over su from /data/local again. The same goes for soff. Once this is done, start up jrummy's Busybox installer to confirm the installed version of Busybox, and upgrade it if you want.

Thanks very much, worked well but sadly I managed to boot loop my phone after rooting it.
Now I need to SIM unlock the phone as the factory unlock code is gone.

F05D rooting
Hi there i have successfully rooted my Fujitsu F05D have root access but I can't seem to loads busy box, I have permission through superuser and it goes through the motions but at the end it says " install unsuccessful".
The files are in the system/bin folder but something is wrong. if I use busy box installer jrimmy16 it just say installing and keeps going and never stops if I got to to scripts and click fix file permissions
" run script" it too just spins round and round..
hmm any hints guys.

Don't do a forced install or whatever it's called, that's how I bootlooped and later SIM locked mine, still yet to send it back haha.

Hello, is this working?? I want to root my Docomo Fujitsu Arrows X F-10.. And also my phone keeps on rebooting Please help.. Any ideas why?

does it work on Fujitsu T-02D?

[Q] CM10, CWR, LBE Privacy Guard, Encyrpted: how to fix the unlock->crash loop?

Yes, I'm a noob, and I was simply installing applications from the store based on reviews. Thank you all for spending the time to read this post; should you respond, thank you even more!
T-Mobile Galaxy S III 16GB.
NO SD card installed! - /sdcard apparently mirrors the phone storage.
Otterbox Defender case installed by the salesman.
On PC, installed Odin 3.0.4
Rooted via http://www.redmondpie.com/how-to-root-galaxy-s-iii-att-t-mobile-or-sprint-model-tutorial/
included the CWM_SuperUser_v3.0.7.zip file from there
Failed to get CM10 installed
Installed ClockworkRecoveryMod 5.8.4.6
Installed CM10 (20121110 Nightly)
Installed Google Apps
Set a long password
** Encrypted storage **
Installed GetJar, Google Play, DroidWall
Set Droidwall to whitelist mode; allowed only GetJar and Google Play store/Download app/Play services access.
Installed LBE Privacy Guard (I had no idea there was any issue with JB)
Granted LBE Privacy Guard Superuser and let it remember SU rights (that was a mistake too)
On PC (Windows 7), installed Android SDK 20.0.3
On PC, used SDK to download platform tools and Google USB driver.
Attempted to follow tmpfs instructions in http://forum.xda-developers.com/showthread.php?t=1401813&page=2
ADB shell responds with "device not found" when in the CWR screen.
ADB shell has a limited amount of time to respond when in the main OS after the decryption password is entered.
After booting the phone into the main OS and decrypting the phone, I can get the normal unlock kscreen. However, the screen goes blank and re-locks right around the time I can get my unlock password entered - if I go really fast, I have a second or two after. Eventually it reboots itself and the cycle starts over.
I can definitely use the power button at the decyrption screen to reboot into recovery or download modes.
In the CWR screen, of course, I can't mount /sdcard, since it's encrypted.
How can I recover to a useful function, either by disabling LBE Privacy Guard, deleting LBE Privacy Guard, or resetting the phone to bare CM10 and/or stock?

On PC:
Followed wiki Howto:_Install_the_Android_SDK
Note that device showed up as Samsung.... before, now it's Android ADB Interface.
Tried again
boot in Recovery
ok
format cache partition
"wipe cache partiton" ok
adb shell mount -t tmpfs none /sdcard
no error
adb push cm-10-20121110-NIGHTLY-d2tmo.zip /sdcard
168375589 bytes in 31.947s
use the recovery to flesh the ROM as usual
??? I tried:
install zip from sdcard
choose zip from sdcard
And the SIII responded:
E:Can't mount /sdcard/
I then tried
adb shell
df
And saw no sdcard
ls -al
showed that the CM-10 was now "sdcard", so I tried:
mv sdcard cm10.zip
mkdir sdcard
mount -t tmpfs none /sdcard
df
this shows /sdcard is a "none" filesystem
mv cm10.zip sdcard
cd sdcard
ls -al
shows cm10.zip
In CWR, I again try "choose zip from sdcard
And again get:
E:Can't mount /sdcard/
In adb shell, I see
df
none 849028 164600 684428 19% /sdcard
ls -al | grep sdcard
drwxrwxrwt 2 root root 60 Jan 3 20:02 sdcard
Again, if anyone can provide me with some assistance, I'd appreciate it.

The actual set of fixes:
1) To remove LBE Privacy Guard, boot into "Safe Mode" by holding down just the lower left "menu" touch sensitive button (NOT the actual home button) during a reboot. Then remove LBE Privacy Guard.
You can then use the phone. Regrettably, neither CWM nor TWRP can see the encrypted data, nor back it up, nor install files from it. Goomanager doesn't, therefore, appear to be able to apply updates to it. Overall, the system tools on Android are just not capable of handling an encrypted device at this point in time.
2) To remove encyrption and allow most of the system level apps to work again:
2a) Back everything up as best you can. I used Titanium Backup Free and Mybackup Root Free to do inital backups, and then "adb root" and "adb pull / drive:\path" to get as much as I could of that local. I also used "adb pull /data/data drive:\path" (or maybe it was "adb pull /data/data/ drive:\path") to make sure I got "drive\path\com.android.providers.contacts\databases" which contains the SQLite Contacts database, just in case.
2b) Boot into TWRP (installed via Goomanager)
!!? Probably not required ?!! 2c) Wipe everything - EVERYTHING. Format EVERYTHING, even when it warns it could be bad.
2d) Use Odin to load up the Stock Root66 rooted ROM from the thread: T-Mobile, Wind, Mobilicity, Videotron Samsung Galaxy S III > T-Mobile Galaxy S III Android Development > [Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates! (sorry, no hotlink - I don't have enough posts)
2di) Remember to follow the instructions in page 2 of that thread VERY CAREFULLY
2e) Boot into Recovery mode again after the device tries to ask you for the encryption password (which no longer works). Then wipe the /data partition entirely. Reboot again
2f) Now you can go through initial setup on your rooted phone and install your preferred ROM normally.

TryingToBeBetter said:
The actual set of fixes:
1) To remove LBE Privacy Guard, boot into "Safe Mode" by holding down just the lower left "menu" touch sensitive button (NOT the actual home button) during a reboot. Then remove LBE Privacy Guard.
You can then use the phone. Regrettably, neither CWM nor TWRP can see the encrypted data, nor back it up, nor install files from it. Goomanager doesn't, therefore, appear to be able to apply updates to it. Overall, the system tools on Android are just not capable of handling an encrypted device at this point in time.
2) To remove encyrption and allow most of the system level apps to work again:
2a) Back everything up as best you can. I used Titanium Backup Free and Mybackup Root Free to do inital backups, and then "adb root" and "adb pull / drive:\path" to get as much as I could of that local. I also used "adb pull /data/data drive:\path" (or maybe it was "adb pull /data/data/ drive:\path") to make sure I got "drive\path\com.android.providers.contacts\databases" which contains the SQLite Contacts database, just in case.
2b) Boot into TWRP (installed via Goomanager)
!!? Probably not required ?!! 2c) Wipe everything - EVERYTHING. Format EVERYTHING, even when it warns it could be bad.
2d) Use Odin to load up the Stock Root66 rooted ROM from the thread: T-Mobile, Wind, Mobilicity, Videotron Samsung Galaxy S III > T-Mobile Galaxy S III Android Development > [Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates! (sorry, no hotlink - I don't have enough posts)
2di) Remember to follow the instructions in page 2 of that thread VERY CAREFULLY
2e) Boot into Recovery mode again after the device tries to ask you for the encryption password (which no longer works). Then wipe the /data partition entirely. Reboot again
2f) Now you can go through initial setup on your rooted phone and install your preferred ROM normally.
Click to expand...
Click to collapse
did this work for anyone?
EDIT: I just fixed permissions and was able to get back into the phone and uninstall LBE from the play store.

[TUTORIAL]All you need to know to flash a ROM on LG-P350

Hi guys, this is my second tutorial and in this one I will show you every thing you need to do to flash a custom ROM on the LG-P350. So let's get started.
DISCLAIMER: This is tampering with the system itself and if done incorrectly a simple factory reset will not fix it. It is YOU who is doing this on your phone and I am in no way responsible if any damage happens to your device. (tough it shouldn't if you follow these steps carefully) You have been warned!
WHAT WE NEED :
1.An LG-P350 running stock Froyo
2.LG mobile united drivers, get them from here https://docs.google.com/file/d/0B7Faau7Enf-Bc1hhbWRtTkczNEE/edit?usp=sharing
3.A PC running Windows (can be done on linux too but this guide is based on Windows)
4.A microUSB data cable.
5.The official Android SDK obtained from http://developer.android.com/sdk/index.html Make sure you select the version for your OS (32-bit or 64-bit)
6.USB debugging to be on. Go to Settings>Apps>Development>Turn on USB debugging
7.ADB to be properly set up.
8.Patience to read this thread carefully
1. Root
Ok so what is root? Well simply said rooting gives us the permission to modify parts of the Android system itself. Normally when you try to tamper with it it would simply say that either you don't have the privilege to do so or it would fail. When we have root permissions then you can change anything you want.
Note: Be careful tough, removing or modifying some parts of the system can damage the system and prevent it from working/booting. Always make a nandroid backup (will talk about this later) before editing anything in the system.
Now for the rooting itself.
Most versions of the software for the P-350 can be rooted using gingerbreak, which can be found here http://forum.xda-developers.com/showthread.php?t=1044765 Get the newest version, copy it and install it on your phone and follow the instructions on screen.
For those who prefer some other root method you can also use z4root which can be found here http://forum.xda-developers.com/showthread.php?t=833953 or superoneclick which can be obtained here http://forum.xda-developers.com/showthread.php?t=803682 (For superoneclick you need the USB cable and drivers installed)
2.ADB
Ok so what is ADB? ADB is a short term for Android Debug Bridge. It is one the most essential tools in the Android world and is used for a number of things such as sending commands (which can do anything you imagine with the device), getting various log data etc.
To set it up you will have to get the latest version of the official Android SDK (look for the link in the Introduction). Once you've downloaded the sdk you will get a .zip file you need to extract. I extracted mine to C:\Program Files (x86)\Android\ (so this guide is based on that) but it can really be anywhere. If you decide to put a different directory then adapt the guide to it. Once extracted you will get two folders. Here we only use the sdk one, the other one is for the Eclipse plugin used for application development. Open up the cmd from the start menu and then input these codes.
Code:
cd C:\Program Files (x86)\Android\sdk\platform-tools\ (you adapt this to your case if you didn't extract it there)
adb shell
Do this with your device connected otherwise it's pointless.
NOTE1: In order for adb to recognize your device you must have the drivers installed.
NOTE2: If you are too lazy to type all this every time you can make a .bat script. Open up notepad and copy/paste these codes
Code:
cd C:\Program Files (x86)\Android\sdk\platform-tools\ (adapt to your location)
adb shell
pause
After that just click on File and click Save as. In the window that opened, under file type select all files and on the file name save it as adb.bat
Now whenever you want to use adb you can just double click on the script you made and it will open up adb instantly leaving out the hassle of typing in commands every time.
3.Recovery
Now that we have root it's time for the recovery module.
The recovery allows us to modify parts (or even the entire) system by "flashing" (installing) .zip files prepared by our developer. They can be tweaks,fixes, additional features or even a completely new version of Android. There are a couple of ways to do this and the choice is yours.
Before you do this you need to get a recovery image. We have a couple of them for our device:
1. AmonRa-The very first recovery for our phone. It is outdated and generally not recommended for use. If anyone wants it you can get it here http://forum.xda-developers.com/showthread.php?t=1080911
2. CWM (clockwork mod recovery)- One of the most popular recoveries around. It is a well made piece of software which will make flashing simple and fast. We have a couple of versions for our phone and the links are here:
http://forum.xda-developers.com/showthread.php?t=2075797&highlight=recovery ClockWorkMod 6.0.2.7
http://forum.xda-developers.com/showthread.php?t=1768895&highlight=recovery ClockWorkMod 6.0.1.4
You will also need a flash_image file gotten from https://docs.google.com/file/d/0B7Faau7Enf-BTURDQmp1OWIzVGM/edit?usp=sharing
Method 1: cmd
Ok so this tutorial is from a developer who has retired and who made the original recovery our phone. All credits for that go to him.
Also note that it is recommended to reboot the device prior to flashing to increase the RAM.
1.Copy the .img file and copy the flash_image file to the rood directory of your sd card NOT in some folder. If you got your recovery in a .zip then extract the .img file from it and copy it and the flash_image file to the root of the sd card.
2.Using ADB shell copy these commands into the cmd :
Code:
$ 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
3.Now flash it:
Code:
$ su
# flash_image recovery /sdcard/*insert image name here*.img Here you should put the name of your .img file without the starts ofc :)
# sync
4.After that if no error occurred you can type this in
Code:
reboot recovery
WARNING: If some sort of error showed up DO NOT type in reboot recovery. This could brick your device. Instead restart the phone and start over.
Method 2: Venkat's toolkit RECOMMENDED
This toolkit does the same from above but it does it automatically without the user having to do anything. You can get it from here http://forum.xda-developers.com/showthread.php?t=1948326 It can also be used for rooting.
It is also recommended to make a nandroid backup of your current system in case you want to go back. Nandroid backup is a complete copy of your system as it is when the backup was made. It backs up EVERYTING not just apps and data, so it is a perfect thing to have if a ROM or a tweak you are trying render the phone unbootable since you can just restore the backup you made and no harm done.
That is recovery. Now you can use it to flash whichever ROM for our device you choose. You can boot to it either by typing in adb/terminal reboot recovery or by pressing the following buttons when the device is turned off: Power + Call + Volume Down. Also don't worry if the touchscreen doesn't work in the recovery. That is normal use the volume up and down buttons to navigate menus and either the menu button(for amon ra) or the call (CWM) to confirm your choice.Use the back/power button to cancel/go back.
4.Flashing
Flashing is a process where we install the entire system or its parts contained in .zip files from the recovery module.
NOTE When you get a flashable .zip package DON'T extract it to the sd card. Copy it as you got it to the root of the sd and then continue.
Now that you've gotten the ROM you desired the process is pretty straight forward. Copy the .zip file you got to the root directory of your sd. Once you've done that, reboot to recovery and make a nandroid backup (if you haven't done so already) and go to the option install zip from sd card. Then choose the .zip you copied and confirm. After it says install complete you can reboot your device.
NOTE 1: Flash only things that are either universal or made for this device. Flashing stuff not made to work on this device could damage it.
NOTE 2: When flashing new ROMs you MUST wipe Dalvik cache,cache and data partitions. It is also recommended to wipe Dalvik cache when flashing kernels.
Those are pretty much all the basics you need to get into the flashing stuff You can find loads of ROMs and other tweaks on the official P-350 forums here on xda http://forum.xda-developers.com/forumdisplay.php?f=1769
You can also find info and development support on our Facebook page https://www.facebook.com/groups/p350development/

Revision 1: Added tutorial for setting up adb, explaining what adb is, as well as an adb script code.

i think this thread need to stick, try to contact mods

A comment on the 'adb' way. Before executing the commands, you might want to cd to where adb.exe is because you will have an error executing the command and the terminal will show 'adb is not a valid command'
Sent from my X8 using xda premium
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
And installing android sdk is optional because there are standalone adb available for download.
Sent from my X8 using xda premium

Ya sticky this thread mods, cuz' i read, Many people stuck at LG Logo or fastboot mode even hard reset when flashing ROM without recovery before..
Sent from my LG-P350 using xda app-developers app

rho57 said:
A comment on the 'adb' way. Before executing the commands, you might want to cd to where adb.exe is because you will have an error executing the command and the terminal will show 'adb is not a valid command'
Sent from my X8 using xda premium
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
And installing android sdk is optional because there are standalone adb available for download.
Sent from my X8 using xda premium
Click to expand...
Click to collapse
It already is set to the adb.exe path that's needed in order for adb to be activated on Windows. That's why we use the cd C:\Program Files (x86)\Android\sdk\platform-tools
And I know but there are a lot of other useful tools as well. And it is most reliable too.

Good job dude

Why complicated more then needed. Just make tut with andking toolkit.

boyan81 said:
Why complicated more then needed. Just make tut with andking toolkit.
Click to expand...
Click to collapse
Not complicated, this is a basic tutorial for those who don't want/can't use his toolkit. It also has some explanations about basic Android terms which you won't find there.

It would be nice if you update the wiki too, as there is an old but yet usable guide which pretty much has the same information written here...
Sent from my GT-S5830M using Tapatalk 2