Related
Hy
i have got myself a new mini (coming from htc) and have some questions.
first what i did already:
rooted the phone (works after flashing update for superSU)
did a nandroid backup
flashed custom rom CM10
flashed gapps
now after doing this, i came to conclusion i needed the original dropbox for getting the free storage (didn't work @cm). i wanted to get this using android manager and now the problems starts:
nandroid manager need other superuser, so i installed superSU again and flashed the update. but now i haven't got root anmore
in recovery a did a restore from my backup => the phone bootes, but give me a lot of errors and freezes a little (gapps, google services,...)
whent back to racovery and flashed again CM10 and gapps => everything works
but now i am back at the beginning and some more questions:
how can i install other superuser in CM10 without problems
why crashes my backup
what can i do if i restore (maybe flash gapps?)
did it also with titanium backup pro but gives error for other bussybox. after installing new one, still not ok
manny thanks in advance
Nobody ??
Please help
_nicolas_ said:
Nobody ??
Please help
Click to expand...
Click to collapse
If you have l9195 follow this and should be able to root and everything http://forum.xda-developers.com/showthread.php?t=2364980
TB works ok...restoring and everything else
dr_jerremy said:
If you have l9195 follow this and should be able to root and everything http://forum.xda-developers.com/showthread.php?t=2364980
TB works ok...restoring and everything else
Click to expand...
Click to collapse
I know. I followed this tutorial. Root wast my probleem
_nicolas_ said:
I know. I followed this tutorial. Root wast my probleem
Click to expand...
Click to collapse
hi,
I have the same problem with stock Rom.
When restoring gapps stope working and the solution is factory reset.
I tried also PhilZ recovery - same result.
I'm still searching a solution.
Next i will try TWRP recovery and i will let you know...
mbgheban said:
hi,
I have the same problem with stock Rom.
When restoring gapps stope working and the solution is factory reset.
I tried also PhilZ recovery e result.
I'm still searching a solution.
Next i will try TWRP recovery and i will let you know...
Click to expand...
Click to collapse
Same here . if factory reset the apps from the play store can't write in data partition . flash arco68 kernel before cwm backup then backup and everything is ok .the problem is the stock kernel(security settings).
yannis11 said:
Same here . if factory reset the apps from the play store can't write in data partition . flash arco68 kernel before cwm backup then backup and everything is ok .the problem is the stock kernel(security settings).
Click to expand...
Click to collapse
I installed TWRP from here and it works fine.
mbgheban said:
I installed TWRP from here and it works fine.
Click to expand...
Click to collapse
i confirm that just flash TWRP backup then restoring and works for me too.the only reason i dont try this recovery is because touch interfase but i manage.so is a bug from cwm or something we doing wrong
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Here is a video I made
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
thanks
MarJava said:
thanks
Click to expand...
Click to collapse
for what? :|
XDRdaniel said:
for what? :|
Click to expand...
Click to collapse
不错啊
MarJava said:
不错啊
Click to expand...
Click to collapse
what's nice?
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
是不是底包问题
MarJava said:
是不是底包问题
Click to expand...
Click to collapse
it isn't? do you know what's causing the problem? did it ever happend to you?
XDRdaniel said:
it isn't? do you know what's causing the problem? did it ever happend to you?
Click to expand...
Click to collapse
我没用MIUI啊
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
pedrosantosobral said:
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
Click to expand...
Click to collapse
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
XDRdaniel said:
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
Click to expand...
Click to collapse
No I had a different issue but I'm 100 sure that problem comes due to your file system...the versions u using is adapted to f2fs so it works but unmodified versions have a lot of issues and some of them doesn't even boot on f2fs
Sent from my OnePlus 3 using XDA Labs
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Diaze said:
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Click to expand...
Click to collapse
Still mm based. It has the firmware included, so you can flash it over any rom.
https://www.androidfilehost.com/?fid=961840155545570150
I am currently using aosp 8.0 ROM as my daily driver. When I found out that the new aosp 8.1 ROM is available,I flashed(did a clean wipe thou)it got encryption issue(and asked me to reset my phone..when I clicked on the reset button it just used to boot me into my Twrp recovery)so thought something was faulty in the ROM
Then I saw pixel experience ROM based on 8.1 flashed got the same issue again.....I tried to install stock 7.0 recovery from Lenovo it say resetting system but the problem is still there....I also tried changing my my data partition to ext4 but the problem still exist.....SOMEONE PLZ HELLLPPPP
..btw every 8.0 and lower version of ANDRIOD ROM works perfectly.
Hi flash this on twrp https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip and let me know if it works for you, had the same problem.
rksayush said:
I am currently using aosp 8.0 ROM as my daily driver. When I found out that the new aosp 8.1 ROM is available,I flashed(did a clean wipe thou)it got encryption issue(and asked me to reset my phone..when I clicked on the reset button it just used to boot me into my Twrp recovery)so thought something was faulty in the ROM
Then I saw pixel experience ROM based on 8.1 flashed got the same issue again.....I tried to install stock 7.0 recovery from Lenovo it say resetting system but the problem is still there....I also tried changing my my data partition to ext4 but the problem still exist.....SOMEONE PLZ HELLLPPPP
..btw every 8.0 and lower version of ANDRIOD ROM works perfectly.
Click to expand...
Click to collapse
Change data partition to ext4 and den reflash
Use Boardsearch
https://forum.xda-developers.com/lenovo-p2/help/encryption-unsuccessful-aufter-flashing-t3732484
I don't understand
roli0201 said:
Use Boardsearch
https://forum.xda-developers.com/lenovo-p2/help/encryption-unsuccessful-aufter-flashing-t3732484
Click to expand...
Click to collapse
What do u want to say mate?
Problem was solved
ASP02 said:
Change data partition to ext4 and den reflash
Click to expand...
Click to collapse
Just wiped all the data and changed it to ext4 and flashed the ROM again it worked for me.thanks
It didn't but
Cuvillier said:
Hi flash this on twrp https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip and let me know if it works for you, had the same problem.
Click to expand...
Click to collapse
Well I was unable to solve my problem with this but I ahve a question when do I have to flash this before flashing the ROM or after flashing this rom I am making a YouTube video on this issue so your opinion will help a lot thanks.
i have the problem on all oreo roms, i press encrypt, then i see the custom logo loading, and at the reboot i am STILL UNENCRYPTED. the problem is that being unencrypted i do not see any option to use the FINGERPRINT scanner!
Hello guys!
Recently the sensor (auto rotate screen, gyro, etc) of my phone stopped working after installed Dot OS 5.1.2 (android 11) , and i didn't liked at all, so i've wiped dalvic, system,cache,internal storage, etc - (default method that everyone does)
and i've installed Corvus OS 9.0 (android 10) again that was the current OS that i'm using right now.
i've downloaded the sensor check that i found in google play, and seems like it's not installed in my device or corrupted, and i don't know what to do.
Could anyone can solve this? use apps to rotate the screen is so boring
Barring a hardware problem, reverting to stock ROM with MiFlash should fix that; if it does, you can then start over with your prefered custom ROM.
pnin said:
Barring a hardware problem, reverting to stock ROM with MiFlash should fix that; if it does, you can then start over with your prefered custom ROM.
Click to expand...
Click to collapse
Alright, i'm gonna try it, this afternoon, thanks so much for help! i will reply later for a new feedback!
It didnt work, i flashed the stockrom using miflash, but It seems like dont has any sensor installed.
VictorBravi said:
It didnt work, i flashed the stockrom using miflash, but It seems like dont has any sensor installed.
Click to expand...
Click to collapse
try flashing persit img ginkgo by recovery,if you don't know how to find this file, just extract the latest fastboot rom stock and it will have persist.img inside the images folder
dalzin said:
try flashing persit img ginkgo by recovery,if you don't know how to find this file, just extract the latest fastboot rom stock and it will have persist.img inside the images folder
Click to expand...
Click to collapse
alright, i guess i'm gonna try this tomorrow (because i've flashed the stock rom, and i forgot to check the box "clean all" instead "clean and block", so i've blocked my bootloader and i have to wait till tomorrow to unblock again and try this method. thanks anyway!
VictorBravi said:
alright, i guess i'm gonna try this tomorrow (because i've flashed the stock rom, and i forgot to check the box "clean all" instead "clean and block", so i've blocked my bootloader and i have to wait till tomorrow to unblock again and try this method. thanks anyway!
Click to expand...
Click to collapse
this might brick your phone !
look for more info before proceeding ...
loopypalm said:
this might brick your phone !
look for more info before proceeding ...
Click to expand...
Click to collapse
yeah, i've bricked my phone before and now i know how to solve that watching youtube videos, thanks for the tip
anyways, i did it, custom rom installed successfully.
now , in this afternoon i'm gonna try to flash the "persist.img" because i'm working now
i'm gonna post the feedback soon
got it guys, thanks so much for the help of you all! it's working everything now! you're the best
VictorBravi said:
got it guys, thanks so much for the help of you all! it's working everything now! you're the best
Click to expand...
Click to collapse
persist , right ?
loopypalm said:
persist , right ?
Click to expand...
Click to collapse
Yeah, it was it! maybe because when i was flashing another rom, in the twrp there was a box to check "persist" and i've checked because i didn't know what was it, so, because of it when i flashed a new rom, the auto rotate isn't working because it wasn't installed. now i can rotate my screen without use secondary apps \o/ thanks a bunch!