Develop Bugs

[Video] How to Unlock n Root GNex with Superboot

Credit for the written tutorial goes to sbenson1226
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.

Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith

CDMA problem
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
This is something I would like to know too.

Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?

If you have clockworkmod installed with your stock rom. Once you restart the phone it will wipe clockworkmod and install back the stock recovery.
Sent from my Nexus One using xda premium

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
Yes you can unroot by flashing the system image... it requires adb check out my channel , I'll try to post the video here asap
Sent from my Galaxy Nexus using XDA App

Master K said:
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K
Click to expand...
Click to collapse
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App

mikeacela said:
Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?
Click to expand...
Click to collapse
You will still be able to accept ota
Sent from my Galaxy Nexus using XDA App

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Click to expand...
Click to collapse
I did not pull the USB. I did it twice so I know the lock unlock sequence fixes the phone.
I did the unlock without issue and then when I do install-superboot-windows.bat the phone reboots, I get the Google with the unlocked padlock and there it sits. Well past 5min. I did an adb logcat and I can see it is stuck in a bootloop so I pull the battery and lock and unlock again. I rebooted and the phone started up as if new. As I said i went through all this twice (never pulling the USB) and the same result.

I followed this guide letter by letter and it worked perfectly. BTW I have the LTE nexus

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
never mind

I downloaded both links,
installed the drivers,
made sure the newly files (superboot) where in a file named root on the C:\
rebooted phone in to fastboot, then plugged it into the computer
started command prompt
made sure I was in the C:\root directory
typed in fastboot-windows oem unlock
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
the instructions mention pdanet... I never saw that install anywhere so maybe i am missing a step

I can not get the drivers i downloaded from the link to work. It took forever to run the exe and install them, like an hour, and then the install was unsuccesful.

Epicrean said:
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
Click to expand...
Click to collapse
Had to boot the phone back in to the bootloader and rerun the install-superboot-windows.bat. Then my phone rebooted right away. Been sitting on the Google screen for a while...past 5 minutes...so hopefully it will go through.
EDIT: Waiting 15 minutes and phone was still stuck on the black screen with the while Google logo. Pulled battery and phone booted and was rooted. Odd....

is it just me or the download link is down as of 12/18/11?

Followed instructions (although I got the driver from elsewhere, so didn't need the PDAnet files).
Installed loads of apps and such. Turned phone off, then on again. After I rebooted though, my phone appears not to be rooted anymore. Superuser doesn't seem to do anything (although it's on the phone) and Root Explorer says it is denied root permissions from Superuser.
Downloaded Superuser fix from the market which says my phone isn't rooted.
If I just type the "install blah de blah" command again (IE, missing out the unlock oem as the bootloader should still be unlocked), then will it wipe my phone? Don't really fancy installing all the apps again.
Will this then be permanently rooted?

owenbeals said:
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.
Click to expand...
Click to collapse
Hmmm, this tutorial looks strikingly similar to the one I created at DroidForums. A little credit would be nice - or please completely rewrite it. Thanks.
Sent from my Galaxy Nexus using XDA App

The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...

Try the PDA net application on your comp, it will properly install the Samsung drivers so you can adb
Sent from my Galaxy Nexus using xda premium

[Q] Fastboot not working

I unlocked the bootloader, root, but when i plug in my xperia play holding search button i get:
18/049/2011 19:49:21 - INFO - <- This level is successfully initialized
18/049/2011 19:49:34 - ERROR - Device connected in normal mode.
18/049/2011 19:49:34 - ERROR - Drivers need to be installed for connected device.
18/049/2011 19:49:36 - INFO - Device connected with USB debugging off
I have to do this if i want clockworkmod recovery and install doomlord kernel right? Please help me i'm trying to learn as fast as i can

Thats flashtool, it has nothing to do with fastboot :|
Sent from my R800i using Tapatalk

AndroHero said:
Thats flashtool, it has nothing to do with fastboot :|
Click to expand...
Click to collapse
And? How do I install a custom kernel? To flash the kernel i have to be in fastboot mode :S but my crappy w7 makes a sound like *du-du-du* and not *du-di!* like when you connect an usb cable

To flash a custom kernel, you use the android sdk. Copy the boot.img to the same folder as fastboot.exe fire up a command prompt. Hold back on device and connect usb cable, then type "fastboot flash boot boot.img into the prompt.
Sent from my R800i using Tapatalk

doesn't work, I hold back and plug in the phone, but it's flash mode; and when i type fastboot flash boot boot.img it just says < waiting for device > and after around 50 sec it exit from flash mode what am i doing wrong?

hold down the search button when turning on...

search button for fastboot mode and back button for flashmode. Use gordongate drivers if you intend to flash. They are supplied with the the flashtool package.

i've installed gordon's gate drivers and the pc recognize the phone in flash mode but fastboot mode still not working
here's the log, first i tried with flash mode and then with fastboot mode but it says error:
20/019/2011 17:19:43 - INFO - <- This level is successfully initialized
20/019/2011 17:19:51 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
20/019/2011 17:19:52 - INFO - Device Status: NOT FOUND
20/019/2011 17:19:53 - INFO - Finished Fastboot Toolbox
20/023/2011 17:23:07 - INFO - Device connected in flash mode
20/023/2011 17:23:49 - INFO - Device disconnected
20/024/2011 17:24:02 - INFO - Device connected with USB debugging off
20/024/2011 17:24:09 - INFO - Device disconnected
20/024/2011 17:24:18 - ERROR - Device connected in normal mode.
20/024/2011 17:24:18 - ERROR - Drivers need to be installed for connected device.
20/024/2011 17:24:20 - INFO - Device connected with USB debugging off

Are you running Windows 7, I had a nightmare with the usb drivers-even the Gordon gate one didn't work-I found the solution in the arc forum, sorry but I can't find the post I think users name was lollylops, check your device manager to see if you have s1boot driver problem if so then you need the different drivers
Sent from my R800i using xda premium

yes i'm running windows 7, and i've found this: http://forum.xda-developers.com/showthread.php?t=1274199 and downloaded drivers for s1boot fastboot from that thread. Now, how do I install them? I've an x86 folder, ethernet, modem, usbwin, i386.... i've no idea, but i think we're close

Celluciano said:
yes i'm running windows 7, and i've found this: http://forum.xda-developers.com/showthread.php?t=1274199 and downloaded drivers for s1boot fastboot from that thread. Now, how do I install them? I've an x86 folder, ethernet, modem, usbwin, i386.... i've no idea, but i think we're close
Click to expand...
Click to collapse
no offence but if you don't no how to install drivers on windows you should not unlock your bootloader
Sent from my R800i using Tapatalk

fma965 said:
no offence but if you don't no how to install drivers on windows you should not unlock your bootloader
Click to expand...
Click to collapse
no offence but i've already unlocked my bootloader with test point

Unfortunately I have the memory of a goldfish, I think that you have to put the phone into fastboot then goto device manager on the pc and update the drivers for s1boot by pointing to where you have put the drivers,
Sent from my R800i using xda premium

fma965 said:
no offence but if you don't no how to install drivers on windows you should not unlock your bootloader
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I had a nightmare with this, it seems some versions of Windows 7 are fussy with certain fastboot drivers, it sound like the op is struggling the same way I did, I was close to giving up until I came across drivers that worked
Sent from my R800i using xda premium

Ok i managed how to install them through device manager. I select the folder but it says (translated to english) : "Device's driver has been found, but an error occurred during the installation. Android ADB Interface - Impossible to find the specified file. WHAT!?
EDIT: PROBLEM SOLVED here's how: http://forum.xda-developers.com/showthread.php?t=1299729 i dowloaded drivers from here and they worked but now i've some QUESTIONS:
1)With unlocked bootloader (i kept drm certificates) and root, can i update trough OTA?
2)Now i'm going to flash doomlord kernel: has it the recovery integrated?

Celluciano said:
Ok i managed how to install them through device manager. I select the folder but it says (translated to english) : "Device's driver has been found, but an error occurred during the installation. Android ADB Interface - Impossible to find the specified file. WHAT!?
EDIT: PROBLEM SOLVED here's how: http://forum.xda-developers.com/showthread.php?t=1299729 i dowloaded drivers from here and they worked but now i've some QUESTIONS:
1)With unlocked bootloader (i kept drm certificates) and root, can i update trough OTA?
2)Now i'm going to flash doomlord kernel: has it the recovery integrated?
Click to expand...
Click to collapse
I think you would be safer flashing firmware from here, ota will, probably brick your own.
Doomlord kernel has got recovery, after installing boot up and when the doomlord picture appears
Keep tapping the back button
Sent from my R800i using xda premium

[Video] How to Unlock n Root GNex with Superboot

Credit for the written tutorial goes to sbenson1226
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.

Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith

CDMA problem
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
This is something I would like to know too.

Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?

If you have clockworkmod installed with your stock rom. Once you restart the phone it will wipe clockworkmod and install back the stock recovery.
Sent from my Nexus One using xda premium

FlagAZ said:
Question, when using superboot, is there a way to unroot the root if needed? If so do you have the steps to unroot?
Thanks,
Keith
Click to expand...
Click to collapse
Yes you can unroot by flashing the system image... it requires adb check out my channel , I'll try to post the video here asap
Sent from my Galaxy Nexus using XDA App

Master K said:
I have a brand new Verizon Galaxy nexus. I have the bootloader unlocked but everytime I tried to do the boot.img step it would just stay on the Google screen forever. I did an adb logcat and I could see it failing and looping over and over again.
Any idea what I should try? Could the update to 4.02 have caused this?
Thanks,
Master K
Click to expand...
Click to collapse
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App

mikeacela said:
Its been a long while since I've done Android mods haha, If I root and stay on stock rom with CWM recovery, Will I still be able to do the 4.0.3 OTA? or will the recovery not be able to apply the update?
Click to expand...
Click to collapse
You will still be able to accept ota
Sent from my Galaxy Nexus using XDA App

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Click to expand...
Click to collapse
I did not pull the USB. I did it twice so I know the lock unlock sequence fixes the phone.
I did the unlock without issue and then when I do install-superboot-windows.bat the phone reboots, I get the Google with the unlocked padlock and there it sits. Well past 5min. I did an adb logcat and I can see it is stuck in a bootloop so I pull the battery and lock and unlock again. I rebooted and the phone started up as if new. As I said i went through all this twice (never pulling the USB) and the same result.

I followed this guide letter by letter and it worked perfectly. BTW I have the LTE nexus

owenbeals said:
This process wipes the data.. did you pull USB during the process... either way go into boot loader and lock boot loader by typing OEM lock instead of OEM unlock and try again this time don't pull the USB cable
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
never mind

I downloaded both links,
installed the drivers,
made sure the newly files (superboot) where in a file named root on the C:\
rebooted phone in to fastboot, then plugged it into the computer
started command prompt
made sure I was in the C:\root directory
typed in fastboot-windows oem unlock
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
the instructions mention pdanet... I never saw that install anywhere so maybe i am missing a step

I can not get the drivers i downloaded from the link to work. It took forever to run the exe and install them, like an hour, and then the install was unsuccesful.

Epicrean said:
Alls I get is a massage saying "waiting for device" (yes the device is hooked up to the computer via USB)
Click to expand...
Click to collapse
Had to boot the phone back in to the bootloader and rerun the install-superboot-windows.bat. Then my phone rebooted right away. Been sitting on the Google screen for a while...past 5 minutes...so hopefully it will go through.
EDIT: Waiting 15 minutes and phone was still stuck on the black screen with the while Google logo. Pulled battery and phone booted and was rooted. Odd....

is it just me or the download link is down as of 12/18/11?

Followed instructions (although I got the driver from elsewhere, so didn't need the PDAnet files).
Installed loads of apps and such. Turned phone off, then on again. After I rebooted though, my phone appears not to be rooted anymore. Superuser doesn't seem to do anything (although it's on the phone) and Root Explorer says it is denied root permissions from Superuser.
Downloaded Superuser fix from the market which says my phone isn't rooted.
If I just type the "install blah de blah" command again (IE, missing out the unlock oem as the bootloader should still be unlocked), then will it wipe my phone? Don't really fancy installing all the apps again.
Will this then be permanently rooted?

owenbeals said:
What do I need?
Superboot : DOWNLOAD
Drivers: You will need to install this driver.
The Process:
Download the above files and install the driver. For the driver, it installs Pdanet on both your computer and phone. Follow the directions carefully. Pdanet will be wiped from your phone once you run Superboot. After the driver is installed, feel from to uninstall Pdanet from your computer – the driver will remain.
Extract the contents of Superboot and rename the folder “root.” Place this folder into C:\ (you may be asked for admin privileges).
Power down the phone.
Connect the phone to your computer.
Boot the phone into the bootloader by simultaneously holding Volume Up + Volume Down + Power.
Open up the command prompt in Windows:
Click Start Menu, then in the search bar type: cmd (this will open the command prompt);
Type the following: cd C:/
Then type the following: cd root
The next step will unlock your bootload - this will wipe all data on your device.
Type the following, in the command prompt: fastboot-windows oem unlock
You will receive a warning about unlocking. Use the volume keys to select an option and use the power button to confirm.
Your bootloader will now say: Lock State – Unlocked (near the bottom) as well as “Fastboot Status – Okay”
Now, to root your device, simply double click: install-superboot-windows.bat that you originally placed in the root folder in step 2.
Your phone should reboot on its own.
Be patient while it reboots, and don’t worry – first boot may take up to 5 minutes.
After phone set up, confirm Superuser app in your app tray.
All credit for this tutorial goes to:
Evostance and
Paul O’Brien
Useful root apps:
Busybox
Rom Manager
Titanium Backup
Root Explorer
Questions?
The above method unlocks your bootloader AND roots your device.
You do not need ADB.
This does not put a custom recovery on your phone.
This does not put a custom rom on your phone.
Yes, your phone is still stock.
Yes, you will still receive OTA’s from Google/Verizon.
This only puts Superuser on your phone, you need to install busybox yourself.
Click to expand...
Click to collapse
Hmmm, this tutorial looks strikingly similar to the one I created at DroidForums. A little credit would be nice - or please completely rewrite it. Thanks.
Sent from my Galaxy Nexus using XDA App

The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...

Try the PDA net application on your comp, it will properly install the Samsung drivers so you can adb
Sent from my Galaxy Nexus using xda premium

[Q] [HELP] C1905 stuck on bootloop, USB debugging off

I modified the build.prop file in the /system because I tried to enable a feature from Xperia Z1 I found somewhere in this forum. (I was a fool, yes.) When I rebooted my phone, it got stuck in a bootloop and I can no longer access recovery mode. I tried to flash stock ROM but unfortunately, USB debugging is off. What should I do? I know a Nexus user who was able to flash his phone with USB debugging off but his procedures are specific for Nexus only. Help me, please
Details:
C1905 15.4.A.1.9
Rooted using Nicki root
Unlocked bootloader

bananabee said:
I modified the build.prop file in the /system because I tried to enable a feature from Xperia Z1 I found somewhere in this forum. (I was a fool, yes.) When I rebooted my phone, it got stuck in a bootloop and I can no longer access recovery mode. I tried to flash stock ROM but unfortunately, USB debugging is off. What should I do? I know a Nexus user who was able to flash his phone with USB debugging off but his procedures are specific for Nexus only. Help me, please
Details:
C1905 15.4.A.1.9
Rooted using Nicki root
Unlocked bootloader
Click to expand...
Click to collapse
I've never had a problem flashing ftfs with UDB debugging off, just make sure you have all of the drivers installed and then select the ftf to flash in flashmode. Once it asks you to connect the phone you will have to take the battery out, put it back in and put the cover back on to connect the USB cable and the flashmode button. When it goes into flashmode the LED will go green and then go off, this is normal. Flashtool will then restore your device to stock.

gamer649 said:
I've never had a problem flashing ftfs with UDB debugging off, just make sure you have all of the drivers installed and then select the ftf to flash in flashmode. Once it asks you to connect the phone you will have to take the battery out, put it back in and put the cover back on to connect the USB cable and the flashmode button. When it goes into flashmode the LED will go green and then go off, this is normal. Flashtool will then restore your device to stock.
Click to expand...
Click to collapse
I get a line containing this:
ERROR - Processing of loader.sin finished with errors.

bananabee said:
I get a line containing this:
ERROR - Processing of loader.sin finished with errors.
Click to expand...
Click to collapse
1) Make a backup of the firmware you already have.
2) Open your original firmware file with WinRar or something like that.
3) Delete the loader.sin file out of the firmware.
4) Proceed to flash your firmware again, this time unticking the wipe cache and data boxes and excluding everything but the system.

Download latest backup from Bonoboo thread.. it has full root and CWM, just restore it via CWM

syedafzal.shah said:
Download latest backup from Bonoboo thread.. it has full root and CWM, just restore it via CWM
Click to expand...
Click to collapse
They can no longer access recovery mode, it says that in the OP. The only option is flashtool.
Sent from my C1905 using XDA Premium 4 mobile app

gamer649 said:
They can no longer access recovery mode, it says that in the OP. The only option is flashtool.
Sent from my C1905 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you can use fastboot drivers to flash CWM.. First download the backup and move it your SD card (use card reader) and insert it back in your phone .Download fastboot drivers and extract it on your computer.
)
Download CWM file and extract it. Now copy the .img file from the folder and copy to the fast boot folder.
Now switch off your phone and connect to the PC in fastboot mode. Press and hold volume up key and connect the phone in the USB cable. [Make sure that you have installed necessary drivers. Else it wont work. ]
open a command window there by holding shift key and right clicking on the white space in fastboot folder (replace boot_image_name.img with the name of .img file in the cwm folder)
Example:::"fastboot flash boot boot_image_name.img"
Wait till it finishes the shell. Done... Now power on your device and when LED turns **** click volume up and down few times, CWM will be opened then restore backup of bonoboo which you moved to your SD card

C:\Flashtool\Fastboot>Boot_image_name.img
'Boot_image_name.img' is not recognized as an internal or external command,
operable program or batch file.
it turn like this in the command window, could somebody help me.
i need the step in more detail how to flash the CMW.

you should type(after changing the directory to the one that has the recovery):
fastboot flash recovery recoveryname.img
Sometimes it doesnt work saying remote command not allowed or something like that, so dont hesitate to flash the boot partition instead because ultimately you are going to restore everything
if the former doesnt work then type:
fastboot flash boot recovery.img
Note:you will first have to change the directory to the one that contains the recovery ex, if i have the recovery file in c:\ then type:
cd C:\

help me guyz.. i have c1904 but its never bootup even if i flash the firmware . alwasys bootlop in xperia animation .. tried to install cwm then from their flash any rom but it never been started .. means its stuck in flashing for every.. please help me.. tried ressurection cm13 both same. unlock bootloader. any way to get in back. seems like its dead in eveyway.

[Q] cant flash kernel boot.img 4.4.4 c11 fxp 341

Hello,
im trying to flash my 4.3 baseband to 4.4.4 c11 FXP 341, bootloader unlocked, but after flash kernel boot.img it show me this two errors.
os: mac os, im using my xperia usb cable
INFO - ERROR: could not get pipe properties
INFO - FAILED (remote: Command not allowed)
after that i cant turn on my phone, after that i always flash ftf then i working but on 4.3
Thanks for help

Hello There!!
mirogo said:
Hello,
im trying to flash my 4.3 baseband to 4.4.4 c11 FXP 341, bootloader unlocked, but after flash kernel boot.img it show me this two errors.
os: mac os, im using my xperia usb cable
INFO - ERROR: could not get pipe properties
INFO - FAILED (remote: Command not allowed)
after that i cant turn on my phone, after that i always flash ftf then i working but on 4.3
Thanks for help
Click to expand...
Click to collapse
Hey there,
Looks like u r just a step away from CM11 and i think i can help u with that, just follow the steps:
Plz check again and again before attempting this, this will work for sure but still
Download Androxyde XPERIA Flashtool
Install the software , then go to C:\\flashtool\flashtool drivers and install drivers for your phone
make sure u install fastboot and flashmode drivers
then, connect ur phone in flashmode (holding volume down key) and wait for flashtool to detect ur device, later click on the icon which says "BLU". ur bootloader will unlock
then connect your phone in fastboot mode(holding volume down key)
Copy the CM11.zip and gapps.zip onto ur sdcard.
extract the boot.img from the CM11 zip file and click on the Flashing button and select fastboot mode and click on kernel to flash , then select boot.img
unplug ur phone, boot into recovery (holding volume up )
Wipe data/cache and dalvik cache
go to mounts, click format system
then go to install from sdcard and select Cm11.zip, later flash Gapps.zip
Reboot , enjoy
the Fastboot and Flashmode keys vary from device to device, i use Sony Xperia M Dual C2004 and the above mentioned keys were for that phone.
plz tell me if this helped or not:fingers-crossed::fingers-crossed::good::good:

hi,
i tried it but same problem, when i flash kernel boot.img from cm11.zip (now no more errors - maybe is it im trying at moment on win7 with new drivers), phone wont turn, led always light on orange. I worried that maybe is cuz of root, so i did ftf new 4.3. So i tried boot "http://forum.xda-developers.com/showthread.php?t=2696259" no problem i went for first time to recovery mode on my xperia m. SU showed in apps. bootloader unlocked, debugg on.
but i dont understand one thing when phone is ON i check drivers in flashtool, i see device and adb drivers in flashtool, but when phone is off it say no adb drivers and debugg off??? but flashing kernel for root worked fine
Thanks

when i try to flash cm11.zip from root kernel in recovery it says Aborted, so why boot kernel from root works and from cm11 no?