Sometimes when I boot in recovery I get a "no OS installed error". I have to reboot the recovery in order to fix it. Does that happen to anyone else? If so, do you know what causes it? It seems to have only started happening recently? Maybe it's the 4.2.2 roms?
SkizzMcNizz said:
Sometimes when I boot in recovery I get a "no OS installed error". I have to reboot the recovery in order to fix it. Does that happen to anyone else? If so, do you know what causes it? It seems to have only started happening recently? Maybe it's the 4.2.2 roms?
Click to expand...
Click to collapse
I haven't seen that before, sounds odd. Try reflashing recovery and wiping cache, also make sure you're updated to the latest CWM
MacHackz said:
I haven't seen that before, sounds odd. Try reflashing recovery and wiping cache, also make sure you're updated to the latest CWM
Click to expand...
Click to collapse
I use TWRP.
SkizzMcNizz said:
I use TWRP.
Click to expand...
Click to collapse
Well then... use CWM and see if the issue goes away
Related
Hello,
I'm currently experiencing a problem where my phone keeps rebooting about every 30 seconds after boot. I'm using the CM11 rom from the cyanogenmod website and have tried like 5 different roms. I am using cwm 6.0.4.8 and have been flashing stock Paranoid GAPP 4.4.2. I have been factory resetting, clearing cache, and dalvak before flashing any of the roms and still the problem persists. Can anyone help?
Thank you!
LameJae said:
Hello,
I'm currently experiencing a problem where my phone keeps rebooting about every 30 seconds after boot. I'm using the CM11 rom from the cyanogenmod website and have tried like 5 different roms. I am using cwm 6.0.4.8 and have been flashing stock Paranoid GAPP 4.4.2. I have been factory resetting, clearing cache, and dalvak before flashing any of the roms and still the problem persists. Can anyone help?
Thank you!
Click to expand...
Click to collapse
Try using TWRP by tdhite - it has better support for CM roms. http://forum.xda-developers.com/showthread.php?t=2651035
StormyNight said:
Try using TWRP by tdhite - it has better support for CM roms. http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
Thank you! Will try
LameJae said:
Thank you! Will try
Click to expand...
Click to collapse
By the way if you can't download the latest version, go to http://goo.im/devs/tdhite/twrp2 and click on the one that's 2.7.1.2.
StormyNight said:
By the way if you can't download the latest version, go to http://goo.im/devs/tdhite/twrp2 and click on the one that's 2.7.1.2.
Click to expand...
Click to collapse
I got the TWRP recovery to work, but the problem persists. I tried flashing a bunch of different CM11 roms and none of them work. What am I doing wrong?...
LameJae said:
I got the TWRP recovery to work, but the problem persists. I tried flashing a bunch of different CM11 roms and none of them work. What am I doing wrong?...
Click to expand...
Click to collapse
Which one are you flashing? Could you link it please? The rebooting problem mainly occurs when you're flashing a GSM ROM on a CDMA device (like the Sprint HTC One M7)
If you're all out of options, http://forum.xda-developers.com/showthread.php?t=2503646 is a pretty surefire method of getting your device fixed up, although you might lose internal storage etc. as this is pretty much a factory reset but via flashing.
I had this problem as well. Turns out my SU Binary needed to be updated. Try updating that by going into SU and it should give you the option to update. That fixed the issue for me.
Hello. I have a little problem with CWM/TWRP... When I'm flashing a zip the phone reboots before the installation ends (or when starting flashing) and the zip isn't flashed. Has anyone any ideas? :crying:
Stachura5 said:
Hello. I have a little problem with CWM/TWRP... When I'm flashing a zip the phone reboots before the installation ends (or when starting flashing) and the zip isn't flashed. Has anyone any ideas? :crying:
Click to expand...
Click to collapse
What are you trying to flash?
fastboot erase cache
Ajxx16 said:
What are you trying to flash?
Click to expand...
Click to collapse
A kernel
Prophet16 said:
fastboot erase cache
Click to expand...
Click to collapse
I did fastboot erase cache but it didn't help
It might be because of the zip file, try checking the md5 checksum to make sure it downloaded properly. Or try flashing another rom so see if that one installs. I've had similar issues with bad downloads before.
Prophet16 said:
It might be because of the zip file, try checking the md5 checksum to make sure it downloaded properly. Or try flashing another rom so see if that one installs. I've had similar issues with bad downloads before.
Click to expand...
Click to collapse
I mean... I'm installing a kernel that has Aroma Installer and when I end setting it up and click Install the screen goes black after half a second and my phone reboots it self
Stachura5 said:
I mean... I'm installing a kernel that has Aroma Installer and when I end setting it up and click Install the screen goes black after half a second and my phone reboots it self
Click to expand...
Click to collapse
Ah that has happened to me a couple times. I think it's an aroma problem, though I thought it was fixed a long time ago. Usually for me all I have to do is switch to TWRP instead of using CWM. But if you have already tried both recoveries and nothing has worked then I guess you should try installing another kernel to make sure that you can indeed install kernels with aroma installer. I'm not sure what else to say besides try other kernels and recoveries. Sometimes you may have to flash over and over again till it works.
Prophet16 said:
Ah that has happened to me a couple times. I think it's an aroma problem, though I thought it was fixed a long time ago. Usually for me all I have to do is switch to TWRP instead of using CWM. But if you have already tried both recoveries and nothing has worked then I guess you should try installing another kernel to make sure that you can indeed install kernels with aroma installer. I'm not sure what else to say besides try other kernels and recoveries. Sometimes you may have to flash over and over again till it works.
Click to expand...
Click to collapse
I found the solution... It was ARHD fault I installed ViperOne without any problems and then I could install kernels too
I have correctly installed the custom recovery onto my X1063, however the recovery will not work. I can get into it, but if I try to install a rom or do a backup it fails and reboots. Has this happened to anyone else? And how do you fix it? Thank you!
philkim423 said:
I have correctly installed the custom recovery onto my X1063, however the recovery will not work. I can get into it, but if I try to install a rom or do a backup it fails and reboots. Has this happened to anyone else? And how do you fix it? Thank you!
Click to expand...
Click to collapse
That's very vague. Which recovery (including version)? Please describe your steps exactly. Also post exactly the error messages.
my phone 626s has the bootloader unlocked, it's rooted and has custom recovery but i have and update i cant install because whenever i try it boots into cyanogen mod recovery and does nothing. So i need to revert to stock recovery install the update and re install the custom recovery. I appreciate any help, thanks in advance.
thehunter8478 said:
my phone 626s has the bootloader unlocked, it's rooted and has custom recovery but i have and update i cant install because whenever i try it boots into cyanogen mod recovery and does nothing. So i need to revert to stock recovery install the update and re install the custom recovery. I appreciate any help, thanks in advance.
Click to expand...
Click to collapse
What update are you looking to install?
kdayyy said:
What update are you looking to install?
Click to expand...
Click to collapse
It's a system update, the notification is driving me crazy...
thehunter8478 said:
It's a system update, the notification is driving me crazy...
Click to expand...
Click to collapse
Turn off the update. And why would u need u need stock recovery? Anyway here's the link for stock recovery https://mega.nz/#!sp0wCThZ!MQVTq6y_8DJShrvNrY4L-JtJBDHOQhnaLRq8UiqLruQ
thanks
thehunter8478 said:
thanks
Click to expand...
Click to collapse
No problem you can download flashify or rashr app to flash it.
kdayyy said:
No problem you can download flashify or rashr app to flash it.
Click to expand...
Click to collapse
so i dont have to do it through cmd? I can just flash it? cool
i think i bricked it... it started the update fine but when it was done i got a warning sign inside the picture of the phone and it wont even turn off.... Never mind my mistake i guess it was still updating it rebooted now its fine.
now wifi wont turn on at all.... today is not my day. Tried erasing cache, removing the sd card, tried turning on wifi hotspot and airplane mode... dont know what else to do.
thehunter8478 said:
now wifi wont turn on at all.... today is not my day. Tried erasing cache, removing the sd card, tried turning on wifi hotspot and airplane mode... dont know what else to do.
Click to expand...
Click to collapse
Factory reset or download RUU stock rom and run it. What carrier are u with?
kdayyy said:
Factory reset or download RUU stock rom and run it. What carrier are u with?
Click to expand...
Click to collapse
Yeah i finally had to do that, thanks now everything is fine. It's my ocd i cant see notifications they drive me nuts when i cant get rid of them.
thehunter8478 said:
Yeah i finally had to do that, thanks now everything is fine. It's my ocd i cant see notifications they drive me nuts when i cant get rid of them.
Click to expand...
Click to collapse
No worries. Who wants a broken ROM?
Yeah... now i have twrp seems better than the cyanogen mod recovery, more complete.
Keep in mind that you can always freeze or uninstall the updater altogether. This can be done with your app manager of choice with root access to system apps. I completely uninstalled the updater as you can see in the screenshots
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
panamera2011 said:
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
Click to expand...
Click to collapse
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
bfürbanane said:
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
Click to expand...
Click to collapse
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
panamera2011 said:
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
Where does it say to install SuperSU? How would that be possible when Android is not booting.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
I'm sorry but it's really strange, never had installation issues with any version of this rom
Have you tried this kernel to install the rom?
https://www.androidfilehost.com/?fid=24052804347829437
Sent from my H60-L02 using Tapatalk
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Sorry but I confused the message with the MIUI 6.2.12 thread [emoji16]
Sent from my H60-L02 using Tapatalk
AutumQueen92 said:
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
Click to expand...
Click to collapse
I tried that. I went to samsung-updates.com and downloaded a version that I believe is compatible with my baseband version. Is there any way to check what baseband version my phone has? Then I flashed with odin and was stuck in a bootloop. I then flashed PhilZ recovery and the boot hangs at the samsung logo.
bfürbanane said:
Is there any way to check what baseband version my phone has?
Click to expand...
Click to collapse
Settings>about phone>
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
The phone is not booting.
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
Doh! sorry not reading what's in front of me. I did once read that you can get phone number via ADB, maybe the same will work for baseband?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
N00b... said:
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
Click to expand...
Click to collapse
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
bfürbanane said:
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
Click to expand...
Click to collapse
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Condox18 said:
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Click to expand...
Click to collapse
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
same problem
bfürbanane said:
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
Click to expand...
Click to collapse
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Condox18 said:
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Click to expand...
Click to collapse
Thanks for the pointer. I subscribed myself to that thread.