Related
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
hey all, im stuck running the jedi elite rom (apps constantly FC, laggy, bulky) and so I downloaded AOSB rom. I booted into recovery, which was TWRP 2.6.3.8 i believe, maybe .9. I made a full backup, then I tried to install TWRP 2.7. I flashed the .zip file from the official site, then after flashing, i went to main menu, reboot, then i hit recovery. when it went to reboot into recovery, it got stuck on the black startup screen, it says
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Click to expand...
Click to collapse
this didnt bother me, as thats what it normally says when it boots up, but this time it was stuck. I downloaded Odin 3.09, then downloaded the TWRP 2.7 .tar and installed that, it booted into my old rom, and i tried to boot into recovery from there, same result. I used odin to boot back into the rom, downloaded goomanager, and downloaded the older 2.6.3.9 recovery and everything installed fine as far as i can tell, rebooted into recovery, nothing. I used odin to flash a CWM recovery, same results. It seems recovery is broken. Can anyone help me? I just want stock, AOSP android, tired of TouchWiz's bullcrap.
bump
Sent from my SM-N900T using XDA Premium 4 mobile app
Version 2.7 of TWRP requires that you have the new 4.4.2 bootloader. Have you installed the new 4.4.2 bootloader?
If not, then downgrade your TWRP version to the previous one.
ah, no I haven't. How do upgrade the bootloader? And am I fine to flash the 4.4.2 AOSB ROM on TWRP 2.6.3.9?
Sent from my SM-N900T using XDA Premium 4 mobile app
I tried to root my device, everything was fine, I was running my tablet normally. Than SuperSU asked to updated binary with CWM. I hit okay, than it opened the recovery, updated binary and rebooted. Only issue is, it rebooted into recovery mode, and that's all I've been able to boot into since. I've tried reflashing a stock ROM and a custom ROM. Nothing is working and I don't know what to do.
iTys206 said:
Than SuperSU asked to updated binary with CWM. I hit okay, than it opened the recovery, updated binary and rebooted. Only issue is, it rebooted into recovery mode, and that's all I've been able to boot into since. I've tried reflashing a stock ROM and a custom ROM. Nothing is working and I don't know what to do.
Click to expand...
Click to collapse
You have got a bootloop to the Recovery, to solve the prob, flash Stockrom,
Than you can try to flash a Custom recovery TWRP, root your Tab , flash a Custum rom and flash Stockrecovery.
For Information check the Thread at the Dev section.
I'm on the latest TWRP (2.8.7.0) and after flashing a custom rom, no matter what it is (Bliss, DN4, CyanideL), it always boots up to recovery (TWRP or stock. Haven't tried CWM). The only way I found to fix it on Bliss is to use CF-Auto Root via Odin and it boots up normally for some reason. But if I try to update that ROM, it has the issue again. DN4 doesn't boot at all no matter what I try.
Any idea how to fix this? I'm on I317M
jokkir said:
I'm on the latest TWRP (2.8.7.0) and after flashing a custom rom, no matter what it is (Bliss, DN4, CyanideL), it always boots up to recovery (TWRP or stock. Haven't tried CWM). The only way I found to fix it on Bliss is to use CF-Auto Root via Odin and it boots up normally for some reason. But if I try to update that ROM, it has the issue again. DN4 doesn't boot at all no matter what I try.
Any idea how to fix this? I'm on I317M
Click to expand...
Click to collapse
Didn't see you try to downgrade the recovery to the last one? Might help fix your problem...
Or you can try using Odin back to stock. And start over with everything fresh.
Now Dn4 not booting, only means you need to flash Agni kernel afterwards. Get it here>Agni kernel downloads.
Good luck.
I had the same problem. TWRP 2.8.5 is the last version that doesn't have this problem on the i317m.
Just wanted to say thanks to @phzi . Same problem, downgraded to TWRP 2.8.5 fixed issue.
Hi, i'm having trouble flashing back to stock.
I've got the latest stock firmware from sammobile.
Using twrp to install it says missing META-INF as the firmware zip isn't made the same as custom firmware.
Adding the tar.md5 to ap in odin flashes the boot and recovery but goes extremely slow when it starts flashing system (left it 2 hours and it hadn't even got half way) I'm guessing that's not normal.
I took a backup with twrp before I started flashing in twrp which flashes fine but I get endless boot loop when trying to start it.
I've tried fastboot but it doesn't detect the tablet.
I've tried different usb ports, cables, different versions of odin and different stock firmware. I'm ready to throw it out the window.
One thing to note is the [P600][Touchwiz] Marshmallow Rom 20170622 works great but also boot loops when I turn it off and on again, I have to boot into twrp then choose reboot in there and then it boots ok, that doesn't work with my twrp backup though.
Anything I'm doing wrong?
Thanks.
Well for some reason after installing marshmallow rom again then installing my backup it boots fine, havn't a clue why it failed to boot the other 4 times.
Nope
Back to continuous boot loop after second reboot.
All I did was turned developer options off and it's boot looping again.
Flashed original stock boot.tar.md5 and recovery.tar.md5 then factory reset and wiped cache but still boot loops.
Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?
Mazert said:
Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?
Click to expand...
Click to collapse
I'm not quite sure what your problem is but you should be able to downgrade, I've done it before.
Try this guide first. I've had success with it.
If all goes well you can then try to flash your stock ROM. The one I've flashed successfully in the past is the one in this post.
Good luck!
You may need to repartition your system. Tick the repartition in Odin. **All data will be lost**
Sent from my SM-N915G using Tapatalk
Thanks, I followed the guide in that post and it flashed ok then I finally managed to flash the latest stock!