Database Develop

TWRP Recovery Problem..

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

[Troubleshooting] (CM 10.2) Stuck at boot screen after reboot

Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app

I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?

knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.

SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.

jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason

knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?

No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000

It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?

nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.

I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?

nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.

tried without the external SD card inserted?

nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000

SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?

knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000

SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!

SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..

I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".

So...which Stock Rooted ROM using to flash?...

heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000

[Q] Phone shutting down before the installation ends

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

[Q] Error while trying to flash CM.. (i9305t)

Im trying to flash a nightly build of CM 11/GAPPS on my Samsung Galaxy S3 (i9305t) it's running TWRP v2.6.3.0 which is the latest version on the TWRP site and this is the error I'm getting. I've wiped dalvik cache and cache and also did a factory reset before flashing CM and GAPPS this is the error I get while trying to flash CM..
Code:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip '/external .......
Error flashing zip '/external_sd/CM/cm-11- ...........
Updating partition details .......
[COLOR="Red"]Failed[/COLOR]
Hopefully someone can help me out with this, there is really no way I can update my TWRP because I'm on the newest version, there's another TWRP for the i9305 which is v2.7.0.0 but my phone is a i9305t..
Thanks for the help guys

Try flashing a different nightly maybe. You could also try flashing it from your internal SD.

ArkThompson said:
Try flashing a different nightly maybe. You could also try flashing it from your internal SD.
Click to expand...
Click to collapse
I tried flashing a different nightly and I also tried flashing from my internal storage. I still get the same error. Can anybody help me please?

Emre1994 said:
I tried flashing a different nightly and I also tried flashing from my internal storage. I still get the same error. Can anybody help me please?
Click to expand...
Click to collapse
Hmm, you should probably make a thread asking if it is safe to flash i9305 recoveries on your i9305t. If it is, then try flashing Philz recovery (http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953) and installing CM with that.

ArkThompson said:
Hmm, you should probably make a thread asking if it is safe to flash i9305 recoveries on your i9305t. If it is, then try flashing Philz recovery (http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953) and installing CM with that.
Click to expand...
Click to collapse
I kind of prefer TWRP I've used CWM and I don't really like it that much. It's taken me nearly 3 days to flash CM it shouldn't really take this long. I'm just trying to find a way to successfully flash it I don't really want to use another different recovery now.

Emre1994 said:
I kind of prefer TWRP I've used CWM and I don't really like it that much. It's taken me nearly 3 days to flash CM it shouldn't really take this long. I'm just trying to find a way to successfully flash it I don't really want to use another different recovery now.
Click to expand...
Click to collapse
You used CWM on your i9305t? I don't really see why it matters which recovery you use so long as it works, they all pretty much do the same thing.

ArkThompson said:
You used CWM on your i9305t? I don't really see why it matters which recovery you use so long as it works, they all pretty much do the same thing.
Click to expand...
Click to collapse
CWM gave me the same error, I'm not that fussed about recoveries at the moment. I'm trying to find out why it has taken me so long to flash something as simple as CM and why is it giving me these errors.
Thank you.

Emre1994 said:
CWM gave me the same error, I'm not that fussed about recoveries at the moment. I'm trying to find out why it has taken me so long to flash something as simple as CM and why is it giving me these errors.
Thank you.
Click to expand...
Click to collapse
The problem is definitely recovery related. Like I said before, try and find out whether you can flash i9305 recoveries on it and if so flash Philz. You could also try putting older versions of TWRP on it until you find one that works.

ArkThompson said:
The problem is definitely recovery related. Like I said before, try and find out whether you can flash i9305 recoveries on it and if so flash Philz. You could also try putting older versions of TWRP on it until you find one that works.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3/help-i9305/twrp-v2-6-3-0-i9305t-t2874745
I'm still waiting for a reply. And how would I downgrade TWRP to a older version? Just flash the file through odin?
Thanks.

ArkThompson said:
The problem is definitely recovery related. Like I said before, try and find out whether you can flash i9305 recoveries on it and if so flash Philz. You could also try putting older versions of TWRP on it until you find one that works.
Click to expand...
Click to collapse
I've just tried 3 previous versions of TWRP and I'm still getting the same error..

Emre1994 said:
I've just tried 3 previous versions of TWRP and I'm still getting the same error..
Click to expand...
Click to collapse
Which version of cwm did you try earlier?

ArkThompson said:
Which version of cwm did you try earlier?
Click to expand...
Click to collapse
I honestly forget but it was the version without the touch feature and it gave me a similar or exact error as what I'm getting now.

[Q] Stuck at Google logo

Ok, currently running CM12.1 nightly (20150704), CM kernel (build 04), and TWRP recovery (v2.8.7.1).
Everytime I've tried to update the ROM recently, it gets stuck at the Google logo. I've tried factory reset from TWRP and dirty flashing with the same result ... stuck at Google for >20 minutes. I'm able to power off the device, then reboot back into recovery and restore my backup with no problem, but I can't seem to update the ROM anymore.
Any ideas?

sundownls1 said:
Ok, currently running CM12.1 nightly (20150704), CM kernel (build 04), and TWRP recovery (v2.8.7.1).
Everytime I've tried to update the ROM recently, it gets stuck at the Google logo. I've tried factory reset from TWRP and dirty flashing with the same result ... stuck at Google for >20 minutes. I'm able to power off the device, then reboot back into recovery and restore my backup with no problem, but I can't seem to update the ROM anymore.
Any ideas?
Click to expand...
Click to collapse
I'd wipe everything, except internal, and flash fresh.

Evolution_Tech said:
I'd wipe everything, except internal, and flash fresh.
Click to expand...
Click to collapse
Already tried that. Stuck at Google.
Sent from my Nexus 6 using Tapatalk

sundownls1 said:
Already tried that. Stuck at Google.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Flash a factory image. Start over.

Evolution_Tech said:
Flash a factory image. Start over.
Click to expand...
Click to collapse
Did that too.
I was on 7-2 build, tried to update to 7-4 build and got stick at Google logo. Did some trouble shooting and comment figure it out, so I flashed a factory image / recovery and started completely from scratch. Rerooted, reinstalled TWRP recovery, etc. Then I installed 7-4 build from that, and haven't been able to update since.
I've tried all the normal things when you soft brick. Just can't figure this one out.
Sent from my Nexus 6 using Tapatalk

try updating your bootloader to the latest, then try reflashing everything. btw, latest bootloader https://www.androidfilehost.com/?fid=23991606952611906

simms22 said:
try updating your bootloader to the latest, then try reflashing everything. btw, latest bootloader https://www.androidfilehost.com/?fid=23991606952611906
Click to expand...
Click to collapse
Thanks. I'll give that a try on my next day off from work. That way I'll have plenty of time to rebuild in case I brick it again.
Sent from my Nexus 6 using Tapatalk