Flashed a new recovery over, tried to install supersu from a rooting process. Rebooted into recovery then backed up rom, formatted everything etc. tried to install several different roms using TWRP and Clockwordmod. CWM gave me a status 7 error and TWRP gave me the error updating binary script. It also said that i had no root and would like to install super su to root it. i said yes and then rebooted and it still did nothing. the only thing i can install are GAPPS files and files that ARENT ROMS. Im stuck and I need desperate help on how to fix this. ODIN wont flash the stock rom thats a tar file but will flash recoveries. PLEASE HELP ME
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
Trying to figure this out. Browsed forums for the last 24 hours, unable to come up with a way to figure it out. I was running Effortless rom, and older version that I can't remember, but it was on NF6 firmware. I wanted to play around with cm11 so I decided to flash back to stock NF6 then update to NF9 for the VOLTE update just to have it. So I triangled away, wiped then rooted and installed TWRP via ODIN, made a backup, everything went fine. Then I downloaded cm11 and gapps 4.4.4 and put them on my internal sd and went to flash in TWRP but cm11 was giving me errors. I figured it may have been TWRP so i decided to flash CWM but no go. It wouldn't stick. Tried again, no luck. Downloaded ROM Manager and this time I installed CWM through there. Tried rebooting in to recovery and ended up getting stuck in the "recovery booting" bootloop, so I flashed stock NF9(since I was on this firmware now) and tried installing CWM again, no luck. When I tried booting to recovery, it was stock NB4 recovery. I'm thinking that I'm stuck on an old bootloader and the recovery isn't NF9, which is the current stock recovery. I'm thinking that the reason why I'm unable to flash anything in TWRP/unable to install CWM at all is because of the stock recovery and possibly bootloader being NB4 for some reason while my baseband and build are both NF9. Any ideas/help would be appreciated. Thanks guys.
re: custom recovery
pyr0path said:
Trying to figure this out. Browsed forums for the last 24 hours, unable to come up with a way to figure it out. I was running Effortless rom, and older version that I can't remember, but it was on NF6 firmware. I wanted to play around with cm11 so I decided to flash back to stock NF6 then update to NF9 for the VOLTE update just to have it. So I triangled away, wiped then rooted and installed TWRP via ODIN, made a backup, everything went fine. Then I downloaded cm11 and gapps 4.4.4 and put them on my internal sd and went to flash in TWRP but cm11 was giving me errors. I figured it may have been TWRP so i decided to flash CWM but no go. It wouldn't stick. Tried again, no luck. Downloaded ROM Manager and this time I installed CWM through there. Tried rebooting in to recovery and ended up getting stuck in the "recovery booting" bootloop, so I flashed stock NF9(since I was on this firmware now) and tried installing CWM again, no luck. When I tried booting to recovery, it was stock NB4 recovery. I'm thinking that I'm stuck on an old bootloader and the recovery isn't NF9, which is the current stock recovery. I'm thinking that the reason why I'm unable to flash anything in TWRP/unable to install CWM at all is because of the stock recovery and possibly bootloader being NB4 for some reason while my baseband and build are both NF9. Any ideas/help would be appreciated. Thanks guys.
Click to expand...
Click to collapse
If I were you the first thing I would do is to ODIN flash TWRP recovery
and go from there.
Here is a direct download link for the latest odin flash twrp
custom recovery for the N900T Note 3:
https://app.box.com/AndroidShare
Once you get into twrp recovery do a complete wipe
which includes wipe data, system, cache, dalvik and
last but not least do a factory reset in twrp.
When that's done odin flash the official stock N900T NF9
firmware which can be found at http://SamMobile.com
After that's done you will need to odin flash cf-autoroot
and then odin flash twrp recovery again.
Here is the download link for cf-autoroot:
https://app.box.com/s/rgovggya5gkc51lc1uax
Then simply copy your favorite N900T zip file rom into
your internal sd and flash the N900T rom of your choice.
Be sure to do a full and complete wipe again before
flashing any custom roms.
Good luck!
i have flash Root and not working and i try alot but also not working can someone tell me what should i do?!?!
You tried flashing latest stable SuperSU via recovery?
Just download the latest stable SuperSU here and put on ExtSD... Reboot into Recovery Mode, install zip and select the "SuperSU.zip", restart the phone and check if rooted.
I have rooted my Samsung Tab 3 SM T-110 running kitkat 4.4.2 an year back and flashed CWM but i forgot about it so what i did was flashed CWM again but it didn't flashed properly i guess and i didn't remember that i installed CWM instead of TWRP so after downloading CWM ROM Manager i rather selected TWRP... Then i booted into recovery mode through the ROM Manager app and now i am not able to go back to system.... I have tried factory reset and formatting dalvik cache but nothing seems to work, the phone gets back to the recovery screen... Please Help.
Thank You
install latest recovery for your device and flash it using odin.
Should fix your issue and boot your device to touchwiz
On the SM-T110/111 is only allowed to Boot Ingo Recovery with the Button Combi, if you try an automaticly Reboot by APP you have an Bootloop to the Recovery