Related
Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically
Today and after deciding to simply restart my Nexus 6P, it booted into TWRP menu, I tried to reboot again, but no luck. can someone please help?
is there a way to get off the TWRP menu and boot my phone normally?
Note: The root used to simply work fine for about a month now.
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Gytole said:
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Click to expand...
Click to collapse
Rooted my phone, and it was working fine for about a month, I done nothing unusual, All i did is restart my phone and it went to the TWRP menu, thats all. Im stuck there now.
I don't recall doing an update or whatever. Im using "BETA-SuperSU-v2.67-20160121175247.zip"
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
MahmoudEMH said:
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
Click to expand...
Click to collapse
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Heisenberg said:
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Click to expand...
Click to collapse
Yes to each one of those questions.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
I will have to call you out here buddy. If you have indeed tried to flash all factory images, you won't even have TWRP in the first place.
Go to this wonderful guide by the wonderful @Heisenberg, and scroll down to "10. How To Flash The Factory Images (And Return To Stock)". You will find very clear instruction on how to return your phone to its factory stock state. This will most likely get rid of the problems you're facing.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
If you had flashed the full factory images I don't see how it's possible at all to be in your current situation. Explain how you flashed them, and exactly what you flashed please.
My phone reboots on DP5 whenever the device locks and it's not charging. It happens in safe mode too, and after factory resets. Any advice?
Thanks!
Tiduszk said:
My phone reboots on DP5 whenever the device locks and it's not charging. It happens in safe mode too, and after factory resets. Any advice?
Thanks!
Click to expand...
Click to collapse
It may be far fetched but check and make sure your case is not putting pressure on Power button.
Witek_M said:
It may be far fetched but check and make sure your case is not putting pressure on Power button.
Click to expand...
Click to collapse
Using a live case, complete cutouts for the buttons. Thanks for offering any help though!
Tiduszk said:
Using a live case, complete cutouts for the buttons. Thanks for offering any help though!
Click to expand...
Click to collapse
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Witek_M said:
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Click to expand...
Click to collapse
Is a dirty flash okay, or should I clean flash?
Witek_M said:
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Click to expand...
Click to collapse
Also, will I still get OTAs if I flash it?
Tiduszk said:
Also, will I still get OTAs if I flash it?
Click to expand...
Click to collapse
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Witek_M said:
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Click to expand...
Click to collapse
Okay. Thank you! I'll report back with results
Witek_M said:
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Click to expand...
Click to collapse
Two new developments. The reboots survived two clean flashes (the first time didn't boot for some reason), and the real cause of the reboots is nothing to do with Google play movies; the phone reboots wherever it locks while connected to a carrier network. I however did find a temporary fix for this, just putting my phone into airplane mode whenever I'm not using it, but that is not sustainable for obvious reasons.
Tiduszk said:
Two new developments. The reboots survived two clean flashes (the first time didn't boot for some reason), and the real cause of the reboots is nothing to do with Google play movies; the phone reboots wherever it locks while connected to a carrier network. I however did find a temporary fix for this, just putting my phone into airplane mode whenever I'm not using it, but that is not sustainable for obvious reasons.
Click to expand...
Click to collapse
Try changing or reflashing the radio?
DJBhardwaj said:
Try changing or reflashing the radio?
Click to expand...
Click to collapse
I'll give it a try, where can I get my hands on it?
Tiduszk said:
I'll give it a try, where can I get my hands on it?
Click to expand...
Click to collapse
Radio flash-able image files are present inside every factory image. What radio version are you currently operating on?
DJBhardwaj said:
Try changing or reflashing the radio?
Click to expand...
Click to collapse
I just reflashed "radio-angler-angler-03.72.img"
I'll reply again with whether or not it worked.
Tiduszk said:
I just reflashed "radio-angler-angler-03.72.img"
I'll reply again with whether or not it worked.
Click to expand...
Click to collapse
Good luck. If it doesn't, try radio version 3.61 from the latest MM factory image (MTC20F).
DJBhardwaj said:
Radio flash-able image files are present inside every factory image. What radio version are you currently operating on?
Click to expand...
Click to collapse
It did not fix it. Thanks for your help though.
DJBhardwaj said:
Good luck. If it doesn't, try radio version 3.61 from the latest MM factory image (MTC20F).
Click to expand...
Click to collapse
Is the marshmallow radio compatible with DP5?
Tiduszk said:
Is the marshmallow radio compatible with DP5?
Click to expand...
Click to collapse
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
DJBhardwaj said:
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
Click to expand...
Click to collapse
Well, I'll try it tomorrow. The worst that could happen is that I need to do a clean flash again.
Tiduszk said:
Well, I'll try it tomorrow. The worst that could happen is that I need to do a clean flash again.
Click to expand...
Click to collapse
DJBhardwaj said:
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
Click to expand...
Click to collapse
Unfortunately it did not help, the issue persisted. I then tried to flash all the way back to stock marshmallow, and that didn't work. With Nougat released today, I flashed to it and my phone still reboots. I was able to further isolate the cause though; the phone reboots when it has a mobile data connection regardless of carrier (I tried Sprint, T-Mobile, AT&T, and China Unicom).
I think my only option left is to RMA it again.
Hi, guys.
I have rooted my Mi A1. But now after facing the problem with October update, I want to undo all changes made on my device and receive and install all future updates without any additional procedures - just receive OTA update click install button and that's all.
My first question is - is it possible?
The second is - can anybody explain me how can I do it?
Note: After flashing and getting root FlashFire shows me that system's active slot is slot B right now. Also after some attempts to install October OTA update (playing with slots A/B) my device shows me that I do not have any root access now. The screenshots are attached.
Thanks beforehand.
I think the best way is to flash stock image you can find on miui download site.
Samhain77 said:
I think the best way is to flash stock image you can find on miui download site.
Click to expand...
Click to collapse
I have acquainted with this material too. I want to know is there any problem if I will do flashing through miflash tool at this situation? Maybe I need to change something before any changing. Or it is not convenient for me right now?
Thanks.
dinozaur516 said:
I have acquainted with this material too. I want to know is there any problem if I will do flashing through miflash tool at this situation? Maybe I need to change something before any changing. Or it is not convenient for me right now?
Thanks.
Click to expand...
Click to collapse
Basically, if you flash the factory image, it should be (or I believe it is) written on the both partitions, so you can start with "clean shield", but on the newest update.
You can even preserve user data within the tool
matcho13579 said:
Basically, if you flash the factory image, it should be (or I believe it is) written on the both partitions, so you can start with "clean shield", but on the newest update.
You can even preserve user data within the tool
Click to expand...
Click to collapse
Ok, i just do not understand why factory image is written on two partitions. Why it cannot be written on one partition? Or it must be so? Can you explain me this issue?
dinozaur516 said:
Ok, i just do not understand why factory image is written on two partitions. Why it cannot be written on one partition? Or it must be so? Can you explain me this issue?
Click to expand...
Click to collapse
I'm not really sure if it's true or not, but I think it it. Like, if you have any problems with either partition A or B, simply flashing factory image over it should fix both, that's why I think it's true.
matcho13579 said:
I'm not really sure if it's true or not, but I think it it. Like, if you have any problems with either partition A or B, simply flashing factory image over it should fix both, that's why I think it's true.
Click to expand...
Click to collapse
As I understood, this device has 2 same images, am I right? And it means if one image size is 4 GB then it is multiplied by 2 and 2 images` size is equal to 8 GB.
dinozaur516 said:
As I understood, this device has 2 same images, am I right? And it means if one image size is 4 GB then it is multiplied by 2 and 2 images` size is equal to 8 GB.
Click to expand...
Click to collapse
Referring from here, it's not true:
A/B updates require an increase of only 320 MiB in flash, with a savings of 32MiB from removing the recovery partition and another 100MiB preserved by removing the cache partition.
Click to expand...
Click to collapse
matcho13579 said:
Referring from here, it's not true:
Click to expand...
Click to collapse
Oh! Thanks a lot. I did not know that
Will do returning to factory image. After the installation, I'll come back with my experience.
dinozaur516 said:
Oh! Thanks a lot. I did not know that
Click to expand...
Click to collapse
Actually it's true as I checked the tables on the site, but it's not that much of a difference if you own a 64 GB device, it won't take more than 400 MB of storage
matcho13579 said:
Actually it's true as I checked the tables on the site, but it's not that much of a difference if you own a 64 GB device, it won't take more than 400 MB of storage
Click to expand...
Click to collapse
Sure
I successfully flashed my Mi A1 to factory image via MiFlash tool. I used "Clean all and lock" mode. Everything is working and the device also installed October updates.
dinozaur516 said:
I successfully flashed my Mi A1 to factory image via MiFlash tool. I used "Clean all and lock" mode. Everything is working and the device also installed October updates.
Click to expand...
Click to collapse
So you have now a clean phone without your old user data?
Samhain77 said:
So you have now a clean phone without your old user data?
Click to expand...
Click to collapse
Yeap. I have installed all apps again. And everything works perfect.
Samhain77 said:
So you have now a clean phone without your old user data?
Click to expand...
Click to collapse
If you choose to save user data, they will be saved, you don't have to wipe user data, but it's recommended tho
matcho13579 said:
If you choose to save user data, they will be saved, you don't have to wipe user data, but it's recommended tho
Click to expand...
Click to collapse
I know, but i made it to be sure that everything will be installed like the first time.
dinozaur516 said:
Will do returning to factory image. After the installation, I'll come back with my experience.
Click to expand...
Click to collapse
i think flashing factory image with mi flash tool will solve the issue. have you flashed?
androwide said:
i think flashing factory image with mi flash tool will solve the issue. have you flashed?
Click to expand...
Click to collapse
Yeap, i made it. And everything is ok. I am on october update right now.
dinozaur516 said:
Yeap, i made it. And everything is ok. I am on october update right now.
Click to expand...
Click to collapse
great, i am also rooted with FlashFire method and going to flash factory image on my device to install the october security patch, but i would try "save user data" and flash, i know the root access will be gone, but i can root again with TWRP method or with the same.
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..