Related
Let me start off by saying I'm not a noob. I have or had every main/big Android phone there was.
Anyway, here goes. I installed Voodo, had an issue so I then restored via Odin. I replaced the kernel as well. After I did this, I had an internal memory issue where it showed 0 mgs. Fixed that. I then tried to re root the device with the one click root through adb. All the steps completed but once it got to the step where it said about 5 minutes and gave you time, it basically stopped. The phone would reboot, but my command prompt window would give me an error. Log below. What am I doing wrong?
******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I5000018ff18 device
*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone
* Then rerun this application
*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
973 KB/s (1867568 bytes in 1.874s)
309 KB/s (26264 bytes in 0.083s)
420 KB/s (196521 bytes in 0.456s)
67 KB/s (5392 bytes in 0.078s)
5 KB/s (281 bytes in 0.052s)
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
* About to exploit your device
* This will take about 3 minutes
*
* If it doesn't respond after waiting 5 minutes then it probably failed,
* so you should close this and run again
*
* Start Time: 23:36:07.13
*
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
*
* Restarting your phone now.
*
error: device not found
* Complete
*
******************************************************************************
Press any key to continue . . .
Is your device in download mode? All Samsung drivers installed properly?
tats_06 said:
Is your device in download mode? All Samsung drivers installed properly?
Click to expand...
Click to collapse
They were, I will try again though. How do I get to download mode?
Here is the root, recovery and etc thread: http://forum.xda-developers.com/showthread.php?t=790004
I just looked over links...and putting into download mode is required for clockwork recovery. Root should be good. Check out the link and see if this method is better than the one you are using.
tats_06 said:
Here is the root, recovery and etc thread: http://forum.xda-developers.com/showthread.php?t=790004
I just looked over links...and putting into download mode is required for clockwork recovery. Root should be good. Check out the link and see if this method is better than the one you are using.
Click to expand...
Click to collapse
That was the other issue actually. I flashed CWR through Odin, but when I get to stock recovery, it says invalid signature...I assume because I'm not rooted?
Breakthecycle2 said:
That was the other issue actually. I flashed CWR through Odin, but when I get to stock recovery, it says invalid signature...I assume because I'm not rooted?
Click to expand...
Click to collapse
What you need to do is when you get into stock recovery, select "apply update.zip from sd card" and it should take you to cwm. When cwm flashes, it puts an update.zip onto sd card...don't delete that under any circumstances.
tats_06 said:
What you need to do is when you get into stock recovery, select "apply update.zip from sd card" and it should take you to cwm. When cwm flashes, it puts an update.zip onto sd card...don't delete that under any circumstances.
Click to expand...
Click to collapse
First, thanks for all your help.
Second, when I flash CW through Odin, and go to stock recovery, it says, "no such file or directory". I had this working perfectly the first time, but since I installed Dirk v2's kernel, everything got all screwy. Still cannot get it to work...lol.
Breakthecycle2 said:
First, thanks for all your help.
Second, when I flash CW through Odin, and go to stock recovery, it says, "no such file or directory". I had this working perfectly the first time, but since I installed Dirk v2's kernel, everything got all screwy. Still cannot get it to work...lol.
Click to expand...
Click to collapse
Finally seems like I got it back now. Thanks!
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
I'm trying to help the 10% Who are suffering from "Lag" and not so Buttery Experience with the latest Official Release of JB From SAMSUNG.
This is merely a Guide of How I managed to install LSZ and how to achieve the smooth experience of jelly bean.
The Rooting tools used here are not my work, and I thank everyone contributed into making them for the community
(Thanks to XDA Community for the great efforts and constitutions)
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
:: Disclaimer :: This Thread is Explaining solely how I Like to install this ROM or any future ROM to ensure Perfect Combination of Stability and Permanence and everyone might have his own Preferences and methods as well ::
How to Install (Coming from Leaked JB, ICS or GB) :
1. Make a Backup of your Applications and Data using Go Backup or Titanium Backup;which ever you Like.
3. Make a Backup of your Internal Storage to your PC.
Note: Mount Your Internal and External Storage to your PC by Either "USB Utilities" or "USB Switcher App *Root*" in case you only have "Media Server USB".
4. Format your Internal Storage from your PC to : FAT32 with File Allocation Size: 4KBs.
a. Right Click on Internal Storage (Usually the one with 11GB) and select "Format".
b. Select type: FAT32 and Allocation Size :4096 Bytes, Untick Quick Format.
5. Install a Safe Kernel From here:
http://forum.xda-developers.com/showthread.php?t=1901191
6. After Installing the Kernel, reboot into Recovery and Do a Factory Reset, and head to Phills Advanced and Look for "Clean For new System Installation" thing and Click it, after finish, shut down the phone.
To Boot into Recovery, Shutdown the Phone : Hold Vol (+) and Home Button and Power Button, release power button when you see Samsung Logo.
7. Now install JB LSZ using PC Odin, you can find the instructions on this Link:
http://forum.xda-developers.com/showthread.php?t=1424997 (Thanks to Dr.Ketan) .
PS: after the phone restarts, leave it until it finishes the Boot, and installs the applications of the system (The Bloatware) and then until it boots to the home screen.
8. Reboot to Download mode and install the latest safe Kernel for LSZ (search for it by this name: XXLSZ-OXA ) from this link on the third post:
http://forum.xda-developers.com/showthread.php?t=1901191
9. After rebooting when completion, go to Settings on the phone and select Factory Reset, and make sure to select to erase internal Storage.
This will ensure a clean system with Aligned memory storage, will kill LAG factor.
10. After booting again, check for lag, and leave it to settle, and then restore your apps and data, and copy your data from PC to Internal again, and leave it for a while to settle again. should be good to go now!
A side tips:
a. I have Uninstalled all the Bloatware using Titanium Backup, which i believe helped in my cause of presuing better speed of LSZ (Like Google+,G music, G magazines, etc).
b. Formatting the External SD card is a must also, to make sure Media Scanner is not having errors on it.
This Hopefully should give you the best Install procedure for LSZ, i have had many lags but after doing this method, I have achieved superb speed. Though, expect few to little lags on the first few boots until the system finishes Media Scanner and making cache files etc.
How to Root LSZ?
1. Install This Kernel using Odin in case you don't have it : XXLSZ-OXA from this link on the third post:
http://forum.xda-developers.com/showthread.php?t=1901191
2. Reboot into Recovery and install the File I have attached here, and you will have root ready, Good luck.
Note: download the zip version of the kernel LSZ to external sd and flash it using stock recovery to avoid yellow triangle if you want.
To clear Yellow Triangle and Counter count on Galaxy Note, please download "Triangle away" by Chain Fire, from this Link and rest it:
http://forum.xda-developers.com/showthread.php?t=1494114
I have gathered this Information though my experience with my Galaxy Note and the information I have found and the tools available on XDA, I don't claim owner ship of any of the Root Tools or Rom it self, If you need help I would try to help you if i can. Best regards
Cool.
Posts like this are always the best world when it comes to help more people in a simple way.
Fortunately, my installation went pretty well, just like the JB running after that.
Just helping the troubled minds and glad you had no issues.
You know that there is a PIT file for Odin which formated all memory on Note? And it can be done in JB installation process,all at once...
Sent from my GT-N7000 using Tapatalk 2
zviki said:
You know that there is a PIT file for Odin which formated all memory on Note? And it can be done in JB installation process,all at once...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
The Pit method can be risky, and ive learned from my older device to not play with Pit files much,... )
AW: [Guide] Installation Tips for LSZ + Rooting Methods [Lag Free]
Sorry, but 2x factory reset, and formating storage? Flashing a kernel with Odin, that will lead to a triangle and increased flash counter? Correct me, If I'm wrong.
Cheers, Markus
in OP, is steps 4 & 5 really necessary?
By what the Dr says here:
http://forum.xda-developers.com/showpost.php?p=38183950&postcount=5587
I would think not..
Perfect way to flash LSZ
Yes brother, for LM5 there is no issue, but in LSZ if you dont do it as in OP you may get bootloops.. i tried..
if you use mobile odin for flashing lsz then need to flash bootloader separately as mobile odin cant flash bootloader.
My way of perfect installation is
Flashing instructions
1. flash any 4.x Philz Kernel
2. reboot recovery
3. Go to Philz settings
4. Select Clean Before Flash new rom
5. Wipe Dalvik Cache
6. reboot to download (advanced)
7. flash the new in using PC Odin (select PDA tab and browse .tar.md5 file)
for just rooting flash supersu as in OP
for a safe kernel, flash Philz LM5 Kernel.
if anyone want to try LSZ custom or cwm versions then first flash any 4.x philz kernel and
Go to Philz settings
Select Clean Before Flash new rom
Wipe Dalvik Cache
Flash rom, then after rom installation reboot to recovery and do flash bootloader separately in cwm.
jeffs99 said:
in OP, is steps 4 & 5 really necessary?
By what the Dr says here:
http://forum.xda-developers.com/showpost.php?p=38183950&postcount=5587
I would think not..
Click to expand...
Click to collapse
very useful. Thanks
Sent from my GT-N7000 using xda premium
installation
i instaled the ROM usig Mobile odin Pro which rooted the device...even got all the application, SMS, contacts back but i guess i am not on (safe Kernel)Philz kernel....everything is good for me except the battery is draining like 1% every min....no air view..or smart rotation..guessing its not included for galaxy note 1......while browsing through EFS to external card folder it shows it to be empty...but My files shows the external card content..through Storage/external card...and camera shortcut through lockscreen seems to be not working for me...what troubles me the most is the battery problem....i need a good batter life....as i am constantly reading books on the note...is there any workaround for the battery?
Gugelhupf said:
Sorry, but 2x factory reset, and formating storage? Flashing a kernel with Odin, that will lead to a triangle and increased flash counter? Correct me, If I'm wrong.
Cheers, Markus
Click to expand...
Click to collapse
Yes bro, to get rid of the triangle just install 'triangle away' and get rid of it, but this will ensure 100% no bootloops.
Sent from my GT-N7000 using xda premium
prajjwal said:
i instaled the ROM usig Mobile odin Pro which rooted the device...even got all the application, SMS, contacts back but i guess i am not on (safe Kernel)Philz kernel....everything is good for me except the battery is draining like 1% every min....no air view..or smart rotation..guessing its not included for galaxy note 1......while browsing through EFS to external card folder it shows it to be empty...but My files shows the external card content..through Storage/external card...and camera shortcut through lockscreen seems to be not working for me...what troubles me the most is the battery problem....i need a good batter life....as i am constantly reading books on the note...is there any workaround for the battery?
Click to expand...
Click to collapse
I believe you should do a clean install to fix your drain issue, as i had that while upgrading from ics to jb with out wipe, now my drain is very minimum like this image.
Sent from my GT-N7000 using xda premium
thanks for the guide.
was about to move from leaked JB rom to the new official release.
already did a nandroid backup
i'll make sure to use a safe kernel.
Welcome
I am a beginner of rooting my Note. I have updated my Note to 4.1.2 from the Samsung Rom
I would like to ask if my note baseband version is N7000XXLSO and the build number is JZO54K.N7000ZSLM5
then i can use your method to root my Note Thank You very much!
can you post the list of all the bloatware apps.?
tangoscar42 said:
I am a beginner of rooting my Note. I have updated my Note to 4.1.2 from the Samsung Rom
I would like to ask if my note baseband version is N7000XXLSO and the build number is JZO54K.N7000ZSLM5
then i can use your method to root my Note Thank You very much!
Click to expand...
Click to collapse
Yes you can use. Better, download the zip version of the kernel LM5 to external sd and flash it using stock recovery to avoid yellow triangle.
tangoscar42 said:
I am a beginner of rooting my Note. I have updated my Note to 4.1.2 from the Samsung Rom
I would like to ask if my note baseband version is N7000XXLSO and the build number is JZO54K.N7000ZSLM5
then i can use your method to root my Note Thank You very much!
Click to expand...
Click to collapse
Yes, you can use my method very safely to root your device.
nokiamodeln91 said:
Yes you can use. Better, download the zip version of the kernel LM5 to external sd and flash it using stock recovery to avoid yellow triangle.
Click to expand...
Click to collapse
I have updated the OP with your word about the .zip version of the Kernel file, should have included it in the first place, thanks a lot lad.
YuE0529 said:
can you post the list of all the bloatware apps.?
Click to expand...
Click to collapse
There are many, But I will tell you which ones I removed:
Google+
Google Magazine
Google Movies
All German Apps
Allshare Play
Music Hub
Video Hub
Readers Hub
Learner Hub
Crayon physics
Polaris Office
Maps (I like to download latest one from Market as this one is old )
YouTube (I like to download latest one from Market as this one is old )
Swype Keyboard
Those all That I can remember at the moment.
CM10.2 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz5.18.4 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM10.2 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). More desired may be the new privacy manager features that allow you to control, on a per app basis, which information you wish to share. Other improvements include an improved lockscreen cLock and a new integrated Superuser.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera/Camcorder
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* When unlocking the screen, sometimes only the capacitative buttons light up, and the screen doesn't come on. This seems to happen about 80% of the time.
Solution: This can be fixed by locking the screen, then unlocking it again. In about 5% of these cases the screen does not come on again. Just repeat the steps again until it does.
This has been fixed as of build 20131029
* You may notice a screen flicker when you first flash this ROM. This is due to a bug where the system can't decide whether to render the graphics with the cpu or the gpu, thus the flicker.
Solution: This is fixed by turning on Settings -> Developer Options -> Disable HW Overlays (You must first enable Developer Options by pressing 7 times on Settings -> About Phone -> Build Number). This will be reset on every boot. if you install Universal Init.d, my 91fixoverlays script will run on each boot and fix this automatically.
This has been fixed as of build 20131029
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 flashable zip which is compatible with CM10.1/CM10.2
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140224 (Latest)
ROM: cm-10.2-20140224-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20140224-signed.zip (106.5MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A dirty flash should work for upgrading , but a clean flash is highly recommended
Build: 20140120
ROM: cm-10.2-20140120-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20131231-signed.zip (103.8MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with CM10.1/CM10.2
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with CM10.1/CM10.2
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]December 23, 2013 - Build 20131223[/B]
* Revert build.prop to use dyn instead of gpu (less problems)
* Added back 91fixoverlays to /system/etc/init.d to disable hw overlays and fix screen flicker on boot
* Re-worked 91fixoverlays script so that it now runs in it's own shell to stop it from blocking other startup scripts and causing a laggy boot
* Fixed up device tree code including adding the correct definitions for boot animation size and update to the build fingerprint
* Synced latest changes from CyanogenMod
[B]December 1, 2013 - Build 20131201[/B]
* Force gpu rendering in build.prop
* Improve fix for screen on delay
* Synced latest changes from CyanogenMod
* Updated GAPPS
[B]October 29, 2013 - Build 20131029[/B]
* Tweaked build.prop to fix screen flicker and notification drawer lockup
* Fixed screen unlock bug - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/5e163ff0c5d90a4518cbc9e14c86dceec095c70a"]Commit 5e163ff0c5d90a4518cbc9e14c86dceec095c70a[/URL]
* Added SmartAssV2 Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/511e45206bb9a1454a0c43b3d626749c1fa2c241"]Commit 511e45206bb9a1454a0c43b3d626749c1fa2c241[/URL]
* Added Adaptive Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6"]Commit 7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6[/URL]
* Added Lagfree Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/d1392017601d27303fbce9da18d2af718e7e1a65"]Commit d1392017601d27303fbce9da18d2af718e7e1a65[/URL]
* Restore Advanced Device Settings - [URL="https://github.com/titanic-fanatic/android_device_samsung_msm8660-common/commit/3126c17c6165c7d96abde4cd7459769e165aa195"]Commit 3126c17c6165c7d96abde4cd7459769e165aa195[/URL] / [URL="https://github.com/titanic-fanatic/android_packages_apps_Settings/commit/9031ffb1f4e4185f397724a27e3d75afe7fd67e4"]Commit 9031ffb1f4e4185f397724a27e3d75afe7fd67e4[/URL]
[B]October 5, 2013 - Build 20131003[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market, and also make sure you have Universal Init.d installed and active. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. When your phone reboots, recovery will warn you that your device may possibly be unrooted. This is because of the install-recovery.sh script that is required to start the superuser daemon which allows SuperSu to manage superuser permissions. You are not unrooted ;-)
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. This needs to be set on every boot unless you are running Universal Init.d and my 91fixoverlays script is present in the /system/etc/init.d folder.
Q. When I unlock my screen, my menu/home/back/search buttons come on but the screen is black?
A. This is a known bug in this ROM and is on the list of things that need to be fixed. For now, when this happens, just lock the screen, then unlock it again and the display should come back. If it does not, repeat until it does (the most number of times i had to do that was 3).
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM10.2 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-10-05
Last Updated 2014-02-23
Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Wow! Thanks so much. Downloading now.
iDynamics said:
Wow! Thanks so much. Downloading now.
Click to expand...
Click to collapse
Wow, you already found it and I wasn't even finished putting everything up... make sure you use the new CWM, very very very important!
Followed the instructions ( to the best of my ability ) but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
iDynamics said:
Followed the instructions but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
Click to expand...
Click to collapse
I totally forgot to update the build.prop with the build type, it is responsible for the red border. Either use a build.prop editor or open the /system/build.prop with a text editor and change the following line:
ro.build.type=eng
Click to expand...
Click to collapse
Change it to:
ro.build.type=user
Click to expand...
Click to collapse
You will need to reboot after making this change.
In regards to the 91fixoverlays script, I do appologize. I forgot to include it in the zip... Please download the attached 91fixoverlays.txt file and rename it to 91fixoverlays and move it to /system/etc/init.d and change it's permissions to match the other files in that directory.
Sorry for missing these two things. I will update the packages ASAP and will post a note when it's done so you know that there is no need to follow the steps in this post.
Much appreciated! No more red flickering. Thanks!
Wow! Thank you!
Sent from my SGH-I757M using xda app-developers app
This. Is. Amazing!!!!!
Downloading now, will install and report back in a bit with findings.
Thanks so much!!
Awesome. Downloading. Will report back. Thanks!
Sent from my SGH-I757M using xda premium
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will do more testing.
Thanks
Zippy Dufus said:
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will so more testing.
Thanks
Click to expand...
Click to collapse
I think this is due to our oddly small cache partition. Only 100MB as compared to the skyrocket at 300MB. Currently, I only moved four apps in the gapps package to the data partition do that their dex files don't end up in the /cache/dalvik-cache dir and instead end up in /data/dalvik-cache. I think I need to move others. I also think that it happens only on first boot without side effects because a couple of the installed apps only run on first boot, then their dex files can be deleted (I think this happens automatically).
Sent from my SGH-I757M using XDA Premium 4 mobile app
Thanks titanic_fanatic, you've breathed new life into an old phone
Sent from my SGH-I757M using Tapatalk 2
Only issue I've run into so far is that auto rotate doesn't seem to work :-/
Sent from my SGH-I757M using XDA Premium 4 mobile app
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
rukusx7 said:
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
Cool, I'll give that a try. Anyone else having auto-rotation issues?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Rotation is not working for me, though I always keep it on portrait anyway so I am not complaining.
Rotation doesn't work here, and every so often I run into spells where the only button that works is the home button and haptic feedback stops working all around. A reboot fixes it and it seems random. Other than those few things this is soooooo smooth. I'm happy. Thanks so much!
Sent from my SGH-I757M using xda premium
Fix for Sensors
Hey guys, to fix the sensors, download this attachment sensors.default.so.txt and rename it to sensors.default.so, move it to /system/lib/hw and give it the same permissions as the other files in that directory, then reboot and your sensors should be working
Works now! Thanks ya muchly.
Sent from my SGH-I757M using xda premium
I often see a lot of people who wants to ROOT but or doesn't want to void warranty,or can't unlock the bootloader
this exploit was found by @jcase at the moto X forum [Huge fan of this guy] and i'm bringing to you this One Click Root
WILL ROOT YOUR MOTO G
EVEN IF YOUR BOOTLOADER IS LOCKED
PLUS YOU DONT HAVE TO DEAL WITH
RECOVERY / CUSTOM ROOM / RISK OF LOSING FILES
unfortunately this only work up to android 4.4.2 [please consider reflashing a stock 4.4.2 room if you updated to 4.4.3]
HOW IT WORKS
1 - Just download OneClickRoot.zip and unzip the ADB folder [ Just 2MB ]
2 - Open adb\OneClickRoot.bat
3 - Wait ~20 seconds and DONE
* Phone must ON,plugged and with USB debugger ON
* in case of error,open your CMD and drag oneclickroot.bat into it and press enter
* Motorola Drivers might be needed (don't worry,the links are on a file and also in this thread)
~~> For more information read ".Read This First.txt"
unfortunately this Root is temporary and will be lost if you restart your phone [ Yeah, you can do this again ]
Content of .Read This First.txt
with Driver's link and also problem solving tips
This might void your warranty.
-This process was made for you to root you motorola phone (might or might not work for other devices) without losing you warranty
(you must know how things are to unlock your bootloader right?)
BUT if anything go wrong i'm not responsible for anything
* 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 this.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I wont do anything
* these files worked for a lot of people and the problem must be you, your computer or your phone.
Root for Motorola devices by Jcase
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623
DOES NOT WORK WITH 4.4.3
I, "72 Off" just put some files from the internet toghether and made the OneClickRoot.bat because i hate to copy and past these 4 lines on cmd
#######
HELP
#######
problem - OneClickRoot.bat Doesn't rooted my device
Answer - this DOES NOT WORK WITH 4.4.3
SHOULD WORK WITH AND UP TO 4.4.2
if you updated and dont want to void your warranty by unlocking bootloader then you CAN flash a Stock 4.4.2 ou 4.3
on your moto G/X/E
Answer - Your phone must be plugged on the computer and turned on (duh)
Answer - USB debugging must be ON
- Go to settings>About phone>build number (tap 7 times or more)
- This will enable the "Developer Options" on settings
- in developer options,turn it on and enable USB debugging
Answer - try first opening CMD and then drag "OneClickRoot.bat" inside and press enter
~> if somebody can,please explain me (72 off) how to fix it (will try to update the .zip)
-try also to paste a CMd from you own computer inside the folder
-Run as administrator if didnt work
Answer - You will need your device drivers for ADB to work
try here
http://d1tsx1og7dz7v4.cloudfront.net/MotorolaDeviceManager_2.4.5.exe
or here
http://forum.xda-developers.com/showthread.php?t=2550635
or here
http://forum.xda-developers.com/showpost.php?p=48193757&postcount=6
or here
http://forum.xda-developers.com/showthread.php?t=2588979
>> I dont know which one I used, but one of these should work
answer - this is all i know
- go to thread of these files on XDA and look for answer
- Google it
#####
Root for Motorola devices by Jcase
Tutorial + .zip with OneClickroot and this file by 72 Off
Click to expand...
Click to collapse
Hope I helped you, if so hit thanks for me and also on jcase thread
If you have any problem, post here [ Dont be lazy, read ".Read This First.txt" before posting here ]
I searched and can't find other tutorial for Moto G, so, I'm making this one [ maybe some mod can make stick for a time so everyone sees ]
Thread closed
Please remember to seek permission before using someone's work
Attachment removed.
ONEPLUS 3 - SUPPORTS ALL VERSIONS UP TO THE LATEST OXYGEN OS BUILD.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Google, Nexus, OnePlus and Samsung Toolkits and supports many 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.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X,6,6P and 9
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google N-Nexus O-OnePlus S-Samsung
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: Grarak or TWRP custom recovery on OnePlus 3, ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, 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, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
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 AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
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 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT 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
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**FAQ**
**VIDEOS**
I have finished all the work on the OnePlus modules for the 1, 2 and 3 devices and it is ready for testing.
You can download and test the Toolkit from the link in post#1. Please remember that this IS a test version at the moment as I do not own any OnePlus devices but I have checked all the code thoroughly and don't see any problems. I am especially pleased with the unlock/lock routines and will probably implement the code for the Nexus modules if it works well.
Everything can be checked (and please do) except downloading a stock build directly from the Toolkit as I am waiting to hear back from AndroidFileHost to see if I can get direct links to use in the Toolkit. The fastboot flash routines are working though and the Toolkit will detect the storage of the device (16GB or 64GB) and flash the relevant userdata image so you do not have to do that manually anymore.
I have used the Universal USB driver pack from CWM so if anyone has not installed OnePlus drivers yet PLEASE test if this works. I did originally include the official drivers from OnePlus but they close the Toolkit when the drivers installation starts and thats not great.
The ALLINONE routine should work fine and I have sent out some pro codes to testers to check it all works.
All builds are covered and the correct version of TWRP will be downloaded depending on the build selected. Please check everything and let me know of any bugs or textual errors (as I used a lot of the Nexus code) so I can release it publicly as soon as possible.
Thanks, Mark.
Great job, thanks a lot!!!
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
Just saying, got that hit when I scanned the installer file. Might be wrong but I will not run it until dev explain why
TheErk said:
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Click to expand...
Click to collapse
Did you read the first post of the thread?
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Click to expand...
Click to collapse
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
I ran this on my Nexus days, the guy is well known around, you can go with this.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
I found the problem right away, just deleted 1 word by accident when I was renaming things.
I have made new device modules and uploaded them. Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Mark.
mskip said:
Did you read the first post of the thread?
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
Click to expand...
Click to collapse
Thought I did! Thanks for the fast reply!
---------- Post added at 11:23 AM ---------- Previous post was at 11:11 AM ----------
Impressive tool you got here! Thanks!
mskip said:
Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Click to expand...
Click to collapse
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
gruntyoldbag said:
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
Click to expand...
Click to collapse
Thanks and thank you for staying with me, I have had to change some of the procedures for the OnePlus.
Should be all fixed now. One of the procedures I had to skip set the filename for the OTA image. Have added it back in.
Clean the module files, download the new ones and retest. Hopefully it should go through.
Mark.
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or you can chose chinese or madarin?)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
************
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
gruntyoldbag said:
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or chinese or whatever)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
Click to expand...
Click to collapse
Thank you. I have uploaded the fixes to all the OnePlus device modules so that part at least should work for them all now.
Does the language selection come up as soon as the device boots to recovery?
I put Install from USB as thats what it said in the flashing tutorial on oneplus.net I will change it to Install from ADB/USB just to be safe for all devices.
Thanks again for the feedback. If you want to test any of the pro functions (ALLINONE) then let me know and I will send an activation code to your inbox.
Mark.
gruntyoldbag said:
It is sideloading now
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
Click to expand...
Click to collapse
Have you unlocked your bootloader? This is required before flashing/bootings images to your device.
I can capture the error when trying to boot/flash with a locked bootloader to provide more help for the user.
Mark.
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
gruntyoldbag said:
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
Click to expand...
Click to collapse
I have changed the text when booting to recovery and added extra error control when flashing or booting an image without the bootloader unlocked. New device modules uploaded.
Now sending a pm to you with a code.
Mark.
PM received - PM sent
New text and error control seems to work :good: