Related
Im getting this error and force close on one of my Heros when I try installing any of my apps on any of the 2.1 roms. Im coming from Fresh 1.1 and following the same procedure I used on my other Hero on which the market is fully functional. Ive wiped everything over and over and cleared data on anything that looked like it at to do with the market. I also tried fix apk mismatches from recovery. Short of RUU which Id like to avoid if at all possible Ive tried everything else I can think of. In searching I have come across this error code on other android phones, but nothing on the hero and nothing specific to trying to install apps. So has anyone else seen this? And would RUU do anything a full data wipe didnt already?
Reading instructions has its benefits grasshopper...
Download the latest recovery and throw it onto your SD Card, boot into the old version of recovery and flash the new recovery as a .zip update, reboot into recovery again and then wipe your phone again, then install android 2.1, don't reboot yet, make sure your rom either has it's own custom kernal or download one for 2.1 and flash it, open up adb and clear dalvik cache and boot cache, then reboot your phone and you should load without any problems.
Thanks. But I did that from the get go. Aside from flashing a kernal, but Im running Darchtrev2 on the fully functional Hero that I mentioned and thats got a custum kernal built into the rom. So thats what I started with on the second one using the exact same process without success. Does wiping from adb do more than wiping from recovery? Thats one other thing I didnt do after the initial install.... But do understand you correctly that you have seen this specific error before?
Just bumpin the tread in hopes of finding a solution. I dont even mind gettin flamed for asking a stupid question if I could get linked up with a fix! lol I see its getting views, just no ideas I guess... It sucks cuz everything else works fine except the market. I get the list of my downloads, when I tap on one to install I the download button instead of the install button, so Ill tap on it and I get get the progress bar saying its downloading. When it gets to 100% I get the error and force close... Anyone?
I would try wiping again then flashing fresh 1.1 see if that boots and everything works ok then I would redownload the recovery and flash that still running fresh then reboot make sure everyhting is cool, then redownload whatever 2.1 rom you want and wipe and flash.
doing this serves 2 purposes
1. make sure that somewhere along the line none of the files corupted
2. if you still have the same problem then it will let you know where the problem is coming from.
just process of elimination
if you still have problems after that then I would say RUU, yes it is different than just wiping from recovery as it restores a completely stock image and gets rid of everything else. all a data wipe really does is get rid of user data.
just my opinion.
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Thanks for the reply and for giving me something different to try. I hadnt thought about trying that. Frustration I guess! It makes sense though. Ill give it shot. Thanks!
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Yeah, Ive been thinking about RUU'n too just to see if making a fresh start would make any difference, but after all the time I spent getting the one Hero working like I want on 2.1 and the troubles Ive had with the second and what Ive read about people bricking trying to RUU or flash recovery Ive been kinda hesitant....
willy900wonka said:
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Click to expand...
Click to collapse
Thanks. I dont know that Im quite that knowledgable though. Im sure I could read a logcat... understanding what the hell I would be reading is something else again. Saving the url though in case I need to dig deeper. Thanks for the reply.
wtphoto said:
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Click to expand...
Click to collapse
Sometimes it's just fun to RUU and do everything again
Alright if you're still having problems then just follow these steps:
Boot into recovery and make a nandroid back up just in case something goes wrong.
Download the latest version of your current 2.1 rom and reflash it from Recovery.
Open up adb and mount the /data directory (adb shell, mount /data)
Enter the following two commands in adb: rm -r /data/boot-cache , rm -r /data/dalvik-cache
Go Back to ADB and type the following commands: cd /data/data/com.android.vending , rm -R cache
Fix UID Mismatches using the tool in Recovery and then reboot your phone
regaw_leinad said:
Sometimes it's just fun to RUU and do everything again
Click to expand...
Click to collapse
or NOT!
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
You should have updated to the latest ruu...
wcgbmd said:
You should have updated to the latest ruu...
Click to expand...
Click to collapse
The latest RUU? I used the 1.56..... I did get it working tho. Flashed the mms. fix zip. Just wasn't expecting to have to as I didn't with my other hero. Don't know what the difference is between the two devices. Both are google branded, but the second one fought me every step of the way.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
First, sorry for the bump.
I just started getting this error and wanted to know if you figured out exactly what it was so I didn't have to go through that whole RUUing process. Thanks.
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
You're the bomb. That worked like a charm.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
Cant believe nobody wrote this first
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
I was having the same problem on DC a couple days ago and that fixed it for me. I was reading this thread wondering why no one had mentioned it yet.
has stopped unexpedectly.
i was messing around with switching the ROMS and when i rebooted, it said this.
i have no home screen, and it keeps popping up but i can still recieve phone calls and texts
anyone have any idea of what to do?
i can't seem to go into recovery mode either..
pacDiesel said:
has stopped unexpedectly.
i was messing around with switching the ROMS and when i rebooted, it said this.
i have no home screen, and it keeps popping up but i can still recieve phone calls and texts
anyone have any idea of what to do?
i can't seem to go into recovery mode either..
Click to expand...
Click to collapse
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up many apps. Also if you switched radio/spl did you run fastboot erase system -w afterwards?
This exception should not be related to the recoveryconsole
easiest is just to wipe everything and reflash, dont forget ext. if youve used it.
If recovery is for some reason unaccesable you can reflash via flash_image() when the phone has booted android.
Also do a logcat
Mod. edit: not dev related, moved to general
ivarson_swe said:
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up many apps. Also if you switched radio/spl did you run fastboot erase system -w afterwards?
This exception should not be related to the recoveryconsole
easiest is just to wipe everything and reflash, dont forget ext. if youve used it.
If recovery is for some reason unaccesable you can reflash via flash_image() when the phone has booted android.
Also do a logcat
Click to expand...
Click to collapse
Yeah bro, I have no idea what you just said.
lol
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up m
Click to expand...
Click to collapse
Yeah bro, I have no idea what you just said.
lol
Click to expand...
Click to collapse
Which rom were you using and which rom are you using now. Did you change your radio or spl before installing this rom.
Load up into recovery and run fix uid mismatches. Reboot and see if that helps.
Does your app launcher work? If so run terminal emulator. Type in su and then enter
Type in fix_permissions and then enter. Let the script run.
Type I'm exit then enter
Type in exit and then enter again. Terminal will close. Reboot phone. If you cannot get to terminal emulator then run it from adb ( if possible )
And the other poster was referring to when you change radios there are a few commands. He wanted to make sure you ran them all
-------------------------------------
Sent via the XDA Tapatalk App
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
fykick said:
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
Is it safe to say you didnt do nandroid restore prior?
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
fykick said:
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
Click to expand...
Click to collapse
When I get home in an hour, I'll factory wipe and make a backup of the stock rom for you.
Any recommendations on where to upload?
I got you man im backing up right ow....going to wipe then backup again and ill upload it so give me a bit
maybe ill be really nice and include some custom transitions for you
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
nandroid
pm'ing you the link
let me know if it works
mount usb storage copy and paste the into clockworkmod/backups
unmount usb storage and restore....gave you all the goodies too
nxt said:
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
Click to expand...
Click to collapse
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
Click to expand...
Click to collapse
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
wdfowty said:
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
Click to expand...
Click to collapse
Now that is a frightening prospect;( How can google make a dev phone thats super brickable... hmmm
JD
AndHel said:
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
Click to expand...
Click to collapse
Can I get the link for the stock nandroid also? I need to use a secure boot image.
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
OKay
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
drexman8244 said:
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
Click to expand...
Click to collapse
maybe you can upload it to mediafire or somewhere else, and create a thread? it might help others out
ill take your advice on that Thanks
adb push may not have been working because your system wasn't mounted properly in Clockwork recovery. I had this issue when trying to root. In Recovery, go to Mounts & Storage and hit "Mount System" THEN adb push the system dump.
You probably didn't need to nandroid. Could have just used adb to reset the density line in your build.prop I assume?
fykick said:
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
Click to expand...
Click to collapse
Please mention it on the Thread Title PROBLEM SOLVED.
An nandroid backup can be found here http://forum.xda-developers.com/showthread.php?t=877601
Hi guys, i'm the developer of LCD Density Changer. Sorry about the problems it caused.
Is it true that the Nexus S, doesn't support a density change. That would be a real bummer! Not for the app, but in general. I just don't hope Google blocks a density change in their new Android versions.
A question: does the "preview/temporarily" density change works in the LCD Density Changer app. If so, there is still hope.
Meanwhile, based on these reports I will put up a note to warn Nexus S users.
Howdi Folks,
Anybody fancy cooking a TWRP flashable ROM for stock LG G4 from Source... Kinda buggered mine, cant change the DPI back... LG Keyboard crashes along with a load of other apps xd....
fkofilee said:
Howdi Folks,
Anybody fancy cooking a TWRP flashable ROM for stock LG G4 from Source... Kinda buggered mine, cant change the DPI back... LG Keyboard crashes along with a load of other apps xd....
Click to expand...
Click to collapse
Have you tried changing it back over ADB? Or maybe while in recovery?
hendusoone said:
Have you tried changing it back over ADB? Or maybe while in recovery?
Click to expand...
Click to collapse
Unfortunately the device has been fact reset by accident, however the DPI remains as is, USB Debugging isnt available
Trying to go through TWRP, but i cant get it to boot into recovery
fkofilee said:
Unfortunately the device has been fact reset by accident, however the DPI remains as is, USB Debugging isnt available
Trying to go through TWRP, but i cant get it to boot into recovery
Click to expand...
Click to collapse
Ooh, that's rough. I got into the stock recovery by doing this:
http://forum.xda-developers.com/g4/help/how-boot-stock-recovery-t3123751
barcodelinux said:
1. Power off
2. Press and hold the Vol - and Power button until the LG boot screen appears.
3. Release the Power button ONLY. Do not release the Vol - button.
4. After 1 second, press and hold the power button again. You should see the white recovery screen.
Use the Vol+/- to navigate and Power to select.
Click to expand...
Click to collapse
That might get you into TWRP.
hendusoone said:
Ooh, that's rough. I got into the stock recovery by doing this:
http://forum.xda-developers.com/g4/help/how-boot-stock-recovery-t3123751That might get you into TWRP.
Click to expand...
Click to collapse
Im currently in TWRP, but adb sideload isnt working and after mounting \System i still cant write to it... lol... Im thinking of going down the line of a Flashable build.prop
fkofilee said:
Im currently in TWRP, but adb sideload isnt working and after mounting \System i still cant write to it... lol... Im thinking of going down the line of a Flashable build.prop
Click to expand...
Click to collapse
Huh, /system should be remountable as rw. The command should be something like this:
adb shell
mount -o remount,rw /system
Once you do that, you should be able to adb pull your build.prop, edit it, then adb push the fixed version.
fkofilee said:
Im currently in TWRP, but adb sideload isnt working and after mounting \System i still cant write to it... lol... Im thinking of going down the line of a Flashable build.prop
Click to expand...
Click to collapse
I got system to mount rw by going into TWRP with it connected via usb doing
adb shell
mount /system/
you should now be able to write to system
Nope... Win 8.1 and 7 both having issues. Can I ask a favour, can someone create me a Flashable Build.prop?
fkofilee said:
Nope... Win 8.1 and 7 both having issues. Can I ask a favour, can someone create me a Flashable Build.prop?
Click to expand...
Click to collapse
Here u go
Dude you are lege!!!!
fkofilee said:
Dude you are lege!!!!
Click to expand...
Click to collapse
Opps, use this. Other was for 560DPI
Arh it didnt work, i think it was the first zip that i flash that i created myself, Think it might have broken the Firmware xd
I have a working recovery so its not a complete loss, Ill just wait until the release the appropriate firmware files or a custom ROM ;p
Unless you have any other ideas ... But beyond that, think there isnt much else I can do
fkofilee said:
Arh it didnt work, i think it was the first zip that i flash that i created myself, Think it might have broken the Firmware xd
I have a working recovery so its not a complete loss, Ill just wait until the release the appropriate firmware files or a custom ROM ;p
Unless you have any other ideas ... But beyond that, think there isnt much else I can do
Click to expand...
Click to collapse
I can make an slim rom from the system i have available, should run. Hopefully .
DocRambone said:
I can make an slim rom from the system i have available, should run. Hopefully .
Click to expand...
Click to collapse
Are you sure sure sure? , If pos that would be awesome. Slim would be great
fkofilee said:
Are you sure sure sure? , If pos that would be awesome. Slim would be great
Click to expand...
Click to collapse
It have to wait until tomorrow tho.
Did you check the TWRP backup you made?
There should be an system.image , approx 4 GB in size. Can you restore that?
DocRambone said:
It have to wait until tomorrow tho.
Did you check the TWRP backup you made?
There should be an system.image , approx 4 GB in size. Can you restore that?
Click to expand...
Click to collapse
What... Is... this... Backup.... Thing....?
No sadly i didnt do one before changing the DPI in the build prop. To be fair I was at work so too many things going on... Normally I do
Tomorrow is awesome, If you want to that is
I have my note 4, Works a treat. For the mean time im not so bother about it. I can get the ROM on via MTP through recovery so not really an issue
Thanks for the help.
Can't get rid of the Unfortunately Google Play Services has stopped notification, Play Store isn't working anymore, tried "everything" (removing updates, removing Google account, downloading fresh Play and Services, etc.(no factory reset yet though) (factory reset done and now in bootloop mode)) so a flashable system zip would be awesome! :good:
Solved :good:
I am stuck on the 'Phone is starting...' screen. This is how I landed here
1. Added Finger Print Customizations when the phone was working and they did work as expected.
2. Noticed update from 9.0.10 to 9.0.10
3. Flashed stock 9.0.10 image over Bluespark and Magisk rooted image
4. Flashing stock 9.0.10 caused getting stuck in the 'Phone is starting...' screen
5. I can hear my phone ringing on this screen, but I cannot answer any calls since the phone is stuck forever on this screen
6. I tried flashing bluespark and magisk in the hopes of being able to boot, but that just cases my old boot screen to show up and then going back to restarting in a loop again
I believe OPSystemUI.apk (file that I replaced under /system/priv-app for getting custom finger print animation) is causing the issue. I do not know how to restore the stock version of this file without wiping all my data clean. I am not sure if this is the file causing the issue. Is there any way to get the phone started by flashing some files via adb?
Appreciate the inputs in advance.
pramathesh said:
I am stuck on the 'Phone is starting...' screen. This is how I landed here
1. Added Finger Print Customizations when the phone was working and they did work as expected.
2. Noticed update from 9.0.10 to 9.0.10
3. Flashed stock 9.0.10 image over Bluespark and Magisk rooted image
4. Flashing stock 9.0.10 caused getting stuck in the 'Phone is starting...' screen
5. I can hear my phone ringing on this screen, but I cannot answer any calls since the phone is stuck forever on this screen
6. I tried flashing bluespark and magisk in the hopes of being able to boot, but that just cases my old boot screen to show up and then going back to restarting in a loop again
I believe OPSystemUI.apk (file that I replaced under /system/priv-app for getting custom finger print animation) is causing the issue. I do not know how to restore the stock version of this file without wiping all my data clean. I am not sure if this is the file causing the issue. Is there any way to get the phone started by flashing some files via adb?
Appreciate the inputs in advance.
Click to expand...
Click to collapse
You don't have launcher installed.
Just sideload any launcher apk using advanced and you should be good..
indian84 said:
You don't have launcher installed.
Just sideload any launcher aok using advanced and you should be good..
Click to expand...
Click to collapse
Are you sure? Before messing it up with stock boot image I had nova running for me and had also kept one plus stock installed. Not sure how I can side load a launcher. Any pointers to that, please?
pramathesh said:
Are you sure? Before messing it up with stock boot image I had nova running for me and had also kept one plus stock installed. Not sure how I can side load a launcher. Any pointers to that, please?
Click to expand...
Click to collapse
Not 100% sure it'll help.
But won't hurt to try..
indian84 said:
Not 100% sure it'll help.
But won't hurt to try..
Click to expand...
Click to collapse
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
pramathesh said:
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
Click to expand...
Click to collapse
Well, I shared a screenshot with you.
It's similar to sideloading a zip..
indian84 said:
Well, I shared a screenshot with you.
It's similar to sideloading a zip..
Click to expand...
Click to collapse
I am unable to open the image you have attached
pramathesh said:
I am unable to open the image you have attached
Click to expand...
Click to collapse
Google would help.
Too lazy to type..
Lol
pramathesh said:
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
Click to expand...
Click to collapse
Adb install name.apk
Where name.apk is the app you're installing
indian84 said:
Not 100% sure it'll help.
But won't hurt to try..
Click to expand...
Click to collapse
I am getting this while trying to sideload apk
C:\Program Files (x86)\Minimal ADB and Fastboot>adb install launcher.apk
adb: connect error for write: closed
If you use bluespark TWRP then you're several weeks late, use officially working TWRP check in ROM section
Sideload the whole ROM to go back to normal, with temporary boot TWRP in fastboot mode
Striatum_bdr said:
If you use bluespark TWRP then you're several weeks late, use officially working TWRP check in ROM section
Sideload the whole ROM to go back to normal, with temporary boot TWRP in fastboot mode
Click to expand...
Click to collapse
I have the 9.0.10 downloaded from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I unzipped them found a .bin file. Is there any guide on extracting the binary files and flashing the entire rom via ADB?
pramathesh said:
I have the 9.0.10 downloaded from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I unzipped them found a .bin file. Is there any guide on extracting the binary files and flashing the entire rom via ADB?
Click to expand...
Click to collapse
Use fastboot ROM in that case. See relevant threads
Striatum_bdr said:
Use fastboot ROM in that case. See relevant threads
Click to expand...
Click to collapse
Let me check, is it okay to PM you?
pramathesh said:
Let me check, is it okay to PM you?
Click to expand...
Click to collapse
No, I've never had to use that, and all is explained clearly in the threads giving fastboot ROM
Ultimate tool is msmdownload, there are dedicated threads also
Striatum_bdr said:
No, I've never had to use that, and all is explained clearly in the threads giving fastboot ROM
Ultimate tool is msmdownload, there are dedicated threads also
Click to expand...
Click to collapse
Sorry for being so naive but I couldn't find any ROM that would have fastboot support. There is very less stuff for 6T to comb from.
pramathesh said:
Sorry for being so naive but I couldn't find any ROM that would have fastboot support. There is very less stuff for 6T to comb from.
Click to expand...
Click to collapse
Not very hard to find
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Striatum_bdr said:
Not very hard to find
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Silly me, I was looking in the ROM section. I will use this and update the thread again
Hey! It worked. The phone is up and running now. Only thing is I lost all the data on the phone
Solution
Next time you face this issue in any ROM, you can do the following to come out of it. However, you would need to have a customised notification panel, which will allow you to go to settings and security option. Also, ensure you do not have a default launcher, if you have more than 1 launcher in your phone that you use.
Just long press any icon which leads to settings, or click on the settings icon from the notification bar.
It will open a blank settings page. Do a scroll up and down, and it will refresh.
Then go to security and privacy and delete the fingerprints.
You may also need to delete the security pin or swipe or the lock screen settings.
NOTE: Do not delete the locksettings.db from Recovery mode. It will break everything and the above steps might not help.
BTW, I am facing this issue for the last 3 days. Have been doing clean flash everytime. I was searching this issue on internet, but yours came up just now, and I read, FingerPrint, and it stuck me. Now it worked. Rebooting now. But posting the comment here in case I face any issues. Want to help you, as I know what the feeling is like. Frustrated and tired, wanting to kill someone.
Edit: Rebooted without any lock pin or FP. Shows phoe is starting, and starts in 2 seconds and allows access.
Will set a pin and check now.
Then will set one FP and check.
Edit2: Set pin lock and rebooted. Works okay..