Hi guys I am new here and here is my problem. After using twrp for some days I just installed cwm via fastboot but I don't know why In some app(flashify, rom manager) it's not showing that I have cwm installed though when I go to recovery it starts cwm everytime........... ?
riley jes said:
Hi guys I am new here and here is my problem. After using twrp for some days I just installed cwm via fastboot but I don't know why In some app(flashify, rom manager) it's not showing that I have cwm installed though when I go to recovery it starts cwm everytime........... ?
Click to expand...
Click to collapse
The apps aren't perfect, they are made to work on all devices, they won't behave the same on every device.
By the way, I suggest you forget all about ROM Manager, it is well known for bricking devices.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Custom recovery will not go whereas supersu will go.
The only possible way where your custom recovery is gone is when you brick your device. Either it may be soft or hard.
Thanks to all
riley jes said:
Hi guys I am new here and here is my problem. After using twrp for some days I just installed cwm via fastboot but I don't know why In some app(flashify, rom manager) it's not showing that I have cwm installed though when I go to recovery it starts cwm everytime...........
Click to expand...
Click to collapse
I don't think my device get brick. Anyway, thanks to all for replies. I just got to know that some cwm recovery not show on apps. My phone working fine and the recovery too. Thanks for the help.?
alex930492012 said:
Custom recovery will not go whereas supersu will go.
The only possible way where your custom recovery is gone is when you brick your device. Either it may be soft or hard.
Click to expand...
Click to collapse
Not true, custom recovery can and does get wiped out accidentally sometimes, it's usually due to user error though.
It just didn't get wiped in this member's case.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Related
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.
Can some one help me please im having trouble with rooting my xoom. i have downloaded and saved everything i was told i needed to root the device to the device and memory card but when i try to load the recovery console i get the android with the red x over it.
Any help is welcome.
ramhuskies7 said:
Can some one help me please im having trouble with rooting my xoom. i have downloaded and saved everything i was told i needed to root the device to the device and memory card but when i try to load the recovery console i get the android with the red x over it.
Any help is welcome.
Click to expand...
Click to collapse
You can not flash a custom recovery from stock android recovery. Which is what the red x recovery is
Is your tablets boot loader unlocked yet?... No matter. Just download thisAIO_scripts_R.A.H._TWRPv2.6.3.zip - 12.00 MB
It's my tool to do everything u need. Unlock boot loader, flash twrp recovery, and then twrp will root it also when you boot into recovery. Just Dow load the zip file. Plug your xoom into your pc and click the runme.bat and chose what you want to do.
sent from::§::
I got into the twrp interface and loaded the omniROM 4.4.2 but it will not load past the omni screen now and give me an error saying could not mount Cache
When i load in to TWRP it is asking me for a password
ramhuskies7 said:
When i load in to TWRP it is asking me for a password
Click to expand...
Click to collapse
Known issue on twrp there is no password just leave blank.
And you will need to ask your Rom related question in the Rom thread because I don't use that Rom and I don't know if it's bigPart Rom or not
sent from::§::
runandhide05 said:
Known issue on twrp there is no password just leave blank.
And you will need to ask your Rom related question in the Rom thread because I don't use that Rom and I don't know if it's bigPart Rom or not
sent from::§::
Click to expand...
Click to collapse
Thanks. i ended up restoring it back to the factory through a process i found on another forum once everything updates to where it needs to be i am going to try and use your version to install the new ROM
ramhuskies7 said:
Thanks. i ended up restoring it back to the factory through a process i found on another forum once everything updates to where it needs to be i am going to try and use your version to install the new ROM
Click to expand...
Click to collapse
Just remember to look at what ever Rom you choose. If it says requires bigpart. Look at the thread in the development section for the steps to make it compatible for bigpart. It's not hard just have to follow a few steps.
sent from::§::
I am trying to unlock my photons Q bootloader on the Motosite which is well known. I check it now a million times if I have a typo and I Dont.
The button with the "request unlock key " comes up, I hit it, and didnt recieve any mail. And I started last week doing it.
The Photon q has a GSM mod done by the almighty CornholioGSM, and I am using a connection from Germany. Since it is a Sprint photon, I thought that it might be discarded, because the ip it comes from is german ?..
Would be great to have someone telling me if there is another solution to this ..
I tried to flash with the locked bootloader the recovery, but get the message "invalid image size" on CWM or TWR.
I hope this Q is not too noob for all of you.
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
arrrghhh said:
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
Click to expand...
Click to collapse
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
x11-nice said:
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
Click to expand...
Click to collapse
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
x11-nice said:
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
Click to expand...
Click to collapse
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
arrrghhh said:
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
Click to expand...
Click to collapse
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
x11-nice said:
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
Click to expand...
Click to collapse
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
arrrghhh said:
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
Click to expand...
Click to collapse
So yesterday Motorola send me the messages with the codes which I apllied for almost 2 weeks ago... I guess the next days will arrive more.
Ofc I tried to unlock and it worked as expected. Now with fastboot flashing tto recovery 2.8.0.1 of TWRP went flawless. Actually I am really impressed how easy it worked, unlike using all the other tools like motochopper and TWRP Manager, which actually didnt solve the problem at all not having a unlocked bootloader.
Now my last Q: Which CM11 is the preferable choice for using it with the Photon. I dont care so much about Nightly or not. What I need is stable VPN and WIFI, and working mail and messenger like Cypher.
And! Thank you so much arrrghhh for all your advice and help. This forum and its users are really a great help to the community of android !
All DONE
Ok used TWRP 2.8.0.1 to install cm-11-20141012-NIGHTLY-moto_msm8960_jbbl and the PA-Gapps-Modular for 4.4.x. Great work on everyone who participated making this possible and developing the necessary tools.
Thanks again to Arrrghhh and Cornholio !
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.