I managed to flash correct following the sticky:
http://forum.xda-developers.com/showpost.php?p=12898827&postcount=3
I decided to use this ROM:
http://forum.xda-developers.com/showthread.php?t=1121333
I already had 2.3.7 installed with an older kernal, but this was first time I did a manual installation. Anyway, from both guides, they say to type "fast flash boot boot.img" etc but this didn't work for me, so I had to type "fastboot flash boot openswift5.0b4_boot.img". I had to do the same for the system image as well. Is this still okay?
Secondly, from that ROM, there were two boot img files. One was called boot, the other was called "nohack boot". I just used the "boot" one then proceeded with the "system" img file. Was this okay as well or have I done something incorrectly?
Thankfully, my phone appears okay and everything worked, but I just want to make sure I did follow the steps correctly so that I don't have any major problems in the future.
Also, I remember reading somewhere that there was a "memory fix" which made things faster. Does this ROM include it or is this memory fix something else I must do.
Fianally, for this current ROM, did I need to change my memory settings because I have never altered any partition sizes etc.
Sorry for the noobie questions, I did try and follow the stickies etc, just want to make 100% sure cheers.
PS: I know it mentions something in he changelog for the ROM about memory fixes etc, but I didn't fully understand what it meant.
djpailo said:
Anyway, from both guides, they say to type "fast flash boot boot.img" etc but this didn't work for me, so I had to type "fastboot flash boot openswift5.0b4_boot.img". I had to do the same for the system image as well. Is this still okay?
Click to expand...
Click to collapse
So far so good...
djpailo said:
Secondly, from that ROM, there were two boot img files. One was called boot, the other was called "nohack boot". I just used the "boot" one then proceeded with the "system" img file. Was this okay as well or have I done something incorrectly?
Click to expand...
Click to collapse
also good!
djpailo said:
Also, I remember reading somewhere that there was a "memory fix" which made things faster. Does this ROM include it or is this memory fix something else I must do.
Click to expand...
Click to collapse
I think you are talking about the V6-supercharger. You can try it out, but for me it didn't work very well. (But that was on IceCreamSwift, don't know about this rom. So just try it.)
djpailo said:
Fianally, for this current ROM, did I need to change my memory settings because I have never altered any partition sizes etc.
Click to expand...
Click to collapse
As a rule of thumb, if the startpost of the rom doesn't say anything about the sizes, leave them to default. If you are still in doubt, check in Titanium Backup or some file explorer or another program how much space is left in your /system partition. I always try to keep at least 10 MB free, just in case, but even 1 kb should be fine.
Good luck!
thanks for your help!
I have noticed a fairly annoying problem, the play store app is gone!
I tried downloading it again from an apk from another website. Every time I open it, it asks me to add an account, but I already successfully added my google account and synced contacts from it etc.
??
Its been nearly two days:
- I have tried flashing to a new version of recovery and then reflashing the same ROM all using the following commands:
fastboot flash recovery recovery_clockwork_3.0.2.4_swift.img
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I still have these major problem with the market. I tried downloading the market application, and whenever it says I need to add an account, I press the add button and it just exits the application and goes back to the previous page.
From the ROM I'm trying to install, the installation instructions are:
use fastboot
adb reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
The one in bold I never used. Doing some digging, apparently this means "this will reboot your phone back into the bootloader (white screen with the android on wheels" but I think I just did a few longer steps to do the same thing..
So does no-one know what my problem is?
adb reboot bootloader is the same like booting into fastboot (camera + power buttons)
try to add your google account in settings>accounts & sync>add new google account
because setup wizard is facing problems sometimes
andreas__ said:
adb reboot bootloader is the same like booting into fastboot (camera + power buttons)
try to add your google account in settings>accounts & sync>add new google account
because setup wizard is facing problems sometimes
Click to expand...
Click to collapse
Yes, I had tried that before.
I tried it again after reflashing and it still doesn't work. I have the account added and email synced, but when I open google play, it still asks me to add an account, and clicking either yes or no just returns to the previous page.
I also tried downloading the gmail app (which didn't come with this rom). It installed, but whenever I open it, it just opens and closes very quickly???
djpailo said:
Yes, I had tried that before.
I tried it again after reflashing and it still doesn't work. I have the account added and email synced, but when I open google play, it still asks me to add an account, and clicking either yes or no just returns to the previous page.
I also tried downloading the gmail app (which didn't come with this rom). It installed, but whenever I open it, it just opens and closes very quickly???
Click to expand...
Click to collapse
Maybe create anther Google account and test if it works
Edit: don't use other market.apk ! Just add Google account and play store will appear
Sent from my LG GT540 using xda premium
Pls delete
andreas__ said:
adb reboot bootloader is the same like booting into fastboot (camera + power buttons)
try to add your google account in settings>accounts & sync>add new google account
because setup wizard is facing problems sometimes
Click to expand...
Click to collapse
andreas__ said:
Maybe create anther Google account and test if it works
Edit: don't use other market.apk ! Just add Google account and play store will appear
Sent from my LG GT540 using xda premium
Click to expand...
Click to collapse
Thanks for your reply! Before I saw this, I decided to try a different ROM and everything worked fine! I'm now using SDSL v2.1. Thanks for your help, and when I flash again and things go wrong, I'll remember your advice to try adding a different account. It was a weird problem though thats for sure!
Related
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
Hi
I record updating to 4.3 without removing root (I just lost it and the recovery asked if I wanted to redo it), so I decided to try the samething with 4.4. Well, things got very bad.
After I got the notification that 4.4 was available, I clicked to download it, the phone then rebooted and I installed it via the recovery.
Then Android booted and got stuck after Google's logo (balls moving) for more than 5 minutes, so I decided something was wrong and shut it down.
So far I tried going to adb shell and mounting sdcard (so I could make a backup), but apparently fstab had /sdcard datamedia /dev/null (huh?)
Then I tried to adb sideload 4.3 and 4.4 (from https://developers.google.com/android/nexus/images ), and both failed for different reasons (4.3 just said "(bad)", 4.4 said something with "set_meta_recursive").
Then I did a "fastboot oem unlock" (please don't tell me this lose all the data - including sdcard) and retried that. Also didn't work.
(I cleaned cache before trying)
Then I found some tutorials telling to "fastboot flash bootloader/radio/...", but those versions (4.3 and 4.4) from the site above doesn't have files named "bootloader-mako-makoz20i.img" or so. I could find it for 4.2 (makoz10), so I tried with that and it apparently worked. Except also got on boot loop (different logo).
Then I downloaded an image that was on a link for 4.3 that had makoz20, so I tried with that and got the same result (it worked, but got on boot loop).
Now even recovery isn't working anymore.
I was careful to not run "fastboot -w" (or flash-all.sh) and/or to delete userdata.img from the .zip, so I have some hope I didn't lose all data.
Any hints on how to proceed from here?
thanks!
Lem0nHead said:
Hi
I record updating to 4.3 without removing root (I just lost it and the recovery asked if I wanted to redo it), so I decided to try the samething with 4.4. Well, things got very bad.
After I got the notification that 4.4 was available, I clicked to download it, the phone then rebooted and I installed it via the recovery.
Then Android booted and got stuck after Google's logo (balls moving) for more than 5 minutes, so I decided something was wrong and shut it down.
So far I tried going to adb shell and mounting sdcard (so I could make a backup), but apparently fstab had /sdcard datamedia /dev/null (huh?)
Then I tried to adb sideload 4.3 and 4.4 (from https://developers.google.com/android/nexus/images ), and both failed for different reasons (4.3 just said "(bad)", 4.4 said something with "set_meta_recursive").
Then I did a "fastboot oem unlock" (please don't tell me this lose all the data - including sdcard) and retried that. Also didn't work.
(I cleaned cache before trying)
Then I found some tutorials telling to "fastboot flash bootloader/radio/...", but those versions (4.3 and 4.4) from the site above doesn't have files named "bootloader-mako-makoz20i.img" or so. I could find it for 4.2 (makoz10), so I tried with that and it apparently worked. Except also got on boot loop (different logo).
Then I downloaded an image that was on a link for 4.3 that had makoz20, so I tried with that and got the same result (it worked, but got on boot loop).
Now even recovery isn't working anymore.
I was careful to not run "fastboot -w" (or flash-all.sh) and/or to delete userdata.img from the .zip, so I have some hope I didn't lose all data.
Any hints on how to proceed from here?
thanks!
Click to expand...
Click to collapse
You may have missed this.. http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
ravindrank said:
You may have missed this.. http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
Click to expand...
Click to collapse
I am facing the same problem. The bootloader is stuck in a loop. Is there any way to recover the stock android??
true! It's interesting how google doesn't show results if you put it on quotes ("set_metadata_recursive: some changes failed")
gonna try that, thanks!
hm, well
I tried flashing using fastboot now (following method D on http://forum.xda-developers.com/showthread.php?t=2010312 ), so I guess set_metadata_recursive or something like that doesn't matter
it flashed correctly, but it still doesn't work (now I get stuck in black screen after google's logo)
oops, sorry. not black screen (I forgot to flash system), not it's stuck on the 4 balls animation, as it was right after the update ;(
you did a factory reset prior to booting and after flashing?
playya said:
you did a factory reset prior to booting and after flashing?
Click to expand...
Click to collapse
no, I'm trying to avoid losing data
since nexus 4 sdcard isn't removable (and now I'm regretting have accepted that), is there anyway to save my data?
as I said, I tried mounting it, but for some reason /sdcard is pointing to /dev/null no fstab.
Now I already flashed the stock recovery, so maybe I need to flash something else to try that again, but is there anything I can do differently?
thanks
Lem0nHead said:
no, I'm trying to avoid losing data
since nexus 4 sdcard isn't removable (and now I'm regretting have accepted that), is there anyway to save my data?
as I said, I tried mounting it, but for some reason /sdcard is pointing to /dev/null no fstab.
Now I already flashed the stock recovery, so maybe I need to flash something else to try that again, but is there anything I can do differently?
thanks
Click to expand...
Click to collapse
stock recovery wipe data and may I ask you what do you think you are going to lose? You are only going to lose apps and app data not photos or files which honestly you should have a free dropbox and save everything on there for the reason mentioned before... NO SDCARD
hm, maybe it's related with encryption I'd set from Security? I know the password, but it doesn't ask me for it anywhere
Lem0nHead said:
hm, maybe it's related with encryption I'd set from Security? I know the password, but it doesn't ask me for it anywhere
Click to expand...
Click to collapse
man just do a wipe...
playya said:
man just do a wipe...
Click to expand...
Click to collapse
I think currently I'm more worried with not losing data than with getting my phone back working.
Sorry, but I find it ridiculous that it isn't easy to extract data from your phone easily. Even if it's encrypted, as long as I know the password there should be a tool to help with that.
Apparently there might be something like "recovery --set_encrypted_filesystem=off" (on adb shell), but I'm getting "sh: /sbin/postrecoveryboot.sh: not found", so no luck yet
Lem0nHead said:
I think currently I'm more worried with not losing data than with getting my phone back working.
Sorry, but I find it ridiculous that it isn't easy to extract data from your phone easily. Even if it's encrypted, as long as I know the password there should be a tool to help with that.
Apparently there might be something like "recovery --set_encrypted_filesystem=off" (on adb shell), but I'm getting "sh: /sbin/postrecoveryboot.sh: not found", so no luck yet
Click to expand...
Click to collapse
what data are you trying to save?
playya said:
what data are you trying to save?
Click to expand...
Click to collapse
encrypted files on /sdcard
Lem0nHead said:
encrypted files on /sdcard
Click to expand...
Click to collapse
wipe/data factory reset from custom recovery has nothing to do with sdcard based files. Its only going to delete any files in your data portion of your rom and not your sdcard. area... two completely different things, have you done your research on android and how everything works. Its good to search and read up on this stuff especially since its interesting and you apparently need a few answers to your questions
playya said:
factory reset has nothing to do with sdcard based files. Its only going to delete any files in your data portion of your rom and not your sdcard area
Click to expand...
Click to collapse
are you sure this stands for nexus 4, which have just an internal sdcard?
Lem0nHead said:
are you sure this stands for nexus 4, which have just an internal sdcard?
Click to expand...
Click to collapse
come on man this aint my first rodeo and do you think every time you did a factory reset it was going to delete your music? Do some research my man there are multiple wipes and an Internal SD Card wipe will delete everything but a factory reset with a custom recovery or factory will only reset your settings to factory
playya said:
Its good to search and read up on this stuff especially since its interesting and you apparently need a few answers to your questions
Click to expand...
Click to collapse
well, as I said before, I was following http://forum.xda-developers.com/showthread.php?t=2010312
it says "this command will wipe your device (including /sdcard)"
maybe this isn't true, but I guess it's a trusted thread
Lem0nHead said:
well, as I said before, I was following http://forum.xda-developers.com/showthread.php?t=2010312
it says "this command will wipe your device (including /sdcard)"
maybe this isn't true, but I guess it's a trusted thread
Click to expand...
Click to collapse
hold on let me take a look now that might be a different procedure I am referring to a wipe from recovery but in your case a full wipe may be necessary
hm, I didn't try any kind of wipe
so which one is safe (so I can try at least)? "wipe data / factory reset" from recovery?
My OnePlus2 phone keeps rebooting and won't give me access to the Android OS after a recent update (OxygenOS 3.0.1 Community Build). The phone has never been tampered with (rooted etc..). I have access to fastboot but not adb (as the phone won't boot). I wish to get the phone working again or at the very least obtain the encrypted data. A data wipe where I loose all my files is not what I am looking for although this would likely fix my booting issues. I have wiped the cache but this did not solve the booting problem.
How do recover the data on my phone?
I have tried to boot and flash several images such as the previous version of OxygenOS (OxygenOS 2.2.1-2 hotfix), recovery.img, TWRP etc... but this keeps failing as fastboot tells me the phone is locked. I try to unlock it using fastboot but the command 'fastboot flashing unlock' is not recognised (despite claiming to be if you launch the software only by typing fastboot) and 'fastboot oem unlock' gives me FAILED (remote: oem unlock is disabled) .
The problem would be solved if I had access to Android and could enable oem unlocking in developer options, but I can't.
Can you get in recovery? Y guess you could flash signed full zip, any fastboot method won't work
Sent from my ONE A2005 using Tapatalk
fburgos said:
Can you get in recovery? Y guess you could flash signed full zip, any fastboot method won't work
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Yes I can get into the stock recovery. That is how I wiped the cache and launched fastboot. At the moment I can't flash anything as fastboot tells me the device is locked. The only way I know of to recover the phone is a complete wipe... I hope there are new things I can try first though...
Same here. After yesterday's update, the phone is stuck rebooting. I also wiped the cache, to no avail. It starts booting (spinner), then shows a blank screen for a while (30 seconds), then prints "android starting" and reboots again.
Any idea? Do you know what gets deleted on "wipe data"? Will it delete all photos etc. or only the apps?
Blendiac said:
Same here. After yesterday's update, the phone is stuck rebooting. I also wiped the cache, to no avail. It starts booting (spinner), then shows a blank screen for a while (30 seconds), then prints "android starting" and reboots again.
Any idea? Do you know what gets deleted on "wipe data"? Will it delete all photos etc. or only the apps?
Click to expand...
Click to collapse
Wiping the data did not help. Due to firewall restrictions the OnePlus people were not able to remotely help me. I will speak with them in a few days when the firewall issue has been resolved.
same here even i can't get in recovery (recovery now is black blank screen) ! i try
forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
but it don't work for me, in my country don't have Oneplus Service Center and i must take my OP2 to trash if no way to fix it .. Please HELP ME !!!
I remember somewhere i read that oos3 is not compatible with encrypted data
Sent from my ONE A2005 using Tapatalk
I read this too (afterwards). I saw it on the thread introducing the newest cyanogenmod OS here on the forums. How stupid to launch an update incompatible with encryption!
Guys... Same problem please help. Can't boot after newest update beacouse I have disabled google app. I have important data which I don't want to lose. What should I do?
Jakic007 said:
Guys... Same problem please help. Can't boot after newest update beacouse I have disabled google app. I have important data which I don't want to lose. What should I do?
Click to expand...
Click to collapse
If developer options were active before you updated your phone then you can use fastboot to recover your (encrypted) data. This is done by booting into twrp which allows you to recover the data. For instructions here. If developer options were not active prior to the update then fastboot is pretty useless (at least to me) and it seems to be very little you can do. I am still waiting an answer.
Boot into fastboot and flash custom recovery. Recover personal data if possible by mounting data to USB... then flash 3.0.1 again
PS: May be this is not even possible... I know nothing about encryption, before you all bash me out.. try this. I had done this, when I had this problem. I don't know about encrypted data and all
krishna442 said:
Boot into fastboot and flash custom recovery. Recover personal data if possible by mounting data to USB... then flash 3.0.1 again
PS: May be this is not even possible... I know nothing about encryption, before you all bash me out.. try this. I had done this, when I had this problem. I don't know about encrypted data and all
Click to expand...
Click to collapse
Your idea probably works but only if you have activated 'developer options' prior to the problem as I explained in my last reply. Since I did not, I can not use fastboot to flash my device.
epud said:
Your idea probably works but only if you have activated 'developer options' prior to the problem as I explained in my last reply. Since I did not, I can not use fastboot to flash my device.
Click to expand...
Click to collapse
Pretty much messed up eh.. hope OnePlus helps you out. :good: :fingers-crossed:
I bought my nexus 6p from this seller and the seller said that errors would pop up, I got home and thought I would fix it, I unlocked bootloader, flashed a custom recovery (TWRP), and flashed a custom ROM (Pure Nexus) and Open GApps ARM64 6.0 Stock (I believed that GApps was the problem) I thought I fixed it. It was working great, I was re downloading all my apps from my old phone then the errors started coming back and got sad I flashed it again to stock (MDA89D) and now updating it to the latest version, hopefully it would be fixed. The phone was at 6.0.1 (MTC19T) when I received it.
Errors that would pop up are all of the google services apps such as gmail, google keyboard, camera, play store, etc.
Also the processandroid.process.acore has stopped
It would also reboot randomly.
Please help.
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 to flash the latest (MTC19X) factory images. Make sure you flash all images except userdata, and make sure you format userdata too. See if that helps.
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 to flash the latest (MTC19X) factory images. Make sure you flash all images except userdata, and make sure you format userdata too. See if that helps.
Click to expand...
Click to collapse
i followed ur guide, thats how i went back to stock (MDA89D), but ill try to go to the latest one (MTC19X) ur guide is really awesome, but i got stuck when the phone was encrypting and i just restarted it and it works, now the wifi is not working
marky31x said:
i followed ur guide, thats how i went back to stock (MDA89D), but ill try to go to the latest one (MTC19X) ur guide is really awesome, but i got stuck when the phone was encrypting and i just restarted it and it works, now the wifi is not working
Click to expand...
Click to collapse
Did you format userdata when flashing that build? Is there a reason you tried the oldest build?
Heisenberg said:
Did you format userdata when flashing that build? Is there a reason you tried the oldest build?
Click to expand...
Click to collapse
yes i formatted the userdata when i flashed that build, the reason why i tried the oldest build is i thought the problem was with the update to (MTC19T) but the errors occurred when i updated to the oldest build
I just finished following step 10, still getting the error im on the latest build now 6.0.1 (MTC19X) but the wifi is working again
marky31x said:
yes i formatted the userdata when i flashed that build, the reason why i tried the oldest build is i thought the problem was with the update to (MTC19T) but the errors occurred when i updated to the oldest build
I just finished following step 10, still getting the error im on the latest build now 6.0.1 (MTC19X) but the wifi is working again
Click to expand...
Click to collapse
Did you flash all images? Wonky WiFi would suggest you may not have.
Heisenberg said:
Did you flash all images? Wonky WiFi would suggest you may not have.
Click to expand...
Click to collapse
yes I followed the guide carefully and flashed everything, im connected to the wifi now but still getting the gapps error
after connecting to the wifi and when prompt the "Got another device?" question i select "no thanks" it would give me "Unfortunately Google Play has stopped" and return to the wifi menu
marky31x said:
yes I followed the guide carefully and flashed everything, im connected to the wifi now but still getting the gapps error
after connecting to the wifi and when prompt the "Got another device?" question i select "no thanks" it would give me "Unfortunately Google Play has stopped" and return to the wifi menu
Click to expand...
Click to collapse
You mentioned flashing gapps earlier. Those look like the correct gapps to be used with a custom ROM, but you're not flashing gapps after flashing the factory images are you?
Heisenberg said:
You mentioned flashing gapps earlier. Those look like the correct gapps to be used with a custom ROM, but you're not flashing gapps after flashing the factory images are you?
Click to expand...
Click to collapse
nope i followed ur guide, i didn't flash any gapps in the process
Heisenberg said:
You mentioned flashing gapps earlier. Those look like the correct gapps to be used with a custom ROM, but you're not flashing gapps after flashing the factory images are you?
Click to expand...
Click to collapse
i got thru the setup page i had to choose the other option, i have access to the homepage now, ill try to redownload all my apps again
the errors are still here it says "google app" stopped, now the google play store isnt working
marky31x said:
i got thru the setup page i had to choose the other option, i have access to the homepage now, ill try to redownload all my apps again
the errors are still here it says "google app" stopped
Click to expand...
Click to collapse
I'm really not sure what's going on. The only thing I can think of is formatting system, reporting to the bootloader, and flashing system again.
Heisenberg said:
I'm really not sure what's going on. The only thing I can think of is formatting system, reporting to the bootloader, and flashing system again.
Click to expand...
Click to collapse
Alright, i'm in the homepage now and i tried re downloading my apps but the playstore crashed and now it would connect to the internet even though im connected to the wi fi
marky31x said:
Alright, i'm in the homepage now and i tried re downloading my apps but the playstore crashed and now it would connect to the internet even though im connected to the wi fi
Click to expand...
Click to collapse
Is this after formatting system with fastboot?
Heisenberg said:
Is this after formatting system with fastboot?
Click to expand...
Click to collapse
nope i haven't done that when this happened, what is the command to format in fastboot?
marky31x said:
nope i haven't done that when this happened, what is the command to format in fastboot?
Click to expand...
Click to collapse
Code:
fastboot format system
Then
Code:
fastboot reboot bootloader
Then
Code:
fastboot flash system system.img
Then
Code:
fastboot reboot
Heisenberg said:
Code:
fastboot format system
Then
Code:
fastboot reboot bootloader
Then
Code:
fastboot flash system system.img
Then
Code:
fastboot reboot
Click to expand...
Click to collapse
I followed the steps and tried opening the play store and still getting the "google play has stopped" error
marky31x said:
I followed the steps and tried opening the play store and still getting the "google play has stopped" error
Click to expand...
Click to collapse
I'm running outta ideas. Perhaps try signing out of your Google account, clear the data and cache for the Play Store and Google Play Services, reboot the phone, sign back into your Google account.
Heisenberg said:
I'm running outta ideas. Perhaps try signing out of your Google account, clear the data and cache for the Play Store and Google Play Services, reboot the phone, sign back into your Google account.
Click to expand...
Click to collapse
well this is strange i selected the "uninstall update" option for google play and stopped google app then my phone restarted and now im not getting any errors so far, ill update if any errors pop up
i think the problem is the Google play service app in the google store, i uninstalled its updates and everything works fine now, but i guess no google services for me
marky31x said:
well this is strange i selected the "uninstall update" option for google play and stopped google app then my phone restarted and now im not getting any errors so far, ill update if any errors pop up
i think the problem is the Google play service app in the google store, i uninstalled its updates and everything works fine now, but i guess no google services for me
Click to expand...
Click to collapse
What version was installed? You could try making sure you're on the latest.
http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-9-4-52-release/
Heisenberg said:
What version was installed? You could try making sure you're on the latest.
http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-9-4-52-release/
Click to expand...
Click to collapse
the version that was installed was 8.x.xx
i just installed the latest one, it was hard to get too, chrome would close before i reach the website T_T but i finally installed it and restarted the phone and its still no good, i thought that would fix the problem too but i guess not. i installed version 9.4.52
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..