Hi all! I have a somewhat embarassing problem.
My son is using my ZUK Z2 Pro. He loves it, thinks it´s awsome and loves that noone else has it
So the other day, he decided to change his password for the screen lock. Problem is, now he doesn´t remember his new password.... he has tried at least 100 different ones and cannot remember it.
I´m trying to find a way how to solve this. Erasing the device via Google find my device doesn´t seem to work. There is an erase/wipe option, but nothing happens when I click it.
I think the phone was running on stock ROM and stock recovery (not sure but I think I tried different ROMs on it but decided to flash stock ROM before giving it to him). At least when I boot into recovery it looks like some stock recovery. I don´t have any option to wipe/reset device in there, just to flash (which fails).
Bootloader seems locked. I tried to issue a "fastboot -i 0x2b4c oem unlock-go" via fastboot, but it fails. USB debugging is probably not enabled, if that makes any difference.
Any ideas?? Feels so stupid not to be able to solve this, I mean it´s a perfectly good phone with one small issue that seems nearly impossible to get around. At least son leared a lesson
Related
Hi guys, I want to change my phone bootloader and also to a friend of mine. But I have some nasty experience with bootloader upgrading so I though that a discussion here would be good, so everyone know what to do in the future.
For example, I use ODIN for firmware upgrades, but as you all know it has a quite big rate of failures, caused by different reasons. On the other hand, we have Heimdall which is supposed to be safer and has more options than ODIN (bootloader flash only and such things).
The point is, while we are in download mode, and the flashing of bootloader fails, after restart... well... there won;t be a start anymore. The phone will be dead. What I was thinking is: what if we don't thick restart on ODIN or Heimdall and if flashing the boot loader fails, the phone will remain in download mode. Couldn't this be the opportunity to try again? After all, all we need is download mode.
We could try second time with Heimdall, or another full firmware with odin... what do you say guys?
Remaining in download mode gives us a second chance to bootloader writing?
Sorry if I've been really fuzzy in my ideas but I'm very sleepy right now.
Crysis21 said:
Remaining in download mode gives us a second chance to bootloader writing?
Click to expand...
Click to collapse
Unfortunately no. If a flash fails it's because the phone has stopped responding to commands. The phone won't continue responding to commands until you've booted into download mode again. It's for this very reason I don't actually have a "no reboot" option for Heimdall, it would be pretty much pointless.
However luckily if you're just flashing a secondary bootloader the device can still be booted up using a custom jig. This is because devices store a backup secondary bootloader that can be used if the first one is corrupt. A custom jig seems to cause the device to boot using this backup secondary bootloader.
However as far as I can tell if you stuff up the primary bootloader then you're toast. This would require a JTAG fix. I'm not actually sure if this has ever even happened though.
The thing is, 4 months ago I ended up on JTAG. After messing the bootloader I managed to get download mode with custom JIG. But after that I don;t know exactly the mistakes I've made, but I ended up with a dead phone. No JIG working, nothing. So... yes it happened. I am toasted already with bootloader changing) that's why I was asking if remaining in Download mode helps with somthing.
Thanks for your answer
Sorry I should have been clear. I know there are cases where users have hard-bricked their phone and not even a custom jig would help so JTAG was required.
During the early stages of Heimdall's development, prior to the custom jig discovery, I bricked my device to the point of not being able to charge. This was because either boot.bin or params.lfs failed to flash due to a bug in a alpha release of Heimdall. We didn't know about custom jigs then so I was unable to actually test if it was recoverable.
However, all the hard-brick cases that I've heard sufficient detail about, turn out to be a result of users flashing a primary bootloader that was not designed for their device. So what I should have said is that I'm not sure if anyone has ever actually failed to sucessfully flash a primary bootloader (other than me with an alpha build).
Anyway unfortunately there's not a whole lot that can be done to 100% remove the risk of bricking. Either the secondary bootloader USB control software is buggy or the hardware itself is crap and sometimes it doesn't get on well with some people's USB ports. Unless we come up with a way to easily replace the bootloaders from the device itself then the best thing you can do is use a reliable USB port.
Thanks for the information...
Hey everyone ^^
Hoping I can find some help here, else it'll be another phone consumed by the bricking plague
I recently tried to flash the latest CM from sourceforge, but the flashing process was interrupted (Powercut FFS). So the phone's stuck at the bootscreen. Normally, it'd be a case of rebooting into download mode and retrying, but....
My home key is buggered, it had a disagreement with some rain. Again, normally it'd be fine. Just use ADB to get into recovery/download, but...
The bad flash has made the phone unable to be recognized. Unsure whether it fails before it initializes USB, but it just won't be picked up on either ADB or Odin.
It's not all bad, I can still see the first Galaxy S bootscreen (The first one being the static, unflashey one).
TL;DR: Phone is buggered, unable to use "conventional" methods to access download mode, bootloader is still intact.
Could somebody please give some advice on this situation? It'd really help me out! Not keen on getting a new phone just yet
Cheers,
Morgan ^^
use JIG mate
http://forum.xda-developers.com/showthread.php?t=819551
thanks to TheBeano.
Yeah, I was looking into that. Unfortunately it'd take a few weeks for the parts to get here (No places like RadioShack etc) and this phone needs to be working ASAP (Usual story, right? ). Short of taking a knife to the AC adapter and hoping that I can find a 300K resistor, I'm at a loss as to what to do...
And now, this is even more interesting. Out of curiosity I decided to try to install my phone's drivers manually (For some reason Windows wasn't picking them up). The ADB drivers installed without any problems and I can now issue commands via ADB
The bad news is, well... Apparently most of the system stuff is missing. No /System/Bin directory at all (The only thing in /System is Lost+Found). Which, obviously, is bad. I tried issuing "reboot recovery" and "reboot download" which both worked, except the phone quickly flashed a white/blue line across the screen and restarted.
Is there any way to restore functionality through ADB? Can I push files to the /System/Bin directory (And all other missing things...)? If so, where would I get the files?
Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
williaam said:
Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
Click to expand...
Click to collapse
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
LaurynasVP said:
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
Click to expand...
Click to collapse
No, I guess I didn't... My bootloader status in Flashtool is : ROOTABLE I'm going to try doing that first. Thank you so much for your fast answer
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
williaam said:
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
Click to expand...
Click to collapse
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
LaurynasVP said:
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
Click to expand...
Click to collapse
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
williaam said:
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
Click to expand...
Click to collapse
Guess so. If even will update to earlier version (4.4.x) or later BE2 won't work, as well as camera stabilization (focus, well, it works, but photos are a bit like blured) and some other functions that I don't remember at the moment. It doesn't matter how did you unlock your bootloader, the fact that you've unlocked your bootloader is the most important. I'm sorry, but there's nothing we can do about it (DRM keys recover) at the moment. Maybe in a future there will be found a solution for this, but then our phone, I suppose will be like a nokia 3310 in nowadays.
Btw, you can still get some functions working, just surf this forum for unlocked bootloader functions "Get back" or sth., don't remember thread name either.. :|
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.
So ive just recieved an s3 8190 mini not an n or l model labled as sapres repairs, i have some experiecne flashing phones including a s3 mini-n so thought i'd grab this one to fix it and sell on...boy was i wrong
many hours later of various flash attmepts and reading troublshooting methods on the problems this phone does little else but restart a lot!
it wont accept anything ive flashed, i cant boot into recovery or root it sucessfully, however it will boot into download mode (a ray of hope perhaps?) after flashing various recoveries and trying to boot into it the bottom leds flash and it restarts again and it just wants to boot up normally no matter what, ive tried the 3 buttons then releasing only the power after i see the logo as ireads that worked for a few
the phone requires a pin to be entered at start which was in the box on a piece of paper, once in the time i get varies before it resets again and any settings i changed are restored things like wifi mode etc are all back...wtf is this? also apps cant be uninstalled!! and more importanly i cant factory reset, i press the first few buttons and then the final one does nothing....there is a missed call dated last year some time that shows up in the notifications area...
im currently flashing official firmware via link on this site that matches the baseband so hoping that might do something, but that seems like bind mans hope in hell, ive tried a few things from this site like a flash that makes the 3 buttons "work" which it did for some, thought not done anyhting with adb/fastboot being new to it, the phone wasnt recognised the few times i tried it.
where now then just what is wrong wiht this phone and can i get it up & running?