Related
SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.
Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!
So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.
I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance
not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?
usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:
almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.
Hi.
I just switched my D802 on yesterday morning and got the screen attached - reboot just show black and this screen again - it seems that the whole screen just went south.
Even though I will try to get a replacement (it is a testing devices) I want to backup my data. The phone and its software (cm11) still works, I just got an alarm this morning.
I could just erase everything with Android device manager, but I would like to save my messages, call logs etc.
Problem: I used a screen pattern to lock the device. I already managed to change it to a passphrase using android device manager,but I don't know any way to unlock without the display -
with this lock, adb access in unsuccessfull (device unauthorized). Is there any way to unlock the device?
Any help would be really appreciated - keep in mind - no access via touch is possible - see device picture.
adb:
Code:
C:\>adb devices
List of devices attached
019537e89498f242 unauthorized
C:\>adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
C:\>
you SHOULD be able to reboot to recovery using power/volume down combo
from there you SHOULD have adb access and can adb pull the /sdcard partition from the phone.
You're right - but it is very hard to press the buttons accordingly without any visual confirmation...
Finally I got it... it was quite a struggle, but I could pull all necessary data from the dead phone, thanks for the hint.
Gesendet von meinem Nexus 5 mit Tapatalk
Need help
webwude said:
Finally I got it... it was quite a struggle, but I could pull all necessary data from the dead phone, thanks for the hint.
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
I met same issue with my phone, could you please write details about implementing steps?
Thanks
Blackmeo said:
I met same issue with my phone, could you please write details about implementing steps?
Thanks
Click to expand...
Click to collapse
You could always use a USB otg cable and a keyboard and enter the password with the keyboard then if you had adb enable you now have access, if you don't you could enable it switching the cable with a slimport adapter to make your phone show up on a tv, see where everything is then unplug it plug baack in a mouse or keyboard and finish.
Hope I helped, I would cry if that happened to my g2
LG K20 Plus ADB "device unauthorized"
Greetings,
I unlocked my bootloader and installed TWRP but somehow my phone virtually explodes with error messages upon reboot. Can't install stock ROM and my recovery file is corrupt. After that, ADB recognized my device as simply, lv517 instead of lgmp260blahblahblah. I tried AGAIN to recover my OS and now ADB is showing lgmp260blahblahblah "UNAUTHORIZED"
Since I can't get past the "Welcome" screen in order to revoke USB Permissions, I am yet again, stuck. Is there a fix?
Thanks in advance for any help
This is a LG G2 thread, not K20 plus.
You are in the wrong forum, mate
Someone please create magisk module for this
Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site
Hi, I have a S4 i9505 with a problem, screen broken and no display at all + usb debugging is disabled.
Phone: Not rooted, original software, usb debugging disabled, no display at all
What I want to achieve: restore all my photos / videos on the phone memory, no sd card
What I have attempted:
installed ADB & fastboot based on instructions from http://forum.xda-developers.com/showthread.php?t=2786395
What I need help with:
- When i try to get into recovery mode, i wasn't sure if i am indeed in there since i can't see anything, but in total there's a vibration when i turn on the phone, and another vibration when i release the power up+power+home after pressing them down for about 5 seconds.
- When in command prompt I type adb devices and there was none, and when i type adb shell it says error: device not found
I have ensured all drivers for my phone are installed (even with PdaNetA4180 & UniversalAdbDriverSetup6 from cynanogen) but the error remains. refer to attached image.
I have done extensive search on the forum but still couldn't find any ways to get usb debugging enabled on my crippled phone.
Any step by step guide would really be helpful! Thanks
Ps. Main problem = device not found in adb , usb debugging disabled, screen no display/cracked
What do you want? To recover files? To my knowledge that is not possible.
You would first need to flash a custom recovery for adb to work in recovery.
Then you would need to allow the connection on your device (which you can't do).
Yes I need to recover photos only. Nothing else.
Please kindly guide the steps on how to flash a custom recovery (w/o control of the phone's display or touch)
Thanks.
Your device is shown connected in windows
Why not use the mtp protocol and copy whatever you want
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
If the photos are deleted by the factory reset then i am sorry to day but you cannot recover them even if you get the screen fixed
bomby481 said:
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
Click to expand...
Click to collapse
Your photos are gone and there is no way to get them back.
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
dalviking said:
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
Click to expand...
Click to collapse
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Extentho said:
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Click to expand...
Click to collapse
Thanks a lot Extentho for your feedback.
I've already tried your fair suggestion: unfortunately, I'm stuck at the end of sideloading the signed .zip.
In fact, I see on screen logs that it's applying the update "unconditionally" (that sounds good), but nevertheless, when finished it returns "xfer: 1.00x" on PC shell and in recovery menu, on device.
Now, either if I reboot or power down and boot it again, the result is the same: still bootloop-ing.
Of course, at any other attempts leveraging on administrative privilege, it says that "device is locked", including those done through the shell tool.
Some excerpts from my last launched commands:
c:\_APP\CM>adb devices
List of devices attached
51f8941d sideload
c:\_APP\CM>adb shell
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb root
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
51f8941d sideload
c:\_APP\CM>adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip
Total xfer: 1.00x
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
my zuk z1 stuck to bootloop,
and android debugging is disabled.
phone can not detecting in fastboot mode.
please help.
Extentho said:
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
Click to expand...
Click to collapse
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
dalviking said:
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
Click to expand...
Click to collapse
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Extentho said:
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Click to expand...
Click to collapse
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
dalviking said:
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
Click to expand...
Click to collapse
Try to post some pics about the troubles you encounter. If we receive a solution, this may be helpful for all of us in the future. Now, exactly, what can you acces on phone(recovery, fastboot, )?
Also, check varios threads from other phones with the same problems(one plus one, lg , htc) ,etc. Find a solved situation like yours, and we may adapt that solution to you
Hi guys,
Just to close this topic.
I was finally able to install the ZUI ROM through the QFIL program.
It's a little bit tricky, due to the fact that it is strongly suggested:
- to use a Windows 7 machine started without Signature Enforcement enabled;
- to start QFIL (admin mode) and be prepared with all needed files loaded in its GUI;
- to power off the phone, then, while pressing volume up button, inserting the USB cable, attached (better if) on a 2.0 port to PC;
- to be fast pressing "Download" button on QFIL program.
After that, I unlocked the bootloader and performed a lot of alternative recovery process.
So, I installed on the device:
- ZUI ROM
- Cyanogen OS convert from ZUI ROM
- Cyanogen OS last updated ROM
- CyanogenMod 12.1 last nightly ROM
- CyanogenMod 13.0 last nightly ROM
and the winner is...
...
...
...
... none of the above.
Each time the very same behaviour: bootloop. So, my last conclusion is: hardware failure (I guess wi-fi module).
I give up.
But for anyone searching a safe way to unlock a bootloader without accessing to developer options: the QFIL method works like a charm (once installed properly).
Thanks for support.
Messed my zuk z1
I tried to flash stock room in my zuk z1 , I downloaded Qualcomm file for the ROM and installed the required in my laptop,I wiped all data in my phone using TWRP .though my power button is not working I used tool kit to reboot my phone by connecting into fast boot mode,here comes the prob by mistake I entered the wrong command which locks my bootloader .I don't know what to do...help me.....