Database Users

Nexus 4 stuck at Google Logo Screen

Before flashing the new Paranoid Android Rom (4.3 one) I decided to to do a data wipe from TWRP...well to wipe out everything including SD card. The phone booted up with the rom which was there but however after flashing the new rom or any rom now. I'm unable to boot my nexus 4. I'm always stuck at the Google screen, the one with the lock. I tried flashing a 4.2.2 rom and still had no luck. So any help with that?

linezero said:
Before flashing the new Paranoid Android Rom (4.3 one) I decided to to do a data wipe from TWRP...well to wipe out everything including SD card. The phone booted up with the rom which was there but however after flashing the new rom or any rom now. I'm unable to boot my nexus 4. I'm always stuck at the Google screen, the one with the lock. I tried flashing a 4.2.2 rom and still had no luck. So any help with that?
Click to expand...
Click to collapse
You're sure you wiped everything except data/media? There isn't anything that could cause this, except if both PA zip and the 4.2.2 zip are somehow both bad downloads. Chech their md5 sums.
Also, post a step by step of what you did.

abaaaabbbb63 said:
You're sure you wiped everything except data/media? There isn't anything that could cause this, except if both PA zip and the 4.2.2 zip are somehow both bad downloads. Chech their md5 sums.
Also, post a step by step of what you did.
Click to expand...
Click to collapse
I'm having the same issue here, I flashed the latest PA ROM, full wiping everything with the latest TWRP, now I'm stuck on Google logo screen.
Now I have tried rolling back to stock 4.2.2 with stock bootloader, stock recovery, stock everything. Not working!
Kinda scary. Fastboot and recovery works fine. Please advise.
EDIT: Second time is the charm I guess. I locked/reunlocked the bootloader and flashed a 4.2.2 stock image again and it booted fine, that's effing weirld.
Anyway, it looks like that some N4s don't like the new bootloader or radio image. Be careful.

Shaldy said:
I'm having the same issue here, I flashed the latest PA ROM, full wiping everything with the latest TWRP, now I'm stuck on Google logo screen.
Now I have tried rolling back to stock 4.2.2 with stock bootloader, stock recovery, stock everything. Not working!
Kinda scary. Fastboot and recovery works fine. Please advise.
EDIT: Second time is the chard I guess. I locked/reunlocked the bootloader and flashed a 4.2.2 stock image again and it booted fine, that's effing weirld.
Anyway, it looks like that some N4s don't like the new bootloader or radio image. Be careful.
Click to expand...
Click to collapse
lucky you, you did it, mine n4 just crashed while normal using, cm 10.1.2, so it was android 4.2.2 and it cant boot now :< i can enter recovery, but phone is always stuck on google logo, even though i installed 4.2 stock that i sideloaded via adb (wasnt working) and then i used adb push, and its still the same... now i have to do as You, lock\relock and stock again
\\\EDIT: wug root toolkit (rootkit xD) helped, flashed 4.2.2 stock + unroot, now root and flash recovery, then pa or some other rom, cant stand lacks of clean android (4.3, and still no changing tracks with volume buttons?!) was worth to buy nexus 4 "unbrickable" android as zte blade sucessor, which is also unbrickable and undestructible

I have the same issue. I took a nandroid backup and flashed Paranoid Android 4.3. Now when I'm trying to restore the nandroid backup, my phone is stuck on 'X' screen during bootup. Logcat is stuck on
"D/dalvikvm( 481): GC_CONCURRENT freed 1501K, 10% free 15065K/16628K, paused 3ms+3ms, total 61ms"

i got that problem too
linezero said:
Before flashing the new Paranoid Android Rom (4.3 one) I decided to to do a data wipe from TWRP...well to wipe out everything including SD card. The phone booted up with the rom which was there but however after flashing the new rom or any rom now. I'm unable to boot my nexus 4. I'm always stuck at the Google screen, the one with the lock. I tried flashing a 4.2.2 rom and still had no luck. So any help with that?
Click to expand...
Click to collapse
hi, i was with that problem too, firsto of all you have to download this hings: adbht, sdk, fastboot, nexus root toolkit and the factory image of android. With those things you could be able to repair your phone the tutorial is here on this webpage

alfredoeguez97 said:
hi, i was with that problem too, firsto of all you have to download this hings: adbht, sdk, fastboot, nexus root toolkit and the factory image of android. With those things you could be able to repair your phone the tutorial is here on this webpage
Click to expand...
Click to collapse
Need help with my Nexus 4 !!
Device was unlocked and rooted. But I just want to return to the original state so I did a "Unroot Nexus 4 to Stock 4.2 on Mac!"
After step 10. When i "wipe data/factory reset" on the "Exclamation Android mascot", I couldn't do anything and got stuck at Google Logo. Couldn't flash anything and just stuck at FASTBOOT and Google Logo. Please help?
Thanks,
EJ

ewejin9394 said:
Need help with my Nexus 4 !!
Device was unlocked and rooted. But I just want to return to the original state so I did a "Unroot Nexus 4 to Stock 4.2 on Mac!"
After step 10. When i "wipe data/factory reset" on the "Exclamation Android mascot", I couldn't do anything and got stuck at Google Logo. Couldn't flash anything and just stuck at FASTBOOT and Google Logo. Please help?
Thanks,
EJ
Click to expand...
Click to collapse
Is your bootloader still unlocked?

I hope it is ok if I post here too..
I am stuck at the google screen.
Backupped everything to my computer.
Using TWRP 2.6.0.0 to full wipe.
Installing 4.3 Rom and gapps, rebooting.
Everything ok, did some app installations.
Reboot recovery.
Format data.
Reboot again.
Everything fine.
Now I installed my apps I use all the time to do a nandroid backup of my new/fresh setup.
Backup runs through, reboot system. Google screen.
Why is that?
Edit:
Nice one. Nandroid restore doesn't work.
:/ Stock image, here I come again!

Shaldy said:
I'm having the same issue here, I flashed the latest PA ROM, full wiping everything with the latest TWRP, now I'm stuck on Google logo screen.
Now I have tried rolling back to stock 4.2.2 with stock bootloader, stock recovery, stock everything. Not working!
Kinda scary. Fastboot and recovery works fine. Please advise.
EDIT: Second time is the chard I guess. I locked/reunlocked the bootloader and flashed a 4.2.2 stock image again and it booted fine, that's effing weirld.
Anyway, it looks like that some N4s don't like the new bootloader or radio image. Be careful.
Click to expand...
Click to collapse
Thank u man, u save my nexus 4

Same...
Having the same problem. After a billion fasboot formats and failed recovery attempts...uhhh, nothing.

Solution?
Fellows, I have a probable solution...worked for me:
http://forum.xda-developers.com/showthread.php?p=45394792&posted=1#post45394792

solved this by flashing stock 4.3 from Google:
https://dl.google.com/dl/android/aosp/occam-jwr66y-factory-74b1deab.tgz

The same happened to me but without doing anything . device totally stock, I rebooted it and when restarted it didn't start anymore.
From there I tried to flash it with the stock 4.4.2 ROM, didn't work. Tried with 4.4 and 4.3 but nothing. Back to 4.4.2 and nothing again.
Any suggestion?

Niddu85 said:
The same happened to me but without doing anything . device totally stock, I rebooted it and when restarted it didn't start anymore.
From there I tried to flash it with the stock 4.4.2 ROM, didn't work. Tried with 4.4 and 4.3 but nothing. Back to 4.4.2 and nothing again.
Any suggestion?
Click to expand...
Click to collapse
Tried with also a cyanogenmod ROM but nothing. The ROM is different but the result is the same... Keeps on turning
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Worked the same for me rolling back to version 4.2.2
Upgrading again brings me back to bootloop.
Is there any chance to have the newest version working?

Niddu85 said:
Worked the same for me rolling back to version 4.2.2
Upgrading again brings me back to bootloop.
Is there any chance to have the newest version working?
Click to expand...
Click to collapse
Update your recovery version
Sent from my Nexus 5

jd1639 said:
Update your recovery version
Sent from my Nexus 5
Click to expand...
Click to collapse
What do you mean? Can u please give me some steps to follow?
Thanks

Niddu85 said:
What do you mean? Can u please give me some steps to follow?
Thanks
Click to expand...
Click to collapse
What custom recovery are you on? Twrp or cwm, update to the latest version
Sent from my Nexus 5

jd1639 said:
What custom recovery are you on? Twrp or cwm, update to the latest version
Sent from my Nexus 5
Click to expand...
Click to collapse
At the moment I flashed all the factory ROMs with the stock recovery via "flash-all.bat" file included . I only used TWRP 2.7.0.0 when I tried with cyanogenmod but I had the bootloop with it anyway
The only working combination at the moment is stock ROM with stock recovery but 4.2.2. I would like to upgrade again to 4.4.2 but I don't know how

SPH-L720T, rolled back from Cm 12.1 to stock OK3, lost all Recovery

I did a search and was not able to find a solution to this problem. Any help would be appreciated.
As stated in the title, I rolled my SPH-L720T from CM 12.1 back to stock Lollipop OK3 downloaded from Sammobile (I was careful to make sure that I download the correct FW for the L720T and not the L720). After the rollback, I am no longer able to access any recovery, not the stock recovery, or TWRP or CWM after installing them.
I want to do a Factory reset but can't find a way to do it other than in Recovery.
Any ideas?

I found this list of Sprint dialer codes, but it doesn't give a code for a full factory reset. Still can't access any recovery however, would still appreciate any help with that.
http://forum.xda-developers.com/showthread.php?t=2261538

doraville said:
I found this list of Sprint dialer codes, but it doesn't give a code for a full factory reset. Still can't access any recovery however, would still appreciate any help with that.
http://forum.xda-developers.com/showthread.php?t=2261538
Click to expand...
Click to collapse
Install recovery with Odin, be sure to uncheck Auto Reboot in Odin before installing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
Install recovery with Odin, be sure to uncheck Auto Reboot in Odin before installing.
Click to expand...
Click to collapse
Thanks for your response! I did that...multiple times, still not able to access recovery, any recovery. No matter what I do it goes ahead and does a normal boot.

doraville said:
Thanks for your response! I did that...multiple times, still not able to access recovery, any recovery. No matter what I do it goes ahead and does a normal boot.
Click to expand...
Click to collapse
You're holding Power+Volume Up until it says Booting Recovery in blue right? If you still can't get any recovery you need to Odin OK3 again until you can at least get to stock recovery.

bilgerryan said:
You're holding Power+Volume Up until it says Booting Recovery in blue right? If you still can't get any recovery you need to Odin OK3 again until you can at least get to stock recovery.
Click to expand...
Click to collapse
Yes, VolumeUp+Power until blue text appears. Also VolumeUp+Power+Home just to be sure. Still always does a normal Boot. Have gone back and reloaded OK3 several times, same result.
I have several L720's, have done this with them no problem. This is the only 720T. I was very careful to make sure that I downloaded the correct FW from Sammobile. I had CWM recovery back when I was running CM12.1, it worked fine. After I rolled back to OK3 is when I lost all forms of Recovery. It's a mystery.
I'm wondering if I might have corrupted the recovery partition somehow. Has anyone heard of this and if there is a way to to repair it?

Well, I don't know what I did differently, but I went back and reloaded OK3 AGAIN (I had already done this three or four times) and I got back Recovery. I'm glad it got resolved but I wish that I knew what I did to fix it.
Anyway, thanks for the help bilgerryan!

OK, it appears that I have reproduced the problem. I had everything working, Recovery, Download, Boot on OK3 unrooted. Installed latest TWRP tar (2.8.4.0) and the problem returned. Reinstalled stock OK3 in Odin, same problem. Tried to Odin an earlier TWRP, same problem.
I'll just keep reinstalling OK3 stock until I (hopefully) get the stock Recovery back, then I'll try to isolate the step that caused the problem. I think next time I'll install CWM using Heimdall to see if that sidesteps the problem.

It appears that the phone will only boot into recovery about one time out of ten attempts, and even then it shows a red triangle while booting into recovery. This will make it impossible to install a custom recovery since you need to be able to be able to boot into recovery the first time after installing a custom recovery.
I've obviously got some sort of problem with the Recovery partition, not sure where to go from here.

Never did figure out why it doesn't reliably boot into Recovery. The only thing I was after on this particular phone was I wanted to enable the Native Hotspot. Was able to Root using Kingoroot, then enabled native Hotspot using SQLlite method. I'll save this recovery mystery for another day unless I stumble across the solution.

doraville said:
It appears that the phone will only boot into recovery about one time out of ten attempts, and even then it shows a red triangle while booting into recovery. This will make it impossible to install a custom recovery since you need to be able to be able to boot into recovery the first time after installing a custom recovery.
I've obviously got some sort of problem with the Recovery partition, not sure where to go from here.
Click to expand...
Click to collapse
The red triangle is simply stock recovery, it always shows that. Nothing wrong there. Don't use Kingo root. I've seen another person experiencing all kinds of problems after using it. Odin TWRP, it has a Root method that it implements when you reboot to system and then you just download SuperSU from the Play Store and you are rooted.

bilgerryan said:
The red triangle is simply stock recovery, it always shows that. Nothing wrong there. Don't use Kingo root. I've seen another person experiencing all kinds of problems after using it. Odin TWRP, it has a Root method that it implements when you reboot to system and then you just download SuperSU from the Play Store and you are rooted.
Click to expand...
Click to collapse
Yes, the problem is that when the phone will only boot into Recovery one out of ten tries it is very difficult (impossible?) to install a Custom recovery because you need to be able to boot into Recovery immediately after installing the Custom Recovery to prevent it from being overwritten with the stock recovery.
I haven't noticed any problems with Kingroot so far. This particular phone's only purpose is to serve as a Hotspot. As long as it will do that reliably I'll be happy with it.

doraville said:
to install a Custom recovery because you need to be able to boot into Recovery immediately after installing the Custom Recovery to prevent it from being overwritten with the stock recovery.
Click to expand...
Click to collapse
This statement is 100% false, stock recovery does not overwrite custom recovery ever unless you Odin stock. You don't have to immediately boot into Recovery either.

bilgerryan said:
This statement is 100% false, stock recovery does not overwrite custom recovery ever unless you Odin stock. You don't have to immediately boot into Recovery either.
Click to expand...
Click to collapse
Also make sure you uncheck Auto Reboot and F Time Reset in Odin before flashing recovery.

bilgerryan said:
This statement is 100% false, stock recovery does not overwrite custom recovery ever unless you Odin stock. You don't have to immediately boot into Recovery either.
Click to expand...
Click to collapse
I think that I am either misunderstanding you, or you are misunderstanding me, or both.
The installation instructions for both TWRP and CWM (see below) say the you must boot into Recovery immediately after installing the custom recovery, otherwise if you allow it to do a normal boot the stock FW will overwrite the custom Recovery IMG with the stock Recovery IMG. I'm pretty sure that I have witnessed this behavior so I don't think they made it up.
The problem that I have with this phone is that, for whatever reason, it will not boot into Recovery but maybe one out of every ten tries.
Not meaning to be argumentative here; I'm sure that we're just miscommunicating. I appreciate your trying to help.
CWM Instructions:
NOTE: Be sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot (appearing as though your custom recovery failed to install).
TWRP Instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

doraville said:
I think that I am either misunderstanding you, or you are misunderstanding me, or both.
The installation instructions for both TWRP and CWM (see below) say the you must boot into Recovery immediately after installing the custom recovery, otherwise if you allow it to do a normal boot the stock FW will overwrite the custom Recovery IMG with the stock Recovery IMG. I'm pretty sure that I have witnessed this behavior so I don't think they made it up.
The problem that I have with this phone is that, for whatever reason, it will not boot into Recovery but maybe one out of every ten tries.
Not meaning to be argumentative here; I'm sure that we're just miscommunicating. I appreciate your trying to help.
CWM Instructions:
NOTE: Be sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot (appearing as though your custom recovery failed to install).
TWRP Instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
So your problem would be solved by not allowing the device to boot. If it doesn't boot into Recovery, pull the battery and try again. Yeah I definitely was thinking about something else, once recovery is installed and you have booted into it it won't revert back to stock. That's the point I was getting to get across. Then once you do that either flash my 5 Way Reboot mod or download a Reboot app from the Play Store that will allow you to boot directly into Recovery and you shouldn't have any problems after that.

bilgerryan said:
So your problem would be solved by not allowing the device to boot. If it doesn't boot into Recovery, pull the battery and try again. Yeah I definitely was thinking about something else, once recovery is installed and you have booted into it it won't revert back to stock. That's the point I was getting to get across. Then once you do that either flash my 5 Way Reboot mod or download a Reboot app from the Play Store that will allow you to boot directly into Recovery and you shouldn't have any problems after that.
Click to expand...
Click to collapse
After thinking about it, with enough patience I should be able to get a custom recovery in there eventually. Then I should be able to use your mod or a Reboot app as you said. Good idea, thanks.
Of course, this still begs the question of why the phone refuses to boot into Recovery. As long as I'm able to work around it one way another I'd rather not go spelunking into the Recovery partition to try to fix it.

random reboot and unstable after rooting with cf-root

Hello,
I got my Galaxy s4 which was running fine (no reboot at all since i got it 6 months ago)....since i decided to root it, because i wanted to use titanium backup (to freeze the samsung update warning evertime you boot). I got Android Kitkat 4.4.2 and i dont want to update at all. Now i just want to restore back my stability, because now that i've installed the cf-root kernel, i got a lot of random reboots during one day! (a shame). I've just installed this: http://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip
The root itself was a success, but supersu ask about uninstalling knox, i told it to uninstall it and it's reported success too. What is causing the random reboots?
I've tried to disable the root, but it's the same.
My Android version number is:
KOT49H.I9505XXUGNJ6 (operator Orange stock ROM)
What should i do?

I don't think it deleted all knox apps.

GDReaper said:
I don't think it deleted all knox apps.
Click to expand...
Click to collapse
Why i have random reboot? What make it reboot? I dont understand. I have the right kernel version or not? This kernel version should be stable right? How can i restore my intial kernel?

Did you try removing supersu using the built-in uninstaller?
You could also re-flash a stock 4.4.2 ROM over the existing ROM. Re-flashing does not remove your data but it is always a good idea to back up your data using kies/smartswitch before re-flashing.

audit13 said:
Did you try removing supersu using the built-in uninstaller?
You could also re-flash a stock 4.4.2 ROM over the existing ROM. Re-flashing does not remove your data but it is always a good idea to back up your data using kies/smartswitch before re-flashing.
Click to expand...
Click to collapse
Yes, i have remove SuperSu with the integrated feature to uninstall itself. This morning i got a unwanted reboot when i used the power button to wake up the phone screen. I noticed it's often when i power/wake the phone that the reboot takes place. I got 2 times another symptom: instead of rebooting, i cannot use the touch screen, the screen is active but i cannot move and i can solve it by doing anoter power/ wake up button. Then it's magically working. I've never had the problem since i rooted the phone.

Could it be a problem with the power button? Try booting into recovery mode and leave the phone for about 5 minutes. After 5 minutes, use the volume buttons to move up and down and then press the power button to selection an option but not the reboot option to see if it reboots when you touch the power button.

audit13 said:
Could it be a problem with the power button? Try booting into recovery mode and leave the phone for about 5 minutes. After 5 minutes, use the volume buttons to move up and down and then press the power button to selection an option but not the reboot option to see if it reboots when you touch the power button.
Click to expand...
Click to collapse
I tried what you said, it's working as expected. It has nothing to do with my power button, it's a software issue with my rooted kernel or the SuperSu that has broke something when it has disabled Knox maybe.

Since it isn't a hardware issue, I would just re-flash a stock ROM using Odin after backing up.

audit13 said:
Since it isn't a hardware issue, I would just re-flash a stock ROM using Odin after backing up.
Click to expand...
Click to collapse
Ok, i've installed clockworkmod recovery and i did a backup into an external SD card. It took something like 2 hours (7GB of backup files). But now i have another issue with the backup from CWM: I cannot find the content of my camera inside the CWM backup. Where is it located into the CWM backup files? I can see browse the data partition backup when i browse the file "data.ext4.tar.a", but i cannot see any folder /data/media?

I forgot to mention somehting:
After doing your test under the stock recovery, i just did "reboot" under the recovery menu. And then i got the fabulous infinite "starting apps" screen. I cannot solve it now. Seriously, what the hell?

I thought the camera content was stored in the DCIM folder.
Personally, I do not use CWM as it has not been updated for a long time and many developers have moved to TWRP.
Looks like it stuck at the starting apps screen because a factory wipe may be required before the ROM will boot.

audit13 said:
I thought the camera content was stored in the DCIM folder.
Personally, I do not use CWM as it has not been updated for a long time and many developers have moved to TWRP.
Looks like it stuck at the starting apps screen because a factory wipe may be required before the ROM will boot.
Click to expand...
Click to collapse
TWRP can save the /data/media subfolder? Because it seems like CWM is not able to for some reason (that i'd like to know).
About my issue:
1)Ok i've solved the stuck at starting apps problem after hours of fight. Finally i could start again after i have flashed the original ROM file. I'd like to know how it solve the issue because i didnt wipe anything.
2)I still got random reboot and no touch screen sometimes. So it seems like the mess that was done by CF-ROOT kernel (maybe the Knox uninstall?) is still there, even after a ROM reflash. Oh MY GOD.
Is there an easy to way get back all my data after doing a factory reset? Because i think i'll have to do that because of that sucky CF-ROOT.

If you flash TWRP, you can boot into TWRP, mount the data partition, and copy files to the computer or insert a microSD card into the phone and copy it there.
Flashing a stock ROM flashes all partitions except the data partition and leaves all data intact. You could try wiping the only the cache from stock recovery to see if this resolves the reboot issue.
Could the reboot issue becaused by an app that was installed?
I have used CF autoroot a number of times and have never had it affect the touch or cause reboots.

audit13 said:
If you flash TWRP, you can boot into TWRP, mount the data partition, and copy files to the computer or insert a microSD card into the phone and copy it there.
Flashing a stock ROM flashes all partitions except the data partition and leaves all data intact. You could try wiping the only the cache from stock recovery to see if this resolves the reboot issue.
Could the reboot issue becaused by an app that was installed?
I have used CF autoroot a number of times and have never had it affect the touch or cause reboots.
Click to expand...
Click to collapse
I've tried 10x to wipe the cache.
How can an application could cause a reboot? How can i know what is the cause of the reboot?

What ROM was on the phone when you flashed cfautoroot? I assume it was a stock ROM and you flashed the correct version of autoroot.
Wiping cache works or doesn't work? Did TWRP install?

I flashed this kernel: http://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip
And my ROM is my operator ROM, the last 4.4.2:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I didnt install TWRP. And wipe cache works but it doesnt solve the random reboot issue.
I just want to know where i can find logs of the reboots? My phone is less stable than Windows Millenium now!

Hmm, looks like the file you flashed was for 5.01.
https://autoroot.chainfire.eu
I normally root phones with supersu and twrp.

audit13 said:
Hmm, looks like the file you flashed was for 5.01.
https://autoroot.chainfire.eu
I normally root phones with supersu and twrp.
Click to expand...
Click to collapse
I just follow this:
http://www.ibtimes.com.au/how-root-...l-android-442-kitkat-xxugng4-firmware-1349050
You say that they put the wrong kernel lol? Are you serious?
Anyways, as i mentioned, i flashed my ROM again. So i dont have any root and modified kernel.
Still i got random reboot.

I looked at chainfire's website and I only see 5.01, not 4.4.2 so maybe the file is only for 5.01 but I am not 100% sure.
If the file is for 5.01 and it flashed the 5.01 kernel, it may have messed up some of the apps and probably needs a factory wipe using stock recovery to fully boot the 4.4.2 rom.

audit13 said:
I looked at chainfire's website and I only see 5.01, not 4.4.2 so maybe the file is only for 5.01 but I am not 100% sure.
If the file is for 5.01 and it flashed the 5.01 kernel, it may have messed up some of the apps and probably needs a factory wipe using stock recovery to fully boot the 4.4.2 rom.
Click to expand...
Click to collapse
You say that it's the wrong kernel file, but it's not. It's the file that you will find on every tutorial for the CF-ROOT on 4.4.2. If it would be a wrong kernel, i couldnt even start the phone, it would boot at all.
That said, what's the best way to migrate data to save them before doing a wipe data/factory reset?

Stuck at loading screen after trying to go from LineageOs 14 to stock to Lineageos

So, in short:
I wanted to try the stock ROM on my Oneplus 5 now that it got an update to Oreo. I was going from Lineageos 14.1 to OOS 5.0.1.
Tried to flash it using TWRP, didn't work. . Found out I had to use an updated TWRP specifically for Oreo. Did that, got Codeworkx's TWRP and flashed it, and then the stock ROM. Stock ROM got stuck in loading screen for 20+ minutes. After that, everything was encrypted when I looked in TWRP. So I wiped everything. Also tried using the stock recovery. No dice, couldn't even install anything from internal storage. After trying a few things I wanted to go back to LineageOS 14.1 (same build as I had before), but now that one's stuck in loading screen as well for over 20 minutes.
Here are the things I've tried:
Using different recoveries, from Codeworkx's TWRP to Blu_spark's to the original TWRP. The Original TWRP recovery does not work anymore. Gives errors when trying to do things like wipe. Installing ROMs gives errors as well.
Tried installing just the ROM, and the rom + Magisk and the rom + magisk + open gapps. Always stuck on loading screen.
I'm trying to flash the latest ROM for Oneplus 5.
I'm trying to push more stuff onto the phone using adb, but right now I'm getting the "error: closed" error message.
The only thing I can try are flashing stock rom, then stock recovery and tehn locking the bootloader, but the latter will erase everything from the internal memory, and if I can't adb sideload stuff anymore, I'm not sure what I can do with the phone...
Edit: Another weird thing I noticed:
After it's been loading for 20+ minutes, the phone shows it's at 0% charge, then when I enter recovery, it's back to 100%. The phone is connected to my computer the whole time.
Edit 2: I tried to flash an android 7.1.1 version of OOS (OOS4) to my phone, this went fine. Booted up the phone, got an "encryption unsuccesful" error. On next boot, recovery is back to stock instead of TWRP. Flashing TWRP and then doing a factory reset has no effect.
These are the errors I see when I use the normal TWRP recovery (so not codeworkx's or blu_sparks' version:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you are updating the OP5 from Nougat to Oreo and you are encrypted you need to format the data on your phone. You can do it with TWRP (the option is part of the wipe tab). That will erase everything on your phone except TWRP. If you plug your phone into a computer it will act like an external hard drive and you can simply copy and paste the ROM zip onto your phone and then flash it with TWRP.
If you are decrypted you need to flash the no verity zip for OOS to boot up.

Thanks for the reply. I managed to get lineageos 15 running on the phone without problems. Not totally satisfied with it, so if/when I flash back to LineageOs 14.1 I'll keep this in mind. Thanks!

I can't install a ROM on my POCO M3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to install a ROM on my M3, the operation stops with an error.
First, I unlocked my M3, and flash the TWRP
Then I downloaded the ROM, and I attempted to install it.
But the operation was failed, and I changed with another ROM, because I thought the ROM was the cause of the problem.
The recovery in the screenshot is the PBRP, but I've tried it on TWRP, and the results are the same.
I think it's related to this problem, I couldn't select "System Partition" and "Product Partition" from the Mount menu,
and I couldn't find "System" option in the Wipe - Advanced menu.
Does anyone have a solution for this problem?

setimmm029 said:
View attachment 5370149
When I try to install a ROM on my M3, the operation stops with an error.
First, I unlocked my M3, and flash the TWRP
Then I downloaded the ROM, and I attempted to install it.
But the operation was failed, and I changed with another ROM, because I thought the ROM was the cause of the problem.
The recovery in the screenshot is the PBRP, but I've tried it on TWRP, and the results are the same.
I think it's related to this problem, I couldn't select "System Partition" and "Product Partition" from the Mount menu,
and I couldn't find "System" option in the Wipe - Advanced menu.
Does anyone have a solution for this problem?
Click to expand...
Click to collapse
Use Twrp
Format data***(not wipe)reboot recovery and check that unmount system etc before flash is not checked.
***Twrp->Wipe->format data write yes reboot Twrp

setimmm029 said:
View attachment 5370149
When I try to install a ROM on my M3, the operation stops with an error.
First, I unlocked my M3, and flash the TWRP
Then I downloaded the ROM, and I attempted to install it.
But the operation was failed, and I changed with another ROM, because I thought the ROM was the cause of the problem.
The recovery in the screenshot is the PBRP, but I've tried it on TWRP, and the results are the same.
I think it's related to this problem, I couldn't select "System Partition" and "Product Partition" from the Mount menu,
and I couldn't find "System" option in the Wipe - Advanced menu.
Does anyone have a solution for this problem?
Click to expand...
Click to collapse
Before installing romom, you must first install xiaomi eu A11, or NO_OSS_VENDOR-MIUI.21.7.21_A11_MIGRATION, and then install custom rom.

Hi. Could anyone solve this problem? I also get this error when try to install custom rom. Tried different roms and the result is the same : Error 1.... Tried Fox recovery. The result is the same. Tried different modified recoveries for Poco M3 from different sources ... the result is the same. Tried last updated fresh versions of both TWRP and FOX and the result is the same. But when I try to install stock Global rom by recovery it installs without any problem and error. Installed Global 12.0.10 without any issue. The problem is only with custom roms. I want to switch to Pixel rom but still can not do that.... If anyone could solve this issue please respond and explain the steps .
Thanks!

T511 said:
Hi. Could anyone solve this problem? I also get this error when try to install custom rom. Tried different roms and the result is the same : Error 1.... Tried Fox recovery. The result is the same. Tried different modified recoveries for Poco M3 from different sources ... the result is the same. Tried last updated fresh versions of both TWRP and FOX and the result is the same. But when I try to install stock Global rom by recovery it installs without any problem and error. Installed Global 12.0.10 without any issue. The problem is only with custom roms. I want to switch to Pixel rom but still can not do that.... If anyone could solve this issue please respond and explain the steps .
Thanks!
Click to expand...
Click to collapse
What is the code name of your device?
Did you format data write yes and reboot recovery?

NOSS8 said:
What is the code name of your device?
Did you format data write yes and reboot recovery?
Click to expand...
Click to collapse
Hi. Codename of my device (Poco M3) is "citrus'' . Yes I tried to format and typed yes then rebooted recovery. And the same error 1. I watched to many videos on youtube regarding this issue and read too many methods on different forums.... and none worked for me... Anyway after several tries I see that I cannot install custom rom I install stock global and installs without any issue or problem. The problem only with custom roms. From time to time I see or hear the new method... try it... and nothing. Continue to get error 1... After several tries reinstall stock global and waiting new method to try.....

T511 said:
Hi. Codename of my device (Poco M3) is "citrus'' . Yes I tried to format and typed yes then rebooted recovery. And the same error 1. I watched to many videos on youtube regarding this issue and read too many methods on different forums.... and none worked for me... Anyway after several tries I see that I cannot install custom rom I install stock global and installs without any issue or problem. The problem only with custom roms. From time to time I see or hear the new method... try it... and nothing. Continue to get error 1... After several tries reinstall stock global and waiting new method to try.....
Click to expand...
Click to collapse
Did you try to mount all partitions before flashing,?
did you try with this one https://androidfilehost.com/?fid=7161016148664800903?

The partitions may have been modified following multiple attempts, to reset everything to zero:
Try to flash the latest android 10 stock rom with miflash.(dont relock bootloader)
https://forum.xda-developers.com/t/guide-use-xiaomi-flash-tool.4262425/
Then flash the last Twrp (link above).
Format data yes reboot twrp

i have the same problem i tried all the proposed solutions but nonthing worked. Had anyone had any success?

setimmm029 said:
View attachment 5370149
When I try to install a ROM on my M3, the operation stops with an error.
First, I unlocked my M3, and flash the TWRP
Then I downloaded the ROM, and I attempted to install it.
But the operation was failed, and I changed with another ROM, because I thought the ROM was the cause of the problem.
The recovery in the screenshot is the PBRP, but I've tried it on TWRP, and the results are the same.
I think it's related to this problem, I couldn't select "System Partition" and "Product Partition" from the Mount menu,
and I couldn't find "System" option in the Wipe - Advanced menu.
Does anyone have a solution for this problem?
Click to expand...
Click to collapse
Flash xiaomi.eu_multi_POCO_M3_21.4.14_v12-11.zip rom using any custom recovery.
Havoc os works fine but dotos unable to boot always reboot to recovery.
I have tested on my poco m3 India variant.
Download link
2.65 GB file on MEGA
mega.nz

T511 said:
Hi. Could anyone solve this problem? I also get this error when try to install custom rom. Tried different roms and the result is the same : Error 1.... Tried Fox recovery. The result is the same. Tried different modified recoveries for Poco M3 from different sources ... the result is the same. Tried last updated fresh versions of both TWRP and FOX and the result is the same. But when I try to install stock Global rom by recovery it installs without any problem and error. Installed Global 12.0.10 without any issue. The problem is only with custom roms. I want to switch to Pixel rom but still can not do that.... If anyone could solve this issue please respond and explain the steps .
Thanks!
Click to expand...
Click to collapse
bro i had the same issue and finally i installed a custom rom. ok first format data
2- install
Download link
2.65 GB file on MEGA
mega.nz
( xiaomi.eu_multi_POCO_M3_21.4.14_v12-11.zip )
the link which
azimdotnet posted.​3- then you will see that it's installing normally when it finish flashing, DON'T reboot just flash any custom rom without doing anything after flashing this xiaomi.eu_multi_POCO_M3_21.4.14_v12-11.zip
then choose your custom rom ( mine was pixel ui ) and it worked fine i couldn't believe that it worked after all this time.
i'm using twrp-3.5.2_10-3-citrus-brigudav.img recovery.
hope this help.

azimdotnet said:
Flash xiaomi.eu_multi_POCO_M3_21.4.14_v12-11.zip rom using any custom recovery.
Havoc os works fine but dotos unable to boot always reboot to recovery.
I have tested on my poco m3 India variant.
Download link
2.65 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
you saved my life bro i flashed this zip first and then falshed my custom rom ( pixel ui) it worked great. bro thank you so much.
best wishes.

setimmm029 said:
View attachment 5370149
When I try to install a ROM on my M3, the operation stops with an error.
First, I unlocked my M3, and flash the TWRP
Then I downloaded the ROM, and I attempted to install it.
But the operation was failed, and I changed with another ROM, because I thought the ROM was the cause of the problem.
The recovery in the screenshot is the PBRP, but I've tried it on TWRP, and the results are the same.
I think it's related to this problem, I couldn't select "System Partition" and "Product Partition" from the Mount menu,
and I couldn't find "System" option in the Wipe - Advanced menu.
Does anyone have a solution for this problem?
Click to expand...
Click to collapse
bro look at my comment in the comment section and i hope it will work for you. best wishes

azimdotnet said:
Flash xiaomi.eu_multi_POCO_M3_21.4.14_v12-11.zip rom using any custom recovery.
Havoc os works fine but dotos unable to boot always reboot to recovery.
I have tested on my poco m3 India variant.
Download link
2.65 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
is this hosted somewhere else? mega is asking me to wait 5 hrs to download it completely