Related
ive flashed to Android 1.6 Recovery Image. and my market doesnt work nor can i flash to anything else.. it will start the update and then abort.. is there anything i can do?
oh my goodness...wrong forum, were u trying 2 flash Cyanogens rom?
yes i was =( can you please direct me to the correct place to ask for help.. thanks in advance
the mods will move it soon, and did u not follow the directions in Cyanogens thread, [email protected] usually all u need
i somehow managed to skip a step .. and i really messed up =(
well idn cuz this has never happend to me, but try a wipe and try reflashing the recovery image, and the rom, but dont skip a step
Help has Arrived!
Cyan's 1.4 Pimped Out Recovery Image:http://forum.xda-developers.com/showthread.php?p=3915123
To install image: copy it to your sdcard and run:
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a “no space on device” error, try using fastboot and erasing first:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
Changes in 1.4:
* Flash ANY .zip from your SD – by krut0n
* New color scheme and images (background from a random wallpaper site, if it’s yours let me know)
* Fixes from Donut
* Updated nandroid-mobile.sh w/ network support from pensive
* Updated GNU Parted (ext4 support, etc)
TMO OTA DRC83 - US
-- Rooted Base - http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO-OTA-US-DRC83-Rooted_update.zip
----- v1.9.2 Expansion Pack - (10/4/2009)http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO_1.6_ExpPack_v1.9.2.zip
CM-4.1.99+
Install instructions from SimpleHelp:http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Install instructions for an HTC Dream/ADP1/G1:
1- Perform a Backup......nandroid, etc
2- Download:http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image.This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download Cyan's ROM. Posted Below
4- Mount your phone and place BOTH 1.6 Image and my ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
8- Apply sdcard:choose zip *Pick cm-4.1.99-signed.zip* from the list.
9- Reboot!
(v4.1.999 - almost-stable-beta version, updated 10/4):
Download:http://n0rp.chemlab.org/android/experimental/update-cm-4.1.999-signed.zip
Mirror1:http://android.phaseburn.net/mirrors/cyanogen/experimental/update-cm-4.1.999-signed.zip
MD5Sum: 7f8b377c5ded60e057140119ab2a3fbd
Audio Resources (unzip to your SD card):
Download:http://n0rp.chemlab.org/android/audio-resources.zip
MD5Sum:7340ba86ddd4fba918ef97601c675ef9
HTC Touch Input:http://forum.xda-developers.com/showthread.php?t=567294
Code Repository on Github:http://github.com/cyanogen
CHANGELOG
---- v4.1.999
* BFS-303 (fixes some regressions like statusbar fling)
* Fixed BT not working (firmware)
* Updated APN list
* New wallpapers from matt_stang
* Fixed crazy compcache settings
* Fixed syntax error in userinit startup
* Fixed build.prop files
* Patch for LocationManagerService wakelock issue
* More nines
---- v4.1.99
* Now 100% open source (TMO apps are included, not sure of licensing on those yet)
* Tons and tons of bugfixes and enhancements, read the Github logs and old threads for now
* Kernel is 2.6.29.6 with BFS-302 and framework changes to support it.
* HTC Framework and apps are gone, deal with it. See the link above for HTC_IME.
THIS SHOULD HELP YOU OUT! If not,I don't know what can help you.Keep looking if you can't figure this out. But here's the help you asked for. Good luck with the flashing man!
OR - GO to the HTC Website and Look for Android 1.6!: http://developer.htc.com/adp.html#s3
andy_lowe02 said:
Cyan's 1.4 Pimped Out Recovery Image:http://forum.xda-developers.com/showthread.php?p=3915123
To install image: copy it to your sdcard and run:
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a “no space on device” error, try using fastboot and erasing first:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
Changes in 1.4:
* Flash ANY .zip from your SD – by krut0n
* New color scheme and images (background from a random wallpaper site, if it’s yours let me know)
* Fixes from Donut
* Updated nandroid-mobile.sh w/ network support from pensive
* Updated GNU Parted (ext4 support, etc)
TMO OTA DRC83 - US
-- Rooted Base - http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO-OTA-US-DRC83-Rooted_update.zip
----- v1.9.2 Expansion Pack - (10/4/2009)http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TMO_1.6_ExpPack_v1.9.2.zip
CM-4.1.99+
Install instructions from SimpleHelp:http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Install instructions for an HTC Dream/ADP1/G1:
1- Perform a Backup......nandroid, etc
2- Download:http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image.This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download Cyan's ROM. Posted Below
4- Mount your phone and place BOTH 1.6 Image and my ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
8- Apply sdcard:choose zip *Pick cm-4.1.99-signed.zip* from the list.
9- Reboot!
(v4.1.999 - almost-stable-beta version, updated 10/4):
Download:http://n0rp.chemlab.org/android/experimental/update-cm-4.1.999-signed.zip
Mirror1:http://android.phaseburn.net/mirrors/cyanogen/experimental/update-cm-4.1.999-signed.zip
MD5Sum: 7f8b377c5ded60e057140119ab2a3fbd
Audio Resources (unzip to your SD card):
Download:http://n0rp.chemlab.org/android/audio-resources.zip
MD5Sum:7340ba86ddd4fba918ef97601c675ef9
HTC Touch Input:http://forum.xda-developers.com/showthread.php?t=567294
Code Repository on Github:http://github.com/cyanogen
CHANGELOG
---- v4.1.999
* BFS-303 (fixes some regressions like statusbar fling)
* Fixed BT not working (firmware)
* Updated APN list
* New wallpapers from matt_stang
* Fixed crazy compcache settings
* Fixed syntax error in userinit startup
* Fixed build.prop files
* Patch for LocationManagerService wakelock issue
* More nines
---- v4.1.99
* Now 100% open source (TMO apps are included, not sure of licensing on those yet)
* Tons and tons of bugfixes and enhancements, read the Github logs and old threads for now
* Kernel is 2.6.29.6 with BFS-302 and framework changes to support it.
* HTC Framework and apps are gone, deal with it. See the link above for HTC_IME.
THIS SHOULD HELP YOU OUT! If not,I don't know what can help you.Keep looking if you can't figure this out. But here's the help you asked for. Good luck with the flashing man!
OR - GO to the HTC Website and Look for Android 1.6!: http://developer.htc.com/adp.html#s3
Click to expand...
Click to collapse
If he messed up wit the instructions from the thread, idn if this is gonna help him, but we'll c
hi,
I have read a cyanogenmod wiki page about clockwork recovery / ROM manager, and naturally I am very confused.
* Where does this install? (SBL/is it called from somewhere like GRUB?)
* What does this modify?
* How does one access this? I presume via Recovery Mode - Does one tell it to boot from an update.zip file that contains a programme to run; What does this programme do, and what does it modify?
* If I install ROM Manager / Clockwork Recovery, then if I decide to return the SGS to Samsung for warranty reasons, and I have not installed any other ROMS (e.g it is running stock), then will Samsung notice anything if they look, other than the update.zip file on the SD card.
* Can the installation and booting ClockWork Recovery damage *anything* on the SGS? (I mean only running it, and not installing any ROM images etc.
Best regards, me.
* Installing ClockworkMod Recovery
If you flashed a previous version of ClockworkMod Recovery using Odin, Flash back to a Stock Kernel using this Odin package: will add soon
Search for ROM Manager in the Market (free or paid) and install the app.
Open the ROM Manager application and choose the first option in the app, Flash ClockworkMod Recovery.
Click on your device Samsung Galaxy S i9000 and then you may need to give the app root permission if it prompts you. If it does prompt for Superuser access, make sure Remember or Always is selected before you choose Allow.
If it hangs after that and freezes up, just allow the app to Force Close. Then open it back up and repeat steps 2 & 3.
Optional: Choose Backup Current ROM from the ROM Manager to create a backup.
On the very first boot of the ClockworkMod Recovery, you may need to manually select "reinstall packages" if the ClockworkMod Recovery does not start. You should only ever have to do this once. It will be automatic from then on.
If the flash was successful a dialog box should pop up saying "Successfully flashed ClockworkMod recovery!". Press OK.
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 8.0 [2012 MODEL] - Drivers, Root, Recovery + MORE
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports a multitude of Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
SUPPORTED MODELS
GT-N5100 3G/WIFI MODEL
GT-N5110 WIFI ONLY MODEL
GT-N5120 LTE MODEL
Click to expand...
Click to collapse
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.3 [8TH DEC 2014]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
Enable Developer options for usb debugging
Go to Settings, System section, About device and tap on 'Build number' 7 times until it says you are now a developer. You can now go to Settings, System section, Developer options and enable USB debug.
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the device.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the device.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.2).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
This feature will be added to the Toolkit after testing has been completed.
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
*reserved if needed*
Mskip
thanks for this
is your version of cwm working properly?
thanks
jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
I think that's for us us to test and tell him
sefrcoko said:
I think that's for us us to test and tell him
Click to expand...
Click to collapse
It's the same version as provided in the development thread.
i flashed the cwm
but cant do anything
cant even reboot
jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
CWM is the experimental port from emwno in *THIS* thread.
I need people to test if the insecure boot image flashes and whether the root process works.
Mark.
madsatan said:
i flashed the cwm
but cant do anything
cant even reboot
Click to expand...
Click to collapse
Flashing custom recovery shouldnt affect the boot process have you tried just holding the power button for about 15 seconds to force a hard reboot?
Are there any lights or anything on the screen?
Mark.
Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app
madsatan said:
Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
As stated the cwm port is still experimental but it is being worked on by emwno and im sure he will get there.
Has anyone tried the root procedure yet with the insecure boot image? I really need some feedback here.
Mark.
Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now
ktmman said:
Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now
Click to expand...
Click to collapse
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.
mskip said:
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.
Click to expand...
Click to collapse
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.
ktmman said:
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.
Click to expand...
Click to collapse
Looks good
Now I just need someone with a full stock firmware flashed that can test the ALL IN ONE process and perform a NAND backup to make sure it works from scratch. Any takers?
Mark.
I will try once I'm home
Sent from my GT-N5110 using Tapatalk HD
n5120
got n5120, lte. can I use tools or I have to wait for n5120 version?
thanx in advance for answer.
goo.im seems to be down. Got a mirror?
thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.
Sardo Numspa said:
thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.
Click to expand...
Click to collapse
Flash Experimental #4 for your specific device (from my thread). Its working properly now.
All credits go to Phil3759 as I just ported it to our device. Original thread, I had to change some stuff like the ramdisk and zImage to make it working on our device.
Touch driver fix (also for aroma) thanks to nickdollahz
Click to expand...
Click to collapse
I'm not responsible for your bricked device!
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 5 Recovery
CivZ version 1.1
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features of this ported recovery:
RECOVERY IS IN TABLET MODE
Touch recovery based on cwm 6.0...
zImage compiled by civato based on Samsung Update2 with Exfat support
Touch driver fixed for aroma thanks to nickdollahz
Backup / restore
Custom backup / restore
EFS backup / restore: It is stored as a hidden file in clockworkmod/backup.
Change theme layout and touch settings
TWRP and CWM restore support
Format data/media = internal_SD will be empty.
Power menu
etc..............................
Full detail from the original thread
touch interface:- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- Friendly Log View and pause on logs: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 30 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- time setting is now applied to all recovery session, including timestamp of created/modified files (v4.92.3+)
- capture recovery screen shots with a gesture action
- one file to save all settings
- backup and restore settings file
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File ManagerNote: after scroll, first touch will select only. After one sec of scrolling or on second touch, it will validate immeadiately. This is by design and not a bug. It is there to limit erroneous validation while scrolling
Read more about it here: Validation Lock after scrolling
First to introduce true JB 4.2 migration: toggle between /data/media and /data/media/0
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT, NTFS and Ext4 support in recovery for external sd
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
you can cancel any nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time incremented copies for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
dual USB mount in recovery support and mount external sd over usb for /data/media devices
adb root in recovery: just wait about a minute to activate
detailed build info in About menu
GT-N5100:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5100-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5100-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
GT-N5110:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
GT-N5120:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5120-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5120-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
CHANGELOG:
23/Okt/2013:
First touch release of this recovery ported from the Philz recovery.
24/Okt/2013: CivZ REV1.1 of the Philz touch 5 recovery
EFS backup changed to original : Backup to external or internal = It is stored as a hidden file in clockworkmod/backup.
Touch driver adjusted and rebuild the kernel for it.
Activated ntfs support in recovery kernel.
With the CWM install package the recovery filemanager is installed.
Click to expand...
Click to collapse
Maybe i forgot to tell you, until I push my sources to phil, try compiling with custom touch driver sources to get the touch interface working.
cm 10.1
plz port for us cm 10!N5100 :crying:
Is it possible to get a signed zip? I have a recovery installed, just not the CWM or TWRP (it is the stock one).
Flash this with odin, I doubt the touch will work properly. Even though, N5110 users try it.
emwno said:
Flash this with odin, I doubt the touch will work properly. Even though, N5110 users try it.
Click to expand...
Click to collapse
Touch and efs backup not working.
civato said:
Touch and efs backup not working.
Click to expand...
Click to collapse
Looks like ill wait till mine arrives and then debug alot. A question, does it not work at all? Or does it register them wrong?
EDIT: talking about the touch input
emwno said:
Looks like ill wait till mine arrives and then debug alot. A question, does it not work at all? Or does it register them wrong?
Click to expand...
Click to collapse
It register them wrong, if you look at it like a portrait mode recovery the buttons are situated for that kind of recovery.
example: pressing top right corner (landscape mode) is pressing the return button, so it is way off. But it is this way in all touch recovery's for now on this tablet. Not a real problem not having touch, for me the efs is more important.
It is the same with the aroma installer touch driver, it is way off so you need to use the hardware buttons.
civato said:
It register them wrong, if you look at it like a portrait mode recovery the buttons are situated for that kind of recovery.
example: pressing top right corner (landscape mode) is pressing the return button, so it is way off. But it is this way in all touch recovery's for now on this tablet. Not a real problem not having touch, for me the efs is more important.
It is the same with the aroma installer touch driver, it is way off so you need to use the hardware buttons.
Click to expand...
Click to collapse
This device is more of a hybrid, half of the time its acting like a tablet and other times like a phone. Ill build one for portrait now and upload in a few
---------- Update ----------
Test2. flash with odin.
1. If recovery is portrait, touch issues should be resolved
2. EFS backup should now be fixed
emwno said:
This device is more of a hybrid, half of the time its acting like a tablet and other times like a phone. Ill build one for portrait now and upload in a few
---------- Update ----------
Test2. flash with odin.
1. If recovery is portrait, touch issues should be resolved
2. EFS backup should now be fixed
Click to expand...
Click to collapse
Still in landscape so touch is still off and efs backup still doesn't work.
It looks like it makes a backup but it don't.
civato said:
Still in landscape so touch is still off and efs backup still doesn't work.
It looks like it makes a backup but it don't.
Click to expand...
Click to collapse
think ill just use ameer's script to backup everything via recovery. and about recovery being portrait, i have one more thing i can try, ill do that tomorrow. for now ill just update kernels to .79
bump?
anyone knows if there's a chance for working PhilZ in foreseeable future?
can I use this recovery instead of CWM or TWRP, flashing your ROM - CivZ-FLEXBEAM-4.2.2-Rev1.5?
on OP instruction on your ROM, it says "Install with CWM or TWRP", I am not sure if PhilZ touch works too?
I don't see why not since it is based on CWM advanced edition.
Full touch version released
New release
Download in OP :
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 5 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
Features of this ported recovery:
RECOVERY IS IN TABLET MODE
Touch recovery based on cwm 6.0...
zImage compiled by civato based on Samsung Update2 with Exfat support
Touch driver fixed for aroma thanks to nickdollahz
Backup / restore
Custom backup / restore
EFS backup / restore: backup is automatic stored as a efs.img on the internal_SD and external_SD (clockworkmod/efsbackup) This was modded by me as the original didn't work, this is based on the emwo script.
Change theme layout and touch settings
TWRP and CWM restore support
Format data/media = internal_SD will be empty.
Power menu
etc..............................
REV1.1 released
24/Okt/2013: CivZ REV1.1 of the Philz touch 5 recovery
EFS backup changed to original : Backup to external or internal = It is stored as a hidden file in clockworkmod/backup.
Touch driver adjusted and rebuild the kernel for it.
Activated ntfs support in recovery kernel.
With the CWM install package the recovery filemanager is installed.
Download in OP
Thanks civato.. In the other forums they just tell us how worthless CWM is. Here you guys fix it and make it better...Worked like a charm.. k9time
Sent from my GT-N5100 using XDA Premium 4 mobile app
Hi would this work on stock 4.1.2? Just rooted device but has no recovery ..
Sent from my GT-N5110 using xda premium
Valholy said:
Hi would this work on stock 4.1.2? Just rooted device but has no recovery ..
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
Yes it works with stock 4.1.2 but if you're on stock recovery, then you have to flash this with odin because you can't flash a custom recovery with a stock recovery. If you already have a custom recovery, then you can flash this with that, but I assume you're still on stock recovery. So:
1. You need a computer with odin and proper samsung drivers installed
2. Download the right GT-N5110 .tar file from this thread
3. Go to download mode and open odin
4. Make sure you have F.Reset time and Auto-reboot checked
5. Click on PDA and choose the .tar file and then flash it
And you're done
Sent from my GT-N5110 using XDA Premium 4 mobile app
Thanks a lot will try it out
Sent from my GT-N5110 using xda premium
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
THIS RECOVERY WILL TRIP YOUR KNOX COUNTER ..AND UR WARRANTY WILL BE VOID
THIS RECOVERY IS ONLY FOR THE S5 MINI(G800H) [QCOM MSM8228]
PLEASE BE CAREFUL ... THIS RECOVERY HASNT BEEN TESTED "FULLY"...ONLY WIPE CACHE AND DALVIK CACHE , INSTALL ZIP IS TESTED
PLEASE BACKUP YOUR DATA AND MAKE SURE YOU HAVE A BACKUP OF THE FIRMWARE BEFORE PROCEEDING..HAPPY FLASHING!
Why twrp ? Why not a pre-rooted firmware which will not void warranty?
Ans : TWRP has many more functionality than stock recovery ! Rooting means to playing around with your device.If some thing goes wrong it you have to flash the whole firmware again instead,backup your ROM through CWM and if something goes wrong restore your backup AS SIMPLE AS THAT !
All you have to do is follow my instructions :
STEP 1 :
-Download and setup ADB drivers for your device
can be found here Drivers !
STEP 2 :
-Download the recovery from ---> Link
-Download odin 3 Link
-Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy S5 Minilogo
-Press vol up to confirm
STEP 3 :
-Now that you are in odin mode connect your device via usb cable !
-Now open Odin3 3.09 that you have downloaded.
-If there is a pop-up like Installing ADB drivers let it get finished it is usually updates !!!!
-Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it
MAKE SURE U UNTICK THE AUTO-REBOOT BUTTON
-Click Start
ONCE IT SAYS PASS ...REMOVE THE BATTERY ...THEN RE-INSERT THE BATTERY AND BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON
HOW TO ROOT THE DEVICE :
-Download SuperSu (obviously the latest one) from here ------> Click here !
-Copy that to internal sd card
-Power off your device and press vol up + power + home button (all at once)
-Select install zip from sdcard --->choose zip from sdcard ---> scroll down and flash UPDATE-SuperSU-v2.xx.zip
Done ! And you are ready to go
BUGS
DATA SHOWN TWICE IN ADVANCED WIPE ... WILL BE FIXED IN THE NEXT BUILD
YOU TELL ME [/SIZE]
NOTE : IF ANY OPTION DOESNT WORK FOR U ... TURN OFF UR PHONE AND THEN BOOT INTO RECOVERY
SOURCES
DEVICE TREE
KERNEL(PREBUILT ... THANX TO SAMSUNG ... AVAILABLE IN THE DEVICE TREE)
CREDITS
TWRP TEAM
A BIG THANKS TO @RGold55 FOR TESTING
reserved
:victory:
Thanks for the mention, you're most welcome, bro!
Thank you very much. Let me confirm if it is for g800h dual sim phone.
My G800H/DS works fine with both sim cards -- sim manager, sms, calls, everything is ok.
"-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it"
In step 3 how to select the recovery file?
I see PDA button. How to select AP. where is it in odin?
drnag said:
"-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it"
In step 3 how to select the recovery file?
I see PDA button. How to select AP. where is it in odin?
Click to expand...
Click to collapse
it depends on the version of odin your using
if your odin has PDA .. then put the recovery there (v 3.07 and before )
if your odin has AP ... Then put the recovery there (v3.09 onwards of odin)
Thank you very much. Done.
cheers
...
Tested
Zip flash ok.
Have a problem... i cannot upgrade my phone to new firmare:
Model: SM-G800F
Model name: GALAXY S5 mini
Country: Italy
Version: Android 4.4.2
Changelist: 1998311
Build date: Fri, 10 Oct 2014 02:45:33 +0000
Product Code: ITV
PDA: G800FXXU1ANJ2
CSC: G800FITV1ANJ1
MODEM: G800FXXU1ANJ2
...after upgrade phone reboot, go into recovery and stopped procedure ?...
In which i can solve it ?
Thnak
Hispa
hispanico957 said:
Have a problem... i cannot upgrade my phone to new firmare:
Model: SM-G800F
Model name: GALAXY S5 mini
Country: Italy
Version: Android 4.4.2
Changelist: 1998311
Build date: Fri, 10 Oct 2014 02:45:33 +0000
Product Code: ITV
PDA: G800FXXU1ANJ2
CSC: G800FITV1ANJ1
MODEM: G800FXXU1ANJ2
...after upgrade phone reboot, go into recovery and stopped procedure ?...
In which i can solve it ?
Thnak
Hispa
Click to expand...
Click to collapse
why did you flash this one??? This is for the G800H .. yours is G800F
G800F:
http://forum.xda-developers.com/showthread.php?t=2922938
Sent from my SM-G800H/DS
can anyone reup the file? it is not longer available on basketbuild.com
Thanks!
mindestens said:
can anyone reup the file? it is not longer available on basketbuild.com
Thanks!
Click to expand...
Click to collapse
I have no clue how the file disappeared but I'll upload it again .. Wen I'm back from college
rutvikrvr said:
I have no clue how the file disappeared but I'll upload it again .. Wen I'm back from college
Click to expand...
Click to collapse
Thank you! Flashed now and works perfect!
Works fine on my G800H/DS. It wont write to the external SD (64GB eXFat) but otherwise it works like a champ.
hello rutvikrvr,
2 short questions.. is it possible to adjust the time settings for different time zones (eg +1 for europe / vienna) ?
If i make a backup to the internal sd i cannot see any content in the TWRP folder with eg. es file explorer, only when i boot with recovery and use the present file manager.. is it a bug or intention?
Thanks!
mindestens said:
hello rutvikrvr,
2 short questions.. is it possible to adjust the time settings for different time zones (eg +1 for europe / vienna) ?
If i make a backup to the internal sd i cannot see any content in the TWRP folder with eg. es file explorer, only when i boot with recovery and use the present file manager.. is it a bug or intention?
Thanks!
Click to expand...
Click to collapse
In advanced settings you should get an option to change the time zone.... And for the second thing... If es file explorer doesn't support reading .ext4 files .. Then it won't show up
rutvikrvr said:
In advanced settings you should get an option to change the time zone.... And for the second thing... If es file explorer doesn't support reading .ext4 files .. Then it won't show up
Click to expand...
Click to collapse
Yes, i found this setting - BUT if I set the time zone to UTC +1 (Berlin, Brussels, Paris) - the correct time zone for vienna too - the time is shown as 8:43 pm - but it is now 7:43 pm - so i think the winter / summertime is not considered?
The second thing.. in the TWRP folder it is a folder called backup and in this also a folder.. if i copy the whole TWRP Folder with the file manager from the recovery to the external sd - i CAN see the whole content from the TWRP folder with ES File Explorer .. on the internal sd not.. Strange