Hi everyone,
So after deciding whether to do it or not, i finally unlocked my BL yesterday. At least when i dial the secret number and look at BL info, it says "UNLOCK".
But I've been trying to flash cwm and rooting but it seems my device is not being recognised in cmd.
And i am having difficulties to install fastboot drivers again because my device is not showing up at all in device manager.
If you could kindly list some simple instructions on how to flash cwm and rooting on unlocked BL (Before you ask, yes i went through all the guides with no avail) or help me to install flashboot drivers properly, it would be appreciated.
Thank you and good day.
EDIT 1: I can boot in fastboot mode, But when i do adb devices, driver installation fails and thus the command for flashing cwm says "waiting for device" and never flashes.
EDIT 2: From what i have searched from previous posts , i need to wait 30mins, I will do that and report.... Hopefully it will work
If you can boot into fastboot then do fastboot devices, adb devices are commands in adb mode, not fastboot mode, instead of flashing through adb use fastboot flash , hope I help!
Sent from my LG-P769 using xda app-developers app
EpicLordPhone said:
If you can boot into fastboot then do fastboot devices, adb devices are commands in adb mode, not fastboot mode, instead of flashing through adb use fastboot flash , hope I help!
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Sorry,
I actually did what u said.
But when i type the command (in cmd) : C:\Android>fastboot devices ---> The command is accepted and there is a driver installation which fails.
Even then i continued and typed : C:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.3.1-p760.img
But with the second command, it simply says "waiting for device" in the command window, but nothing happens.
kirakun said:
But with the second command, it simply says "waiting for device" in the command window, but nothing happens.
Click to expand...
Click to collapse
Put recovery.img on sdcard
Using Android Terminal Emulator:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
P.S Sorry my ENG
Lgeob said:
Put recovery.img on sdcard
Using Android Terminal Emulator:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
P.S Sorry my ENG
Click to expand...
Click to collapse
But I only have an unlocked BL and I do NOT have root either :/
kirakun said:
But I only have an unlocked BL and I do NOT have root either :/
Click to expand...
Click to collapse
What prevents get root?
Lgeob said:
What prevents get root?
Click to expand...
Click to collapse
When i enter fastboot mode, pc installs drivers but driver installation fails. Cannot use fastboot commands. I try to re-install fastboot drivers (omap4boot drivers) but i cannot find device in device manager
kirakun said:
When i enter fastboot mode, pc installs drivers but driver installation fails. Cannot use fastboot commands. I try to re-install fastboot drivers (omap4boot drivers) but i cannot find device in device manager
Click to expand...
Click to collapse
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Lgeob said:
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Click to expand...
Click to collapse
okay ill try this
Lgeob said:
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Click to expand...
Click to collapse
I don't have spritebud, so LGPwn.apk does not work
kirakun said:
I don't have spritebud, so LGPwn.apk does not work
Click to expand...
Click to collapse
Try this method.
Casserole said:
Try this method.
Click to expand...
Click to collapse
Thanks for the reply ^^ I was planning to use this as last resort XD Do u think its reliable o-o?
And also after installing this i can flash cwm ?
kirakun said:
And also after installing this i can flash cwm ?
Click to expand...
Click to collapse
Do it.Не ссы :good:
Related
I tried to upgrade my recovery image to RA-hero-v1.6.2.
However I got a problem
I use adb shell method to flash the new recovery image.
when I type mount -a it show four lines of fails. and then I type flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img. After that I press reboot. My phone is now keep stay in HERO BOOT SCREEN. nothing happen. please help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
For adb + fastboot method
I type adb shell reboot bootloader, it success.
but when I type fastboot boot recovery-RA-hero-v1.6.2.img it said recovery-RA-hero-v1.6.2.img cannot be load. Please help.
Can you boot your phone normal now at all or not?
If you can, use BTDAG's guide in my signature and install the custom recovery using the flashrec method.
I cannot it stuck at the "HERO" boot screen :'(
what I can do is that I can use the adb shell the browser the files inside the phone.
try flashing it via android commander mate i had that problem my self once and that fixed it
skedone said:
try flashing it via android commander mate i had that problem my self once and that fixed it
Click to expand...
Click to collapse
He can flash the recovery through Android Commander? .... Interesting.
skedone said:
try flashing it via android commander mate i had that problem my self once and that fixed it
Click to expand...
Click to collapse
Can you provide me steps?
animation said:
Can you provide me steps?
Click to expand...
Click to collapse
http://tinyurl.com/232pnzr
Have a go,.... then report back.
ddotpatel said:
http://tinyurl.com/232pnzr
Have a go,.... then report back.
Click to expand...
Click to collapse
the link is just link to google?
Its for Android Commander. Either try that,... Or see if you can get into the recovery you currently have,.... wipe what you can, then flash another rom.
ddotpatel said:
Its for Android Commander. Either try that,... Or see if you can get into the recovery you currently have,.... wipe what you can, then flash another rom.
Click to expand...
Click to collapse
I can't go into the recovery mode.
I can only go into the fastboot mode.
Try this,... Go into fastboot.
Hit BACK to enter the fastboot bit.
I should now say FASTBOOT USB or something similar.
Then you need to cd into the right directory using CMD.
example,... I have to type...
cd c:\sdk\tools ................But it might be different on yours.
then type
fastboot devices
It should bring up your device serial number.
Then type
fastboot oem rebootRUU
fastboot erase cache
Then reboot.
ddotpatel said:
Try this,... Go into fastboot.
Hit BACK to enter the fastboot bit.
I should now say FASTBOOT USB or something similar.
Then you need to cd into the right directory using CMD.
example,... I have to type...
cd c:\sdk\tools ................But it might be different on yours.
then type
fastboot devices
It should bring up your device serial number.
Then type
fastboot oem rebootRUU
fastboot erase cache
Then reboot.
Click to expand...
Click to collapse
What are these two lines did? fastboot oem rebootRUU
fastboot erase cache
I think it erases old data?
animation said:
ddotpatel said:
animation said:
After reboot? what should I do?
when I type fastboot boot recovery-RA-hero-v1.6.2.img it always said
downloading 'boot.img' ... FAILED <remote: not allow>
Click to expand...
Click to collapse
I didn't say that?.... Try what I said to erase cache,... then see if it boots.
Click to expand...
Click to collapse
I tried, but it also stuck at the boot screen.
Click to expand...
Click to collapse
The only other thing I can suggest is go into fastboot,...
then run,...
fastboot oem rebootRUU
fastboot erase cache
Keep it plugged in, then run an RUU .exe.
,... Then start from scratch again,...
sorry its droid explorer and here is link to info about program and its pritty easy to use
http://de.codeplex.com/wikipage?title=Features&referringTitle=Home
try the HEROIMG.zip method
Hello,
just another idea:
- download an original RUU.exe (preferably of an older version, rootable) and extract rom.zip (a lot of guides in the forums)
- rename to HEROIMG.ZIP and put in sdcard root
- restart hero with volume down pressed
- normally it should find the heroimg.zip and flash it and you are back to normal
Hi, I just successfully installed ViperX+ 1.08 in my phone and I have have TWRP 2.4.4.0 in my HOX+ International phone and would like to update it to version 2.5.0.0. Is there a guide on how to update it properly? Thanks
rokidzgm said:
Hi, I just successfully installed ViperX+ 1.08 in my phone and I have have TWRP 2.4.4.0 in my HOX+ International phone and would like to update it to version 2.5.0.0. Is there a guide on how to update it properly? Thanks
Click to expand...
Click to collapse
Simply flash the image using hasoon's toolkit, that is the easiest way.
Else you can use ADB tool...
rokidzgm said:
Hi, I just successfully installed ViperX+ 1.08 in my phone and I have have TWRP 2.4.4.0 in my HOX+ International phone and would like to update it to version 2.5.0.0. Is there a guide on how to update it properly? Thanks
Click to expand...
Click to collapse
Like mentioned by the guy above, use the toolkit or use the command fasboot flash recovery (recovery name).img
e.g.
In command prompt (CMD) type
fastboot flash recovery recovery.img
That should do the trick. Since its a recovery flashing, hardly anything goes wrong. HOWEVER, DO CHECK THAT YOUR PHONE IS CONNECTED. I cannot emphasize the importance of this. It caused me a massive problem so i'm warning you before hand. Type into command prompt, adb devices and check that your device/s is attached. That's it! :laugh:
Addicted2xda said:
Simply flash the image using hasoon's toolkit, that is the easiest way.
Else you can use ADB tool...
Click to expand...
Click to collapse
ace_viknesh said:
Like mentioned by the guy above, use the toolkit or use the command fasboot flash recovery (recovery name).img
e.g.
In command prompt (CMD) type
fastboot flash recovery recovery.img
That should do the trick. Since its a recovery flashing, hardly anything goes wrong. HOWEVER, DO CHECK THAT YOUR PHONE IS CONNECTED. I cannot emphasize the importance of this. It caused me a massive problem so i'm warning you before hand. Type into command prompt, adb devices and check that your device/s is attached. That's it! :laugh:
Click to expand...
Click to collapse
Thank you guys. You mean I don't have to remove the existing TWRP version and just use hasoon's tool to update the old TWRP to 2.5.0.0?
rokidzgm said:
Thank you guys. You mean I don't have to remove the existing TWRP version and just use hasoon's tool to update the old TWRP to 2.5.0.0?
Click to expand...
Click to collapse
No, it will erase the older version....
Addicted2xda said:
No, it will erase the older version....
Click to expand...
Click to collapse
Did use hasoon's tool and it was updated. thanks again
Earlier i have my root for the mobile usuing towel root .. Trying to flash kernels now and recovery .. But i cant .. I followed the steps .. Wrote " fastboot flash boot boot.img " and everything .. But it keeps writing waiting for device .. Is there a solution for that ?
Sent from my D5503 using XDA Free mobile app
Chelshady said:
Earlier i have my root for the mobile usuing towel root .. Trying to flash kernels now and recovery .. But i cant .. I followed the steps .. Wrote " fastboot flash boot boot.img " and everything .. But it keeps writing waiting for device .. Is there a solution for that ?
Sent from my D5503 using XDA Free mobile app
Click to expand...
Click to collapse
in cmd try "fastboot devices" you should see your device, if not ,install drivers and try again it should work
Thats what happens when i type fastboot devices
Sent from my D5503 using XDA Free mobile app
Typical causes of that:
Not having the fastboot.exe in the folder you are working in on the PC.
or
Not in bootloader mode on the phone.
es0tericcha0s said:
Typical causes of that:
Not having the fastboot.exe in the folder you are working in on the PC.
or
Not in bootloader mode on the phone.
Click to expand...
Click to collapse
fastboot.exe is in the folder i`m sure .. but i run the phone in fastboot mode .. what is bootloader mode ?
Ohhh...is this on the D5503? Sony Xperia Z Compact? You sure you're in fastboot and not flashmode? What color is the LED? If you go into your device manager, does it show your device with or without an exclamation mark? Might have some helpful info here:
http://techglen.com/2014/03/26/inst...-14-3-a-0-681-4-4-2-kitkat-official-firmware/
I think you might have to unlock the bootloader before regular fastboot commands work.
es0tericcha0s said:
Typical causes of that:
Not having the fastboot.exe in the folder you are working in on the PC.
or
Not in bootloader mode on the phone.
Click to expand...
Click to collapse
es0tericcha0s said:
Ohhh...is this on the D5503? Sony Xperia Z Compact? You sure you're in fastboot and not flashmode? What color is the LED? If you go into your device manager, does it show your device with or without an exclamation mark? Might have some helpful info here:
http://techglen.com/2014/03/26/inst...-14-3-a-0-681-4-4-2-kitkat-official-firmware/
I think you might have to unlock the bootloader before regular fastboot commands work.
Click to expand...
Click to collapse
The LED color is blue
es0tericcha0s said:
Ohhh...is this on the D5503? Sony Xperia Z Compact? You sure you're in fastboot and not flashmode? What color is the LED? If you go into your device manager, does it show your device with or without an exclamation mark? Might have some helpful info here:
http://techglen.com/2014/03/26/inst...-14-3-a-0-681-4-4-2-kitkat-official-firmware/
I think you might have to unlock the bootloader before regular fastboot commands work.
Click to expand...
Click to collapse
this is the device manager
Ok, so what are you trying to do in fastboot?
Also, try this command to see if it works:
fastboot.exe -i 0x0fce getvar version
es0tericcha0s said:
Ok, so what are you trying to do in fastboot?
Also, try this command to see if it works:
fastboot.exe -i 0x0fce getvar version
Click to expand...
Click to collapse
Tried before and it worked.
es0tericcha0s said:
Ok, so what are you trying to do in fastboot?
Also, try this command to see if it works:
fastboot.exe -i 0x0fce getvar version
Click to expand...
Click to collapse
trying to flash a kernel
It seems like the bootloader is not unlocked then. You won't be able to install a kernel without doing that first.
Sent from my One using XDA Premium 4 mobile app
es0tericcha0s said:
It seems like the bootloader is not unlocked then. You won't be able to install a kernel without doing that first.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
NNow dial *#*#7378423#*#* and navigate to Service info > Configuration > Rooting Status
Now look for Bootloader Unlock Allowed
If Bootloader Unlock Allowed: Yes, then you may proceed
i tried that and it said yes :\
Ok, good deal. That means you can go through the steps to unlock the bootloader, not that it is already unlocked. Refer to the guide I posted and it has what other steps you need to do to proceed.
es0tericcha0s said:
Ok, good deal. That means you can go through the steps to unlock the bootloader, not that it is already unlocked. Refer to the guide I posted and it has what other steps you need to do to proceed.
Click to expand...
Click to collapse
everything is great until i have to type " fastboot devices " happens like what i told you before
You got the key from Sony and it went through and wiped your phone and all that and still no fastboot connection?
es0tericcha0s said:
You got the key from Sony and it went through and wiped your phone and all that and still no fastboot connection?
Click to expand...
Click to collapse
yes it reboots showing blue LED when i hold volume up while i connect the usb .. still the same problem :\
Try replacing the normal fastboot command with this:
fastboot.exe -i 0x0fce
Just to clarify - You signed up @ Sony's dev site and they emailed you the key to input in the commands to unlock the bootloader?
es0tericcha0s said:
Try replacing the normal fastboot command with this:
fastboot.exe -i 0x0fce
Just to clarify - You signed up @ Sony's dev site and they emailed you the key to input in the commands to unlock the bootloader?
Click to expand...
Click to collapse
you mean that ?
Chelshady said:
you mean that ?
Click to expand...
Click to collapse
Yes, and the key worked, wiped your phone and all that? If it still isn't working, then just use the flash tool to install the kernel.
http://www.androidizer.com/how-to-flash-custom-kernel-using-flashtool/
Error : can not open recovery.img. pls help me guys.... When i try to install TWRP recovery error msg came it saying can not open recovery.img
pgpselva said:
Error : can not open recovery.img. pls help me guys.... When i try to install TWRP recovery error msg came it saying can not open recovery.img
Click to expand...
Click to collapse
I think you are not booted in boot loader, give following command
adb reboot-bootloader
then after few seconds check whether you booted in bootloader or not.
fastboot devices
It will show your device.
fastboot flash recovery recovery.img
It will flash recovery.
no.... I'm in bootloader
First i enable usb debuging ->vonnect my mobile to pc ->in cmd gave adb devices-> adb reboot bootloader->fastboot flash recovery recovery.img
pgpselva said:
First i enable usb debuging ->vonnect my mobile to pc ->in cmd gave adb devices-> adb reboot bootloader->fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Have you unlocked bootloader?
yes bro i unlocked my bootloader
Error can not open.
........ In mobile max download size
make sure your recovery.img is not corrupt
No
pgpselva said:
No
Click to expand...
Click to collapse
before flash "fastboot devices"
hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!