Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?
No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app
Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?
Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards
I'm trying to put a rom on a tm-sm217s
i flash twrp, boot right to recovery and flash the rom.
no dice. it boots right back to the stock sprint touchwiz rom. however, there are some odd app- that would be with the non-samsung rom now installed. they don't work- no root.
go to boot back to recovery, can't need to goto bootloader and reflash twrp.
any ideas wtf i'm doing wrong?
I flashed a new rom yesterday and tried to go back and flash a kernel but I can't get into recovery. Just a black screen 705 fastboot
I installed twrp and tried reinstalling recovery but still didn't work
Ideas?
dakoop said:
I flashed a new rom yesterday and tried to go back and flash a kernel but I can't get into recovery. Just a black screen 705 fastboot
I installed twrp and tried reinstalling recovery but still didn't work
Ideas?
Click to expand...
Click to collapse
Twrp should still be there. That rom you installed probably had a incompatible kernel which is what is sending you into fastboot. If you cant get into recovery for some off the wall reason flash back to stock with a tot or kdz.
any off the wall ideas on how to get into recovery
dakoop said:
I installed twrp and tried reinstalling recovery but still didn't work
Click to expand...
Click to collapse
Am I to understand this as you installed the TWRP Manager apk? Or do we read this as TWRP is the recovery you had originally installed? (Not trying to be funny here)
If the TWRP Manager was used from within the ROM, instead, use Flashify to reflash the recovery, not TWRP manager. Get the IMG file from HERE first, and tell flashify where you saved it.
If you are completely unable to boot as well as not access recovery, you will have to start from scratch. Follow THESE instructions to get back to stock and start over. (Choose Restoring Stock/Removing Root Flag)
I recently flashed CM12.1 on my S3. I was running rooted stockmod 4.3. Everthing went fine. I made a nandroid first. I was able to flash back to with my nandroid and then back to a nandroid of CM12. I tried to flash back again and booted into Touchwiz ROM with no Google services and most of many (too) many apps gone. I then tried to flash back to my CM12 Lollipop nandroid in recovery and got stuck in a bootloop. I could not get past the the Teamwin screen.
Even though my USB port is dicey I was able to use ODIN on my pc to flash back to stockmod_root 66. I then installed TWRP using TWRP manager on device. This went fine.
I then tried to flash back to CM12 in recovery using my nanback but the phone reboots after a few seconds with any task, even just wiping partitions. I am also now getting an error message after trying to load the same stockmod I used successfully earlier. The message is in Chinese so I have no idea what it says.
Any hope here?
Edit: I managed to load the stock image in ODIN and it is flashing now. Still do not understand what did wrong so as not to be able to restore my nan back of CM12. Was there a problem with my installation of TWRP with TWRP manager?
Thanks
So i was trying to flash hacker kernel
It bootlooped.
So i reflashed renegade and tried reflashing.
it rebooted
now everytime i try and flash anything it reboots
super su is missing.
I installed super su from play store
when i go to flash binaries it reboots.
I updated TWRP
still same thing.
If i flash anything it just boots back to recovery.
Any thoughts?
Flashed back to stock and rerooted.
Did the trick.
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
koop1955 said:
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
Click to expand...
Click to collapse
No I had previously been rooted fine and dandy. for some reason TWRP started just rebooting on any flash.
so is it not going into bootloop mode anymore? because i've been having this problem for the last 6 months. i thought i'd try again and still doing the same, it'll get to the setup at the beginning and then reboot back to twrp????