Hello,
I got the device back from an employee who left the company but he didn't reset the phone nor did he give us the unlock code, so its encrypted and we can't use it for someone else atm.
I tried everything to get the phone unlocked.
The last thing I tried is removing the back cover from the phone and short a little circuit to get it to boot in EDL mode.
I was able to flash a stock rom but after the succesfull flash its STILL locked and can't setup the phone.
What more can I try??
See images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
michelmau5 said:
Hello,
I got the device back from an employee who left the company but he didn't reset the phone nor did he give us the unlock code, so its encrypted and we can't use it for someone else atm.
I tried everything to get the phone unlocked.
The last thing I tried is removing the back cover from the phone and short a little circuit to get it to boot in EDL mode.
I was able to flash a stock rom but after the succesfull flash its STILL locked and can't setup the phone.
What more can I try??
See images:
Click to expand...
Click to collapse
FRP I guess?
Dude, you've been making these posts and asking for help. If an employee gave it to you, just call the employee and get the PIN number or ask him to come and unlock the device for you. This is not that hard. If the device is FRP locked, you won't be able to unlock it anyway so stop trying and making us think you stole the device. I suppose gnide93 is also you?
marstonpear said:
Dude, you've been making these posts and asking for help. If an employee gave it to you, just call the employee and get the PIN number or ask him to come and unlock the device for you. This is not that hard. If the device is FRP locked, you won't be able to unlock it anyway so stop trying and making us think you stole the device. I suppose gnide93 is also you?
Click to expand...
Click to collapse
Dude this is litterally my first topic on this forum, and no i'm not gnide93.
Also hes not an employee anymore and you don't know the situation.
I can't contact him anymore.
If you really think I stole the damn phone I can show you the contract he signed for the fricking phone.
Try wipe device in TWRP, after wipe reboot device and continue normally, in setup don't connect co WiFi and finish first setting, after this go to setting in phone and go to reset option and reset drm... And finally make normal default reset
czeckpage_FUZE said:
Try wipe device in TWRP, after wipe reboot device and continue normally, in setup don't connect co WiFi and finish first setting, after this go to setting in phone and go to reset option and reset drm... And finally make normal default reset
Click to expand...
Click to collapse
TWRP = No Go. His problem is it's a FRP locked phone and it still has locked bootloader.
I suggest service center is the way to go. Or ask the original owner about password politely
Related
Ok, so my friend has a galaxy nexus and its was working fine for him and then one day its was fuxzored. He told me the last thing he did was installed a cracked version of gta. the game worked so i dont think its a virus but thats the only thing fishy i know of that he did with his phone.
so, the state the phone is in is it goes into a boot loop when trying to start the thing, the google logo comes up and then there is a glitch in the screen for a second then back to google logo and then a restart.
i am able to get into the bootloader but when i try to go into recovery the android is lying on his back with a red exclamation point over him(most of the time i cant even get to that point. sometimes the screen goes black or glitches and it reboots.), so i press all three buttons and i have the option to wipe data or flash from cache, but there is nothing in the cache.
so i thought i might be able to use fastboot with the gnex toolkit to flash his recover to cwm. well the bootloader is unlocked but recovery is still messed up. nothing seems to work.
im out of ideas. please help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=1366806
brummie028 said:
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
This won't help if he can't get into recovery mode.
rljetsetradio said:
...
i am able to get into the bootloader but when i try to go into recovery the android is lying on his back with a red exclamation point over him(most of the time i cant even get to that point. sometimes the screen goes black or glitches and it reboots.), so i press all three buttons and i have the option to wipe data or flash from cache, but there is nothing in the cache.
...
Click to expand...
Click to collapse
The droid with the exclamation mark is the stock recovery. If you push volume up + power you get the recovery menu. Maybe a factory reset there will bring a solution? (Only thing I can think off right now).
How about Odin?
Can you get into download mode?
dario3040 said:
How about Odin?
Can you get into download mode?
Click to expand...
Click to collapse
Yeah Odin would fix it.
Try this - http://goo.gl/sXXGN
'fastboot erase recovery'
'fastboot flash recovery cwm.img'
Try that
What bk201doesntexist said. As long as you can get into the bootloader, you are good to go.
OK so I've looked through the forum (admittedly the Galaxy Nexus specific one only) and tried some searches but may not be able to articulate this problem in clear way. Basically, I'm continuously crashing - started with a stock, but unlocked/rooted install. Now it won't boot and crashes in the boot loader as well after a few seconds (thus not allowing any non-trivial actions to actually complete.)
The first crash was after enabling face unlock for the first time. When I hit the power button to shut things off, the display "tore" and then went totally dark. Phone was completely unresponsive till I pulled the battery for a few minutes (found that one from search.) Couldn't complete a boot sequence though - would go to the animation, then display would go wonky and then shut down. Would usually have to pull battery again to get any response from that.
Went to recovery mode and wiped data - which completed - same problem on boot. Only thing I'd done was unlock and root (for eventual root apps, none of which had been run) so decided to undo that (using "Galaxy Nexus Root Toolkit 1.3.") On the factory restore there are several steps (boot loader, radio, etc.) and I haven't been able to complete that process.
I suspect it might even be bad hardware at this point, but can't go back to VZW with the phone still showing unlocked. Phone is a recent eBay purchase to replace a lost device but seemed fine for the 2-3 days I used before this all started.
Anyone seen something like this before?
So your able to get into recovery still? If it doesn't boot into the os it's probably a compatibility error between the kernel and rom your using (Just clearning data in recovery won't fix this).
So what rom/kernel combination were you using at the time?
Also have you tried flashing a completely different custom rom to the one your having issues with.
And any nandroid backups you have made in the past?
What's weird is that I was in stock kernel / rom at the time. (At least I'm nearly sure - it did come from eBay after all...)
I'll also try changing the ROM, that could be it. The big question is if that can complete before the thing melts. If I boot to recovery and wait, doing nothing, the system crashes in a minute or two.
My current thinking is that I might have a bad recovery / clockwork mod install.
can you still get to the bootloader and is it stable to sit on the bootloader?
I can get to the boot loader but it is not stable there (I think I was conflating the two.)
does your bootloader look like this? i want to make sure you and i are talking about the same thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yep, that's the one (before it crashes. I have a pic of the amusing video display when it does that I'll put up when I hit the magic 8 posts...)
try using ODIN to restore your phone. instructions are found here: http://forum.xda-developers.com/showthread.php?t=1394051
also, how long can you sit on the bootloader before it crashes?
I'll try that as tonight - thanks!
Varies on time to crash, but no less than 30 seconds and no more than 5 minutes so far. Requires a battery pull and wait to come back after that.
i would like to see the picture of the crash you are talking about.
also, you can relock the bootloader real fast before you take it to VZW. only takes 1 command once you get to the bootloader
fastboot oem lock
Wow, same crash while in download mode. That can't be good...
yeah thats not good at all. i'd lock the bootloader and return it
http://dulinor.smugmug.com/photos/i-XkKWCrg/0/S/i-XkKWCrg-S.jpg
This is the crash I'm seeing
Yeah return to the store and show them this, the board is probably bad.
thats rough, but since you got it on ebay returning it may be a hassle and if the phone is not a north american model samsung might not even accept it for warranty.
did you try to flash the stock google image using fastboot instead of using the toolkit? it will only take a few mins. when you display crash like that does it still take commands from fastboot? you can test it when the display crash like that type in fastboot devices and see if you get the id number in command prompt. if your build was yakju then you can get the factory images from here http://code.google.com/android/nexus/images.html
Just got back from the store - they issued a replacement, none on hand so one should ship out today. (Thanks for the tip on re-locking it - not sure if they checked, but was happier having that.)
So of course, it actually completed booting (for the first time) but crashed during activation. Once they saw it crash on the Odin screen, they were happy to do the swap.
I had been trying to re-flash OEM Google - which it should have been all along.
Thanks everybody for your help.
Well, I have a problem. I am using viperx, with my phone unlocked, obviously. I was listening to music when it suddenly reboot. It runs in bootloader. And... with a message LOCKED and security warning. I dont know what happened. It was in my car holder, I didn´t touch anything... If I reboot, it says for a second "this build is for development purposes only. Do not distribute outside of htc without htc's written permission. Failure to comply may lead to legal action". Then back to the bootloader.
The phone was perfectly cold when it reboots...
A couple of screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help? I suposse I have to unlock it again?
Unlock it again. Use the Unlock_code.bin that you should have in your email.
death__machine said:
Unlock it again. Use the Unlock_code.bin that you should have in your email.
Click to expand...
Click to collapse
Well, I was going to do it, but.. it doesnt boot now... :crying:
racatapum said:
Well, I was going to do it, but.. it doesnt boot now... :crying:
Click to expand...
Click to collapse
after unlock don't forget to flash custom recovery and then fastboot erase cache.
is this the leaked JB hboot?
AgoeZ said:
after unlock don't forget to flash custom recovery and then fastboot erase cache.
Click to expand...
Click to collapse
Yes, but the problem is that the phone doesnt start now...
hamdir said:
is this the leaked JB hboot?
Click to expand...
Click to collapse
No, I didnt upgrade to jb yet...
Cant boot, cant charge it (no leds)...
If phone does not start and you cannot go into HBOOT and it does not get recognized as APX in your computer.
You are ****ed or battery is done.
xmoo said:
If phone does not start and you cannot go into HBOOT and it does not get recognized as APX in your computer.
You are ****ed or battery is done.
Click to expand...
Click to collapse
then.. to the sat?
Timebomb? What build were you on?
There is no way to charge it if it is power off?
webpatrick said:
Timebomb? What build were you on?
Click to expand...
Click to collapse
I was using the last viperx rom...
I would try to charge it using the charging script.
http://forum.xda-developers.com/showthread.php?t=1738274
As your phone doesn't start up / boot at all there might be something completely different that's messed up, I'm guessing it's faulty hardware that has first caused your phones software to go haywire and now the phone simply won't start. You could try the charging-script above but I'd probably go for the warranty, HTC might be a bit tricky about that though.
well his phone says locked and not relocked, the only thing there is the security warning, but i guess he can claim never to have rooted the phone.
i´m not sure about it though
Unlock again.
Well, yesterday night, I left the phone plugged to the wall carger. During the night, It starts (don´t know why) and entered bootloader. Unfortunatelly, I was too slept to try anything...
HTC wont take it to the SAT till monday, so any ideas will be really appreciated!
racatapum said:
Well, yesterday night, I left the phone plugged to the wall carger. During the night, It starts (don´t know why) and entered bootloader. Unfortunatelly, I was too slept to try anything...
HTC wont take it to the SAT till monday, so any ideas will be really appreciated!
Click to expand...
Click to collapse
It reboots again. In fastboot, of course. My pc read it. Tried the battery charger pluggin. It worked, but didt start again. It is off again. What can I do if it starts again? erase cache?
racatapum said:
It reboots again. In fastboot, of course. My pc read it. Tried the battery charger pluggin. It worked, but didt start again. It is off again. What can I do if it starts again? erase cache?
Click to expand...
Click to collapse
Mayby try install ruu for your country
Sent from my HTC One X using xda premium
I was going to restore via clockmodworld recovery mode. Before that I had format data, clear cache, factory reset. Then it showed that the MD5 of the backup I wanted to restore is mismatched. I had no choice so I chose reset.
Then now my phone is all in black screen, I can't enter download mode or recovery mode, can't boot, no charging battery sign when plug in. Is my phone hard bricked ? Anyway to fix it ?
Thanks
IT_Fan said:
I was going to restore via clockmodworld recovery mode. Before that I had format data, clear cache, factory reset. Then it showed that the MD5 of the backup I wanted to restore is mismatched. I had no choice so I chose reset.
Then now my phone is all in black screen, I can't enter download mode or recovery mode, can't boot, no charging battery sign when plug in. Is my phone hard bricked ? Anyway to fix it ?
Thanks
Click to expand...
Click to collapse
Pull battery for 30 secs reinsert the try download mode vol down. Home. Power. If you cant get download mode or recovery id say its bricked. I bet you got a n7100. Without a doubt..
Sent from my GT-N7105 using xda premium
Someone told me I need these tools, are they JTAG ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IT_Fan said:
Someone told me I need these tools, are they JTAG ?
Click to expand...
Click to collapse
What ever they are thats certainly a messy workstation. lol
Sent from my GT-N7105 using xda premium
IT_Fan said:
I was going to restore via clockmodworld recovery mode. Before that I had format data, clear cache, factory reset. Then it showed that the MD5 of the backup I wanted to restore is mismatched. I had no choice so I chose reset.
Then now my phone is all in black screen, I can't enter download mode or recovery mode, can't boot, no charging battery sign when plug in. Is my phone hard bricked ? Anyway to fix it ?
Thanks
Click to expand...
Click to collapse
Your phone might have succumbed to SDS. In that case the only way is to approach the Service and get the Mother Board replaced.Sorry to say this.But I was also a victim for this unhappy situation.
I took it to warranty service and got mainboard replaced.
pnsdhrn said:
Your phone might have succumbed to SDS. In that case the only way is to approach the Service and get the Mother Board replaced.Sorry to say this.But I was also a victim for this unhappy situation.
Click to expand...
Click to collapse
I think so, I got my mainboard replaced but now check with emmc brick checker still get "Yes. Insane chip" result. Is it possible it will SDS again in future ? :crying:
p/s : before my phone died I did update stock rom 4.1.2 and latest kernel perseus. Any idea ?
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.
Anyone ?
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?
xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.
XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here