3 different OPO´s - ONE Q&A, Help & Troubleshooting

I owned 3 OnePlus (1 white and 2 blacks). The last purchased was the sandstone version, and i bought it 2 days ago. My Question is simple: the first 2 OPO are running without any problems (sensor, touch, disply). But the third one (the newer one) from the start the proximity sensor doesnt work, the auto brightness is very strange (lowering and rising the brightness its not smooth, it´s like it´s choking). After many roms, i´ve succed in find a fix for the proximity sensor, but i have to flash it everytime i install a rom. I do not understand, what is so different with this model?
BTW: when i opened for the first time, it had version of 4.4.4, that i didnt saw it before 11.0-XNPH28R! And with that rom i had to manually upgrade to cm12, because the update system was telling me that is up to date.

SoRiNuS said:
I owned 3 OnePlus (1 white and 2 blacks). The last purchased was the sandstone version, and i bought it 2 days ago. My Question is simple: the first 2 OPO are running without any problems (sensor, touch, disply). But the third one (the newer one) from the start the proximity sensor doesnt work, the auto brightness is very strange (lowering and rising the brightness its not smooth, it´s like it´s choking). After many roms, i´ve succed in find a fix for the proximity sensor, but i have to flash it everytime i install a rom. I do not understand, what is so different with this model?
BTW: when i opened for the first time, it had version of 4.4.4, that i didnt saw it before 11.0-XNPH28R! And with that rom i had to manually upgrade to cm12, because the update system was telling me that is up to date.
Click to expand...
Click to collapse
Sounds like a firmware issue to me. When you say you upgraded to CM12 do you mean the nightlies or the stock ROM (Cyanogen OS 12)? And what method did you use to upgrade? By flashing the stock images with fastboot? Or flashing a ROM zip with recovery?

Heisenberg said:
Sounds like a firmware issue to me. When you say you upgraded to CM12 do you mean the nightlies or the stock ROM (Cyanogen OS 12)? And what method did you use to upgrade? By flashing the stock images with fastboot? Or flashing a ROM zip with recovery?
Click to expand...
Click to collapse
I´ve updated to Cyanogen OS 12 YNG1TASI3 using TWRP, but i´ve flashed the firmware with fastboot (this after i say that i have problems). But it´s the same. The only fix for proximity that work is the one from here: http://forum.xda-developers.com/one...es-mmwolverines-opo-mods-tips-tricks-t3027926
BTW: i´ve flashed EUPHORIA Rom, and the same, the problems persist (and i think that on this rom, the autobrightness issues is bigger, the brightness changing choking is more visible).

SoRiNuS said:
I´ve updated to Cyanogen OS 12 YNG1TASI3 using TWRP, but i´ve flashed the firmware with fastboot (this after i say that i have problems). But it´s the same. The only fix for proximity that work is the one from here: http://forum.xda-developers.com/one...es-mmwolverines-opo-mods-tips-tricks-t3027926
BTW: i´ve flashed EUPHORIA Rom, and the same, the problems persist (and i think that on this rom, the autobrightness issues is bigger, the brightness changing choking is more visible).
Click to expand...
Click to collapse
I think your best bet is to wipe your slate clean and start fresh. Go to my guide thread and use the instructions in section 8 to flash the stock images to your device with fastboot (don't worry about flashing the userdata.img as it'll only wipe your internal storage which is unnecessary, and don't worry about flashing the recovery.img as you'll need TWRP again anyway). You can grab the latest stock images from here. Once you've flashed the stock images flash whatever ROM you want and you should have no more issues (hopefully).

Heisenberg said:
I think your best bet is to wipe your slate clean and start fresh. Go to my guide thread and use the instructions in section 8 to flash the stock images to your device with fastboot (don't worry about flashing the userdata.img as it'll only wipe your internal storage which is unnecessary, and don't worry about flashing the recovery.img as you'll need TWRP again anyway). You can grab the latest stock images from here. Once you've flashed the stock images flash whatever ROM you want and you should have no more issues (hopefully).
Click to expand...
Click to collapse
Holly, thanks man! It finally worked, NO MORE proximity sensor issues, i guess after all it was a firmware issue. Thanks!

SoRiNuS said:
Holly, thanks man! It finally worked, NO MORE proximity sensor issues, i guess after all it was a firmware issue. Thanks!
Click to expand...
Click to collapse
No problems, glad to help.

Related

STAR N9770 DUAL CORE MT6577/ulefone N9770.

This is a new thread for the star n9770 mt6577 Dual core.
ROOT
I have just used this method to safely root my star n9770 and worked perfect,it just wipes your time and date after root so just reset them and that's it.
you must follow instructions....
http://colonelzap.blogspot.co.uk/search?q=n9770
Thank you Rumpelstilzchen for that!
(does not seem to work with new 13/07 firmware but fine with earlier)do not try on devices running firmware later than 13/07/12 it will naff them
FIRMWARE STAR N9770 DUAL CORE MT6577/ulefone N9770.
STAR N9770 DUAL CORE MT6577/ulefone N9770.
CUSTOM RECOVERY
https://rapidshare.com/files/4163487113/STAR-N9770_Custom_Recovery.zip
CWM
https://rapidshare.com/files/3326837023/CWM-SuperSU-v0.93_tirannozaurus.zip
FLASHTOOLS AND DRIVERS
https://rapidshare.com/files/3354053184/FlashTools_driver.rar
FIRMWARE 13/07/2012 Thanks kylie 1965
https://rapidshare.com/files/2757089569/20120713_e1809c_v77_gq1008_9p017.N9770.zip
STOCK FIRMWARE 4.0.9
I have received this today from my supplier of device n9770 dual core
https://rapidshare.com/files/2825524946/欧乐风N9770-2012-0712.zip
http://www.mediafire.com/?eyci9chr527chu9 10/08/2012 latest for devices running 5647 firmware only
latest firmware N9770-20120725_e1809 c_v77_gq1008_5647.zip 25/07/2012
Will fix back camera issues due to additional sensors in device.
http://www.mediafire.com/?2fcalamvy7hvlyo
HOPE THESE HELP.
THIS IS ORIGINAL FIRMWARE FROM FIRST ISSUE AND IS OLD AS ARE THE ROOT EXPLOIT AS WAS FOR FIRST N9770 MADE.
NOW THERE ARE MANY MODELS CALLED N9770 SO PLEASE READ THREAD FOR MORE UPDATED FIRMWARE AND EXPLOITS ROOT ETC. ENSURE YOU MAKE A NOTE OF YOUR DEVICE FIRMWARE IN SETTING /ABOUT PHONE AND WRITE IT DOWN BEFORE YOU START FLASHING THE FIRST FIRMWARE YOU FIND.
ALWAYS BACKUP DEVICE
Thank you !
Do you know whats the differences between the both firmwares in your post are ?
My N9770 will not fall into Deep Sleep. It just clock the CPU down to 250mhz, but its still on and drains the battery within 12 hours.
I tried several ROMs i've found but all the same. Maybe your stock firmware solves the problem.
hardi75 said:
Thank you !
Do you know whats the differences between the both firmwares in your post are ?
My N9770 will not fall into Deep Sleep. It just clock the CPU down to 250mhz, but its still on and drains the battery within 12 hours.
I tried several ROMs i've found but all the same. Maybe your stock firmware solves the problem.
Click to expand...
Click to collapse
i have no idea but i have tried to install the stock firmware i got today but it wont happen,and flashed with the other firmware i got from kylie and its not good.
if you have any working roms i would seriously appreciate a link to some roms as my colours are washed out with the kylie firmware and stock need to be done in recovery but can not do it as wont have saying not signed?so i need a little help
ref battery you need to root and then set cpu to ondemand i use no frills cpu from play to do this
managed to sort out colour issue flashed with mdt and changed the grapics driver so the colour is good now but i have the problem that i started with which created all this hassle and that is the cameras...How do i swap from the front to back camera???
i dont have the little icon to change cameras.
sas007 said:
i have no idea but i have tried to install the stock firmware i got today but it wont happen,and flashed with the other firmware i got from kylie and its not good.
if you have any working roms i would seriously appreciate a link to some roms as my colours are washed out with the kylie firmware and stock need to be done in recovery but can not do it as wont have saying not signed?so i need a little help
ref battery you need to root and then set cpu to ondemand i use no frills cpu from play to do this
Click to expand...
Click to collapse
I tried out this Taiwan101 ROM, this one from a russian forum (25/07?) and this one from a chinese forum (newer Taiwan?).
I also had the issue with these strange colors, its the wrong display driver. I fixed it with SP_MDT by selecting RX_50NT_401B as display driver. It seems that these ROMs had all RX_50NT_365A as default which end up in wrong colors.
With the 25/07 Firmware i also killed my cameras, should also be fixable with the correct drivers.
This 'not signed' error appears also with custom recovery ?
yep i can not get the back camera to work/switch, going to try your later rom is it rooted?
How do i install these roms?the later newer Taiwan as i am not used to dual core,do you copy zip to sd card (internal) and go to recovery and update via sd card?
and how would you change the display driver if not flashing via tools
Did you ever have the cameras working as they should?
100 questions.......
hope we can get there in the end
sas007 said:
How do i install these roms?the later newer Taiwan as i am not used to dual core,do you copy zip to sd card (internal) and go to recovery and update via sd card?
Click to expand...
Click to collapse
Yes exactly, you had to copy the file to the sd card and flash it via recovery. But you had to install a custom recovery first (i flashed only the recovery. Flashing also the boot.img and the preloader out of this zip ended with a not booting phone.
sas007 said:
and how would you change the display driver if not flashing via tools
Click to expand...
Click to collapse
I flashed the driver with tools. Not the hole ROM, just the uboot.bin. It seems that sp_mdt saves the driver in uboot when you close the programm. I did so and flashed the uboot with the 'normal' flashtool.
sas007 said:
Did you ever have the cameras working as they should?
Click to expand...
Click to collapse
Both cameras survived every change of firmware until i flashed the 25/7 ROM.
It seems that there are several hardware version. With the Taiwan101 firmwares the external sd card will not be recognized. I flashed the boot.img from the 13/07 firmware and the sd card came back. SD card is also out of function with your stock rom.
I still had the problem with phone not going into deep sleep. Also NoFrills couldn't change that. Maybe i've not found the right ROM for my hardware yet. I got it from CECT.
Hi i have flashed with the firmware from kylie and changed the display driver whilst flashing with mdt..display is good
I do not have back camera i see no way to switch to back but the front works fine and i have no idea as when i flashed with default driver it was the same no back camera
I do have external SD no problem with 32gb
I had no problems with imei
i need a recovery to flash
found these
http://translate.google.com/transla...um.china-iphone.ru/viewtopic.php?f=70&t=21147
http://translate.google.com/transla...um.china-iphone.ru/viewtopic.php?f=70&t=21147
but no help to me
The root tutorial posted here does not work with new firmware,so i copied recovery image from custom recovery (brunos)and replaced recovery in new firmware and flashed using mdt with the driver change for graphics..it worked and installed custom recovery and i then proceeded to root with the cwm-su zip in recovery and it worked.
but still no back camera
Cameras and display are working now with these drivers selected in sp_mdt :
mt9p017_raw hi704_yuv RX_50NT_401B
Which display driver have you choosen ? The same ?
hardi75 said:
Cameras and display are working now with these drivers selected in sp_mdt :
mt9p017_raw hi704_yuv RX_50NT_401B
Which display driver have you choosen ? The same ?
Click to expand...
Click to collapse
yes i used the same settings but still no back camera and other non stock camera apps will not work
i am uploading the modified firmware with these settings in the uboot and with the custom recovery in so can be straight flashed in one go.
sas007 said:
yes i used the same settings but still no back camera and other non stock camera apps will not work
i am uploading the modified firmware with these settings in the uboot and with the custom recovery in so can be straight flashed in one go.
Click to expand...
Click to collapse
You have tested all possible drivers ? Did the second camera work befor flashing ?
I changed the driver and bootet into system test (power+vol. down) to see if the cams are back or not. Its a bit faster than waiting for android to boot completely.
hardi75 said:
you have tested all possible drivers ? Did the second camera work befor flashing ?
I changed the driver and bootet into system test (power+vol. Down) to see if the cams are back or not. Its a bit faster than waiting for android to boot completely.
Click to expand...
Click to collapse
hi ran the test and main camera is fail...great back it goes
sas007 said:
hi ran the test and main camera is fail...great back it goes
Click to expand...
Click to collapse
Maybe I could try note firmware. I have used same settings for drivers with the same firmware as you but the main camera still dead. Strange.
how do you get the stock firmware signed,i wish i could use it as may hold the key
Sent from my ONDA MID using xda premium
N9770 topic
sas007 said:
I have used same settings for drivers with the same firmware as you but the main camera still dead. Strange.
how do you get the stock firmware signed,i wish i could use it as may hold the key
Click to expand...
Click to collapse
I've not used the 13/07 version u posted, i got it from this link. Should be se same but who knows. Maybe released
You have flashed the custom recovery which you have posted on the first page ? I got these not signed errors only with stock recovery.
hardi75 said:
I've not used the 13/07 version u posted, i got it from this link. Should be se same but who knows. Maybe released
You have flashed the custom recovery which you have posted on the first page ? I got these not signed errors only with stock recovery.
Click to expand...
Click to collapse
Hi used your firmware link outcome the same no camera so i flashed taiwans rom still no back camera,used uboot from n8000 has the correct drivers for cameras but not display...uboot from i9220 has wrong drivers as has the uboot from note.
used the firmware sent to me by supplier renamed it update zip and installed over taiwans rom and still no back camera.
was getting error "can not connect to camera" several times through out the process,have called it a day and am returning device..
Repartition N9770
Has anyone come out with the 2.5g repartition yet??
Try clearing your cache and removing your battery. Then, install any free basic new Jellybean cam app from the market. See if that re-installs your camera.
sas007 said:
Hi used your firmware link outcome the same no camera so i flashed taiwans rom still no back camera,used uboot from n8000 has the correct drivers for cameras but not display...uboot from i9220 has wrong drivers as has the uboot from note.
used the firmware sent to me by supplier renamed it update zip and installed over taiwans rom and still no back camera.
was getting error "can not connect to camera" several times through out the process,have called it a day and am returning device..
Click to expand...
Click to collapse
ronbo76 said:
Try clearing your cache and removing your battery. Then, install any free basic new Jellybean cam app from the market. See if that re-installs your camera.
Click to expand...
Click to collapse
Hi and thanks for your suggestion i had already tried that with 3-4 different apps,all stated they could not connect to camera,for me it is a hardware fault as i have done everything humanly possible to resolve.i have now returned device and await a new one.
having talked with china supplier the n9770 has a lot of problems and was released to market to early..most of the models sent out have been recalled due to major faults and they said it wont be until middle of September before the chipset mt6577 is back,whether there is any truth in that i do not know..but they had no replacement for me and have already issued a full refund and postage costs on emailing proof of postage so they seem honest....ummm
Cheers

[Q] Help! Lost all sensors after ColorOS -> CM11

Hi all,
Got my OnePlus One last week. It's a Chinese version that comes with ColorOS. I immediately tried to flash CM11 nightly onto it after I checked the phone is working.
For some reason I thought I could flash CM11 directly, and so the first thing I did was installing TWRP 2.8.0.1. Then, I copied CM11 zip in to /sdcard , booted to TWRP recovery, wiped all partitions (including System) and then flashed CM11. In hindsight, I believe it was the wrong way to get CM11. I could have wiped something really important (sensors drivers?) when wiping System.
Initially, CM11 nightly seemed to work OK. Then I noticed the Auto-Rotate is not working at all. I installed CPU-Z and *gasp*, there's not a single sensor listed in the CPU-Z Sensors tab!
I spent hours today trying various methods (flash CM11S, flash ColorOS, flash /persist, /reserve4 partitions). However, the sensors are still dead! Besides auto-rotate, I think auto-brightness, proximity sensors are all dead.
Is there any way to get the sensors working again? Your help is much appreciated!
Try http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and see if your sensors work after restoring to factory images.
Someone else said only twrp 2.7 is supported for opo, another guy had similar device breaking problems with 2.8.
I'm using TWRP 2.8.0.1 and have no problems. TWRP 2.8 had problems, but 2.8.0.1 resolved them.
Thanks a lot for the quick reply, zephiK! I've run flash-all.sh and I'm in CM11S now.
CPU-Z no longer shows an empty Sensors list! however, only the following 4 sensors have readings:
AK8963 Magnetometer
AK8963 Magnetometer Uncalibrated
TMG-3993 IR_Gesture & Proximity
TMG-3993 Ambient
No readings for the rest...
Does auto rotate work? I'm not really sure how your sensors disappeared in the first place, its very odd.
/system is wiped on every ROM flash anyway so that's not the reason. Glad it's working better at least. Any more issues with the sensors other then some not showing?
Nope, the auto-rotate is still not working.
I've just rebooted CM11S, and... the Sensors tab in CPU-Z became empty again! This is very strange indeed...
I think t is a kernel problem,
Maybe you van flash the original boot.img
Rebooted again. The list of sensors are showing in CPU-Z again, and the same 4 lines have readings (AK8963 Magnetometer, TMG-3993). Still no auto-rotate.
My gut feeling is that there is a low level corruption in one of the "special" partitions. By special I mean the ones that are there but not included in any of the ROMs or factory images. Unfortunately, I don't have a NANDROID backup to restore from (Huge mistake on my part).
Is there a way to download an NANDROID image containing those special partitions?
@gurby1, I thought about kernel problem too, but I've tried flashing many ROMs and kernels:
CM11S 33R
CM11 Nightly 20140296
Franco Kernel r20
ColorOS 2.0 beta
ColorOS 1.2
and the results were the same - broken auto-rotate.
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
DecemberNexus said:
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
Click to expand...
Click to collapse
Hello,
Did you find a solution ? I have exactly the same issue as you. It even worst, I don't see any sensor on my device. I have installed many ROMs without any success. I hope it is not a HW problem
Thanks.
Guys.. I also have this issue..
Glad if there any solution on this...
Same problem
Guys any solution yet? I'm getting annoyed by this so much.. Please post here if u have found any solutions. Thx.
I also have the sensor problem which is all sensor is "not supported" in antutu and empty in CPU-Z sensor tab. I fixed it by flashing the persist.img from this thread http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Dzhedaj said:
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Click to expand...
Click to collapse
Have you try flash the persist.img?
TheDynamiteGuy said:
Have you try flash the persist.img?
Click to expand...
Click to collapse
Tried flashing everything, modems, persist.img, etc. Nothing helps, so seems something is toast in the hardware...

I'm stuck

Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.
Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/
I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.

[6045O] Attempting to upgrade to Lineage 13

Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.
I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.

stable android 11 released for op7p

why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......
Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?
There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.
Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???

Categories

Resources