For the record, rooting causes a violation of the garantuee policy of Samsung. Furthermore there is a possibility of demaging the Android-system(bricking). This has not happend as far as I know, but it should be mentioned. As advanced user it is usually always possible to recover the system, but still, just to let you know.
So whoever takes the risk, takes the responsibility
Advice: Use a PC without any drivers or software from other Android devices, this may causes conflicts with the drivers in the ADB.
Rooting
Rooting via Recovery mode(SD card)
Note: This instructions is written for the stock recovery. It has been reported that custom recoverys are causing problems during rooting. If you use a custom recovery which causes problems, please flash the stock recovery via ODIN first(scroll down to Other). Than apply the rooting
1. Download this Zip-file copy this into the internal SD card.
2. While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on.
{
"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"
}
As soon as you see the Android with the box, release the Home- and Volume Up-button.
After you hit the menu-button shown on the last image, the screen will gray out, you will have to wait until the recovery menu appears.
3. Navigate with the volume up and down to apply sdcard:update.zip in Recovery Menu. To confirm your selection use the home-button.
4. Choose (with volume buttons) the update.zip file on your internal sd card and confirm again with Home-button. You will have to wait 5 seconds.
5. Now choose reboot system now and confirm with home button.
Now you device should be rooted.
The original thread
================================================================================================
Rooting with the manual method
Note: It has been reported that this method no longer work for firmwares later than LA2.
1.a On the Mobile: Got to Settings -> Applications -> Development -> and checkmark USB debugging.
1.b Auf dem Handy: Geht auf Settings -> Applications -> and checkmark Unknown sources.
2.Connect the device to your PC(USB) and wait until all the drivers have been successfully installed .
3. Download and install the Android SDK.
4. Download thisZip-File and extract all the files into the folder platform-tools, which should be located by default at C:\program files\Android\android-sdk\platform-tools.
5. Run CMD(prompt) (as Administrator) (and change the direction on: C:\program files\Android\android-sdk\platform-tools.
To do so you will have to enter following command in the prompt:
Code:
chdir C:\program files\Android\android-sdk\platform-tools
(Every line/row has to be confirmed with the ENTER-Key to get to the following line)6. Now enter following code in the prompt:
Code:
adb push zergRush_samsung_w /data/local/
adb shell
(Every line/row has to be confirmed with the ENTER-Key to get to the following line)7. You should be now in the ADB Shell, now enter following code:
INFO: The $-sign in the prompt is to indicate that you are in the ADB-shell
Code:
chmod 755 /data/local/zergRush_samsung_w
/data/local/zergRush_samsung_w
Now you will have to wait 3-4 minutes. If this step was successful the following last two lines will appear:
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root..enjoy!
8. Now you should be out of the ADB-shell(no $-sign) Now you will have to enter the following code in the prompt:
Code:
adb remount
adb push Superuser.apk /system/app/
adb push su /system/bin/
adb shell
After the last entry you will get back into the ADB-shell($-sign).9. In the ADB-shell you will have to enter:
Code:
chmod 644 /system/app/Superuser.apk
chmod 4755 /system/bin/su
reboot
INFO: 4755 stands for read and write permissions, so this is not a tipping error!
After the restart you Samsung Galaxy W should be rooted.10. You may have to update Superuser via the Android market ->Menu-Button->My Apps Superuser -> update.
Have fun with the root access!!!
The original post
================================================================================================
Rooting with the auto-method(DoomLord v.3) (for Windowsuser)
Note: It has been reported that this method no longer work for firmwares later than LA2.
1.a On the Mobile: Got to Settings -> Applications -> Development -> and checkmark USB debugging.
1.b On the Mobile: Got to Settings -> Applications -> and checkmark Unknown sources.
2.Connect the device to your PC(USB) and wait until all the drivers have been successfully installed .
3. Download this Zip-File and extract all the files into a random folder.
4. Run the runme.bat-file as Administrator and press any key.
5. Now you will have to wait for 3-6 Minuten. The program will have to process all the necessary steps.
6. If you get the message "ALL DONE!!!" you device should be successfully rooted.
7. You may have to update Superuser via the Android market ->Menu-Button->My Apps Superuser -> update.
Have fun with the root access!!!
The original thread
================================================================================================
Unrooting
Unrooting via Recovery mode(SD card)
IMPORTANT: Only use this method if you have used the rooting method via Recovery mode !!!
I personally haven't tested it yet, so it is not confirmed by my person.
1. Download this Zip-file copy this into the internal SD card.
2. While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on.
As soon as you see the Android with the box, release the Home- and Volume Up-button.
After you hit the menu-button shown on the last image, the screen will gray out, you will have to wait until the recovery menu appears.
3. Navigate with the volume up and down to apply sdcard:update.zip in Recovery Menu. To confirm your selection use the home-button.
4. Choose (with volume buttons) the unroot.zip file on your internal sd card and confirm again with Home-button. You will have to wait 5 seconds.
5. Now choose reboot system now and confirm with home button.
Now you device should be now unrooted.
The original thread
================================================================================================
Automated unrooting DoomLord(for Windowsuser)
IMPORTANT: Only use this method if you have used the automated rooting method of DoomLord !!!
I personally haven't tested it yet, so it is not confirmed by my person.
1.a On the Mobile: Got to Settings -> Applications -> Development -> and checkmark USB debugging.
1.b On the Mobile: Got to Settings -> Applications -> and checkmark Unknown sources.
2.Connect the device to your PC(USB) and wait until all the drivers have been successfully installed .
3. Download and install this Zip-file and extract all the files into a random folder.
4. Run the runme-UNROOT.bat-file as Administrator and press any key.
5. Now you will have to wait for 3-6 Minuten. The program will have to process all the necessary steps.
6. If you get the message "ALL DONE!!!" you device should be successfully unrooted.
The original thread
Credits
Thanks to
qzem who helped me unrooting my device and wrote the instruction of most of the manual rooting method :thumbup:
DoomLord
team Revolutionary
Ch4lky
mirred
KeksKlip
Please let me know whom else I should add!
I have only written the instructions!
good day, i rooted my phone using doomlord's automated root and it was successful, but i updated it yesterday and it was unrooted. i tried using doomlord's rooting method but to no avail? help?
mike_kenji said:
good day, i rooted my phone using doomlord's automated root and it was successful, but i updated it yesterday and it was unrooted. i tried using doomlord's rooting method but to no avail? help?
Click to expand...
Click to collapse
Can you let us know which version you are using ? Settings->About phone->Build number
As far as I know there is a build version, I don't know which it was, which is not rootable with Doomlord.
EDIT: Rooting via Recovery works.
BTW: Have you tried the manual method ?
greets
THE-E
The provided instruction does not work on LA2 firmware. You still can get root from Recovery-Mode using update.zip with busybox, su and etc.
The root instruction is almost the same as http://forum.xda-developers.com/showthread.php?t=1253707.
I have used attahed files to get root. Thanks Dronson from 4pda for the provided files.
mirred said:
The root instruction is almost the same as http://forum.xda-developers.com/showthread.php?t=1253707.
I have used attahed files to get root. Thanks Dronson from 4pda for the provided files.
Click to expand...
Click to collapse
thanks for this! i already rooted my phone.
mirred said:
The root instruction is almost the same as http://forum.xda-developers.com/showthread.php?t=1253707.
I have used attahed files to get root. Thanks Dronson from 4pda for the provided files.
Click to expand...
Click to collapse
Hi, thanks for this!!
Just to be clear, can this method be used with Custom RZRecovery, or only with Stock Recovery?
Also, has anyone tried the Root tool contained in the RZRecovery Plugins package:
http://rzdroid.com/ftp/recovery/gingerbread/plugins/RZR-plugins-bundle-update.zip
PLUGINS
This bundle contains 4 plugins:
Disable/enable Dalvik bytecode verification in Android
Disable OTA downloads in Android
Fix Permissions
Root the installed ROM
After installing this update, there will be a new menu in Extras called Plugins.
Click to expand...
Click to collapse
I tested the Rooting via Recovery and it works like a charm. I managed to root the latest firmware (XXLA2) that was unrootable with Doomlord or manual method.
fender90 said:
I tested the Rooting via Recovery and it works like a charm. I managed to root the latest firmware (XXLA2) that was unrootable with Doomlord or manual method.
Click to expand...
Click to collapse
Hi fender.....
were you answering my question, just above, about rooting with the RZRecovery, or did you use the Stock Samsung Recovery?
Thanx in Advance
irishpancake said:
Hi fender.....
were you answering my question, just above, about rooting with the RZRecovery, or did you use the Stock Samsung Recovery?
Thanx in Advance
Click to expand...
Click to collapse
I rooted using Stock Samsung Recovery, and I'm sure RZRecovery could do the same
This root can use on XME 2.3.6 ?
iCyberWorld said:
This root can use on XME 2.3.6 ?
Click to expand...
Click to collapse
AFAIK, XME 2.3.6 can be rooted ONLY via Recovery Mode, thus use that method
I rooted my HH about 10 hours ago using that method
mike_kenji said:
good day, i rooted my phone using doomlord's automated root and it was successful, but i updated it yesterday and it was unrooted. i tried using doomlord's rooting method but to no avail? help?
Click to expand...
Click to collapse
Try this link, it helped me: www.unlockroot.com/unlockroot.php
good luck! hubie53
---------- Post added at 12:02 AM ---------- Previous post was at 12:00 AM ----------
mirred said:
The provided instruction does not work on LA2 firmware. You still can get root from Recovery-Mode using update.zip with busybox, su and etc.
Click to expand...
Click to collapse
This works in most cases: www.unlockroot.com/unlockroot.php
mike_kenji said:
good day, i rooted my phone using doomlord's automated root and it was successful, but i updated it yesterday and it was unrooted. i tried using doomlord's rooting method but to no avail? help?
Click to expand...
Click to collapse
Try this link: www.unlockroot.com/unlockroot.php
It worked for me even on the 2.3.6 version LA2!
hubie53
---------- Post added at 06:04 AM ---------- Previous post was at 06:02 AM ----------
mirred said:
The provided instruction does not work on LA2 firmware. You still can get root from Recovery-Mode using update.zip with busybox, su and etc.
Click to expand...
Click to collapse
Try this link: www.unlockroot.com/unlockroot.php
It worked for me even on the 2.3.6 version LA2!
hubie53
My SGW comes with 2.3.5. Will the above rooting work ?
Also, which method out of the 2 is the best to use, for flashing future ROMs and kernels etc.
How to update from 2.3.5 to 2.3.6 ?
Ibn Saeed said:
My SGW comes with 2.3.5. Will the above rooting work ?
Also, which method out of the 2 is the best to use, for flashing future ROMs and kernels etc.
How to update from 2.3.5 to 2.3.6 ?
Click to expand...
Click to collapse
First do the Update via Over The Air(search for it) or Samsung Kies.
After successfully updating use the first method rooting via recovery. This works for now and could work in future.
greets
THE-E
THE-E said:
First do the Update via Over The Air(search for it) or Samsung Kies.
After successfully updating use the first method rooting via recovery. This works for now and could work in future.
greets
THE-E
Click to expand...
Click to collapse
Just installed Kies.
Someone recommended that i use Odin instead of Kies for upgrading from 2.3.5 to 2.3.6 ?
Would there be a problem if i upgrade my stock 2.3.5 to 2.3.6 via Kies instead of Odin for rooting and then flashing of future roms ?
i just bought Galaxy W with 2.3.6 already installed. ive tried many ways to root this device but no luck (
cupez80 said:
i just bought Galaxy W with 2.3.6 already installed. ive tried many ways to root this device but no luck (
Click to expand...
Click to collapse
Damn it! I pressed the thank you button instood of the quote-button. Thanks for the report anyway ;-D
Have you tried the recovery method ? And please explain where you had dificulties.
Which firmware are you using ?
greets
THE-E
ive tried recovery method but still no root access (no problem when doing recovery method / success ).
Baseband=I8150DXKL1
Kernel=I8150DXLA2
Related
If you are stuck on a ROM you don't like (t-mobile/asian carrier etc.) you can use this howto to create a goldcard to bypass the CID checks so you can downgrade and root your Hero.
01. Download QMAT 5.06 here
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work.
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here
13. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 (which you can get here) from which you can fastboot boot and/or root your phone with flashrec.
Done.
Credits:
Original heads up by tangzq with link to this
That site used the XDA Sapphire goldcard howto here
And apparently myself and XDA as this builds on the HTC knowledge from the old days (here)
In any case, enjoy your new found freedom
Holy ****znit it works! Downgrading!!!!!
Hmm. I've followed the guide and successfully skipped the CID lock check of the device and flashed it to version 2.73.405.5 WWE. Problem is, I can't seem to get the device to boot into recovery mode after using flashrec (I did download and flash it just fine). the recovery mode (home + power) booted the device but it hangs at the boot screen where it says HERO. Any idea?
Edit: Ah. a little bit of the update. while the buttons do not work, i can use adb shell reboot recovery; however, after using flashrec, it still shows the old recovery screen ?
Edit2: confirmed, recovery flasher doesn't work now im using the SEA rom
I'll try the RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoD river.exe rom later
I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.
it worked!!!
Thanks so much! I did the exact process before (see other thread) but I must have missed something. Following this process exactly is what did it. I am guessing something about the reboot and the RUU is where i went wrong before.
I can confirm this works on the 2.73.707.9 ROM
Yaaahaaaayyhaahhahahaahaayyyyyyyyyyyy!!! I feel so happy for all you guys who had this problem (although I myself did not!!)
I kind of half gave up at 6:00 am yesrterday and i just woke up (1
:27pm) and followed the instructions here and BAM! got a working nandroid backup and a custom rom \o/!!! thanks to all of you!
so it's tested and proven for 2.73.707.9?great!
umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?
dying4004 said:
umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?
Click to expand...
Click to collapse
yup, we couldn't root certain asian carrier roms and t-mob rom and they couldnt downgrade so the where stuck, until now....
tianci86 said:
so it's tested and proven for 2.73.707.9?great!
Click to expand...
Click to collapse
CONFIRMED! it works on 2.73.707.9 , just got 2.73.405.5 , im so happy , thanks soo much guys your the best
My Hero..... lol
Thanks, I thought I would be owned by T-Mobile for ever after the ROM update
Now I'm back to the HTC default ROM (NOT T-Mobile G2 Touch!!!), cup of coffee time before Rooting flashing etc and remaining from now on faithful to Paul and the MoDaCo ROM
hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany
gyounut said:
hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany
Click to expand...
Click to collapse
ja das stimmt
thx jesterz
successfully update singapore hero 2.73.707 to 2.73.405, rooting in a while...
{
"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"
}
d0s said:
I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.
Click to expand...
Click to collapse
Did it last night and got it working, used the AMON Hero recovery image instead and partitioned my sd card without going through the manual adb solution.
Cheers
could this be adapted for the sprint hero?
Sprint Hero support request strongly seconded, i am desperate to get my CDMA Hero rooted.
have you guys tried using thesame method and got anywhere? I mean, from what I know is that you can't even boot in to recovery mode right? have you guys tries the adb method to boot into rec mode at least?
Aces!!!!
Worked on Indian 2.73.720 like a charm.
Thanks.
Overview
1. Recovery
2. Download-Mode
3. RAMDUMP-Mode
4. What is Root ? Why should I root my SGW ?
4.1 How can I root my Samsung Galaxy W ?
4.2 How can I undo the rooting of my Samsung Galaxy W ?
5. What are Custom ROMs ?
6. What is overclocking ?
7. What is flashing for ?
7.1 How can I flash a firmware ?
8. What is the IMEI-Number?
8.1 How can I view the IMEI-Number?
9. Sales Code
10. Net/SIM-Lock Status
11. Several Dialer Codes
1. Recovery-Mode
While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on and keep pressing the Home- and Volume Up-button.
{
"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"
}
As soon as you see the Android with the box, release the Home- and Volume Up-button.
After you hit the menu-button shown on the last image, the screen will gray out, you will have to wait until the recovery menu appears.
reboot system now
Reboots the system.
apply sdcard:update.zip
Install diverse updates like themes, custom roms etc.
wipe data/factory reset
Deletes all the apps, data and system settings(Files on the external SD-card will stay untouched)
wipe cache partition
Only wipes (formats) /cache partition (sometimes used as temp storage for updates, market downloads, etc) it hasn't anything common with Dalvik-cache which is in /data by default and it implies that the following boot after wiping cache partition will not be any longer than usually.
2. Download-Mode
While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on.
The download-mode is being used to flash firmwares, without using the official method of Samsung Kies. This should be reachable even if you have a corrupted firmware installed.
3. RAMDUMP-Mode
While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on.
4. What is Root ? Why should I root my SGW ?
Rooting the phone gives you all adminstrator rights, like you are used to on the PC.
Advantages:
All apps, also the sytem-apps like the ones from Samsung etc. are deletable (Titanium Backup required)
You can make your apps free from advertisements (AdAway,AdFree etc.)
All directories are viewable and editable (with ES Explorer or Root Explorer)
Swapping external SD and internal SD(with some tweaks)
Disadvantages:
Officially: losing the warranty (but after unrooting or reflashing firmware, no evidence of rooting left)
4.1 How can I root my Samsung Galaxy W ?
Here is a detailed HowTo with different methods of rooting.
4.2 How can I undo the rooting of my Samsung Galaxy W ?
Therefore you will have to unroot your device this is also described in this HowTo. It is of importance to choose the right method to unroot your SGW.
5. What are Custom ROMs ?
Custom ROMs are customized firmwares developed by different developers. They are very often better in peformance, because they can free up from bloatware(apps which are unnecessary for most of us) and can be optimized according to the need.
Most famous custom ROMs are: CyanogenMod (CM) and Android Open Kang Project (AOKP)
CM7 = CyanogenMod with Android 2.3.+ (Gingerbread)
CM9 = CyanogenMod with Android 4.0.+ (Ice Cream Sandwich)
CM10 = CyanogenMod with Android 4.1.+ (Jelly Bean)
6. What is overclocking ?
By overclocking the processor, you can increase the clock rate and gain more performance (of course it has to run stable). The default clock rate is set at 1401MHz(1,4GHz) for the Samsung Galaxy W. Increasing the clock rate usually provokes a growth of temperature.
Underclocking is also possible, which might improve battery life.
7. What is flashing for ?
If you have gained root access, you will be able to delete important apps which may be necessary for android to work. Deleting these apps could end up with a boot loop(the phone stucks at the bootscreen) or other problems. In this case flashing is the only possibility to get the phone running again.
7.1 How can I flash a firmware ?
Here is a detailed HowTo
8. What is the IMEI-Number?
The International Mobile Station Equipment Identity (IMEI) is a unique 15-digit serial number, with this a GSM- or UMTS-device can be identified
8.1 How can I view the IMEI-Number?
Open the your dialer app and type
Code:
*#06#
9. Sales Code
Open the your dialer app and type
Code:
*#272*IMEI-Number#
Changing the sales code causes a hardreset !!!
10. Net/SIM-Lock Status
Open the your dialer app and type
Code:
*#7465625#
11. Several Dialer Codes
Open the your dialer app and type
Phone Information:
Code:
*#*#4636#*#*
PDA, Phone, CSC, Build time, Changelist number:
Code:
*#*#44336#*#*
Modify Bandwide of GSM/WCDMA:
Code:
*#*#2263#
Hard Reset:
Code:
*2767*3855#
Touch Screen Test:
Code:
*#*#2664#*#*
Proximity Sensor Test:
Code:
*#*#0588#*#*
GPS Test:
Code:
*#*#1575#*#*
Melody Test:
Code:
*#*#0673#*#*
Shows WiFi MAC address:
Code:
*#*#232338#*#*
WiFi Test:
Code:
*#*#526#*#*
Please help me, to improve this thread. Whether it is an advice, a spelling or grammar mistake, please let me know, so I can correct it.
This is very useful FAQ, now we can just link user who will have questions about this topic.
in recovery mode, if i reboot it (the 1st choice) does it will wipe out all internal n external data?
sumerduk said:
in recovery mode, if i reboot it (the 1st choice) does it will wipe out all internal n external data?
Click to expand...
Click to collapse
Your question isn't very precise, so I guess you mean to ask whether it will delete your external and internal sd, if you select wipe data.
The external sd card will stay untouched. I am not 100% sure about the internal sd, usually it should stay untouched too. But I would advise you to make a Backup of the internal sd and, if you want to be on the safest side you should take out the external sd ;-D.
greets
THE-E
Download-Mode...........Where should be the firmware be placed ?
andynroid said:
Download-Mode...........Where should be the firmware be placed ?
Click to expand...
Click to collapse
This will be supplied externally via ODIN.
http://forum.xda-developers.com/showpost.php?p=20275502&postcount=173
greets
THE-E
Restoring Stock ROM
qzem said:
This is very useful FAQ, now we can just link user who will have questions about this topic.
Click to expand...
Click to collapse
Yes I agreed......a day before updated via OTA to 2.3.6 now the phone in unrootable.
Now downloading the ori FW to get it back to 2.3.5
Best of Luck to Me !
Now downloading the ori FW to get it back to 2.3.5
Best of Luck to Me ![/QUOTE]
if you already rooted in 2.3.5 and want to maintain the root in 2.3.6 you just need to update via phone (wifi) only and not kies. it'll install crucial new update only. if you update via kies or odin it'll install whole new firmware.
what i've noticed, update 2.3.6 via kies it need to download almost 500mb of data but only 15.33mb if via phone (wifi)
mine updated via phone (wifi), work perfectly and maintain rooted after update. but one of my friends lost the root after updated via kies.
---------- Post added at 08:19 AM ---------- Previous post was at 08:10 AM ----------
THE-E said:
Your question isn't very precise, so I guess you mean to ask whether it will delete your external and internal sd, if you select wipe data.
The external sd card will stay untouched. I am not 100% sure about the internal sd, usually it should stay untouched too. But I would advise you to make a Backup of the internal sd and, if you want to be on the safest side you should take out the external sd ;-D.
greets
THE-E
Click to expand...
Click to collapse
so,what is the function of "reboot the system" in the recovery mode? sorry for asking stupid question.
Odin Partition Script........Where to get this ?
NVM Settled...Fully Re-Stored Back to 2.3.5........Rooted n Now Doing Recovery !!!
andynroid said:
NVM Settled...Fully Re-Stored Back to 2.3.5........Rooted n Now Doing Recovery !!!
Click to expand...
Click to collapse
If you want rooted 2.3.6, you need to do the Root method using recovery. The automated script no longer work. I confirmed this is working.
See similar discussion: http://forum.xda-developers.com/showthread.php?t=1317394
I have a quick question. Do I need root to flash CWM via Odin?
I really like to flash KezraPlanes Rom afterwords.
klingel_One said:
Do I need root to flash CWM via Odin?
Click to expand...
Click to collapse
No, flashing in Download Mode does not require a rooted phone.
But I will need root, when i'm going to flash KezraPlanes' Rom over CWM?
klingel_One said:
But I will need root, when i'm going to flash KezraPlanes' Rom over CWM?
Click to expand...
Click to collapse
Nope, no root needed.
Inviato dal mio GT-I8150 usando Tapatalk
fender90 said:
Nope, no root needed.
Inviato dal mio GT-I8150 usando Tapatalk
Click to expand...
Click to collapse
Hi Guys,
I'm just bought this Galaxy W. I install the Kies and when plug in my phone, it prompt me to update firmware. I click yes and leave it there for more than 1 hour.
Now it loaded with new firmware 2.3.6
So do I need rooted for this?
Sorry if this is noob question.
Just added the code to check the SIM/Net-Lock status.
Are there more hidden codes left ? If so please let me know, I will add them.
greets
THE-E
Hidden codes
This code is file copy *#*#273283*255*663282*#*#* can't really see a use for it but still.
I have added an overview, a couple of questions and have resorted a bit.
I ask you to help me improving this FAQ in whatever way you can (questions, advices, spelling correction, etc.).
greets
THE-E
Small grammar/spelling mistake:
All directions are viewable and editable (with ES Explorer or Root Explorer)
Click to expand...
Click to collapse
I think you meant:
All directories are viewable and editable (with ES Explorer or Root Explorer)
Click to expand...
Click to collapse
Symphony W25 device Finally Rooted !
{
"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"
}
All credits go to jason_cheng
Procedure given below:
1. First of all, you need Drivers For your symphony W25 (Smphony.W25/Karbonn.A7/Mobistar.S01/Ktouch.W650 All are the same phone)
Driver for winXP
Get them here (uploaded by prasad12ka4) Or Here uploaded by rainwalker
Click to expand...
Click to collapse
Drivers for Win 7 / Win 8
Get them here
Click to expand...
Click to collapse
64-Bit Win 7 Drivers
Get them here
Click to expand...
Click to collapse
Install them while connecting your phone on "USB debugging mode", and going to "device manager > other devices" on your pc. After installation disconnect the phone.
(I believe some of you are having problems installing the drivers. I recommend you install the drivers on a freshly installed winXP pc. I faced a lot of trouble doing it on my Win8 pc)
2. Download Android software development kit (SDK) from Here and install in pc. Default installation Directory should be C:\Program Files\Android\android-sdk
3. Android SDK may need Java development kit (JDK) installed in pc. If you need jdk, go here or go to their Website to download
3. Download Fastboot From Android Central and keep it inside
C:\Program Files\Android\android-sdk\platform-tools folder
4. Download Clockwork Mod Recovery for w25 from Link #1 or Link #2, unzip and copy to the same folder. replace duplicate (if prompted).
5 hook your phone up with pc in USB debugging mode and go to C:\Program Files\Android\android-sdk\platform-tools folder, Press Shift+right click inside that folder and select "open cmd window here". It opens a cmd window for that folder.
In the cmd window, type
Code:
adb devices
If the driver installations are correct, you'll see your device connected as w650 (as symphony is re-branded from k-touch w650)
6. Disconnect phone from pc and reboot it into the bootloader, by turning it off and holding [vol-up]+[power]
Till screen turns green and says fastboot:recovery ?, Like below
7. Plug your phone into your computer. On cmd window, type:
Code:
fastboot devices
Reply should be "???????????? fastboot" Meanng fastboot detected the device.
8. In the cmd line, type
Code:
fastboot boot recovery-english.img
And that's it. You'll have booted into the custom recovery (cwmr), and from there you can do a full backup, or restore a backup, or wipe the phone. Use vol up/down to navigate through screen and Power to select an item.
9. Use CWMr to backup your ROM. (It will be saved in: "SD card/clockwork mod/backup" on phone.) and reboot. Copy the backup into pc for further use.
Step 8 was to make sure cwmr works on the phone. It's a temporary port of cwmr on your device.
if problem occurs (less likely to occur), let us know in a comment and don't proceed further.
Otherwise, Proceed below for permanent port..
10. Repeat step 6 and 7. Go to C:\Program Files\Android\android-sdk\platform-tools folder and click on recovery.bat file. Click on it and in the next window, Press any key
Permanent port will be completed
reboot phone if not rebooted automatically.
11. To check cwmr, Repeat step 6 but keep pressing the two buttons even if the screen turns green (fastboot). Continue until.....
screen is red (recovery). after that you'll see Clockwork mod recovery page.
You'll need it to restore your original rom if you mess up anything.
12 In CWMr,
a)]Go to Advanced
b) Choose "Wipe dalvik-cache"
c) Now go to "Mounts & Storage"
d) Choose "Format /cache"
e) Shutdown your phone
13. Download and unzip bootrepack from this post (by jason_cheng). Copy the "boot.img" file from "rootrepack" folder and paste to C:\Program Files\Android\android-sdk\platform-tools folder
14. Repeat steps 6 & 7 (green screen)
15. In cmd window type
Code:
fastboot flash boot boot.img
and
Code:
fastboot reboot
see image below if you have any confusion.
16. After the phone is restarted, type in cmd window:
Code:
adb shell id
which should result "uid=0(root) gid=0(root)"
Rooting is now Unofficially completed
17. To verify, Type each line in cmd window, and press enter
Code:
adb shell
Code:
echo "1" > /system/pwned
Code:
cat /system/pwned
If the Reply to the last line is "1", Congrats ! you have root access to your phone!!
Now remove that test file you created just now. Type:
Code:
rm /system/pwned
What now?
18. Install "Superuser" from Play store
It does not come with su binary. For that, Go to this post and download only the attachment. Unzip it and put the files in C:\Program Files\Android\android-sdk\platform-tools folder.
19. Now open cmd window, type each line and enter.
Code:
adb remount
Code:
adb push su /system/xbin/su
Code:
adb shell
Code:
chmod 4755 /system/xbin/su
now open superuser and check for su binary. I don't recommend su update.
20. Install "Busybox free" from Play store (optional)
Rooting Officially Complete.
If you face problems at any step, please let us know in comments. We'll try to help.you out.
Also feel free to try out the IceCream Sandwitch based roms & the upcoming Jelybean rom for Symphony W25 on the second post of this thread.
If any of you come across a new rom for w25. Please do share.
If you come across dead links on my thread, plz let me know by posting comments, or PM me.
If you find this post useful, then plz hit the thanks button and share it with people who have this phone and waiting for root
End of tutorial.
.usefull links:
Karbonn Mobile A5 & A7 (Android 2.3.6)
Link2sd tuorial in bangla: সহজেই বাড়িয়ে নিন অ্যান্ড্রয়েডের ইন্টারনাল মেমোরি
How To Solve Internal Memory Problem(Great Post)
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Here you'll find Custom ROM For Karbon A7 device. Which might also be campatible for Symphony w25. Read the respective posts/ comments carefully before downloading and installing.
(first of all back up your existing ROM with cwmr before any change you do to it.)
1) ICS ROM v1 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
2) ICS ROM v2 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
3) MIUI Gingerbread 2.3.7 ROM (update.zip file), moded By rainwalker
Click to expand...
Click to collapse
4) Rooted Stock ROM of Symphony W25 (update.zip file), uploaded By rainwalker
Click to expand...
Click to collapse
5) Stock Google android gingerbread for a7 by meosuper
Click to expand...
Click to collapse
6) ICS Huawei For Karbonn A7 / S01 by meosuper, Uploaded by ItsmezakiR
Click to expand...
Click to collapse
7) Official ICS ROM for Karbonn A7/Symphony W25 Uploaded by The Droid Master
Click to expand...
Click to collapse
8) Walton Primo ROM modified for A7 Uploaded by vinodkbishnoi
Click to expand...
Click to collapse
9) XION ROM FOR A5/A7 Uploaded by deadlyindian
Click to expand...
Click to collapse
10) ICS refresh V3 Uploaded by meosuper
Click to expand...
Click to collapse
11) CyanogenMod 10 (Karbonn A7) Beta Posted by prasad12ka4
Click to expand...
Click to collapse
12) Backstreet MOD™ v4.1.1 created by The Droid Master
Click to expand...
Click to collapse
13) Lithium 7 for Karbonn a7, symphony w25 and Mobiistar s01 Created by rainwalker
Click to expand...
Click to collapse
14) XINIX 8 for Symphony w25 Created by rainwalker (Recommended)
Click to expand...
Click to collapse
15) CyanogenMod 10 rom for W25 [Beta]
Click to expand...
Click to collapse
16) JELLYBEAN rom for W25 [Beta]
Click to expand...
Click to collapse
Maybe is needed to extract the "boot.img" to remove the restrictions on it, and make it rootable... Have you tried with generic "rooters"?
ICS Baseband Versions For Karbonn A7
ICS Baseband Versions For Karbonn A7 (= Symphony W25)
ItsmezakiR said:
1. 591369_8379_WCDMA_V000001
2. 591357_8376_WCDMA_V0005
3. 591352_8376_WCDMA_V0007
4. 591347_8376_WCDMA_V3070
Click to expand...
Click to collapse
ICS Search Key to Power Key (for Symphony W25)
vinodkbishnoi said:
Hi,
Karbonn A7 ICS. Now you can use search key of your A7 as power key.
Follow the procedure...
1. Download 7x27a_kp.kl.zip file and extract it.
2. Open terminal/Command prompt.
3. Connect your phone to PC via USB.
4. Run following commands.
c:/> adb devices
c:/> adb pull /system/usr/keylayout/7x27a_kp.kl
now copy this file on a safe place. So that if anything goes wrong you could be able to restore it.
now open folder where you have extracted the zip file. The extracted file will be of same name as "7x27a_kp.kl"
c:/> adb push <path to file 7x27a_kp.kl> /system/usr/keylayout/
Now reboot your phone. You will be able to use your search key as power key.
Click to expand...
Click to collapse
Change partition size on A7/W25
Part1:
Anil_Sharma said:
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Click to expand...
Click to collapse
Part2:
vinodkbishnoi said:
Hi,
I am attaching a file named "appsboot.mbn". This is used to determine partition size on android system.
There are two ways you could use it.
1. Replace appsboot.mbn file in any baseband update BP folder.
2. If you are handy with fastboot commands there is very simple method. Just boot your phone in fastboot mode (green screen mode) and use
following command....
C:\>fastboot flash APPSBL <path to appsboot.mbn>
And you are done.
You will find following changes.
1. Your partition size will be as shown in screenshot.
2. When you run command adb devices you will no more find S01 there, it will be A7
Download file here...
Download
Thanks
Click to expand...
Click to collapse
no one for help??
ahmed.zunaid said:
no one for help??
Click to expand...
Click to collapse
Your phone is the same with mobiistar s01 and karbonn a7, maybe the developer of symphony keep the original cpu clock(1ghz) and s01, a7 was underclocked to 800 to save battery. Now if you want to root.you must install fastboot driver and install cwm recovery for a7 first.then backup your current rom... when done, install rooted rom for s01 and you will have root, but your cpu will be underclocked to 800ghz.
And can you send me the link to download your backup rom??? I need the 1ghz kernel to mod my rom... thanks.
(If install drivers on w7 pc fail, try to use another pc with wXP-32bit).
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
ok ...
jason_cheng said:
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
Click to expand...
Click to collapse
I've used SuperOneClick before. In both 7 and XP machines. It gets stuck at "step 7".
Ok i'll try to do it again following your steps. I'll upload the screenshots
thanks for helping btw ...
No use ....
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
ahmed.zunaid said:
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
Click to expand...
Click to collapse
Unfortunately, CWMR needs to be built for your hardware in order for it to work. I think CWMR for the Karbonn should work without modification if it has the same hardware, so see if you can find info on getting CWMR onto the Karbonn. If the bootloader is really locked then you'll have to find some way to unlock first.
Backup the recovery partition [1] before doing anything, although I cannot verify whether it's the same partition across all phones. If anything goes wrong you will lose the ability to boot into recovery mode, but your phone will work. With a backup of the partition you can just bit-copy and rewrite the partition exactly as it was.
Because you already have the drivers installed using SuperOneClick, you may like to see now if Unlock Root works [2]. Else, go ahead and root the phone using the manual method. First, run the exploit [3]. Tell us how this goes, then we'll continue (basically upload the su binary and optionally the Superuser app). Otherwise we need to see what other exploit works.
[1] http://forum.xda-developers.com/showthread.php?t=1160213
[2] http://lifehacker.com/5873745/unlock-root-roots-nearly-250-android-devices-in-one-click
[3] http://forum.xda-developers.com/showthread.php?t=1296916
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks. I suspect the W25 does not have the Karbonn A7 hardware. If the Karbonn is a rebranded Mobilstar S01 then it has a Qualcomm ARMv7 processor. The Symphony phones (hypothesis based on the only one phone I have, that is a W10) are rebranded Tinno [1] phones, with MediaTek processors.
My W10 is ARMv6, so it depends on whether the W25 has an SoC based on the latest MTK proc (which is ARMv7) [2]. That is highly unlikely because it (the proc) would be too powerful for the model number. As you may or may not know, binaries are not portable across ARM cores.
The phones do indeed have the same chassis and general specs, but any attempt to port and/or copy files/ROMs must be taken with great care and precautionary steps. There is, of course, no rule that each model must depend on the same manufacturer, but it's better to be safe than sorry.
[1] tinno.com (i'm not allowed to post links, funny, did so in the previous post)
[2] mediatek.com
jason_cheng said:
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks.
...... ...... ......
Click to expand...
Click to collapse
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
ahmed.zunaid said:
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
Click to expand...
Click to collapse
Well, popular devices have more people tinkering with them and hence more results I suppose for budget devices we are on our own. After all, I believe these phones are pretty value for money and the effort to tinker is worth it.
Anyway, my suspicions are wrong. Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A.
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
jason_cheng said:
..... Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A. ....
Click to expand...
Click to collapse
it says HTC Desire VC T328d, Huawei Ascend C8812 ...
jason_cheng said:
............
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Not sure how to use these commands. It says that the phone needs to be rooted to use these.
I'm trying to install clockworkmod.
meanwhile, If you have time, plz provide a simplified tutorial.
The zergrush in http://forum.xda-developers.com/showthread.php?t=1296916 doesn't download btw
Sorry, yes, that needs root. You must do everything you can to get root on the phone, because whatever you do you must have a backup. For CWMR, you must back up your recovery partition, else if your CWMR image does not happen to be compatible with your device you risk losing recovery mode.
For MTK devices like the W10, there is a method for non-rooted phones to carry out the backup [1], but I'm not sure about Qualcomm. So in the end, root is unavoidable.
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
[1] bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
jason_cheng said:
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
Click to expand...
Click to collapse
Hellions with blue flames !
See The attached pic
I have the same phone It's original model is ktouch w650
i evem tried to use update.zip method but it says sd storage not found
how do i know if my bootloder is unlocked or locked
tried unlock root with driver installed it says failed to aquire root access\
in adb shell it shows $ sign and if i try to get root acess it says acess denied
Oh boy, it looks like the vulnerability has been patched in your version of Android. Either that, or there is some hardware peculiarity (buffer size being reported wrongly - that's also when this zergrush error comes up) which I do not yet know how to deal with. There is another exploit called 'tacoroot' but I do not prefer going that route as it's not as foolproof/universal as zergrush.
Update zips need to be signed. When your recovery tries to verify the signature it fails, as it is not the signature of the manufacturer that made the update.zip.
Have you guys tried ALL the rooting methods posted in the A5/A7 thread? In the meantime I'll take a look at how Qualcomm ROMs can be dumped.
edit: I'm pretty sure your device has a fastboot mode. If so, you can "hot" boot any cwmr image without flashing it using "fastboot boot theimage.img" as far as I can recall. Having fastboot is a blessing (which the MTK devices do not have) so follow the first few pages of the A7 thread.
thanks
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
shaon121 said:
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
Click to expand...
Click to collapse
Sorry, the W10 is my first ever experience with Android (I was looking for a cheap way to find out how the stuff works), and as it does not even have a bootloader mode I have no idea about fastboot. I have only been with this phone/Android for about a month, so there's still a lot more to learn.
But as far as I can tell "AP Fastboot" already implies that you are in fastboot mode. You need the fastboot drivers installed on your PC, and then when you are at the green screen the phone will accept fastboot commands. [1]
If you guys manage to do this, what I would suggest is hot-loading a Karbonn A7, Mobiistar S01 or any other potential compatible CWMR image, then immediately making a full ROM backup. You can then upload recovery.img and I'll see if I can port it, and after that boot.img so we can at least get you root adb shell if by then rooting is still a problem.
And btw, if it was not clear in my previous post, rooting using current "standard" methods is not going to work as the latest gingerbread vulnerability (which zergrush exploits and many of the tools use zergrush) has been patched since December 2011. Unfortunately, it looks like the build of 2.3.6 that the W25 has is from a period after that, so zergrush on the W25 is a no-go. If you want to try, just follow the adb steps above which was posted for ahmed.zunaid.
[1] http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus
INTRODUCING THE SAMSUNG GALAXY NOTE2 TOOLKIT
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
NOTE: If you want a new build added to the Toolkit then download and install, Type 'A' in the Model Selection screen and follow the instructions.
HOW TO VIDEOS ARE ON POST#4 (THANKS TO WWJOSHDEW) MAKE SURE YOU HAVE A LOOK AT THEM AS A VIDEO IS WORTH A THOUSAND WORDS
FUNCTIONS OF SAMSUNG GALAXY NOTE2 TOOLKIT V4.1.0 [9TH APRIL 2013]
Install 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 (different options)
Root with Superuser (ChainsDD) or SuperSU (Chainfire) via CWM (works on ANY build)
[*]Root+busybox+rename recovery restore files via Custom Recovery
[*]Unroot (delete root files and busybox)
[*]Many root/unroot options including adb, recovery and sideload via custom recovery
[*]Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC
[*]Pull /data and /system folders, compress to a .tar file and save to your PC
[*]Auto Update ToolKit to latest push version on startup (donator feature)
[*]Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
[*]Install BusyBox binary on phone
[*]Flash Stock Recovery
[*]Flash CWM Recovery (thanks to Clockworkmod Team) or TWRP Recovery (thanks to Team Win)
[*]Rename Recovery Restore files if present
[*]Flash Insecure Boot Image for adb mode
[*]Flash Stock Boot Image back to your phone
[*]Create tar file to flash via Odin (from upto 10 image files) with 1-click process
[*]Download, Extract and Flash Stock Rom (full DETAILED steps) ESSENTIAL FOR WARRANTY RETURNS
[*]Rip cache.img to zip file in CWM format for editing and flashing (thanks to Adam Lange)
[*]Install a single apk or multiple apk's to your phone (being worked on)
[*]Push Files from your PC to your phone
[*]Pull Files from your phone to your PC
[*]Set Files Permissions on your phone
[*]Dump selected LogCat buffers to your PC
[*]Dump BugReport to your PC (if installed)
[*]Help, Information Screen for various tasks
[*]Mods Section to Modify your phone (being worked on)
[*]Reboot Phone options in adb mode
[*]Change background, text colour in ToolKit
[*]Device Information screen which pulls info directly from device
[*]Activate Professional features from within the ToolKit
--------------------------------------------------------------
Mod edit: Download link removed
MD5 Sum for V4.1.0: 37360aabdf3869aad55d12dd2c2b0b07
NOTE: As the ToolKit.exe and ModsSection.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.
IMPORTANT: ONLY FLASH ROMS THAT ARE SPECIFICALLY MADE FOR YOUR PHONES MODEL NUMBER AS FLASHING AN INCORRECT ROM CAN SOFT BRICK YOUR DEVICE!
Credits: ChainsDD for Superuser, Chainfire for SuperSU, Chenglu for modded cwm.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN FREE (PUBLIC) AND DONATE (PROFESSIONAL) VERSIONS?
THE FREE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD POSSIBLY NEED TO MANIPULATE YOUR PHONE. NOTHING IS RESTRICTED. ACTIVATING THE DONATE VERSION WILL ADD THE ABILITY TO CHECK FOR UPDATES VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED TO MY SERVER WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. THIS ALSO MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE VARIANT OR CARRIER SO DONATOR VERSIONS WILL BE UPDATED SOONER. IF YOU ARE NOT ABLE TO, OR DO NOT WANT THE AUTO UPDATE FEATURE THEN ALL UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL DOWNLOAD VERSION AS SOON AS TIME ALLOWS AND THERE ARE ENOUGH UPDATES TO WARRANT IT. DONATORS WILL ALSO HAVE THE QUICK PICKS AND EXTRAS SECTIONS UNLOCKED AND THE 'NAG' SCREEN ON EXIT WILL BE DISABLED. NEW DONATOR FEATURES WILL ALSO BE ADDED TO THE TOOLKIT IN THE FUTURE.
AUTO REPLY LINKS FOR PAYPAL AND GOOGLE CHECKOUT TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
AUTO UPDATES ARE BY FAR THE EASIEST WAY TO KEEP THE TOOLKITS UP TO DATE AS I HAVE LOTS OF OTHER TOOLKITS TO LOOK AFTER. IF ANYONE HAS ANY VIEWS ON THIS PLEASE PM ME OR CONTACT ME AT [email protected]. PLEASE DO NOT POST YOUR VIEWS IN THIS THREAD AS I WANT TO KEEP IT CLEAN FOR USER SUPPORT.
{
"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"
}
(Changelog at the Bottom of Post#1)
--------------------------------------------------------------
PLEASE READ THE *FAQ* IN POST#2 BEFORE ASKING QUESTIONS
--------------------------------------------------------------
1. INSTALLING GALAXY NOTE2 DRIVERS
The first thing you need to do is to install the drivers. These are needed so that you can communicate with the phone via the PC and perform the tasks that the ToolKit offers.
NOTE: If you have Kies installed then it is advisable to uninstall it first to avoid conflicts.
a. Make sure your phone is booted into Android and the USB cable is unplugged.
b. Select Option 1 in the ToolKit to install the Samsung USB Driver pack. This should install all the neccessary drivers you need.
C. While the drivers are installing make sure that USB Debugging is enabled on your phone via the Settings, Developer options Screen.
d. After the drivers have been installed connect the USB cable and the PC should detect the phone and install the correct drivers. This will also happen when you enter Download Mode and Recovery Mode for the first time.
e. If you want to check the drivers then go to your Control Panel on your PC and open the Device Manager. With the USB cable connected you should see a device listed as 'Samsung Android Phone' or something similar and a driver attached to it.
NOTE: If you are having trouble with your device being detected or the drivers installing correctly then you could try rebooting your phone, using a different usb port and making sure no other drivers are installed on your pc.
--------------------------------------------------------------
2. USING MSKIPS' SAMSUNG GALAXY NOTE2 TOOLKIT
a. Download the Samsung Galaxy Note2 ToolKit package and run to install the ToolKit to your PC. The installation will also create a Shortcut on your desktop for easy access. You have the option to include or exclude the drivers files at installation so if you already have your drivers set up and are just updating the ToolKit then you can untick the drivers if you wish.
b. Once the ToolKit is installed make sure your phone is booted and plugged in via USB cable and double click on the shortcut on your desktop to run it.
c. You will be asked if you want to check for an Update. If you type 'yes' this will download and check the latest version numbers against the versions in the ToolKit. If there is an update available then you will have the option to download and install it (professional feature).
d. You will now be presented with a Model Selection Screen to choose the Model/Build that you are currently on. Type the number that corresponds to your desired selection. For example type '12' for INTERNATIONAL GSM MODEL [GT-N7100] 4.1.1 [Build ALJ1-ALJ3]. If you cannot find the build your device is using then type 'h' to select the HELP option to get more info.
NOTE: If you have a new build that isnt covered by the Toolkit you can also type 'a' in the Model Selection screen to see instructions on how to pull your stock image and send it to [email protected] so support can be added.
e. The Toolkit will now locate and download the boot image pack for your chosen Model. This is a new feature so the Toolkit is not limited to how many Models can be added and it cuts down ALOT on the download size. After the zip file has finished downloading it will be extracted to the correct folders and the files checked to make sure everything is ok.
f. When you enter the Main Menu you will see 'Adb Mode' at the top. If you have installed your drivers correctly then you will see your devices serial number under the text with 'device' next to it. If you see this then your device is connected and you can carry on.
NOTE: If you haven't installed the drivers and don't see a serial number at the top then this is the FIRST thing you want to do so the Toolkit can operate properly.
g. Each option in the ToolKit has full information on what it is and how to use it.
--------------------------------------------------------------
3. FLASHING A ROM, RADIO OR KERNEL VIA CWM RECOVERY
a. Download your chosen Rom, Radio or Kernel from the Development Forum, then make sure your phone is booted up as normal and connect your usb cable so it goes into MTP Mode. Copy the .zip file (DO NOT UNZIP IT FIRST) to the 'Internal Storage' part on your phone. Do not copy it to a Sub Directory as it will be harder to find when flashing it.
b. Enter CWM Recovery (shut down the phone then hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds).
c. Select 'Install zip from sdcard' and select 'choose zip from sdcard' if the file is on Internal Memory.
d. Scroll to your zip file and select. Then select 'Yes' in the list to start flashing.
e. When flashing is finished press the BACK Button to go back until you get to the Main Menu and then select 'reboot system now' to reboot your phone into Android.
--------------------------------------------------------------
4. FLASHING A ROM, RADIO OR KERNEL VIA DOWNLOAD MODE USING ODIN
Odin can be used to flash image files or parts of your phone. You can flash something as simple as a boot image or a complete system. Everything is packed in a tar or tar.md5 file on your PC and flashed via Odin which is a Windows OS program.
a. Make sure you have your tar file stored on your PC.
b. Reboot your phone to Download Mode [shut down your phone, then hold down the Home + Volume DOWN Buttons and press the Power Button for about 2 seconds until a Warning screen appears. Press Volume UP to continue to Download Mode.
c. Connect your phone via usb and the first box at the top under ID:COM should turn blue and have some text in it. If you are using Download Mode on your phone for the first time then you will notice drivers being installed to use it.
d. The site or page you downloaded the file from will usually give you instructions to set Odin but if not you want to load boot/recovery/system files to the PDA location and have 'Auto Reboot' and 'F.Reset Time' ticked and nothing else.
e. Click on 'Start' to start the flash. You can see what is happening in the text box in the lower left.
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
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 phone.
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.
--------------------------------------------------------------
ChangeLog
ToolKit v4.1.0 (9th April 2013)
+Updated complete Toolkit structure for easier support and faster updates
+Added GT-N7100T and GT-N7105T models to the support list
+Added 4.1.2 support for many models. See screenshot for full list
+Updated CWM and TWRP Recovery to the latest model specific version
+Added TWRP NAND backup/restore procedure to backups section
+Updated SuperSU Root procedure to V1.25
+Updated Samsung usb drivers to 1.5.18.0
+Added more error detection and updated many parts of the Toolkit procedures
+Added Activation option and support procedure for new builds to Model Screen
+Updated Stock firmware download section with new Samsung images
+Adb server is now shut down if you exit from Model Selection screen
+Added more error control Toolkit processes
+Updated mods section
ToolKit v3.0.0 (18th December 2012)
+Rewrote soo many parts its hard to list them all
+Changed the Model Selection screen
+Split up images for all supported models to make them easier to distinguish
+Added support for Verizon, GT-N7105 (lte), AT&T and Korean SK Telecom
+Added new options to Root/Unroot Screen
+Added root+busybox+rename recovery restore files via Custom Recovery
+Added Root/Unroot via Sideload feature in Recovery
+Updated CWM Recovery to 6.0.1.9
+Updated TWRP Recovery to 2.3.2.3 for all available Models
+Updated SuperSU to 0.99
+Added Device Information Screen
+Added instant reply donate link to Toolkit
+Soo many more behind the scene changes
ToolKit v2.0.0 (27th October 2012)
+Added FULL support for Sprint (SPH-L900)
+Added FULL support for TMobile (SGH-T889)
+Added FULL support for US Cellular (SCH-R950)
+Updated SuperSU Root zip file to V0.96
+Updated CWM Recovery to V6.0.1.5
+Added TWRP Recovery V2.3.1.1
+Added option on all Root procedures to root with Superuser (ChainsDD) or SuperSU (Chainfire)
+Added option in ALLINONE Root routine to flash cwm or twrp Recovery
+Improved Root procedure on all builds
+Made some edits for Toolkit stability
+More tweaks
ToolKit v1.0 (7th Oct 2012)
+First version of Samsung Galaxy Note2 ToolKit released
--------------------------------------------------------------
*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. 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 (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android 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 the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.
**RESERVED FOR MANUAL INSTRUCTIONS**
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
http://www.youtube.com/watch?v=M9zF6x1MURM
How To Flash Stock Recovery
http://www.youtube.com/watch?v=9CL5x84Tu_U
How To Manually Boot to Custom (or Stock) Recovery
http://www.youtube.com/watch?v=9m6Uugh8ps8&hd=1
Sent from my SPH-L710 using Tapatalk 2
Can i unroot with toolkit?.Many thank for awesome work..:good:
thank you! worked like a charm!!!
simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
Yes you can.
Mark.
So does this add to the flash counter?
Tiffany84 said:
So does this add to the flash counter?
Click to expand...
Click to collapse
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Mark.
simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
mskip said:
Yes you can.
Mark.
Click to expand...
Click to collapse
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
GREAT work and thank you for getting this into an easy toolkit form, as many people will be helped out by this!! I was already rooted, as some others were too, but you created a tool that needs a BIG :good:
teshxx said:
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
Click to expand...
Click to collapse
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Is TWRP supported on the TMo Note II?
mskip said:
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Click to expand...
Click to collapse
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Oh ok. I would, but I haven't rooted mine yet. Still deciding if I want to keep my grey one or exchange it for the white lolol. Hopefully, someone who is already rooted will be kind enough to do it for you.
Thanks for your effort and time.
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
PM sent w/ link for stock T889 kernel.img. build number is the file name. sorry i can't help with stock recovery.img since i already rooted and flashed CWM recovery.
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
hey mark, if u wanna post or PM me instructions i'll get u the mount points.
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
So nice to see you here. Thanks for all u do!!
Sent from my SGH-T889 using Tapatalk 2
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
LvDisturbed1 said:
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
Click to expand...
Click to collapse
I can use my extSD with CWM so it's something on your end. I used the toolkit for the N7100 but same stuff...
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
I just sent you a pm with the stock recovery.img from my device(T-Mobile Galaxy Note 2). My build number is JRO03C.T889UVALJ1. Hopefully this gives you what you need. Thanks again.
---------- Post added at 03:53 AM ---------- Previous post was at 03:43 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Just sent you a pm with the mount points for the T-Mobile Galaxy Note 2. Thanks for this tool. It's incredible.
................................
2013-07-21 -->> OP update links for download file UPDATE-SuperSU-v1.41.zip.
2013-06-22 -->> OP update links for download file UPDATE-SuperSU-v1.34.zip.
2013-06-08 -->> OP update links for download file UPDATE-SuperSU-v1.32.zip.
2013-06-03 -->> OP update links for download file UPDATE-SuperSU-v1.30.zip.
OP update links for put CWMv6: Direct download CWMv6 (recovery.img) by williegomezt.
For new JB V07 update: Direct download drivers and SP_Flash_Tool_exe_v3.1224.01.
Do you think this will work with other BLU devices? I am thinking about buying a Dash 4.0, but I wouldn't want it without root.
dskrilz said:
Do you think this will work with other BLU devices? I am thinking about buying a Dash 4.0, but I wouldn't want it without root.
Click to expand...
Click to collapse
You searched if there is someone who managed to ROOT your device here in xda?
Root MANY ANDROID! [Upd: 24.04.2013]
I'm also on other forums and had been trying to help a friend who needed to ROOT [BLU Tank 4.5] that has fastboot mode.
[TUTORIAL] Root Blu Dash 4.0
We try ROOT through this process and believe that you can try too. So I do not have these devices, and you must read a lot before making a decision. Before any procedure must have stock ROM or at least a backup of it.
BLU Dash 4.0 has [Chipset Qualcomm MSM8225 Snapdragon]. Furthermore, this procedure Super_Su did not work for with the original recovery BLU VIVO 4.3 ROM JB 4.1.1. With recovery original it says "Installation aborted".
Blu Vivo 910a Jelly Bean generic Rom- How to root
I have a Blu Vivo 4.3 910 a which I updated with the generic Rom from Blu.Did someone root this version.
I tried many like One Click, z4root Version 1.3, root with reset version v.29, but nothing is working.
Also it does not accept update zip Version v.25 it says aborted.
How could it be rooted?
lopestom said:
Download to perform ROOT (if your choice) and place them on your sdcard ---> UPDATE-SuperSU-v1.25.zip
[03.03.2013] SuperSU v1.25 ---> http://forum.xda-developers.com/showthread.php?t=1538053 << --- >> original link -- Thanks for this xda developers.
With the phone turned off, press POWER and VOL +.
Appears CWM v6 -> select install zip from sdcard ---> choose zip from sdcard -> find file with VOL - or VOL + file [UPDATE-SuperSU-v1.25.zip]
{
"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"
}
Select YES with POWER. There, at the end of the process SU is installed.
Go + ++ Go Back + + + up to find -> reboot system now. Select with POWER.
When you restart the phone, mark in ---> configuration ---> Security --> Unknown sources.
For more details see my other Thread --> Loss IMEIs
So you now have installed a upgraded SuperSU-v1.25.
This it! Your device is ROOTed. :good:
Credit to xda developers for UPDATE-SuperSU-v1.25.zip .
For helping to make it happen => Mario Doce; williegomezt
Click to expand...
Click to collapse
bluvivo said:
I have a Blu Vivo 4.3 910 a which I updated with the generic Rom from Blu.Did someone root this version.
I tried many like One Click, z4root Version 1.3, root with reset version v.29, but nothing is working.
Also it does not accept update zip Version v.25 it says aborted.
How could it be rooted?
Click to expand...
Click to collapse
You must have knowledge of tool SPFT- [SP Flash Tool] to put on BLU VIVO 4.3 device only file "recovery.img" by @williegomezt (CWMv6 - see my signature).
---------------------------------------------------------------------------------------------
Download links are directly updated in the forum.
lopestom said:
You must have knowledge of tool SPFT- [SP Flash Tool] to put on BLU VIVO 4.3 device only file "recovery.img" by @williegomezt (CWMv6 - see my signature).
---------------------------------------------------------------------------------------------
Update links direct in forum.
Click to expand...
Click to collapse
Thanks but there to I get the recovery.img file? The Flash Tool I have.
bluvivo said:
Thanks but there to I get the recovery.img file? The Flash Tool I have.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=33100711&postcount=51
Download [VIVO 910a CMW by williegomezt.rar] unzip the rar file with the password for placed on the post. Inside this file rar have [recovery.img (CWMv6)].
I have the img.file and the flash tool all goes well but and the download and the phone conected it does not have the driver for the USB.
So there is no download.I download the driver but still is not working.Any help?
lopestom said:
http://forum.xda-developers.com/showpost.php?p=33100711&postcount=51
Download [VIVO 910a CMW by williegomezt.rar] unzip the rar file with the password for placed on the post. Inside this file rar have [recovery.img (CWMv6)].
Click to expand...
Click to collapse
Correct procedures to install the drivers.
bluvivo said:
I have the img.file and the flash tool all goes well but and the download and the phone conected it does not have the driver for the USB.
So there is no download.I download the driver but still is not working.Any help?
Click to expand...
Click to collapse
What system you are using Win XP/Vista/7/8?
I'll pass the correct procedures to install the drivers:
On the computer:
Go to the Drivers folder and run "InstallDriver" (for the file I'm sending you).
On your device:
Connect the device to your computer, go to Settings, Options programmer, Activate and check "USB Debugging" and press OK.
On your computer:
1 - Go to device manager, click on unknown device or wrongly recognized (MT65XX Preloader);
2 - MT65XX Preloader updating drivers, click browse for driver software on this computer;
3 - Type of Device, click Show All, and then click Have Disk and browse to the folder "Driver\ADB" and select the file [android_winusb.inf];
See this image for [android_winusb.inf]:http://forum.xda-developers.com/showpost.php?p=38864558
4 - Select Android Composite ADB Interface;
5 - If message appears, requesting confirmation to install, confirm, appear to Windows Security box, asking if you want to install Google Inc, Select Always Trust and install;
6 - Now just do the procedure in SPFT to put only the recovery (CWMv6).
Remember that with Win7 installations should always be run as administrator!
Check this with @tanmay5 in mmxA110 #38 ------->>>> http://forum.xda-developers.com/showthread.php?t=2167244&page=4
For Win8 disable UAC:
3. open control panel in win8 the metro you one not classic one. I think u all might be knowing how to go there.
There click on general tab then click - advanced startup n press restart.
then go to troubleshoot option in press option 7 i.e disable driver signature. Thats the most Important step.
4. your pc will get restarted null enter in the in that option.
5. your UAC (User Account Control) must be enabled atleast to the recommended level/2nd one from the top.
Click to expand...
Click to collapse
This is information within [VIVO 4.3 Tool\Driver_Auto_Installer\Driver_Auto_Installer]:
Driver_Auto_Installer_v1.1208.00
ReadMe.txt
Click to expand...
Click to collapse
Code:
This application will install USB com port driver for MediaTek's device those IDs are listed below:
1."VID_0E8D&PID_0003" (FeaturePhone & Smartphone BootROM - MTK USB Port)
2. "VID_0E8D&PID_0023&MI_00" (FeaturePhone - MTK USB Modem Port)
3."VID_0E8D&PID_0023&MI_02" (FeaturePhone - MTK USB Debug Port)
4. "VID_0E8D&PID_2000" (SmartPhone - PreloaDer USB Port)
5. "VID_0E8D&PID_2001" (SmartPhone - DA USB Port)
6. "Vid_0E8D&PID_2006&MI_02" (SmartPhone - Kernel Gadget USB port, Please customize your kernel VID/PID)
"Vid_0E8D&PID_2007"
"Vid_0E8D&PID_200a&MI_02"
The application user must belong to Administrator group or have the privilege to install driver.
the execution of the InstallDriver.exe will install the driver, and the UninstallDriver.exe is special for remove driver.
the InstallDriver.exe will remove the legacy version of driver before install current driver automatically.
Notes:
1. Windows 2003 use the INF files which under the 2K_XP_COM
2. The device which generates two com ports (USB Modem Port Driver & USB Modem Debug Driver) only support Systems after Win XP sp3 version.
If you want to support these devices in Win XP Sp2, add these patchs:
http://support.microsoft.com/kb/918365/
http://support.microsoft.com/kb/935892/
lopestom said:
Download to perform ROOT (if your choice) and place them on your sdcard ---> UPDATE-SuperSU-v1.34.zip
[03.03.2013] SuperSU v1.34 ---> http://forum.xda-developers.com/showthread.php?t=1538053 << --- >> original link -- Thanks for this xda developers.
Works for both models BLU VIVO 4.3 - D910a and D910i. If you are not with this device, then you should search or create CWM for your own device.
For put CWM v6 in BLU VIVO 4.3 see this: HOW TO PUT CWM v6.0.1.2 by williegomezt
For more details to put "recovery.img" using SPFT see Flashing only part of the ROM: [TUT]MTK Android (Sp flash tool ) tutorialhttp://forum.xda-developers.com/showthread.php?t=1982587
Download SP_Flash_Tool_exe_v3.1224.01 and INSTALL drivers: VIVO 4.3 Tool 20130322.rar
On your device ---> configuration ---> Security --> check the option=> Unknown sources.
Instructions after putting CWMv6: With the phone turned off, press POWER and VOL +.
Appears CWM v6 -> select install zip from sdcard ---> choose zip from sdcard -> find file with VOL - or VOL + file [UPDATE-SuperSU-v1.34.zip]
Select YES with POWER. There, at the end of the process SU is installed.
Go + ++ Go Back + + + up to find -> reboot system now. Select with POWER.
So you now have installed a upgraded SuperSU-v1.34.
That's all! Your device is ROOTed. :good:
Credit to xda developers for UPDATE-SuperSU-v1.34.zip .
For helping to make it happen => Mario Doce; williegomezt
Click to expand...
Click to collapse
I have an error when I use SPFT. I downloaded and installed the MT6577 USB VCOM drivers from http://www.filecrop.com/MT6575-USB-VCOM-drivers.html and they installed fine.
I then followed your instructions for loading your recovery.img file to my phone. I got as far as the blue load line and then I got an SPFT error
BROM EROR : S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
and then it stops.
Any ideas?
rederikus said:
I have an error when I use SPFT. I downloaded and installed the MT6577 USB VCOM drivers from http://www.filecrop.com/MT6575-USB-VCOM-drivers.html and they installed fine.
I then followed your instructions for loading your recovery.img file to my phone. I got as far as the blue load line and then I got an SPFT error
BROM EROR : S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
and then it stops.
Any ideas?
Click to expand...
Click to collapse
This is something related to installing drivers. Another interesting case is USB plug behind the PC.
Check this for more drivers MT6577. Download your version for SO (W8/W7/Vista/XP )--> [TUT] Instructions MTK6577 USB VCOM Driver Installation
I read in other posts that you have Win8 and this is not good. But many friends managed. Read post # 10, disable UAC, see picture of correct installation and try again. See this for correct install drivers: http://forum.xda-developers.com/showpost.php?p=38864558
Another attempt is to use scatter file this on my forum [TUT] HOW TO INSTALL ROM 4.1.1 JB - BLU VIVO 4.3 D910i. Download the BLU_D910i_V06_GEN_T8113_20130322_CWM.rar, unzip. In SPFT, select only the option [RECOVERY].
Root blu dash 4.0
dskrilz said:
Do you think this will work with other BLU devices? I am thinking about buying a Dash 4.0, but I wouldn't want it without root.
Click to expand...
Click to collapse
Watch this video: youtube-->How to root Blu Dash 4 0
follow his link to get the rootme pack...
You will need the adb driver... since BLU doesn't provide this anywhere you can install it via installing pdanet...
search google for "topnotchtablets installADBDriver"
I first installed ADB, then I ran the root script and voila my BLU DASH 4.0 was rooted... took me a while to find this out.. searched everywhere for the correct adb driver...
enjoy!:good:
I cannot post links yet because I just registered to this forum today... I would have posted the links tho.. sorry
zachpainter77 said:
Watch this video: youtube-->How to root Blu Dash 4 0
follow his link to get the rootme pack...
You will need the adb driver... since BLU doesn't provide this anywhere you can install it via installing pdanet...
search google for "topnotchtablets installADBDriver"
I first installed ADB, then I ran the root script and voila my BLU DASH 4.0 was rooted... took me a while to find this out.. searched everywhere for the correct adb driver...
enjoy!:good:
I cannot post links yet because I just registered to this forum today... I would have posted the links tho.. sorry
Click to expand...
Click to collapse
I have helped some users BLU. Since then sought to unite all and maybe we can do a full forum here on xda.
So, see this #47: Blu Dash 4.0 D270i Rom damaged after Root
and this: [Q] Custom ROM for the BLU Dash 4.0???
BLU Users Unite
lopestom said:
I have helped some users BLU. Since then sought to unite all and maybe we can do a full forum here on xda.
So, see this #47: Blu Dash 4.0 D270i Rom damaged after Root
and this: [Q] Custom ROM for the BLU Dash 4.0???
Click to expand...
Click to collapse
y this is a good idea . . . There is not enough support for BLU devices out there . . .
ROOT in BLU VIVO 4.3 - JB 4.1.1 - without using SPFT
Hello I did otherwise the root device of people who do not know or do not want to use SPFT.
So read the instructions well and be happy. I researched other ways, but just found this one with Chinese software. Remember: It will install an application Chinese. But I made a tutorial that this app can be removed later.
TUTORIAL ROOT in BLU VIVO 4.3.pdf
VRoot_1.2_Setup.rar
Or see more images here: Guide - How to Root BLU VIVO 4.3 with JB 4.1.1
HOW TO INSTALL ROM 4.1.1 JB - BLU VIVO 4.3 D910a
"Follow my instructions:
- Start again with a new download of the official file.
The battery must be at least half the load.
1. Visit the website: blu.kiwibed.com You must enter the username and password to access the folders
Username: blusoft
Password: aplic10
2. Enter the folder Aplic Software / Software Vivo 4.3 generic.
3. Select the model of your phone (BLU-D910I or BLU-D910A)
4. Download the zipped file on your computer
5. After downloading the file, upload it to the direct sdcard. No need to unpack
6. Turn off the phone and turn it back on leaving the keys pressed simultaneously volume + and power.
7. Menu will appear in the android recovery. With the volume buttons you browse options in this menu and the power button validates the selected option.
8. Appear => Execute/Press --> Wipe factory
9. Appear => Execute/Press --> Wipe cache
10. Choose the option: "apply update from sdcard"
11. Browse by sdcard and choose the file you downloaded.
12. Then the phone will restart and update the new version of android."
I followed the above instructions, now my phone won't boot. Message was; Installation Aborted. So I re-boot it and got stuck to the "Blu Logo". Any help is greatly appreciated to go back to stock rom (ics).
Fherby said:
I followed the above instructions, now my phone won't boot. Message was; Installation Aborted. So I re-boot it and got stuck to the "Blu Logo". Any help is greatly appreciated to go back to stock rom (ics).
Click to expand...
Click to collapse
You're writing in the wrong place. Furthermore, the update should be placed with the original recovery. If you have a BLU VIVO 4.3, then you should not fear anything. So many people make the direct download to phone. This is wrong!
First on the PC and then put the sdcard. It may be that the file you downloaded came with errors.
If you have CWMv6 and backup, is back to normal. If not, try again another update file. If not, put JB version 6 in forum [TUT] HOW TO INSTALL ROM 4.1.1 JB - BLU VIVO 4.3 D910i. Read all the posts and see how to put the JB version 7.
Do not write here again on other matters, that is not the issue ROOT!
lopestom said:
You're writing in the wrong place. Furthermore, the update should be placed with the original recovery. If you have a BLU VIVO 4.3, then you should not fear anything. So many people make the direct download to phone. This is wrong!
First on the PC and then put the sdcard. It may be that the file you downloaded came with errors.
If you have CWMv6 and backup, is back to normal. If not, try again another update file. If not, put JB version 6 in forum [TUT] HOW TO INSTALL ROM 4.1.1 JB - BLU VIVO 4.3 D910i. Read all the posts and see how to put the JB version 7.
Do not write here again on other matters, that is not the issue ROOT!
Click to expand...
Click to collapse
Sorry for writing my comments in the wrong place. Anyway, thanks for the additional info you've provided.