Hello, i have a ZTE - Blade white - Orange UK, and it has too many pattern lock attempts, & my friend has forgotten the token googlemail account she set up with her phone....
so i figured i can just reflash it. but to my reading dismay, it seems i need to identify whether the handset is gen 1 or 2....
is there anyway to tell using the phone serial number?
is there any way i haven't found to hard reset the handset?
is my phone most likely a gen 1, and should i proceed?
You could flash a rom like GSF that is compatible with Gen 1 and 2. That way it doesn't matter which it actually is. You can check after you've flashed the rom then decide what you want to do after that. GSF thread is here.
thanks, nexrt problem....
Ok i downloaded the clockworkmod recovery, i figure i can use that the restore to factory settings.... i already have adb installed.
i grabbed the ZTE usb drivers & installed them. i connect the phone, ran the new hardware wizard successfully.
however in ADB it lists the device as offline? on the off chance it recognises the usb device at all...
If it's still on the Orange UK stock rom (android 2.1), then it is definitely a gen1 phone.
For adb: Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging). However, if you can't get past the pattern lock, you might not be able to do it.
If you're wanting to wipe it & flash another rom, then a TPT would be the easiest way. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=1258855 You'll need a microsd card reader to copy the files (poundland sell them)
well i couldnt get to the status bar to enable usb debugging but the TPT worked a treat.
Related
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
I have a Galaxy Note 4 (SM-N910G) and don’t normally muck around with the system. I have limited experience with Android.
My phone is locked (with important data stored in it)– a couple of days ago (presumably after a system upgrade) it suddenly would not recognise my fingerprint nor backup password.
I tried unlocking the phone using Android Device Manager but although I could get my phone to ring or display text, I could not change the password after locking the phone.
I called Google who said that Android Device Manager only works on earlier Android Versions - ?4 and below and most likely my phone would be running Marshmellow.
I called Samsung who said my only option is to restore to factory settings.
I wanted to use ADB and downloaded it and tried to use it from the c:\ prompt but I don’t have USB debugging enabled. No device was recognised when running ADB.
I had not registered for a Samsung account so I could not use Find My Mobile.
I tried to apply an update via external storage in recovery mode (I downloaded files such as Lockscreen_Security_bypassV1.1.zip or Pattern-Password-disable.zip) but unfortunately when I tried to apply them, it came up with E:footer is wrong, E: signature verification is required.
(I also tried “Android Multi Tools”).
I do not have CMN recovery loaded nor Aroma+File+Manager, but have downloaded zip files for them.
My question is: should I try and use Odin (have downloaded odin3_v3.11.2.zip) and TWRP to try and enable USB debugging or try to disable footer/signature verification??
Any other suggestions to try and unlock my phone???
At the minimum this has been an education!
Thank you for your help!
Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.
hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
bro do u find solutions for this
I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!
jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.
Hi all,
:crying: - Looking for a way to get my Mi Note 2 back to life!
This device has never been unlocked or ROMed before (although it has been re-flashed successfully via Xiaomi's own pushed updates).
It is running MIUI 10.0.something (cannot access menus to verify exact).
The problem
----------------
I did a standard factory reset on the phone.
Once restarted, it takes you through the normal setup screens such as 'language', 'region', 'wifi network' after which I am given the option to select "copy your data from an old phone" or "set up as new", no matter which I select, my phone goes to the next screen which shows "Checking for updates". Here it stays - endlessly...
What have I tried?
----------------------
I have tried a different wifi network but it does the same.
I have also tried selecting "copy your data" instead of "set up as new" but it does the same.
Thoughts
------------
I thought I would try to install a new stock ROM to see if that would fix the issue. However, in order to unlock with the Mi bootloader unlock tool (and then use their flashing tool), apparently to do this, I need to enable something under developer options - clearly impossible when I cannot get to any android menus.
The phone *can* be re-started into the fastboot screen but does this help me at all?
On the MIUI website I noticed the following in the tips and tutorials forum: How to install a MIUI update without unlocking the bootloader: https://en.miui.com/thread-3852597-1-1.html
The above got me slightly excited before I realised that I have no way to place a ROM into the ‘downloaded_rom’ folder in the internal storage of my device (as the article instructs). Note that the reason for this (on my phone at least) is that although a Windows explorer window does open when I connect the phone to my laptop, it is empty (i.e. you cannot see any files/folders in it). BTW - I know what causes that specific issue as that bug was present in the device ages ago - basically, the phone seems to default to be in USB charge mode and in order to see the folders in Windows Explorer, you have to go into developer options and manually change the USB mode and then change it back to MTP mode. Once that is done, you can see the files/folder structures. However, I cannot get to any developer options as I cannot get to Settings at all.
What can I do?
------------------
So my burning question is this: How can I re-ROM this theoretically 'working' device, given the above constraints?
Is there any way to do anything while the phone is in the fastboot mode perhaps?
Is there some method maybe used to recover a bricked device that I could employ here?
Thank you for any help offered!
Cheers!
So my nephew brings me his galaxy s6 t-mobile phone... He forgot his lock pin so he factory reset it. Now he can no longer get into the phone because he doesnt know the correct email or password. I did some digging through the net watched a few videos... and found none of the methods they used to bypass the lock would work on his phone. Then I read about the Combination Rom (Factory Binary)... At this time I do not have any windows pc's and my VM will not read the usbs of the phone... (im not that experienced with vm to set this up) So i grabbed JOdin for linux and proceeded to try to flash the binary. However, JOdin did not work for me. So i found Heimdall and installed to learn that i had to find some weird way to run it as SU for it to work... Tho Heimdall worked like a charm.... With Heimdall I had to take the rom and completely extract it to a folder and find all the img files in it to install on heimdal like sboot, boot, cm, system, and quite a few others as well.I used the "PIT" file from the combination rom (which came in the download). When done installing the phone boots into Factory Binary... Interesting little rom... From here you can access settings, tho the instructions tell you to enable developer options and turn on usb debugging... in this rom they are set on by default i believe, so that was kind of a waste of time... then from the main menu you click the icon that looks like a calculator and type in "*#0808# where you are then presented with usb options. Select the last one on the list with adb at the end of it, click save and reboot. At this point I thought i was supposed to install the stock rom back (that was where i was lost) however all you have to do is let it boot back to binary. After it has reloaded... plug it into the pc and send it the proper adb instructions to disable frp lock. Techeligible has a batch file for use in windows, however if you dont have windows like me that does no good... So I went into the batch file with a text reader and extracted the information i needed ( 3 adb commands).In terminal i made sure my adb and fastboot were updated and working. I learned that when you type "adb devices" it will show the phone and if it says nothing else you are good to go. However it may give you a problem with permissions. If this is the case then unplug and make sure usb debuggin is on, you can also check that the adb is enabled again by doing the *#0808# command again and make sure the last selection is checked. When all is in order... At first I thought all commands must work for it to succeed... However this is not true at all. Only one of the adb commands will not give an error and at that time you can reboot into download mode and install the stock rom back on. After installation the phone will reboot and FRP Lock is no longer on... Now you can go into settings open up developer settings (tap build number till it unlocks) and select "OEM Unlock" and turn it on. Make sure usb debugging is on and you can boot back into download mode and install TWRP without a hitch.
I tried installing a couple of custom roms, however I have had no success with getting one to boot. (always stuck in boot loop even with wipe or factory reset) so I gave up and left him with the stock rom. If anyone has any idea of how i could get passed the bootloop maybe i can try again for him sometime and see how he likes various custom roms, but now he is happy he has his phone back working and it only took me a week of off and on frustration to figure it out... Hope this helps someone... (please dont ask for links) but if you do need help or have questions feel free to ask.