I consider myself quite knowledgeable at flashing etc but while devloping my app (Carbon Tweaks) I have experinced something i havent seen before. If i try to boot into recovery normally its cwm. And by any other method thats where i go. But recently most likely after one of my flashes if i use a piece of code in my app to tell recovery to flash a zip on reboot into it, it boots me into a weird mess. The image in the centre is a combination of about 4 different recovery images (From previous kernals) and the progress bar is a mass of multicoloured lines. My flash errors with a status 7 and the menu for stock recovery comes up with onlt the normal Un-cwm options. If i then click reboot system it will hang until i hold down the power and on turning backon with reboot into cwm recovery.
I literally have no idea what it is o.o I'm able to flash fine in regular cwm, Some zips flash fine in the weird stock mess so any help would be great
I'm on liquid smooth with franco r4 for the record
Related
I installed CM6 stable on my N1 after performing a nand backup. I restored to the original rom today to check something out. Now I can't boot into recovery. I get the exclamation android Guy. I used amonRA. Any suggestions?
i've got the same error and i tried with awrecovery.img instead of recovery-RA-nexus-v1.7.0.img and its working
forum.xda-developers.com/showthread.php?t=636795
I think the stock ROM flashes stock recovery when you reboot. You are actually in stock recovery when you see that screen. Try hitting the volume down and power buttons at the same time. Same exact thing happened to me.
I just decided to skip the stock ROM for that reason.
I bet there is a workaround for it though.
One work around would be to flash recovery using rom manager.
pwig is right, you replaced your recovery with the stock one.
You need to re-root (if the stock isn't rooted - which I believe it isn't, since the only builds that include recovery are completely stock), and after rooting re-flash the recovery with Amon_RA's recovery.
So the phone tunred black screen when 1 day i was trying to turn off the wifi( if i remember correctly),
and then i started it again using power button, after showing the logo and boot animation, sunddenly it(sometimes during the boot animation) turned black screen and dead.
I got to recovery successfully and installed again the last custom rom(paranoid rom 3.x) and gapps i installed couple of days ago, and then reboot , same thing happened, couldnt get past the boot animation,, done factory rest, wipe everything and installed the last rom and gapps, same thing. (it's the only rom i had on my internal /sdcard which in the recovery i can browse through with no problem)
i tried to push another rom to /sdcard/ using adb, i can see my device under "adb devices" fine but it gave me "unauthorized devices" error.
then i downloaded the latest stock rom(4.1.2) and flashed using odin, flash completed successfully but still again same thing happens, cant get past the samsung boot animation.
----
after flashing the stock rom, now i cant even get into recovery,... and it seems there's no flashable recovery tar file for n7000.,...
any ideas?
thanks in advance
There is a tar flashable kernel. Philz
nokiamodeln91 said:
There is a tar flashable kernel. Philz
Click to expand...
Click to collapse
thanks for the reply!
i flashed the recovery using odin, but still cant get into it
then i accidently found that i can get into recovery mode when usb plugged in,,, but if i try to flash in that recovery mode, it will fail and end in black screen..
guess im completely fked and maybe it's due to some weird, hard-to-replace, unexpected, hardware problem,,,
In the Philz CWM recovery, are you able to format data and cache partitions?
nokiamodeln91 said:
In the Philz CWM recovery, are you able to format data and cache partitions?
Click to expand...
Click to collapse
yeah , i was able to,,,
and also i was able to mount the storage to my desktop and copied a couple of roms and recovery to it
but still cant flash them in the recovery casue black screen will occur druing the "installing update" phase, before any of the process bar was even filled
Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
samcool55 said:
Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
Click to expand...
Click to collapse
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
rog_star said:
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
Click to expand...
Click to collapse
Tried that, but UKF says device unsupported, don't know why... I have used it before and it worked then.
Any other options?
I got it fixed. But tbh i still don't understand how. I flashed JB stock with odin and when it rebooted, i got automaticly into CWM weirdly enough... Wasn't going to waste my maybe only chance so i flashed the custom rom, wiped everything again, reboot, went again automaticly into CWM. anyway i was third time lucky and it booted as it should. Everything is working now! Anyway thanks for trying to help.
Hello!, my device is GT-i9305 and i seem to have a problem of some sort. (I have had three devices before this and installed lots of custom roms, but never have i encountered something like this)
Whenever i try to install a custom rom (omnirom/pacrom/cyanegenmod) i get stuck in the splash/boot screen animation, but when i flash back to stock rom (4.4.4) using odin it loads up and everything works like its supposed to.
I have tried using TWRP and CWM-recovery. (With CWM i can get omnirom to boot, but i wont be able to dial or use mobile-data etc. (Seems like my efs files or something are missing) and i also get some error message about androidcore or somethinglikethat.
Most common fixes for this in the forums are to wipe dalvic and cache after installing. Which i have done + some other odd "fixes" i found.
I am really baffled. Whats wrong?
Did you flash TWRP 2.8.7.0? That recovery is buggy and does not work. You have to stay on 2.8.5.0 for the moment. There are people already trying to fix the faulty recovery. CWM won't get any updates anymore. It does still work but you might come across some ROMs which won't work with CWM.
To start all over again with no issues: flash 4.4.4 Stock, install TWRP 2.8.5.0 and you're good to go
Thankyouthankyouthankyou
That totaly fixed it! Thank you sooooo much, no more sleepless nights because of this.
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
gebauer said:
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
Click to expand...
Click to collapse
I suspect that your device is boot-looping on custom ROMs because there is incompatible stuff on your /data partition. The data partition needs to be wiped and you can't really do that with ODIN. You need to find a custom recovery that allows you to flash using ODIN and that is compatible with the custom ROM you are trying to flash. You also need to wipe /data (format it) before your first boot. You will loose all your info, even the stuff that was in your internal sd but the device should boot.
BUT:
I note that you said your HOME button is not working and that is required to manually boot into recovery. Additionally, with out a booting ROM you can not issue the "adb reboot recovery" command which would do it for you. There is a trick that I have learned but I only know how to do it with "heimdall" in the Ubuntu Terminal.
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
The partitions for the kernel and recovery on this device are typically kernel and kernel2 respectively.
kernel -> kernel
recovery -> kernel2
So:
recovery -> kernel ( Will boot recovery on a normal boot ).
I hope I have explained this well enough. You are going to have to do some learning if you want to get this working. Good luck.
P.S. If you are thinking of asking follow questions, don't, Google it instead.
Heimdall: http://glassechidna.com.au/heimdall/
Meticulus said:
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
Click to expand...
Click to collapse
Dear Meticulus,
thanks a lot for your help. I was away for the week-end; thus the late reply.
With your help it took me only an hour to get my smartphone working again. The main tipps, which helped me was the Heimdal tool, which I wasn't aware off and the possibility to flash the recovery directly into the kernel...
It worked like a treat. The smartphone booted into TWRP directly, which finally gave my access to wipe the data partition.
It took a couple of trials before I was able to flash an android image back to the kernel/system but this also worked nicely.
So thanks again and this brick is solved :good:
Jan