Related
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus
Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom
Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk
Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).
Very exited, good job
so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)
coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk
unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.
Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Try provide with a logcat, might be more useful in helping you.
No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.
Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz
I run CM 13 and want to back to color os because it is not run so smooth. I format and then flash stock recovery image (then recovery) via twrp and reboot to stock recovery.
In stock recovery i wipe data and cache. That's problem come. Before finish, the screen goes black. I try to power on the device, back to wipe data then the screen goes to black again. I try to boot to recovery and fastboot but it remain the same, back to wipe data and then the screen goes to black..
I try repair it using msm tool but because my comp not recognize the device, i use QFIL. And then i can use the fastboot to boot stock recovery. Suceed. But no os inside. Try and error many times, i can power on the device at the end.
But now the other problem comes. My wifi and bluetooth not work. And message nv backup appear.
Flash project spectrum. Wifi and bluetooth work. I flash back to stock os. Wifi and bluetooth not work again..
May someone help me to solve the problem (make bluetooth and wifi work again)?
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
uyab.com said:
I run CM 13 and want to back to color os because it is not run so smooth.
Click to expand...
Click to collapse
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
kishd said:
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
Click to expand...
Click to collapse
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
celoxocis said:
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
Click to expand...
Click to collapse
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
uyab.com said:
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
Click to expand...
Click to collapse
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
celoxocis said:
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
Click to expand...
Click to collapse
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
uyab.com said:
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
Click to expand...
Click to collapse
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
celoxocis said:
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
Click to expand...
Click to collapse
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
uyab.com said:
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
Click to expand...
Click to collapse
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
celoxocis said:
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
Click to expand...
Click to collapse
wish me luck. I will try your suggestion.
uyab.com said:
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
Click to expand...
Click to collapse
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
kishd said:
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Oya.. Let me try it..
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
Which method fixed the issue in the end?
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
hi sir im having the same problem with my R7 plus can you help me
i already flash my phone using QFIL with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is only OPPO Logo
flash the phone with Msm8x38 with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is phone will boot normal but the problem is same with your problem with WIFI and Bluetooth also appear something with NV partion but can be manage with *#268# but with wifi and bluetooth i cant solve
please help me.
thank you in advance
I'm so sorry. I just log in after a long time and read your problem. Have you solved the problem?
same problem for me, no wifi and no bluetooth after flashing stock rom.
Any idea?
uyab.com said:
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
Click to expand...
Click to collapse
hello,
please ask me where to find persist.img and the method for flashing it.
thanks in advance
Hi,
So i have been on arrow os for maybe 6 months now, i wanted to update to the latest build but it told me that i had to factory reset the phone to do so, so i thought lets try some other rom on the way, i flashed the pixel experience rom, then switched to the latest build of Arrow os.
Now since i am on arrow os OSS Vendor A11, i wanted to move back to pixel experience, i tried flashing it but it would not. I flashed evolution X and rebooted the system but i was back in recovery (bootloop), i cleaned data and flashed pixel experience (successfully this time) but i was again greeted by a bootloop.
I flashed arrow os back and it turned on the device into arrow os. How can i switch to any other non OSS rom? Is it possible without adb protocol or mi flash tool? What would be the way to do so?
Thanks
Download and flash any full MIUI recovery ROM. They include stock vendor and firmware.
Some custom ROMs require A10 firmware+vendor, some others need A11, so pick accordingly.
perform format data if you're encrypted, reboot to recovery, then flash any ROM of your choice.
RogueBanana said:
Download and flash any full MIUI recovery ROM. They include stock vendor and firmware.
Some custom ROMs require A10 firmware+vendor, some others need A11, so pick accordingly.
perform format data if you're encrypted, reboot to recovery, then flash any ROM of your choice.
Click to expand...
Click to collapse
Thanks for your answer. Last night i flashed dots rom on my phone after format data and my phone went into a bootloop and i was unable to flash back arrow os because recovery would say "unable to mount system/root" and 2 more errors like this. Anyways it took me like an hour to flash arrow back and boot up.
Can you give me link to the MIUI recovery rom?
ramnoob said:
Thanks for your answer. Last night i flashed dots rom on my phone after format data and my phone went into a bootloop and i was unable to flash back arrow os because recovery would say "unable to mount system/root" and 2 more errors like this. Anyways it took me like an hour to flash arrow back and boot up.
Can you give me link to the MIUI recovery rom?
Click to expand...
Click to collapse
Of course, here you go:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I had the same issue back then (system mount error), I also have no idea what caused it.
Good luck!
RogueBanana said:
Of course, here you go:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I had the same issue back then (system mount error), I also have no idea what caused it.
Good luck!
Click to expand...
Click to collapse
Thanks again, please check that
https://xiaomifirmwareupdater.com/firmware/surya/stable/V12.0.9.0.QJGMIXM/
Flashing this before flashing the rom would work?
Also for you, how did you make it mount again? Just in case i fall in that loop again haha
ramnoob said:
Thanks again, please check that
https://xiaomifirmwareupdater.com/firmware/surya/stable/V12.0.9.0.QJGMIXM/
Flashing this before flashing the rom would work?
Also for you, how did you make it mount again? Just in case i fall in that loop again haha
Click to expand...
Click to collapse
Check your ROM requirements, for different ROMs need different firmware versions(see "Android" column on the website)
Usually the required firmware is written in the ROM description.
If you're not sure, you can always ask the ROM developer.
For the dot-OS ROM you are about to flash, I think it needs A10 firmware. CMIIW