Database Users

Need help please!!!!! locked out on screen! Android password!

Hey guys I have a dilemma here. My 3 year old was playing with my tablet and when I powered it back on there's a little Android Guy with a password I have to login. I tried to restore a backup but I moves files around so MD5 were mismatched. I tried flashing a rom for a fresh install and still the Android icon still wants a password. Is there any way to bypass this? A clean install should erase any password that was in the.old rom right? Need advice fellas. Thanks!

an Nflash, which would wipe out everything would take out the password, sure. It should be fine though if you backup regularly, just flash your backup over recovery.

Doesn't it make you sign in with your google account if you get the password wrong 3 times? Try that
Sent from my Transformer TF101 using xda premium

my phone makes me log in with my google account after trying the wrong password 15 times. after that you can change the password, i think it will be the same with the TF.

That is fascinating info, I had no idea. Excellent to know in case you run into something like this in the future.

Lakeshow423 said:
Hey guys I have a dilemma here. My 3 year old was playing with my tablet and when I powered it back on there's a little Android Guy with a password I have to login. I tried to restore a backup but I moves files around so MD5 were mismatched. I tried flashing a rom for a fresh install and still the Android icon still wants a password. Is there any way to bypass this? A clean install should erase any password that was in the.old rom right? Need advice fellas. Thanks!
Click to expand...
Click to collapse
Yeah, after a certain number of failed attempts you can log in via google account.
FYI if you want to do it via the flashing a rom route, it will only work if you wipe data and cache in cwm.

goodintentions said:
Yeah, after a certain number of failed attempts you can log in via google account.
FYI if you want to do it via the flashing a rom route, it will only work if you wipe data and cache in cwm.
Click to expand...
Click to collapse
That's what's crazy..I wiped data, cache and formatted system then flashed a rom and it was still there. When I get home from work I'll start inputting passwords till it asks me for a Google account login.

Lakeshow423 said:
That's what's crazy..I wiped data, cache and formatted system then flashed a rom and it was still there. When I get home from work I'll start inputting passwords till it asks me for a Google account login.
Click to expand...
Click to collapse
Can you let everyone know the outcome of this? I'd like to know if eventually I can use my google credentials (If the same thing ever happened to me).

Alright fellas I tried typing in like 100 passwords and nothing. It never asked me to login to Google account. Maybe its because I have just flashed a new rom? My 2 backups got corrupted so that's out of the question. I'm going.to try installing ARHD I might think the full superwipe might work but the link is down. If anybody has the superwipe file can you please post it. I'm new to tablets but not new to android and been reading up on NV flash. I'm hesitant though to try it. My Tablet was on the latest us update and rooted with razeeclaw one click. What do.you guys recommend? I know it's fixable cause I can still get into recovery and flash roms. Its just.that password verification shoes IP everytime, it wont even let me boot into the screen. Ill take a picture of the screen I see later. Please help lol.

I just tried this out on my transformer because I was bored.
After 5 attempts it locked me out for 30 seconds. After 5 more attempts it rebooted into recovery mode and then launched android. It had wiped all my data. Home screen layouts, apps, app data - the works.
I just restored from a CWM backup so no harm done - but this could be really annoying for someone who didn't have that option.
I'm guessing that it was the exchange server that my email account is linked to that caused the wipe.

Here is the lockscreen I'm getting whenever I load up after full wipes. I never uses the Asus lockscreen only the pattern so I don't know if this is the password default one. I'm gonna try flashing the superwipe then ARHD before I go the nvflash route. Is there a good tutorial for nvflashing? Sorry for the nooby questions but this is all new to me. Thanks!
{
"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"
}

Ok fellas...after the superwipe script and flashing ARHD it finally booted into the main screen without asking for a password! Thanks for the help guys !

Lakeshow423 said:
Ok fellas...after the superwipe script and flashing ARHD it finally booted into the main screen without asking for a password! Thanks for the help guys !
Click to expand...
Click to collapse
Nice man. I think you probably could have wiped that manually to get it working too but it never hurts to superwipe. I'm sure you know but there is a superwipe lite version too that doesn't wipe the internal sd card.
3VO Sent

Where does one acquire superwipe lite?
~ Kelly ~
"Two things are infinite: the universe and human stupidity; and I'm not sure about the universe!" -Albert Einstein
- Sent from my Transformer TF101 via Tapatalk

Was it because the filesystem was encrypted? I recently purchased a transfomer and noticed there was an option to encrypt the local filesystem and it would a require a password during bootup that is not tied to your google account.

Yeah, looks like encryption was turned on. That's why it didn't ask for a password, this is before the system boots

rykatemom said:
Where does one acquire superwipe lite?
~ Kelly ~
"Two things are infinite: the universe and human stupidity; and I'm not sure about the universe!" -Albert Einstein
- Sent from my Transformer TF101 via Tapatalk
Click to expand...
Click to collapse
One would acquire that right here.

I'm having the same issue with the same screen and keyboard minus the safe mode text. I updated to the newest version of the revolver rom, then the next day I was using the tablet it went dark then came up with the password screen. Ive tried super wipe, reflashing and restoring, nothing is working, still boots with the revolver animation and ends up at the keyboard. Help!

ifly4vamerica said:
One would acquire that right here.
Click to expand...
Click to collapse
Is that the light version that doesn't wipe to external sd card? Is there a thread for the superwipe?

I'm still stuck at the password screen, Someone has to be able to help me out, I have a B70, So I cant nvflash..

[Q] Camera Error "Cannot connect to camera " in STOCK 4.2.2

So i have a Nexus 10 running 4.2.2.
-Stock
-Non rooted
-Non unlocked
Since about a day i have been getting the error
Camera Error
" Cannot connect to the camera"
I have tried to
-Clear the cache
-Multiple reboots
-Services cache clear
None of them worked and im getting the same error and none of the onscreen camera controls work.
Help is appreciated.

??
poikilo said:
So i have a Nexus 10 running 4.2.2.
-Stock
-Non rooted
-Non unlocked
Since about a day i have been getting the error
Camera Error
" Cannot connect to the camera"
I have tried to
-Clear the cache
-Multiple reboots
-Services cache clear
None of them worked and im getting the same error and none of the onscreen camera controls work.
Help is appreciated.
Click to expand...
Click to collapse
Any advice ?

Best advice is to contact Samsung and start harassing for an RMA, sadly. It looks like hardware issue.

poikilo said:
Any advice ?
Click to expand...
Click to collapse
Factory reset? Reflash stock image?
Sent from my Nexus 4 using Tapatalk 2

Some background service is probably using your camera. It will probably show up under battery stats near the top of the list.
You can do a factory reset to verify if you are willing to lose your settings.

Update
zivan56 said:
Some background service is probably using your camera. It will probably show up under battery stats near the top of the list.
You can do a factory reset to verify if you are willing to lose your settings.
Click to expand...
Click to collapse
I havent done a factory reset yet. I will update this as soon as i do so.
I just wanted to know if there are any known fixes for this.

I used to have this problem on ICS on my Droid4. No one at the stores or online could ever seem to figure out a fix... but I did! (Yay me! Uh-huh!) Sadly, its not a silver bullet for you, because this was the fix:
-Remove the SD card, reboot the phone, access the camera (which will then work), then shut down, re-insert SD card, turn back on
You should play around with:
-USB settings, such as MTP mode and developer settings USB debug = try turning them on and off, rebooting and camera attempts in between
-File Explorer utilities that could allow you to wipe or reformat the emulated SD portion
Best of luck,
bm

I've had the camera connect error on a custom ROM/Kernel with Google Goggles. First time I've had the issue actually. Upon reboot, all was well, so it seems it was only a one-time thing.

If everything else fails you could try to open the tablet and see if the camera became disconnected from the rest of the hardware. The camera plugs into the mainboard via a tiny ribbon cable.
front camera:
{
"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"
}
rear camera:

Replies
EniGmA1987 said:
If everything else fails you could try to open the tablet and see if the camera became disconnected from the rest of the hardware. The camera plugs into the mainboard via a tiny ribbon cable.
front camera:
rear camera:
Click to expand...
Click to collapse
Im too scared to dismantle my tab. But if all else fails, i will try this and contact you. Thanks.
bigmatty said:
I used to have this problem on ICS on my Droid4. No one at the stores or online could ever seem to figure out a fix... but I did! (Yay me! Uh-huh!) Sadly, its not a silver bullet for you, because this was the fix:
-Remove the SD card, reboot the phone, access the camera (which will then work), then shut down, re-insert SD card, turn back on
You should play around with:
-USB settings, such as MTP mode and developer settings USB debug = try turning them on and off, rebooting and camera attempts in between
-File Explorer utilities that could allow you to wipe or reformat the emulated SD portion
Best of luck,
bm
Click to expand...
Click to collapse
Problem is N10 doesnt have an SD card so i get that the fix wont work for me
I do not know which File Explorer allows me to reformat the emulated SD portion WITHOUT ROOT. If you happen to know anything please let me know. Thanks.

poikilo said:
Im too scared to dismantle my tab. But if all else fails, i will try this and contact you. Thanks.
Problem is N10 doesnt have an SD card so i get that the fix wont work for me
I do not know which File Explorer allows me to reformat the emulated SD portion WITHOUT ROOT. If you happen to know anything please let me know. Thanks.
Click to expand...
Click to collapse
You may have to be in the recovery to formati t.

poikilo said:
Problem is N10 doesnt have an SD card so i get that the fix wont work for me
I do not know which File Explorer allows me to reformat the emulated SD portion WITHOUT ROOT. If you happen to know anything please let me know. Thanks.
Click to expand...
Click to collapse
Yeah, that's the catch 22. When I had the problem on my Droid4 even 'factory reset' wouldn't fix it, but the SD card pull did.
You could root your phone, then use a root utility to do some formatting, then reinstall factory everything. It would be a lot of work, but it could all be done w/out physically opening the device. But - no guarantees it will fix it. Still, if its been a few days now and the camera STILL isn't back, a lot of work in reformatting etc would be worth it.
As for what root utility/explorer would be best, I am not the best guy to answer - but I suspect TWRP can accomplish this. Vets, care to chime in?

A simple unlocking and then relocking the bootloader will also do a complete wipe of the entire tablet. Just make sure you know how to reflash the factory image through fastboot otherwise you wont have an OS.

EniGmA1987 said:
A simple unlocking and then relocking the bootloader will also do a complete wipe of the entire tablet. Just make sure you know how to reflash the factory image through fastboot otherwise you wont have an OS.
Click to expand...
Click to collapse
It will only do a factory wipe and then that must be done from the recovery, upon unlocking it. I imagine locking up the bootloader may do the same as you would no longer be able to flash an operating system with it locked.
Sent from my Nexus 10 using XDA Premium HD app

EniGmA1987 said:
A simple unlocking and then relocking the bootloader will also do a complete wipe of the entire tablet. Just make sure you know how to reflash the factory image through fastboot otherwise you wont have an OS.
Click to expand...
Click to collapse
dibblebill said:
It will only do a factory wipe and then that must be done from the recovery, upon unlocking it. I imagine locking up the bootloader may do the same as you would no longer be able to flash an operating system with it locked.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think either of these are totally correct? I thought unlocking the boot loader warns you that you will lose your stuff but doesn't actually format userdata or cache on the N10.
All data on the phone is erased, i.e. both the applications' private data and the shared data that is accessible over USB, including photos and movies. Be sure to make a backup of any precious files you have before unlocking the bootloader.
On Nexus 10, after unlocking the bootloader, the internal storage is left unformatted and must be formatted with
$ fastboot format cache
$ fastboot format userdata
http://source.android.com/source/building-devices.html
Sent from my Nexus 4 using Tapatalk 4 Beta

Major update
Major Update
I downloaded this app called " All-In-One Toolbox" and did a maintenance update by deleting all my cache, history, app files, unused data and etc. After that i did a restart and voila, the camera app started working perfectly. ( Both the front and rear cameras ).
Im so happy, now i need not reset my tab and moreover that it is not a hardware issue.
Ill keep this thread open for a while for people with similar problem to comment.

Thanks
Thanks to all over hear for their suggestions.
Hope this thread helps all those who need it.

OS command delay

Hi,
I recently bought a refurbished Nexus 7 and after creating 4 users and installing some apps on them the tablet started to act strange... e.g. when I open settings and tap any of the category it doesn't open... I need to press back and wait 30 sec or more. The same happens with Google Play when I tap install. Also with all other apps (EXCEPT games). Note: The tablet isn't laggy. I don't know what to do Please help
Sent from my Nexus 7 using xda app-developers app

Up.
Please help !!!!! :crying: This thing is getting worse

Try wiping cache. In recovery preferably.

Okay. And that will erase the temporary files and cache files NOT user data, correct? :fingers-crossed:

You've tried rebooting?
Sent from my Nexus 7 using Tapatalk HD

Yes. The same thing happens. I tried to enter recovery mode to erase the cache but i got the message "no command" and the green Android laying on its back with a red triangle over it. Any opinions?
BTW, on boot a white open padlock appears. That means is rooted? I also installed Root Checker and said that i don't have root acces. If it's rooted then can I unroot? (bcz i'm thinking of a warranty replacement)

The open lock means the boot loader has been unlocked. You still need to install super user, there's instructions posted search for it. Recovery wasn't installed properly. I missed a step my first time and had the same dead android, again is posted in the instructions on rooting and installing cwm.
http://forum.xda-developers.com/showthread.php?t=2150661
Sent from my Nexus 7 using Tapatalk 4 Beta

It probably means recovery wasn't installed at all.

SlowCobra96 said:
The open lock means the boot loader has been unlocked. You still need to install super user, there's instructions posted search for it. Recovery wasn't installed properly. I missed a step my first time and had the same dead android, again is posted in the instructions on rooting and installing cwm.
http://forum.xda-developers.com/showthread.php?t=2150661
Click to expand...
Click to collapse
Umm, ok.. But, I don't need CMW and Root on my N7. So, there is a way to come back to the original, pure JB 4.2.2 ? To be like a brand new unit? (with NO mods at all)

If you want it completely stock like factory new there is a thread sticky on how to do that as well.
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using Tapatalk 4 Beta

Thanks! And what about the recovery mode/'no command' error? ---- The link you gave me will solve this problem as well?
Sorry for n00b questions

bv31top said:
Thanks! And what about the recovery mode/'no command' error? ---- The link you gave me will solve this problem as well?
Sorry for n00b questions
Click to expand...
Click to collapse
The problem is that it appears there is no recovery installed thus the no command error. So you need to start with using the knowledge from the first thread I posted to get a recovery installed. From there you can try to wipe cache and dalvik cache then fix permissions. Or just follow the second thread to start completely fresh with a new install of jb 4.2.2.
EDIT: here is a guide for using adb and fast boot. http://forum.xda-developers.com/showthread.php?t=2225405
Sent from my Nexus 7 using Tapatalk 4 Beta

bv31top said:
Umm, ok.. But, I don't need CMW and Root on my N7. So, there is a way to come back to the original, pure JB 4.2.2 ? To be like a brand new unit? (with NO mods at all)
Click to expand...
Click to collapse
Gonna lag for sure then.
Rooting's best side effect is being able to tweak and streamline your device to make it as zippy as possible. Never will be as smooth running unrooted stock with no tweaks.
Sent from my SGH-T989D using xda app-developers app

I did a factory reset and now I made two users and installed around 5 apps. Now it's ok (no more delay). I think the problem is that the RAM/CPU becomes very slow with 4 users and many apps on them. I can only hope 4.3 will be better in managing multi-user devices. Anyway, the open padlock is still there.
Or just follow the second thread to start completely fresh with a new install of jb 4.2.2.
Click to expand...
Click to collapse
So, a fresh install with the method you gave me in the 2nd link can fix recovery mode (no command) and lock the bootloader?
Yes or No?

bv31top said:
I did a factory reset and now I made two users and installed around 5 apps. Now it's ok (no more delay). I think the problem is that the RAM/CPU becomes very slow with 4 users and many apps on them. I can only hope 4.3 will be better in managing multi-user devices. Anyway, the open padlock is still there.
So, a fresh install with the method you gave me in the 2nd link can fix recovery mode (no command) and lock the bootloader?
Yes or No?
Click to expand...
Click to collapse
Highly recommend you look into MultiROM. Like having multiple operating systems on a PC, you can install how ever many ROMs you want on your device that you will be able to pick which to boot from. There is less lag running different ROMs on there then stock 4.2.2.
{
"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"
}

Username invalid said:
Highly recommend you look into MultiROM. Like having multiple operating systems on a PC, you can install how ever many ROMs you want on your device that you will be able to pick which to boot from. There is less lag running different ROMs on there then stock 4.2.2.
Click to expand...
Click to collapse
Interesting...But, I'm not interested in setting up multiple OSs on my N7. At least not now.
Thanks, anyway.

bv31top said:
Interesting...But, I'm not interested in setting up multiple OSs on my N7. At least not now.
Thanks, anyway.
Click to expand...
Click to collapse
Why do you prefer to have 4 accounts on 1 ROM? Especially when it is causing you increasingly more trouble? And I am doubtful 4.3 would be a significantly better at "multi-usering".

Username invalid said:
Why do you prefer to have 4 accounts on 1 ROM? Especially when it is causing you increasingly more trouble? And I am doubtful 4.3 would be a significantly better at "multi-usering".
Click to expand...
Click to collapse
Just hoping U know... I know that it's 90% sure that will run ultra-smooth and problem-free, but I don't want to mess around with rooting, ROMs etc.
Now I'm waiting for @SlowCobra96 to respond to my question cuz his explanation was kinda odd.
One more question: When I tried to clear cache (from the UI because the recovery is f***ed up) I ended up with ~500MB cache from 600MB
Did anybody experience this problem?

bv31top said:
Just hoping U know... I know that it's 90% sure that will run ultra-smooth and problem-free, but I don't want to mess around with rooting, ROMs etc.
Now I'm waiting for @SlowCobra96 to respond to my question cuz his explanation was kinda odd.
One more question: When I tried to clear cache (from the UI because the recovery is f***ed up) I ended up with ~500MB cache from 600MB
Did anybody experience this problem?
Click to expand...
Click to collapse
Read the links I included they tell you what they do and how to do it. One is to install cwm and then a new rom if you so choose the other is to make the tablet like the day it came out of the box.
Sent from my Nexus 7 using Tapatalk 4 Beta

SlowCobra96 said:
Read the links I included they tell you what they do and how to do it. One is to install cwm and then a new rom if you so choose the other is to make the tablet like the day it came out of the box.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok... I think I will give it a try with the 2nd link.
And the cache problem?

[Q] Odin Flash Failure - Advice Please

I've tried to flash my GT-I9505 using Odin and it's failed (please see screen grab below).
I used "I9505XXUBMH1-PRE-ROOTED-ODEX-FULL" from post 5 of this thread
Code:
http://forum.xda-developers.com/showthread.php?t=2250824
{
"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"
}
A few weeks ago, I tried "I9505XXUBMGA-PRE-ROOTED-ODEX-FULL" from the same thread and that failed and locked up my phone.
Which I had to pay to get the phone re-flashed properly.
(I've used the above successfully in the past).
Now, I'm in the same position again with a failed flash and probably paying to have it fixed again.
On the phone itself, the progress bar is only 2mm long. So if I switch it off, it will probably mess everything up.
What should I do now, while it's still connected to the PC and how can I successfully flash it in the future ?
Thank you.

What firmware's currently on the phone ?

MistahBungle said:
What firmware's currently on the phone ?
Click to expand...
Click to collapse
It's 4.2.2.
I've managed to get the phone "working" again, by using "I9505XXUAME2-PRE-ROOTED-KNOX".
Which is on the same thread.
But, since I got the phone working again, I can't get WiFi to switch on. Factory reseting via Settings doesn't fix it.
All the ROMs I downloading in the past (MF8, MGA and MH1) with "ODEX" in the title from the same thread don't work.
Odin (any version), says "Not Responding" when I try them and fails to update (using Win 8.1).

0-0-0 said:
It's 4.2.2.
I've managed to get the phone "working" again, by using "I9505XXUAME2-PRE-ROOTED-KNOX".
Which is on the same thread.
But, since I got the phone working again, I can't get WiFi to switch on. Factory reseting via Settings doesn't fix it.
All the ROMs I downloading in the past (MF8, MGA and MH1) with "ODEX" in the title from the same thread don't work.
Odin (any version), says "Not Responding" when I try them and fails to update (using Win 8.1).
Click to expand...
Click to collapse
Try clearing data , cache and dalvik cache from cwm and do a factory reset in cwm
sent from my GT-I9082 using xda app-developers app

asifcheer said:
Try clearing data , cache and dalvik cache from cwm and do a factory reset in cwm
sent from my GT-I9082 using xda app-developers app
Click to expand...
Click to collapse
Sorry, but I've no idea what you're talking about.
Simple instructions, please.
If it's for post 3: If it's the same as powering off the phone and starting it with Vol. up, Home and Power keys and resetting it that way.
That didn't for resetting the phone and the WiFi problem.
If it's for post 1, please ignore.

0-0-0 said:
Sorry, but I've no idea what you're talking about.
Simple instructions, please.
If it's for post 3: If it's the same as powering off the phone and starting it with Vol. up, Home and Power keys and resetting it that way.
That didn't for resetting the phone and the WiFi problem.
If it's for post 1, please ignore.
Click to expand...
Click to collapse
Edit:
Just to update.
I've lost all sound and I can't play any music or videos, even the Samsung material.

have u flashed a custom-recovery like cwm, Philz or TWRP?
If "clearing data , cache and dalvik cache" are new for you, plz read more about this all.

btmz said:
have u flashed a custom-recovery like cwm, Philz or TWRP?
If "clearing data , cache and dalvik cache" are new for you, plz read more about this all.
Click to expand...
Click to collapse
Thanks for the reply.
CWM
I've deleted the cache partition and wipe data/factory rest.
I can't find the "dalvik cache", I've seen a YT video about it, but it's in "advanced settings", which I don't have.
I'm rooted , SuperSU is installed.

delvik cache is under advance option of philz recovery
AND DO INSTALL THE LATEST PHILZ RECOVERY V 6.0.0.1

Clearing cache/Dalvik ain't going to fix your problem. Your sound/WiFi is busted due to that bootloader issue. You need to flash a 'WiFi fix' (non-HLOS modem) to match your current firmware/bootloader. Go to the modem thread (search; easily found) & find a non-HLOS modem to match your current firmware (and I don't mean 4.2.2 or whatever, I mean XXUA, etc, etc)

Thank you for the replies and help.
This is the WiFi Fix page http://d-h.st/users/DjeMBeY/?fld_id=16262#files
But, my current FW isn't listed (ME2), I've tried ME3 and MEA, I think those are the ones before and after ME2 (maybe wrong).
But, they don't work. I've tried them multiple times.
I'm not sure which others to try.
I'm going to pay and hopefully get it fixed today.
But, I'd still like to know how to fix it, for future use.
It will mess up again, when I root it. That is unless I just stick with "I9505XXUAME2-PRE-ROOTED-KNOX" and not try later updated ROMs which have worked in the past).

0-0-0 said:
0-0-0 said:
I've tried to flash my GT-I9505 using Odin and it's failed (please see screen grab below).
I used "I9505XXUBMH1-PRE-ROOTED-ODEX-FULL" from post 5 of this thread
Code:
http://forum.xda-developers.com/showthread.php?t=2250824
A few weeks ago, I tried "I9505XXUBMGA-PRE-ROOTED-ODEX-FULL" from the same thread and that failed and locked up my phone.
Which I had to pay to get the phone re-flashed properly.
(I've used the above successfully in the past).
Now, I'm in the same position again with a failed flash and probably paying to have it fixed again.
On the phone itself, the progress bar is only 2mm long. So if I switch it off, it will probably mess everything up.
What should I do now, while it's still connected to the PC and how can I successfully flash it in the future ?
Thank you.
Click to expand...
Click to collapse
Maybe this helps ya: HERE
Click to expand...
Click to collapse

Joku1981 said:
0-0-0 said:
Maybe this helps ya: HERE
Click to expand...
Click to collapse
Thank you.
My phone is currently at the shop, waiting to be fixed.
But, I'll try those.
Click to expand...
Click to collapse

0-0-0 said:
Joku1981 said:
Thank you.
My phone is currently at the shop, waiting to be fixed.
But, I'll try those.
Click to expand...
Click to collapse
pla report whats happend.
Click to expand...
Click to collapse

btmz said:
0-0-0 said:
pla report whats happend.
Click to expand...
Click to collapse
I'm due to collect the phone tomorrow, I received info from them today (Geek Squad at Carphone Warehouse, a company based in the UK), saying that it had been fixed.
I'm guessing they reflashed it. But no info was given on what they did.
After I get it back, I think I'll get rid of it and get a HTC One instead.
Using a custom pre rooted ROM, just seems to mess the phone up.
Hopefully there's another way for the HTC. Plus, I shouldn't need to worry about Knox.
Click to expand...
Click to collapse

http://forum.xda-developers.com/showpost.php?p=40778466&postcount=4
Download and flash modem for old bootloader and everything will be back to normal
Sent from my GT-I9505 using XDA Premium 4 mobile app

lazybeard said:
http://forum.xda-developers.com/showpost.php?p=40778466&postcount=4
Download and flash modem for old bootloader and everything will be back to normal
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you.

Rooted V20 with Google Assistant with seemingly obvious flaw

I looked but apparently no one is talking about this, unless, I overlooked it, or I'm just the ONLY one it 'affected.' Also, apology's if i posted in the wrong area. Will move if needed.
When I heard about the Google assistant I was interested in it. I wanted to mess with it. But obviously to officially get it you need, well, a Pixel. That's when I heard that rooted phones could get it with minor edits of the build.prop file. I rooted my (Verizon) V20 a few days ago (big thanks to @me2151 and his team).
So, for those of you who don't already know, all you have to do is change your model name in the build prop to a 'Pixel XL' and another line that actually adds the assistant, reboot clear 'Google' data, then press and hold home button to set it up.
I did it and it works. Simple.
Done little testing. But it works. Until, I noticed that all my SD card data was not officially accessible through the OS. Like the system doesn't see it, but it knows it's there, after checking with root explorers.
The 'problem' itself is pretty obvious. As stated in the title. So, that proposes the question. Is there a fix to where you can have both? Obviously, the SD wins over the Assistant. But having both would awesome.
Thanks guys! :good:

Ill be 100% honest. I haven't tried Google assistant. Im not sure if it would break anything or not. Ill set it up on my device and see how it goes. Do you have a link to a "Guide"?

I have Google assistant, and no issues with SD card that I've noticed.
Note: I'm on at&t. And used Pixel in the build prop instead of Pixel XL. Just for note sake
.
Sent from my Pixel using Tapatalk

Both are working fine for me. I'm not sure why one would affect the other. Did you lose access to your SD card when you installed assistant?
Sent from my Pixel using XDA-Developers mobile app

me2151 said:
Ill be 100% honest. I haven't tried Google assistant. Im not sure if it would break anything or not. Ill set it up on my device and see how it goes. Do you have a link to a "Guide"?
Click to expand...
Click to collapse
I can just tell you, go to your root of your device in a root manager. I made a back up of the build prop just in case.
-Travel from there, to /system/build.prop view as a text.
-Look for ro.product.model=* your device model * Mine was in the first 50-100lines or it could be towards the bottom.
-edit it to look like * ro.product.model=Pixel XL *
-then go all the way to the bottom, add a new line and add this * ro.opa.eligible_device=true *
-Save, then reboot
You can use my post for the rest of the instructions if needed lol
But, Ill pm you a link to the guide i used, it wont let me post it here.
Oh! "Ok, Google" works as well!

anaarkey said:
Both are working fine for me. I'm not sure why one would affect the other. Did you lose access to your SD card when you installed assistant?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. Well, mostly. When I go to storage in my device settings it just shows me my internal storage. *Just tested* its even gone when i plug it in my computer, again, just internal storage. But i can use my sdcard via root managers.

me2151 said:
Ill be 100% honest. I haven't tried Google assistant. Im not sure if it would break anything or not. Ill set it up on my device and see how it goes. Do you have a link to a "Guide"?
Click to expand...
Click to collapse
Okay. New problem. Whenever i discovered my sdcard wasnt usable, i put the original build.prop back, but then backed up the modded one. With some thought, i put back the modded one, to try a reboot to see if that would fix anything. But now its just sitting at the LG screen, i pulled the battery and tired again, same result, at reply of this post, its still sitting at LG boot screen. Its be 10-15ish minutes. Great.

My sdcard is visible and everything works fine. I used google assistant - root from the market.
Edit: tapatalk posted me using a pixel xl. Lol.
Sent from my Pixel XL using Tapatalk

leyvatron said:
My sdcard is visible and everything works fine. I used google assistant - root from the market.
Edit: tapatalk posted me using a pixel xl. Lol.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Well, now i have another problem as stated above, I tired replacing the buildprop with the original, changed my mind put the modded google assistant one back, tired to reboot to see if it would restore my sd card, instead i got stuck a the LG boot screen, and its not letting me boot into recovery manually, like its not working, i can boot into recovery from in inside the OS, but obviously that in lies a problem lol
Guess im stuck...

nightra88 said:
Well, now i have another problem as stated above, I tired replacing the buildprop with the original, changed my mind put the modded google assistant one back, tired to reboot to see if it would restore my sd card, instead i got stuck a the LG boot screen, and its not letting me boot into recovery manually, like its not working, i can boot into recovery from in inside the OS, but obviously that in lies a problem lol
Guess im stuck...
Click to expand...
Click to collapse
You TRIED replacing the build prop? Meaning you weren't so sure how to return it back?
I wonder why your phone is acting up... Pull battery and remove sdcard, and restore build prop correctly. Reboot.
Download the app I mentioned and let it do all the work. It also has a restore feature. Hopefully that fixes your sdcard issue.
Use flashify from the market to boot into recovery. I also have a hard time getting to recovery manually.

leyvatron said:
You TRIED replacing the build prop? Meaning you weren't so sure how to return it back?
I wonder why your phone is acting up... Pull battery and remove sdcard, and restore build prop correctly. Reboot.
Download the app I mentioned and let it do all the work. It also has a restore feature. Hopefully that fixes your sdcard issue.
Use flashify from the market to boot into recovery. I also have a hard time getting to recovery manually.
Click to expand...
Click to collapse
Before I edited the build.prop I backed it up. Then I went back to it, edited it manually, saved and rebooted and it worked minus the SD card issue. So. Until I got some responses I put back the original build prop, then I thought, after I already added the original back. Why not just reboot again and see if that works? When I put back the original build prop, I backed up the modded one. So, I put back the modded one. Rebooted got stuck at the LG logo. Pulled battery restart, same result. After fighting it for a few tires, I got into recovery, and restored a back up. Booted up. Got the app, used it, rebooted, booted up, cleaned Google, held down the home button, no assistant only Google now.
Rebooted again. And same result. Maybe I'm not meant to have it lol

nightra88 said:
Before I edited the build.prop I backed it up. Then I went back to it, edited it manually, saved and rebooted and it worked minus the SD card issue. So. Until I got some responses I put back the original build prop, then I thought, after I already added the original back. Why not just reboot again and see if that works? When I put back the original build prop, I backed up the modded one. So, I put back the modded one. Rebooted got stuck at the LG logo. Pulled battery restart, same result. After fighting it for a few tires, I got into recovery, and restored a back up. Booted up. Got the app, used it, rebooted, booted up, cleaned Google, held down the home button, no assistant only Google now.
Rebooted again. And same result. Maybe I'm not meant to have it lol
Click to expand...
Click to collapse
Lol. Same thing happened to me. I had to do it twice. Erase both even though it shows 0 mb. Then go into your Google search icon and it should start up.

leyvatron said:
Lol. Same thing happened to me. I had to do it twice. Erase both even though it shows 0 mb. Then go into your Google search icon and it should start up.
Click to expand...
Click to collapse
I must be doing SOMETHING wrong. I just reapplied the stock build, cleared google data, rebooted, used the 'get assistant', it claimed to have been successful, rebooted, CLEARED DATA AGAIN. Went to home screen pressed home button. And Google now. Reapplied the mod through the app, without a reboot on stock, rebooted again. Cleared data, bam. Google now. I even checked the build.prop to make sure. And it was right! Why did it work last time, but not now? Am I honestly not meant to have nice things lol :crying:

nightra88 said:
I must be doing SOMETHING wrong. I just reapplied the stock build, cleared google data, rebooted, used the 'get assistant', it claimed to have been successful, rebooted, CLEARED DATA AGAIN. Went to home screen pressed home button. And Google now. Reapplied the mod through the app, without a reboot on stock, rebooted again. Cleared data, bam. Google now. I even checked the build.prop to make sure. And it was right! Why did it work last time, but not now? Am I honestly not meant to have nice things lol :crying:
Click to expand...
Click to collapse
Technically, it starts off as Google now then it goes into an assistant prompt. All I can say is keep trying. I tried twice before getting it.

leyvatron said:
Technically, it starts off as Google now then it goes into an assistant prompt. All I can say is keep trying. I tried twice before getting it.
Click to expand...
Click to collapse
Just making sure I understand you correctly.
You're saying that I should just keep it as it, with a modded build prop, then it should turn into Google assistant? Sorry I don't mean to be so much trouble lol

nightra88 said:
Just making sure I understand you correctly.
You're saying that I should just keep it as it, with a modded build prop, then it should turn into Google assistant? Sorry I don't mean to be so much trouble lol
Click to expand...
Click to collapse
{
"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"
}
Thats how my google assistant looks like. It should look like that but with more voice options.
I'm keeping my phone with the modded build prop. I don't see any harm in that unless I can't download some apps from the play store.
Pretty much your google now is your google assistant.
Look at my tapatalk sig.
Sent from my Pixel XL using Tapatalk

leyvatron said:


Thats how my google assistant looks like. It should look like that but with more voice options.
I'm keeping my phone with the modded build prop. I don't see any harm in that unless I can't download some apps from the play store.
Look at my tapatalk sig.
Click to expand...
Click to collapse
Well that's just the thing, before I had to restore I had it. Legit user interface and all. So I don't understand why it would change now. I appreciate all your help.

nightra88 said:
Well that's just the thing, before I had to restore I had it. Legit user interface and all. So I don't understand why it would change now. I appreciate all your help.
Click to expand...
Click to collapse
This is the interface I get when I say "ok google"
Sent from my Pixel XL using Tapatalk

leyvatron said:
This is the interface I get when I say "ok google"
Click to expand...
Click to collapse
Yep. I'm definitely not getting that lol

nightra88 said:
Yep. I'm definitely not getting that lol
Click to expand...
Click to collapse
Lol.
Maybe try restoring and try again.
Sent from my Pixel XL using Tapatalk