Related
Affected models:
Galaxy Tab 8.9" P7300 (confirmed by me) / P7310 (confirmed by whitehart)
Galaxy Tab 7.7" P6810 (confirmed by sebi1964)
Other Galaxy Tab series, including 10.1" (lot's of complaints on XDA, please confirm in this thread)
Symptoms:
No lockscreen, regardless of the setting
"Factory Mode" icon on homescreen, that opens up a calculator
Power button powers off the device instantly: no menu appears
No setup wizard after factory reset
Open Lock icon at boot screen - maybe it's not a related issue (please confirm)
Myth:
Only Samsung repair center can fix it - FALSE!
Workaround:
Type *#7594# in the Factory Mode application and uncheck the box in the Shutdown App that appears after entering the code - Works in some cases, temporarily, till you restart
Fix:
Rooted device
Mounted /efs partition (if in recovery)
Execute the following commands:
Code:
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Reboot device
Optionally: factory reset to get rid of the Factory Mode icon (or just delete it from homescreen)
Result:
All of the symptoms mentioned above are gone, except the lock icon at boot screen.
Needs investigation:
The lock at the boot screen may, or may not be related to the issue. It happens on my P7300, but to the following user's P7510 too: http://forum.xda-developers.com/showpost.php?p=18833764&postcount=1
What are the advantages of having a Galaxy Tab with unlocked bootloader? Or disavantages of having a locked one? How to relock?
Reference:
I've adopted Odia's solution for the Galaxy S3, spent some time with reverse engineering to see if it applies to our Tab's, if so, what are the differences, and voila!
Donators:
wojt.eu
RipplingHurst
Donations are always welcome PayPal
*#7594# did not work on my P6810
sebi1964 said:
*#7594# did not work on my P6810
Click to expand...
Click to collapse
7.7" might need different syled commands, try *#*#7594#*#*
tracid said:
7.7" might need different syled commands, try *#*#7594#*#*
Click to expand...
Click to collapse
Same thing. Is something like this "enable shutdown at long press...". It is not checked. But even if is checked or not my lockscreen missing.
sebi1964 said:
Same thing. Is something like this "enable shutdown at long press...". It is not checked. But even if is checked or not my lockscreen missing.
Click to expand...
Click to collapse
If the "enable shutdown at long press" is unchecked, does changing the setting at Settings -> Location and security -> configure lock screen have any effect?
I suppose you have the Factory Mode icon, else you couldn't type in the code, right?
EDIT: I've helped sebi1964 and my fix solved his problem.
Open lock icon on boot screen just means you have a fully unlocked (nvflash is accessible) Tegra device. About half of Tab 10.1s sold were like this, many of them got locked by an update but if you never took the update in question it would remain unlocked.
Some of the other stuff I have seen once - on a special developer device (with socketed eMMC) in the hands of a Samsung engineer. It was an I9100.
Entropy512 said:
Open lock icon on boot screen just means you have a fully unlocked (nvflash is accessible) Tegra device. About half of Tab 10.1s sold were like this, many of them got locked by an update but if you never took the update in question it would remain unlocked.
Some of the other stuff I have seen once - on a special developer device (with socketed eMMC) in the hands of a Samsung engineer. It was an I9100.
Click to expand...
Click to collapse
Yes, I've read about those 10.1". But this is a 8.9". So the only advantage is that I boot into nvflash (APX?) mode without the battery drain trick?
Yeah i got my P7500 in factory mode after had a main-board and screen replacement(under warranty) all the symptoms are correct.
I have to returned it back to Samsung and the technician doesn't even know what to do, after much debate that i want the factory mode gone finally it returned to normal mode. I didn't know what Samsung did, but my guess is that my tab doesn't have imei and board serial number and missinf efs folder, that is why it is entering in factory mode. just a guess though as when i check last time my serial and imei was 0000 and 0000 something.
I wish people acknowledge this problem back then, i felt like an idiot asking in the forum and no one else had it and everyone said that i had done something wrong.
Fortunately samsung fixed the tablet.
My major problem with tablet in "factory mode" is that power button shuts off tablet immediately without menu,
cheers.
tracid said:
Yes, I've read about those 10.1". But this is a 8.9". So the only advantage is that I boot into nvflash (APX?) mode without the battery drain trick?
Click to expand...
Click to collapse
No, the advantage is you can actually USE APX mode - if locked, APX mode requires a key that we don't know.
Tab 10.1 and having the same issue.
I had installed a custom firmware after it returned from repair and had no issues. The issues started after I updated to the official ICS rom. But there is no factory mode app to be seen on the phone. However all the symptoms persist.
I tried to run the adb commands through recovery but it just keeps giving me not found errors.
When I try in debug mode the commands go through by the looks of it. Is it supposed to show me some sort of an output on cmd ?
Either way after the reboot issues still persist. :/ Any ideas?
Try to mount /efs partition from the "Mounts and storage" menu in recovery.
Posting here as it seems more people post here
I have same issue after the device was repaired (new board) I have tried the code with teh device rooted, the only thing that works is the engineers code which is temp, as soon as you reboot it its lost'
Here is my original post (8.9 tablet)
http://forum.xda-developers.com/showthread.php?p=31680609#post31680609
If anyone can help it would be great otherwise it'll have to go back to the repair centre again
thanks in advance
What do the commands return in terminal?
tracid said:
What do the commands return in terminal?
Click to expand...
Click to collapse
managed to get it to work, I did a reset factory data
rebooted now it has the lock screen - soo pleased - I've rebooted it a few times and it seems fine now fingers crossed its fixed
Cheers
Glad you did it. It's a P7300 or P7310?
tracid said:
What do the commands return in terminal?
Click to expand...
Click to collapse
tracid said:
Glad you did it. It's a P7300 or P7310?
Click to expand...
Click to collapse
P7310
i have all 4 first Symptoms on sgs3
and i did the solutions and nothing works please help!!
baster72 said:
and i did the solutions and nothing works please help!!
Click to expand...
Click to collapse
There's a link in the first post to Odia's solution for SGS3... http://forum.xda-developers.com/showpost.php?p=28113616&postcount=14
tracid said:
There's a link in the first post to Odia's solution for SGS3... http://forum.xda-developers.com/showpost.php?p=28113616&postcount=14
Click to expand...
Click to collapse
I've tried this on a Gt-P5113 and it works.
1. Root the device and then download SuperUser first and Terminal Emulator from Google Play store.
2. After that launch SuperUser app and then use Terminal Emulator to type in the following commands:
Code:
su
echo -n ON > /efs/FactoryApp/factorymode
That should solve the issue.
---------- Post added at 07:18 AM ---------- Previous post was at 07:13 AM ----------
One more thing is that for me, I've also tried to flash it back to an original ROM to remove root and I noticed that the edited settings are persistent.
baster72 said:
and i did the solutions and nothing works please help!!
Click to expand...
Click to collapse
me too.I have GS3. Please help us
Hey guys I'm a newbie here and I am probably way over my head but I have an issue. I did something stupid and edited some build props to try to get a game to work. Now when I start my kindle its stuck on "starting applications: updating kindle". Like I said I'm really new to all this rooting stuff and even just android products. I have a jailbroken iPhone 4 and I thought all this we b cool to try. I successfully rooted my kindle fire he 7 a few days back and was having fun with the play store but I got way over my head and now I'm stuck. I need to know how to restore or reset my kindle thru the computer bc it doesn't even turn on.. Oh and by the way I'm really bad with all this adb, recovery, fastboot stuff like I said newbie.. PLEASE HELP
lacoursiere18 said:
Hey guys I'm a newbie here and I am probably way over my head but I have an issue. I did something stupid and edited some build props to try to get a game to work. Now when I start my kindle its stuck on "starting applications: updating kindle". Like I said I'm really new to all this rooting stuff and even just android products. I have a jailbroken iPhone 4 and I thought all this we b cool to try. I successfully rooted my kindle fire he 7 a few days back and was having fun with the play store but I got way over my head and now I'm stuck. I need to know how to restore or reset my kindle thru the computer bc it doesn't even turn on.. Oh and by the way I'm really bad with all this adb, recovery, fastboot stuff like I said newbie.. PLEASE HELP
Click to expand...
Click to collapse
You will need to get into fastboot somehow to fix it.
You are new to adb but you had to have had the drivers installed to root, so when you connect it to the computer does it show up in your device manager?
If yes, then you can get into fastboot by opening a cmd prompt where you have access to adb. If you used the qemu root tool then the files you need will be in there.(Or since you will need it anyway, download KFHD Restore tool from here: LINK, you will want v1.2.3, it also has adb files you'll need). To open a cmd prompt from that folder, hold shift and right click on the folder. There should be an option to "open cmd prompt from this location", or something to that affect.
In the cmd prompt use these cmds(press enter between each cmd):
Code:
adb shell
su
reboot bootloader
After you are in fastboot then follow the directions in the Restore Tool post from the link above.
If you can't get into fastboot that way then you will need a factory cable, You can make your own or here is where you can buy one: Factory Cable by Skorpn. I've also heard of people purchasing on amazon but not as quality as Skorpn's
onemeila said:
You will need to get into fastboot somehow to fix it.
You are new to adb but you had to have had the drivers installed to root, so when you connect it to the computer does it show up in your device manager?
If yes, then you can get into fastboot by opening a cmd prompt where you have access to adb. If you used the qemu root tool then the files you need will be in there.(Or since you will need it anyway, download KFHD Restore tool from here: LINK, you will want v1.2.3, it also has adb files you'll need). To open a cmd prompt from that folder, hold shift and right click on the folder. There should be an option to "open cmd prompt from this location", or something to that affect.
In the cmd prompt use these cmds(press enter between each cmd):
Code:
adb shell
su
reboot bootloader
After you are in fastboot then follow the directions in the Restore Tool post from the link above.
If you can't get into fastboot that way then you will need a factory cable, You can make your own or here is where you can buy one: Factory Cable by Skorpn. I've also heard of people purchasing on amazon but not as quality as Skorpn's
Click to expand...
Click to collapse
Now when I plugged it in the first time I saw it in the device manager with a yellow triangle and an explantion mark. Yes I was definetly rooted bc I had the google play store and access to a lot. When you say you can open a command prompt where you have access to adb.. what do you mean. Like I said a newbie. I know where command prompt is on my computer but Im not sure about this adb thing. Could you explain step by step Windows XP. And the folder your talking about is the one you provided the link for? Sorry so many ?'s I really appreciae you time.
anybody... PLEASE
You are in the wrong forum. This is for 2nd generation Kindle Fire 2/Kindle Fire HDs, and you obviously have an original 1st generation Kindle Fire.
You need to take a step back for a second and do a little research before you proceed and get a better idea of what's going on. A great place to start is a thread in the Amazon Kindle Fire General forum titled "Kindle Fire for Beginners". It will give you a better understanding of how things work and possibly how to fix it.
Outside of that, there are tools and utilities to help you along the way but in your situation, you really need to understand why your Kindle isn't working properly for them to do you much good.
Oh, and if you're looking for "step-by-step" instructions from someone, it probably won't happen. The information is there, you just have to find it. You wouldn't start working on your car without having the knowledge to do so, therefore why would you try with a technological piece of equipment?
That being said, if you have a question or need help understanding something in particular, I'm sure there will be plenty of people who would be wiling to assist you.
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
You are in the wrong forum. This is for 2nd generation Kindle Fire 2/Kindle Fire HDs, and you obviously have an original 1st generation Kindle Fire.
You need to take a step back for a second and do a little research before you proceed and get a better idea of what's going on. A great place to start is a thread in the Amazon Kindle Fire General forum titled "Kindle Fire for Beginners". It will give you a better understanding of how things work and possibly how to fix it.
Outside of that, there are tools and utilities to help you along the way but in your situation, you really need to understand why your Kindle isn't working properly for them to do you much good.
Oh, and if you're looking for "step-by-step" instructions from someone, it probably won't happen. The information is there, you just have to find it. You wouldn't start working on your car without having the knowledge to do so, therefore why would you try with a technological piece of equipment?
That being said, if you have a question or need help understanding something in particular, I'm sure there will be plenty of people who would be wiling to assist you.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Nice quote.. Well at least I know now who not to talk too in this forum. If YOU CAN READ in my origanl post it says I have a Kindle Fire HD 7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! That being said I have done a lot of research on this throughout the day and I am planning on attempting what the origanl replier was talking about. Don't be a ****, life's to short.
lacoursiere18 said:
Nice quote.. Well at least I know now who not to talk too in this forum. If YOU CAN READ in my origanl post it says I have a Kindle Fire HD 7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! That being said I have done a lot of research on this throughout the day and I am planning on attempting what the origanl replier was talking about. Don't be a ****, life's to short.
Click to expand...
Click to collapse
Ok i'm going to back up a little bit and appologize for calling you a ****. But, maybe you need re read what you wrote or maybe I took you text out of context. For a newbie on this site, you came accross pretty offensive. But I took your advice and read the Kindle Fire for Begginers and learned quite a bit. I will def have to re read it several times but it helped. So again I apologize and thank you
lacoursiere18 said:
Nice quote.. Well at least I know now who not to talk too in this forum. If YOU CAN READ in my origanl post it says I have a Kindle Fire HD 7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! That being said I have done a lot of research on this throughout the day and I am planning on attempting what the origanl replier was talking about. Don't be a ****, life's to short.
Click to expand...
Click to collapse
Yes I did read what you wrote, and you said when you plug the device in, all you see is the "yellow triangle". Typically speaking, the "yellow triangle" is typical of a modified bootloader which can only be found on the original Kindle Fires. It is possible we aren't speaking about the same yellow triangle so I apologize for making the assumption. But when you see as many egregiously ignorant questions I see from new users every day, and the extraordinary number of users that don't know the difference between the different KF devices, you'll see how easy it is to make that mistake.
I've helped a lot of people around here, and my "matter of fact" way of going about it has prevented a lot of unneeded mishaps, so for that, I won't apologize. And if you think I'm a **** for expecting a new user to adhere to the policies and guidelines set forth by XDA and research basic tasks like using the command prompt and ADB, so be it. But the fact still remains, people here are more likely to give you general instructions and expect you to know how to carry them out on your own, than spend the time to write out explicit step-by-step instructions for something that takes more than a few lines of text to explain, and in such a way that someone who knows nothing about it can understand.
Take my advice or don't, but whether you think so or not, I am trying to help by getting you going in the right direction, so you can get your problem solved in a more efficient manner.
soupmagnet said:
Yes I did read what you wrote, and you said when you plug the device in, all you see is the "yellow triangle". Typically speaking, the "yellow triangle" is typical of a modified bootloader which can only be found on the original Kindle Fires. It is possible we aren't speaking about the same yellow triangle so I apologize for making the assumption. But when you see as many egregiously ignorant questions I see from new users every day, and the extraordinary number of users that don't know the difference between the different KF devices, you'll see how easy it is to make that mistake.
I've helped a lot of people around here, and my "matter of fact" way of going about it has prevented a lot of unneeded mishaps, so for that, I won't apologize. And if you think I'm a **** for expecting a new user to adhere to the policies and guidelines set forth by XDA and research basic tasks like using the command prompt and ADB, so be it. But the fact still remains, people here are more likely to give you general instructions and expect you to know how to carry them out on your own, than spend the time to write out explicit step-by-step instructions for something that takes more than a few lines of text to explain, and in such a way that someone who knows nothing about it can understand.
Take my advice or don't, but whether you think so or not, I am trying to help by getting you going in the right direction, so you can get your problem solved in a more efficient manner.
Click to expand...
Click to collapse
ok now I am stuck. I have got my adb drivers installed and I believe correctly. I use the cmd prompt to navigate to the folder and execute those commands given. My kindle now has a Fastboot logo, that it nothing else. I went to use the tool in the LINK given and I try option 3? EDIT: ok so I hit option 3 and it went through its thing. It restarted my kindle and it was stuck on the highlighted kindle fire logo forever....
lacoursiere18 said:
ok now I am stuck. I have got my adb drivers installed and I believe correctly. I use the cmd prompt to navigate to the folder and execute those commands given. My kindle now has a Fastboot logo, that it nothing else. I went to use the tool in the LINK given and I try option 3? EDIT: ok so I hit option 3 and it went through its thing. It restarted my kindle and it was stuck on the highlighted kindle fire logo forever....
Click to expand...
Click to collapse
Ok i am officially out of luck and knowledge. I truned off my kindle when it was stuck on the highlighted kindle logo. I went to restart and now my computer does not recognize it. I am starting form scracth I deleted everything on my computer I dont know what to do
lacoursiere18 said:
Ok i am officially out of luck and knowledge. I truned off my kindle when it was stuck on the highlighted kindle logo. I went to restart and now my computer does not recognize it. I am starting form scracth I deleted everything on my computer I dont know what to do
Click to expand...
Click to collapse
You're still ok, I sent you a PM on what you'll need to do.
fire is upgrading, starting applications stuck
onemeila said:
You're still ok, I sent you a PM on what you'll need to do.
Click to expand...
Click to collapse
I have also the similar problem with my hdx 7, it stuck at "fire is upgrading, starting applications", i have tried factory reset, but it proved to be useless. I have talked to Amazon, they ask me to send my hdx back them(without any repayment) and buy a new one. So amazon will not help solve this problem, then do u have a solution pls?
Hi, I recently ran into the same problem with the "fire is upgrading, starting applications" screen and could not solve it yet. First of all let me tell you the facts:
Kindle Fire HD 7 (3rd generation)
FireOS 4.5.5.1 (no update available when checking for update on the Kindel Fire itself)
Developers mode enabled
adb is unauthorized (unfortunately)
OTA was unfortunately on
Rooted with Kingroot
I was playing around with my Kindle and checked out Kingroot and rooted my Kindle with it. Unfortunately I got distracted forgot to disable OTA updates and guess there lies the problem of my misery, i.e. the sudden Kindle Fire update over night with the starting applications message (where the starting applications takes a long time, i.e. never ends). Hence, I can not operate my Kindle Fire, and moreover I cannot access it over adb since the device is unauthorized. Side note, I'm using Linux and OSX and have Win7 in a VM (if there are OS specific solutions/tools for solving my problem). I'm not in possession of a factory cable (also don't have tools to build one). However if someone has a suggestion there it is welcome.
Now to my questions:
Will I need the factory cable?
If not, where should I focus on first?
If yes, any tips and tricks are welcome.
Hope someone can help me here, thanks.
buschko said:
Hi, I recently ran into the same problem with the "fire is upgrading, starting applications" screen and could not solve it yet. First of all let me tell you the facts:
Kindle Fire HD 7 (3rd generation)
FireOS 4.5.5.1 (no update available when checking for update on the Kindel Fire itself)
Developers mode enabled
adb is unauthorized (unfortunately)
OTA was unfortunately on
Rooted with Kingroot
I was playing around with my Kindle and checked out Kingroot and rooted my Kindle with it. Unfortunately I got distracted forgot to disable OTA updates and guess there lies the problem of my misery, i.e. the sudden Kindle Fire update over night with the starting applications message (where the starting applications takes a long time, i.e. never ends). Hence, I can not operate my Kindle Fire, and moreover I cannot access it over adb since the device is unauthorized. Side note, I'm using Linux and OSX and have Win7 in a VM (if there are OS specific solutions/tools for solving my problem). I'm not in possession of a factory cable (also don't have tools to build one). However if someone has a suggestion there it is welcome.
Now to my questions:
Will I need the factory cable?
If not, where should I focus on first?
If yes, any tips and tricks are welcome.
Hope someone can help me here, thanks.
Click to expand...
Click to collapse
Short update:
I now have a factory cable but I'm stuck at the moment. My first try was to get TWRP and somehow get into recovery. Thus I started with booting into fastboot with the factory cable and issued
Code:
fastboot -i 0x1949 flash recovery recovery.img
and the command succeeded. Then I wanted to issue:
Code:
fastboot -i 0x1949 oem idme bootmode 5001
however, the command got stuck and nothing happened. I just tried a reboot and after that I was able to issue the command. Thus I started my Kindle again and it shortly flashed and went black. Nothing further. Thus reset and start again. Now it just gets stuck in the grey Kindle Fire screen. If I try to boot into recovery (power + volume down) also nothing happens.
Can anyone give any tips here?
buschko said:
Short update:
I now have a factory cable but I'm stuck at the moment. My first try was to get TWRP and somehow get into recovery. Thus I started with booting into fastboot with the factory cable and issued
Code:
fastboot -i 0x1949 flash recovery recovery.img
and the command succeeded. Then I wanted to issue:
Code:
fastboot -i 0x1949 oem idme bootmode 5001
however, the command got stuck and nothing happened. I just tried a reboot and after that I was able to issue the command. Thus I started my Kindle again and it shortly flashed and went black. Nothing further. Thus reset and start again. Now it just gets stuck in the grey Kindle Fire screen. If I try to boot into recovery (power + volume down) also nothing happens.
Can anyone give any tips here?
Click to expand...
Click to collapse
Next update. I switched from my MacBook with OSX to my Desktop with Linux. Now I can issue more than one fastboot command in a row. However I'm stuck again. I issued the following commands:
Code:
fastboot -i 0x1949 oem format
fastboot -i 0x1949 flash boot hijack.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 continue
Now I wait for the Amazon logo with the orange underline, however, I'm continue to see the fastboot screen. Thus I'm stuck again.
Hence, I just powered off and on again and then I was able to issue fastboot commands again. Continued with
Code:
fastboot -i 0x1949 flash boot recovery.img
fastboot -i 0x1949 oem format
fastboot -i 0x1949 continue
Now the amazon arrow was there. Repeated the last command chain, and I ended up in TWRP.
Hello,
My 3rd gen stock Fire HDX also stuck at "Fire is upgrading..." screen. This thread say there is no solution but looks like you found a way to get TWRP on it. Is this correct? If so, once you get TWRP, you can recover right?
I am on ubuntu14?
When I do a fastboot -i 0x1949 oem format, it just hangs at <waiting for any device>
How to get fastboot to see device, what mode do you boot your HDX to? Do I need to use a fastboot usb cable or will the stock HDX usb cable work?
When I run adb command it show the device D0FCA... unauthorized
Thx
Any clear solution on this problem ?
Stuck on "updating kindle".
Hello there,
I've got this phone with blocked pattern because was tried several times and now is asking for google account and pass to unblock it;
is there any way to bypass this even by jtag without lose the info's from the phone?
Any idea is welcome.
Thanks!
MarianG said:
Hello there,
I've got this phone with blocked pattern because was tried several times and now is asking for google account and pass to unblock it;
is there any way to bypass this even by jtag without lose the info's from the phone?
Any idea is welcome.
Thanks!
Click to expand...
Click to collapse
Login with your google account! Theres no other way
Verstuurd van mijn GT-I9070 met Tapatalk
Without losing info? ... I think you could use adb pull command from stock recovery to pull the files you need from your phone to your pc, and then wipe data to remove the pass lock.
panda00 said:
Without losing info? ... I think you could use adb pull command from stock recovery to pull the files you need from your phone to your pc, and then wipe data to remove the pass lock.
Click to expand...
Click to collapse
ok than, what stock recovery do you recommend me with adb enabled?
I need the phonebook from the phone and the messages.
I don't know the firmware from the phone but I think it's 2.3.6
Oooo damn, contacts? I dunno where the contacts are stored in the phone really, but I'll try to find out and get back to you.
---------- Post added at 07:53 PM ---------- Previous post was at 07:41 PM ----------
Wait a sec... are you rooted?
Let me be a little more clear: thee phone I received it with locked pattern unlock (is asking for google account to unlock it) and I need the dat from the phone like is contacts messages etc; the phone I think it's with 2.3.6 android version and surelly is not root-ed.
The phone connects to the pc only in MTP mode.
MarianG said:
Let me be a little more clear: thee phone I received it with locked pattern unlock (is asking for google account to unlock it) and I need the dat from the phone like is contacts messages etc; the phone I think it's with 2.3.6 android version and surelly is not root-ed.
The phone connects to the pc only in MTP mode.
Click to expand...
Click to collapse
So the phone isn't rooted...
If you just received the phone, how come you got your contacts in there in the first place... Anyway, you can try to use the adb command
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db ./
with the ./ in the end
Send me a PM in our language with your problem. Maybe I understand better what are you talking about.
In the phone is not my phonebook; I just need to save the informations from that phone wich has a blocked pattern and ask for google account to unlock it.
Sent from my Lumia 920
go to recovery and wipe data and reset and Boom
MarianG said:
In the phone is not my phonebook; I just need to save the informations from that phone wich has a blocked pattern and ask for google account to unlock it.
Sent from my Lumia 920
Click to expand...
Click to collapse
try this.. see the video..
http://forum.xda-developers.com/showthread.php?t=1800799
There has been something around here about getting past the lockscreen, but it is only possible on Jelly Bean. The topic has to be here somewhere!
Sent from my GT-I9070 using xda app-developers app
Thanks for all help:
I wrote stock kernell, root files via sd card and reset pattern with srsroot tool.
I've succesfully removed the pattern without losing the data from the phone.
Regards!
I was installing EliteRom v4 but data partition was damaged and i could not change its filesystem to f2fs and I rebooted then and got the eRecovery telling data partition is damaged so i pressed "fix". it rebooted and now i cant access twrp or , just huawei software update and eRecovery, eRecovery pops up when booting without any key combinations, just power button. Any help? EDIT: FASTBOOT IS ACCESIBLE
Deleted post
EeliX7 said:
Okay, found another post and used its info to solve this.
Click to expand...
Click to collapse
Link to the post please which helped you to solve your problem?
It may be helpful for others
I was way too fast in editing that post didnt solve my problem as i cant turn usb debuggin on (was off at the moment i was installing) and the command line gives an error "remote:command not allowed" when attempting to unbrick by flashing system, boot, cust and recovery img (sorry for his terrible writing im on my tablet that is antique lags like hell even tho i have cm13)
EeliX7 said:
I was way too fast in editing that post didnt solve my problem as i cant turn usb debuggin on (was off at the moment i was installing) and the command line gives an error "remote:command not allowed" when attempting to unbrick by flashing system, boot, cust and recovery img (sorry for his terrible writing im on my tablet that is antique lags like hell even tho i have cm13)
Click to expand...
Click to collapse
So you are still stuck? Need help?
Well I sent the phone to repair due to TRUE laziness... So I don't need help with that anymore, thanks anyway
EeliX7 said:
Well I sent the phone to repair due to TRUE laziness... So I don't need help with that anymore, thanks anyway
Click to expand...
Click to collapse
I hope the tech repair guys fixes it. :angel:
sniperlife:D said:
I hope the tech repair guys fixes it. :angel:
Click to expand...
Click to collapse
Well they are equipped to fix this
shashank1320 said:
Well they are equipped to fix this
Click to expand...
Click to collapse
Yes. But I experienced tech guys before who were new to a certain problem. They were not able to fix it then.
Back in 2011 when I was a kid, it took 2 weeks to "repair" my bricked tab. The tab travelled over 400 kilometres!
THIS REPLY IS THE 3000th post in Honor 5C QnA
EeliX7 said:
THIS REPLY IS THE 3000th post in Honor 5C QnA
Click to expand...
Click to collapse
Good achievement:good:
Goes to show how active honor forums are.
sniperlife:D said:
Goes to show how active honor forums are.
Click to expand...
Click to collapse
More than active...lol.
This is since honor 5X development started to get boost. People came to honor forum
lol the people on the goddamn service centre actually thought there was warranty left... FREE REPAIR!
EeliX7 said:
lol the people on the goddamn service centre actually thought there was warranty left... FREE REPAIR!
Click to expand...
Click to collapse
Thats cool. I got mine extended for 6 months when i relocked bootloader and no one could identify lol.
Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!
y5r43l said:
Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
Try the unlocking code again
sd_shadow said:
Try the unlocking code again
Click to expand...
Click to collapse
It won't allow. It asks to enable OEM Unlock under Settings -> Developer Options.
Thanks for the answer!
y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7.
Sent from my ali using XDA Labs
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.
pastorbob62 said:
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.
Click to expand...
Click to collapse
This was his way of knowing that, you and i, we have been here for a long time, i learned this years ago, now he knows it
Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.
y5r43l said:
Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.
Click to expand...
Click to collapse
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!
y5r43l said:
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!
Click to expand...
Click to collapse
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on
darkherman said:
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on
Click to expand...
Click to collapse
Hi, darkherman,
thank you for you reply.
Unfortunately it won't work as according to documentation: "Make sure you enabled adb debugging on your device(s)."
I have to boot the system to enable it in Developer Options.
Thanks anyway!
Is there a way to bypass the Google Wizard and boot the system without logging in?
About the warning on startup I've read somewhere that's not possible because of some var value obtained from:
Code:
fastboot getvar allCODE]
Don't remember exactly what var, but its value may be 0, 1 or 2 that means locked, unlocked and relocked (not necessarily in this order)
-- runnig the above command I saw some variables such as securestate, verity-state and iswarrantyvoid than may mean something.
But, as far as I know, we have no command such as "set-iswarrantyvoid false" or "set-verity-state 1" or something like that.
Maybe this could be done by replacing/updating the firmware if possible, but I think it doesn't worth the risk of making the device irreversibly bricked.
Thanks again for your reply.
It seem there's no way to rescue it.
Gonna just give up and throw it away.
Thanks for those who tried to help!
y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse
KtownJeff said:
y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse
Hi, thank you for your reply!
I really never have took apart a phone nor know about test point shorting so this is not an option for me. I could even try to do it but probably won't be able to mount it back.
It's a no carrier phone, but in my country, there's no so easy return policy that I know of, unfortunately.
The bypass won't work because the second pass, "Connect your Motorola Moto G7 Plus to your Wi-Fi", as I think this is the biggest problem, I cannot connect to Wi-Fi. I also tried the method suggested by @darkherman throught gnirehtet with no success.
Click to expand...
Click to collapse