Database Info

Can't access bootloader menu

Howdy XDA, lurking for a few weeks now, first time posting.
I have a Vodafone Smart 2, which runs pretty much the same hardware as the Alcatel V860. I previously rooted it myself, removed crapware, blah blah. This worked fine until I updated the firmware through the Firmware Upgrade Manager, which restored all the crapware on my phone and somehow removed my root privileges.
Now, when I try to root using the same method I used to root the phone previously, I run into an error. Normally, I would root from a zip file on the SD card through the bootloader/recovery menu. Now, when I try to access this menu, I'm greeted with a message stating: 'All data will be lost, continue?' in various languages.
This obviously doesn't allow me to root my phone through the familiar method, which was, as far as I know, the only method to root this particular type of phone. I have tried using the sdk manager but this came up as a dead end.
I would be extremely grateful if anybody can give me any information or ideas as to how to root this phone again?
Cheers.

Maybe you're pressing the wrong buttons? I remember that if I pressed volume down + power button instead of volume up a different thing happened.

Scorpius666 said:
Maybe you're pressing the wrong buttons? I remember that if I pressed volume down + power button instead of volume up a different thing happened.
Click to expand...
Click to collapse
Hi there, thanks for replying.
Normally I would hold the power & the volume + buttons, which would bring me to the bootloader menu. Doing so now just brings up the 'All data will be lost, continue?' message.
Interestingly enough, holding the power & the volume - buttons causes the phone to freeze on the android startup logo, which leaves me with no other option than the pull the battery and try again.

Can't you use adb reboot recovery or sth like that?
Sent from my GT-I9100 running CM10

MemoryController said:
Can't you use adb reboot recovery or sth like that?
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Hi there, using the command 'adb reboot-recovery' simply refreshes the list that first comes up when you execute adb.exe within Command Prompt.
I am able to reboot using the 'adb reboot' command though, so the drivers must be in working order.

seanmaxwell99 said:
Hi there, using the command 'adb reboot-recovery' simply refreshes the list that first comes up when you execute adb.exe within Command Prompt.
I am able to reboot using the 'adb reboot' command though, so the drivers must be in working order.
Click to expand...
Click to collapse
Hi there
do what you did using "adb reboot" dos command, but type in " adb reboot recovery " instead while the phone is on, phone goes off and on into boot menu , where you can do your rooting(update.zip) from sdcard.
hope that helps you,

[Guide]How to Fix BSOD/No Bootloader

THIS GUIDE WAS MADE WITH CWM Installed.
This post is to try and combine all the resources i used and found in one simple guide. I really hope this can get sticked so it doesnt get lost.
So after i flashed Hells-Core kernel for the N4 on My N5 i sorta screwed up my Nexus to the point that it wouldnt boot. Not even into bootloader. So unable to find anything on google i came to XDA for help. Well while waiting for a response on here my GF (who has No android knowledge about an average user.) took to google and found what i was looking for without even really Trying. The nexus 5 has a SECOND bootloader option that Alot of users dont know about. To access that second bootloader and fix the BSOD here are the steps you follow.
I AM NOT HELD RESPONSIBLE SHOULD YOU FULLY BRICK YOUR DEVICE BY DOING THESE STEPS!
1.) Plug your device into your PC or laptop (NOT required BUT it does make it easier to do the steps.)
2.) If your device is powered on but again you cant see anything hold Down+power till you hear your device eject from your Computer.
3.) As soon as you hear it eject press and hold Down+up+power. You are now in the secondary bootloader
Now for the Fun and Dangerous stuff.
1.) Open CMD prompt and direct yourself to your ADB location
2.) Type adb devices. If your device shows up here skip the next step.
2a.) If your device DOESNT show up navigate to the recovery option and load recovery. Once your in recovery proceed to the next step.
3.) in CMD prompt type adb shell. if you see # your good. if not type SU
4.) once you have root access in adb shell enter the following command: dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6" and hit enter you should see something like this
dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6"
1024+0 records in
1024+0 records out
524288 bytes (512.0KB) copied, 0.136945 seconds, 3.7MB/s
Click to expand...
Click to collapse
5.) after all that is done you are good to go. Reboot your device and pat yourself on the back seeing as your Soft-Bricked device and bootloader is now fixed and in working order again.
Again We at WolfRoms© are Not responsible for ANY damage that results from these steps.
Thanks*
Andriy2 and his post with the partition command:
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
cargobr151 for the partition list:
http://forum.xda-developers.com/google-nexus-5/general/info-partition-list-nexus-5-t2517503
And lastly grim489 for helping me out on another post i had.
Guide written by Wolf
Founder and one man dev team of WolfRoms©

Thanks for the guide. You are the second guy who saved his phone thanks to the secondary bl.
Tapatalk-kal küldve az én Nexus 5-el

Yeah, you're the 2nd person I've seen fixing his bootloader. Kudos man!
Even I think that this guide should be in the stickies

Thanks everyone. We shall see if it becomes a sticky. But hey if you could just hit the Thanks button id appreciate it

Shameless bump. Trying to get this as a sticky

wolfirotisha said:
Shameless bump. Trying to get this as a sticky
Click to expand...
Click to collapse
Have you reported it that to mods?
Tapatalk-kal küldve az én Nexus 5-el

This reminds me about SuperCID11111111 on HTC phones.
an extra warning. Do not edit mmcblk..... files by any means or will have a totally murdered phone.

I have one question.
3.) As soon as you hear it eject press and hold Down+up+power. You are now in the secondary bootloader
Click to expand...
Click to collapse
At this phone your screen is on? What do you see? Or the phone's screen remains black during the process?

bitdomo said:
I have one question.
At this phone your screen is on? What do you see? Or the phone's screen remains black during the process?
Click to expand...
Click to collapse
During that step, your phone is still bricked and screen should be off. (if the screen is on, then this guide might not be needed for your device)
It should light up after "Now for the Fun and Dangerous stuff" step ( 4&5 )

GUGUITOMTG4 said:
During that step, your phone is still bricked and screen should be off. (if the screen is on, then this guide might not be needed for your device)
It should light up after "Now for the Fun and Dangerous stuff" step ( 4&5 )
Click to expand...
Click to collapse
I found out the screen turn ons
2.) If your device is powered on but again you cant see anything hold Down+power till you hear your device eject from your Computer.
3.) As soon as you hear it eject press and hold Down+up+power. You are now in the secondary bootloader
Click to expand...
Click to collapse
Otherwise how we could navigate to the recovery?
2a.) If your device DOESNT show up navigate to the recovery option and load recovery. Once your in recovery proceed to the next step
Click to expand...
Click to collapse
So we see the normal fastboot screen right?

bitdomo said:
I found out the screen turn ons
Otherwise how we could navigate to the recovery?
So we see the normal fastboot screen right?
Click to expand...
Click to collapse
If you screen turns on, you could solve your issue in another manner. what happened to your phone that brought you here?
To navigate to recovery, given that the phone is on the alternate bootloader, just would need to press 2 times either vol- or vol+ and press power.
like we do normally.

GUGUITOMTG4 said:
If you screen turns on, you could solve your issue in another manner. what happened to your phone that brought you here?
To navigate to recovery, given that the phone is on the alternate bootloader, just would need to press 2 times either vol- or vol+ and press power.
like we do normally.
Click to expand...
Click to collapse
My phone is fine. I am just curious.
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
I found out the screen turn ons
Otherwise how we could navigate to the recovery?
So we see the normal fastboot screen right?
Click to expand...
Click to collapse
i can get into recovery but i have no zip on interal so im stuck. pc wont see device so i can transfer a rom over to the phone

I flashed trinity kernel for the n4 onto my n5, 3 times in a row accidentally! after it not booting 3 times, I realized my mistake. I went ahead and flashed the n5 trinity kernel after, and to my surprise it booted, with everything normal. no issues after. I assumed it would've changed my partitions, but it did not.

Georgiazen said:
i can get into recovery but i have no zip on interal so im stuck. pc wont see device so i can transfer a rom over to the phone
Click to expand...
Click to collapse
Reboot to recovery.
Connect your phone to the PC
Download usb drivers http://forum.xda-developers.com/showthread.php?t=2386956
Open device manager and update the driver for AOSP on Hammerhead device.
If you are running windows 8 or 8.1 then you have turn off the driver signature enforcement to install the driver.
Install this http://forum.xda-developers.com/showthread.php?t=2588979 skip the driver installation.
Create a new folder on the root of your C drive and name it to flash
Download a rom zip.
Rename the zip to flash.zip make sure you will not rename it to flash.zip.zip then copy it to the C:\flash folder
In recovery enable adb sideload. If you are using TWRP then it is in the ADVANCED menu.
Open CMD window and type these commands:
cd C:\flash
adb sideload flash.zip

Georgiazen said:
i can get into recovery but i have no zip on interal so im stuck. pc wont see device so i can transfer a rom over to the phone
Click to expand...
Click to collapse
well, you'll need to find and install a working driver for your pc, so adb can see your device(while in recovery). after that, it'll take 2 minutes to adb push to your device and flash.

bitdomo said:
Reboot to recovery.
Connect your phone to the PC
Download usb drivers http://forum.xda-developers.com/showthread.php?t=2386956
Open device manager and update the driver for AOSP on Hammerhead device.
If you are running windows 8 or 8.1 then you have turn off the driver signature enforcement to install the driver.
Install this http://forum.xda-developers.com/showthread.php?t=2588979 skip the driver installation.
Create a new folder on the root of your C drive and name it to flash
Download a rom zip.
Rename the zip to flash.zip make sure you will not rename it to flash.zip.zip then copy it to the C:\flash folder
In recovery enable adb sideload. If you are using TWRP then it is in the ADVANCED menu.
Open CMD window and type these commands:
cd C:\flash
adb sideload flash.zip
Click to expand...
Click to collapse
ok but it doesnt say asop it says android device and mtp

Georgiazen said:
ok but it doesnt say asop it says android device and mtp
Click to expand...
Click to collapse
Then update that, maybe the name depends on the version of windows you are using and thr version of the recovery.

this what i see 1. android phone - composite adb devive
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
now it says google nexus adb interface

Georgiazen said:
this what i see 1. android phone - composite adb devive
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
now it says google nexus adb interface
Click to expand...
Click to collapse
:good:

HELP! Can't get fastboot to recognize device and can't get into bootloader / recovery

ok so:
i was trying out the new PAC build today, and i went into philz to wipe, and wiped the old OS and data. i accidentally hit reboot system, instead of installing a new os and then getting into it.
"no big deal" i thought. figuring i'd just boot into bootloader and get into recovery and then flash away
i seem to be stuck at the nvidia screen and cant get past that.
when i hold vol down and power, it just brings me to the nvidia screen with nothing to do there. using cmd i can:
adb devices: shows my serial and offline, makes sense
fastboot devices: does nothing and goes back to the command prompt
fastboot any command brings me to <waiting for devices>
my device manager shows "portable devices: shield tablet" and "android device: android composite adb interface"
anyone have any clue what i may have done....or what i can do? i am freaking out a little over here, thinking i may have bricked this thing

Hold Volume down pressed, but release Power immediately after pressing it and you will enter the bootloader. When this succeeds you should never see the nvidia screen.

Gnurou said:
Hold Volume down pressed, but release Power immediately after pressing it and you will enter the bootloader. When this succeeds you should never see the nvidia screen.
Click to expand...
Click to collapse
if i could kiss you. i would
thank you so much... STUPID NVIDIA!

That's how it is explained in the recovery flashing instructions, although I agree this is somehow confusing.

Gnurou said:
Hold Volume down pressed, but release Power immediately after pressing it and you will enter the bootloader. When this succeeds you should never see the nvidia screen.
Click to expand...
Click to collapse
I could kiss you too...I did almost the same thing. You are my favorite person on the planet atm.
Sent from my xt926

Unlocking bootloader on shield
minieod said:
if i could kiss you. i would
thank you so much... STUPID NVIDIA!
Click to expand...
Click to collapse
How did you managed to succeed with this minieod ?
I get the message <waiting for device> as you... Please help.
---------- Post added at 10:51 PM ---------- Previous post was at 10:22 PM ----------
Wulfpk said:
I could kiss you too...I did almost the same thing. You are my favorite person on the planet atm.
Sent from my xt926
Click to expand...
Click to collapse
How did you managed to succeed with this Wulfpk?
I get the message <waiting for device> as you... Please help.

djebm2 said:
I get the message <waiting for device> as you... Please help.
Click to expand...
Click to collapse
Just to confirm, you are using fastboot for bootloader and not adb right?

Unlocking bootloader on shield
amartolos said:
Just to confirm, you are using fastboot for bootloader and not adb right?
Click to expand...
Click to collapse
Yes amartolos. adb is able to print my shield talbet serial number, but not fastboot...

You need administrative privileges for fastboot command but not for adb. If you're using linux, make sure to do sudo fastboot; if you're in Windows, make sure you started command prompt with Administrative privileges. Hope that helps =)

Unlocking bootloader on shield
amartolos said:
You need administrative privileges for fastboot command but not for adb. If you're using linux, make sure to do sudo fastboot; if you're in Windows, make sure you started command prompt with Administrative privileges. Hope that helps =)
Click to expand...
Click to collapse
Admin privileges does not solve the problem.

[Q] Bootloop - how to recover file?

Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander

Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?

alexs77 said:
Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander
Click to expand...
Click to collapse
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :

el_daYa said:
Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?
Click to expand...
Click to collapse
Yes, I do have a custom recovery setup. Yes, I do have adb and fastboot setup on my computer.
No, I don't get into fastboot or the custom recovery. If I try to, it will reboot right away, as shown on the video. [emoji30]

bitdomo said:
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :
Click to expand...
Click to collapse
Uhm, well, losing my warranty is of course also something, I would not want [emoji26]

Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.

el_daYa said:
Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.
Click to expand...
Click to collapse
I do know my way around adb
adb devices will only show the device , if it is booted. It does not boot - what happens, is visible in the Google+ post, which contains a video.
I tried plugging it in and it is not shown. Also not with the fastboot command (ie. "sudo fastboot devices" shows nothing. Adb also does not find the device). That is, what I meant with "I cannot adb to the device".

Then I am afraid you'll need assistance from a higher level my friend, sorry I wasn't much help.

Help unlocking/rooting Lenovo Vibe C2 K10a40

So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!

Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk

still waiting for rooting app, too...

Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?

Kirzoczek said:
Why Godzin why??!! Why Google d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Well i'm pissed of. Lenovo just turn off vol up button. U just can't press it in fastboot mode to unlock bootloader. F...... ?

Kirzoczek said:
Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Google isn't the the one that has control of that, that's controlled by the device manufacturers and/or each mobile carrier. In this case, it's controlled by Lenovo
The only devices that Google has control over whether they're rootable or not is only the Nexus and Pixel devices, not any of the others.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
---------- Post added at 04:01 PM ---------- Previous post was at 03:47 PM ----------
Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
The command is supposed to be
fastboot OEM unlock
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Yes, you have right. But what with this vol+ button?

Volume+ button is not working on Lenovo C2 ?

GPSSlovakia said:
Volume+ button is not working on Lenovo C2 ?
Click to expand...
Click to collapse
I mean that vol up did' t work in fastboot mode. When u try to unblock bootloader u have two options. U may choose yes or no. Offously vol up is for "yes" answer. And whoop!!! It don't work

How to restore the imei number of this phone ..i tried several methods to restore..pls help me

rijukrishnan said:
How to restore the imei number of this phone ..i tried several methods to restore..pls help me
Click to expand...
Click to collapse
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Sent from my SM-S903VL using Tapatalk

then what can i do next to make it in stock condetion

What is this message means

rijukrishnan said:
What is this message means
Click to expand...
Click to collapse
I think it is saying that the connection between PC and your device was interrupted for some reason. I was probably a problem with your cable being loose and losing connection where it plugs into your device.
It is not very likely but it could also be an unstable electrical supply grid in your area, the power in the building where you are could have dropped momentarily, I doubt this was the cause though, but it is one possibility.
Use a different cable or find a way to make sure it connects and stays connected, then try flashing again.
The error you have is described in the attachment below, it explains how to solve.
For future reference, the link below has a list of all flash tool errors and how to solve them.
https://forum.hovatek.com/thread-439.html
Sent from my SM-S903VL using Tapatalk

Droidriven said:
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Click to expand...
Click to collapse
i have a bckup of imei number

Eh..,,.... no unlock oem ... no root , bad phone

Droidriven said:
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us

medzbody said:
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us
Click to expand...
Click to collapse
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I do not know how to build twrp for my device you can help me

What about making a TWRP and then flashing it thru modified scatter file in flash tool