Related
I have downloaded and installed super user and its been working fine. Now when i open the super user app it says binary needs to be updated and it gives me a few options (normal) or (TWRP). I have installed TWRP but when i click on it it boots me into TWRP recovery with no file to flash. I guess im asking if anyone knows where i can get the latest version of super user apk at, so that i can flash it on my device. Im running 4.1.1 Thanks for any help in advance
So when it boots back into TWRP it doesn't start updating automatically?
Sent from my Evita
timmaaa said:
So when it boots back into TWRP it doesn't start updating automatically?
Sent from my Evita
Click to expand...
Click to collapse
Well, the screen kinda just sits there at the main menu. Il try again and just give it 10 minutes and see what it does. BTW thanks for the quick response
yeah its just staying at the main screen.
Have you try to flash SuperSu v1.80 or Superuser 3.2-RC3 in twrp (don't know wich version you have ?)
Have you tried just updating the binary the "normal" method? I know it says something about the recovery method being better for most HTC devices. But I've never had an issue doing it the "normal" way.
Hey all. Just wanted to let anyone know that doesn't already that the recovery installer for the F400 and D855 works on our variant. Just used the apk and have functional custom recovery. I was able to flash the volume boost mod I had on my G2 and it worked flawlessly. If you use it, when you click reboot system it will come up with a message saying "Potential loss of root, would you like to fix?" Just click no. Clicking no reboots system and root isn't lost. Clicking yes boots into stock recovery and gives an error message but you can still reboot system normally without loss of root. I did both options to check before I posted this .
This isn't a total traditional recovery flash. It's an apk that flashes a temporary custom recovery while leaving stock recovery intact. When you click the apk you'll have the option to install recovery. Once you do it will allow selection of rebooting into recovery. You have to go into the apk to reboot into custom recovery each time but its a temporary solution until we get fully functioning perm custom rec. You can make nandroid and restore nandroid. Tested both and they are working.
BreakingVZW said:
Hey all. Just wanted to let anyone know that doesn't already that the recovery installer for the F400 and D855 works on our variant. Just used the apk and have functional custom recovery. I was able to flash the volume boost mod I had on my G2 and it worked flawlessly. If you use it, when you click reboot system it will come up with a message saying "Potential loss of root, would you like to fix?" Just click no. Clicking no reboots system and root isn't lost. Clicking yes boots into stock recovery and gives an error message but you can still reboot system normally without loss of root. I did both options to check before I posted this .
This isn't a total traditional recovery flash. It's an apk that flashes a temporary custom recovery while leaving stock recovery intact. When you click the apk you'll have the option to install recovery. Once you do it will allow selection of rebooting into recovery. You have to go into the apk to reboot into custom recovery each time but its a temporary solution until we get fully functioning perm custom rec. You can make nandroid and restore nandroid. Tested both and they are working.
Click to expand...
Click to collapse
good to know, thanks... but it doesn't have the full abilities of custom recovery, eg: flashing kernels/roms. correct? we still need to unlock the bootloader for that, yes?
screwyluie said:
good to know, thanks... but it doesn't have the full abilities of custom recovery, eg: flashing kernels/roms. correct? we still need to unlock the bootloader for that, yes?
Click to expand...
Click to collapse
Yes you are correct. I believe that the Chinese recovery doesn't allow writing to the system partition of the phone so you won't be able to restore a backup. People say you can make one though. It may be able to flash a ROM bit that is untested due to the lack of something to flash and test. But if you needed to flash a small mod then this should work. Although be careful because I think I've read that the partitions may not be correct so use at your own risk.
Sent from my LG-D850 using XDA Premium 4 mobile app
roughneckboren said:
Yes you are correct. I believe that the Chinese recovery doesn't allow writing to the system partition of the phone so you won't be able to restore a backup. People say you can make one though. It may be able to flash a ROM bit that is untested due to the lack of something to flash and test. But if you needed to flash a small mod then this should work. Although be careful because I think I've read that the partitions may not be correct so use at your own risk.
Sent from my LG-D850 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I should have included that in my OP. It works well enough for minor mods and you can make backups. Thanks for adding that.
Got a link to download the apk?
http://forum.xda-developers.com/showthread.php?t=2825865
Be aware of the faults in this.
Sent from my LG-D850 using XDA Premium 4 mobile app
ReggieSmith said:
Got a link to download the apk?
Click to expand...
Click to collapse
If you're only flashing minor mods you'll be fine. Don't expect to be able to flash kernels or ROMs though.
Could you check the qfuse, see if it tripped?
mrhaley30705 said:
Could you check the qfuse, see if it tripped?
Click to expand...
Click to collapse
Mine didn't.
BreakingVZW said:
Hey all. Just wanted to let anyone know that doesn't already that the recovery installer for the F400 and D855 works on our variant. Just used the apk and have functional custom recovery. I was able to flash the volume boost mod I had on my G2 and it worked flawlessly. If you use it, when you click reboot system it will come up with a message saying "Potential loss of root, would you like to fix?" Just click no. Clicking no reboots system and root isn't lost. Clicking yes boots into stock recovery and gives an error message but you can still reboot system normally without loss of root. I did both options to check before I posted this .
This isn't a total traditional recovery flash. It's an apk that flashes a temporary custom recovery while leaving stock recovery intact. When you click the apk you'll have the option to install recovery. Once you do it will allow selection of rebooting into recovery. You have to go into the apk to reboot into custom recovery each time but its a temporary solution until we get fully functioning perm custom rec. You can make nandroid and restore nandroid. Tested both and they are working.
Click to expand...
Click to collapse
By chance, do you have a screenshot of this recovery? We can all enter the built in recovery quickly using the Quick Boot app found in GPlay. I would like to see what this recovery offers, different from the stock recovery.
Thanks
TonyStark said:
By chance, do you have a screenshot of this recovery? We can all enter the built in recovery quickly using the Quick Boot app found in GPlay. I would like to see what this recovery offers, different from the stock recovery.
Thanks
Click to expand...
Click to collapse
How would I go about getting you a screen shot? I can't use the screenshot method bc the recovery isn't touch and if you press the traditional hardware key method it makes selections in the recovery bc of the use of the power key.
BreakingVZW said:
How would I go about getting you a screen shot? I can't use the screenshot method bc the recovery isn't touch and if you press the traditional hardware key method it makes selections in the recovery bc of the use of the power key.
Click to expand...
Click to collapse
A webcam, camera etc. If you are unable to do this, no worries.
TonyStark said:
A webcam, camera etc. If you are unable to do this, no worries.
Click to expand...
Click to collapse
I can do that for you when I get off work.
PROBLEM SOLVED, THREAD CLOSED, THANKS FOR YOUR HELP
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock
Try BETA-SuperSU-v2.65.
lost101 said:
Try BETA-SuperSU-v2.65.
Click to expand...
Click to collapse
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app
@Chainfire please do have a look, it's a supersu problem.
Sent from my MotoG3 using XDA-Developers mobile app
@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.
Aman Dewett said:
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you try 2.62-3?
lost101 said:
@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.
Click to expand...
Click to collapse
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Sent from my MotoG3 using XDA-Developers mobile app
Aman Dewett said:
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Click to expand...
Click to collapse
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.
lost101 said:
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.
Click to expand...
Click to collapse
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
That is the reason everything was working perfectly before and still i'm following the same process but this time after flashing supersu on stock it stuck on logo.
Sent from my MotoG3 using XDA-Developers mobile app
MrTooPhone said:
Did you try 2.62-3?
Click to expand...
Click to collapse
Yes
Sent from my MotoG3 using XDA-Developers mobile app
Aman Dewett said:
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
Click to expand...
Click to collapse
Please state clearly that you did a Factory data reset via Settings > Backup & reset.
lost101 said:
Please state clearly that you did a Factory data reset via Settings > Backup & reset.
Click to expand...
Click to collapse
No i did not performed "factory data reset" through backup & reset settings.
I format phone through twrp only..
At first i wiped it normally, then format it through advance wipe option and removed whole os from phone then flashed stock through CMD.
Sent from my MotoG3 using XDA-Developers mobile app
I cannot help you as you refuse to follow the instructions I have provided.
lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
Ok this time i will follow proper instruction likewise format phone through backup & reset option and then will open boot loader mode and flash the rom according to instruction (commands) provided. Let's see what will happen.
As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.
lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
I did properly what you said, at first i "factory reset" through backup & reset option, then i open bootloader mode and flashed it according to given instructions. At the end after flashing supersu 2.65 stuck n logo. Same issue.
arunhebbare said:
As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.
Click to expand...
Click to collapse
removed cache and user data as well bro didn't worked.
I faced the same problem on 6.0.1 only, and I tried every su version "UPDATE" "BETA", rooted with kingroot and unfortunately I lost my SIM card recognition!
Sent from my MotoG3 using Tapatalk
Aman Dewett said:
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock
Click to expand...
Click to collapse
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?
arunhebbare said:
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?
Click to expand...
Click to collapse
If you can read i mentioned in OP that phone gets freeze on logo, It is not going on booting stage.
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
easiest way is to factory reset from recovery, if you can afford it.
First off it is stuck on boot animation, wipe data (factory reset) from recovery and you're good to go hopefully
Transmitted via BACON
ipsmaxes said:
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
Click to expand...
Click to collapse
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Hi it my case too. And I did disable some anoying Google apps.
mathsjob said:
Hi it my case too. And I did disable some anoying Google apps.
Click to expand...
Click to collapse
In my experience, it's Google App the only one causing problem, I removed Google Play Books, Play Videos, Play Music, Google+, etc. and not a problem
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
mathsjob said:
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
Click to expand...
Click to collapse
I fixed the problem dirty flashing again the ROM but if you already wiped data and flashed again the ROM, you may have another different problem causing the bootloop.
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
mathsjob said:
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
Click to expand...
Click to collapse
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
brath23 said:
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
Click to expand...
Click to collapse
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
mathsjob said:
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
Click to expand...
Click to collapse
If you don't have TWRP recovery, you could try to fastboot this ROM: http://builds.cyngn.com/factory/bacon/cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18.zip
There are plenty of guides to do this, even some scripts to make the process kind of automatic.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
More guides on XDA:
http://forum.xda-developers.com/showpost.php?p=63294096&postcount=4
And some script to make the process easier.
https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/
Make sure you choose your Oneplus ONE version correctly (16GB/64GB)
Thanks a lots for your quick answers, I will try using your ADB process.
Hey so yeah I already factory reset from recovery,
I didn't wipe my data yet because I still want to recover some files from the phone.
and yeah I did have almost every google app disabled (not removed).
after a factory reset these are normally activated again though? so idk what's up with that.
also does somebody know a way to retreive all files from the phone, through adb maybe? since I can't acces the file system on my pc rn
I'm gonna try to fastboot that rom you linked later (after I attempt to recover my files)
brath23 said:
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Click to expand...
Click to collapse
I did it yesterday
A disaster....
tommy92tc said:
I did it yesterday
A disaster....
Click to expand...
Click to collapse
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
brath23 said:
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
Click to expand...
Click to collapse
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
tommy92tc said:
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
Click to expand...
Click to collapse
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
brath23 said:
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
Click to expand...
Click to collapse
Genius!!!!
Unfortunately it's too late, I already reinstalled all the apps and everything, now I have a clean system so I'll stay with that.
However it's a good way to restore, I'll remind it if anyone else will need it
Other than CM Recovery I cannot get anything to install, not even the stock or TWRP. They all install fine and say that it is all flashed fine regardless of how I flash the recovery, but then when booting into recover I get the boot screen for around 5-10 seconds a brief flash of a plain black screen with some text (though sometimes not even this shows up) and then nothing, the phone is still on however as I have to turn it off before turning it back on again, there is just nothing displayed on the screen.
Also my boot image still shows as FreedomOS however since freedom I have had Paranoid and CM installed so not sure (the boot animation is CM but the image shown with the one plus logo has FreedomOS at the bottom)
Any help would be wonderful
Thank you
Never heard of that rom. What device do you have?
Sent from my A0001 using XDA-Developers mobile app
Did you Root before ?
DerRomtester said:
Never heard of that rom. What device do you have?
Click to expand...
Click to collapse
I have a OnePlus 3
Cholerabob said:
Did you Root before ?
Click to expand...
Click to collapse
I did root yes
McreativeH said:
I have a OnePlus 3
Click to expand...
Click to collapse
Wrong forum bro. Search for OnePlus 3 in search bar. You may get some help on freedom os is there.
It seems like you had a Firmware flash. You can try flashing recovery using a "PC with adb".
Secondly Google and download Firmware for one plus 3 . And flash it using recovery.
Again. Try booting into recovery, if you can't , you have lost recovery while flashing Firmware. Flash the recovery again using "PC with adb".
Hope it helps. Thanks.
shubhaemk said:
Wrong forum bro. Search for OnePlus 3 in search bar. You may get some help on freedom os is there.
It seems like you had a Firmware flash. You can try flashing recovery using a "PC with adb".
Secondly Google and download Firmware for one plus 3 . And flash it using recovery.
Again. Try booting into recovery, if you can't , you have lost recovery while flashing Firmware. Flash the recovery again using "PC with adb".
Hope it helps. Thanks.
Click to expand...
Click to collapse
I see... I clicked the my device section via the XDA app and for some reason it said I have a OnePlus One
McreativeH said:
I see... I clicked the my device section via the XDA app and for some reason it said I have a OnePlus One
Click to expand...
Click to collapse
Hope your phone didn't turned into OnePlus One.
Regards! Delete the thread and start over there. See you