My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Prince parth said:
My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Click to expand...
Click to collapse
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash moun kernel in different ROMs to check whether it works or not?
ImSSin said:
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash mourn kernel in different ROMs to check whether it works or not?
Click to expand...
Click to collapse
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine??
Prince parth said:
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine
Click to expand...
Click to collapse
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
ImSSin said:
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
Click to expand...
Click to collapse
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Prince parth said:
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Click to expand...
Click to collapse
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Don't need to flash stock ROM I'm on Resurrection Remix treble ROM and for flashing I followed steps stated in forum.. it's work for me no bootloops.
First fastboot flash userdata userdata.img and then boot into Twrp and flash ROM zip that's all.
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Userdata.img is not necessary, just install the rom and format data(must) then reboot
Thnx for the help guys but after spending hours flashing different ROMs, TWRPs and kernels, I finally found the solution for the touch screen bug.
eXtreme kernel is the only kernel that was able to fix the screen completely. Its working in all of the custom ROMs (tried on LOS15.1 & 16, RR, LR Oreo and pie, etc.)
The stock versions of francokernel, void kernel are able to fix the touch screen but it breaks WiFi so they are not a complete fix.
And btw stock versions of Franco,extreme,void kernels work on the stock ROM.
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
yasars said:
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
Click to expand...
Click to collapse
have you tried flashing the extreme kernel?
extreme kernel v11 not working only V8 working for me.
What about you guys??
only with kernal 4.9 based custom roms, i have touch issues as described in here. and yeah i had screen replacement too.
now i can't flash any new pie roms as they all are based on 4.9 kernals and i can't find the old pie roms based on 3.18(link dead)..right now on los15.1
:crying::crying::crying::crying::crying::crying::crying:
Same problem here
ImSSin said:
have you tried flashing the extreme kernel?
Click to expand...
Click to collapse
ImSSin
Were you able to solve this problem? Can you put the link to download the kernel?
Related
Hey everyone. I recently started messing with ROMs on my Oneplus Two, and for some reason I keep getting error 7 after trying to install ROMs.
I'm doing everything the exact same for every ROM I try, but it seems a third of the time I get error 7. I was wondering if there's something specific with my phone that could be causing this?
I've asked my friend to try out some of the same ROMs on his Nexus 6 and they seem to work fine.
One ROM in particular I'm having this problem with is Resurrection Remix.
I'm fairly sure I'm installing everything correctly, so any feedback on this issue would be great.
Thanks!
You need to use hybrid recovery. Look for garak twrp hybrid 3.0.2.0 and flash within twrp. Bootloader is set on lollipop and marshmallow ROM conflicting.
Change the Twrp version or go for Grarak's Twrp that will be fine
Akash1998 said:
Change the Twrp version or go for Grarak's Twrp that will be fine
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904 is this a working recovery that will flash all ROMs to the oneplus 2? Or is Grarak's the only solution as of now? Thanks
I'm in Garak version on TWRP (Orange one) and currently on CM13. Now I'm trying to clean flash AOSPA but getting Error 7, Any way to fix this?
Edit : Tried flashing Official firmware OOS 3.0.2 and then flash again AOSPA but still same error.
Edit 2 : Flashed TWRP 3.0.2.0 and all is fine now.
FIXED!
Alright cool I ended up installing the hybrid twrp and it works great now! Thanks guys.
I made this thread just to make sure i'm not the only one for whom VoLte doesn't seem to work on any rom except Miui and Aosp 5.0. I've tried so hard to get VoLte restored efs from miui mm tried differet roms, bricked my device no. of times experimenting but all in vain. VoLte is not a big deal for me ( i can use Jio4gvoice) but yet it's working for so many people and i get sometimes jealous. Moreover i don't wanna go back to MiUi.
If anyone after going through all this trouble was able to enable VoLte in any Nougat rom please do share your experience. It may be helpful for so many users searching for the VoLte fix here and there in all the threads.
I also try so many things but finally a got volte....
First i flash other rom by Abhishek987 cyanogenmod 14.1 as described in op restart and finishing Complete booting
I got volte....
Again boot in zxc twrp recovery
factory reset
Flash remix rom follow gaps pico
Restart.. Again i got volte
That's it.
nravin said:
I also try so many things but finally a got volte....
First i flash other rom by Abhishek987 cyanogenmod 14.1 as described in op restart and finishing Complete booting
I got volte....
Again boot in zxc twrp recovery
factory reset
Flash remix rom follow gaps pico
Restart.. Again i got volte
That's it.
Click to expand...
Click to collapse
I guess getting VoLte depends all on luck xD
iamharish said:
I guess getting VoLte depends all on luck xD
Click to expand...
Click to collapse
You may try my method
nravin said:
You may try my method
Click to expand...
Click to collapse
You said you just booted cm14.1 by @abhishek987 and it was working fine.
iamharish said:
You said you just booted cm14.1 by @abhishek987 and it was working fine.
Click to expand...
Click to collapse
Yes
Same problem here
voLTE working on miui and aosp 5.0 only
BTW you are also using alka twrp?
Use zcx twrp, try leak aosp 6.0.1 which has volte.
Sent from my Redmi Note 3 using XDA Free mobile app
Got VoLte working!
rajatchawla66 said:
Same problem here
voLTE working on miui and aosp 5.0 only
BTW you are also using alka twrp?
Click to expand...
Click to collapse
Hi there! Recently i got VoLte working on every single rom. I will make a thread soon of the procedure i follwed.
P.s- That procedure will work 110%
Edit- follow this guide
http://forum.xda-developers.com/redmi-note-3/how-to/guide-volte-fix-nougat-roms-users-t3518614
Hi there,
I tried almost all the nougat ROMs here and none of them were working for VoLTE. So decided to follow the Nougat VoLTE Patch thread [http://forum.xda-developers.com/red.../volte-patches-nougat-based-cm-roms-t3509257], but it still didn't work while following the procedure provided on the thread. So I decided to play on myself and did a few trail and error.
Somehow this worked for me to get the VoLTE working:
- I downloaded the Abhishek's
CM14.1 and Firmware which said to have the VoLTE support: http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-14-1-t3500569
- Then I downloaded the lastest SuperSU to flash because I had flashed a MIUI Global Stable, so it had locked my bootloader again and I wanted to root again, and I think this is what did the trick but I'm not sure: https://download.chainfire.eu/696/supersu/
- Downloaded the volte_cm-161123TheStrix.zip and the volte.zip from the Nougat VoLTE Patch thread: http://forum.xda-developers.com/devdb/project/?id=18113#downloads
- Then I flashed them in this sequence by adding them all together in queue in TWRP.
First I wiped system, data, cache/dalvik in TWRP (I already had a backup)
Then added SuperSU>Firmware>CM14.1>volte_cm-161123TheStrix.zip>volte.zip to the flash queue and flashed them all together and rebooted. It got stuck in the bootloop, so booted into fastboot and rebooted again by holding the power button. Then it booted successfully and had the HD :laugh:
Then my aim was to flash the latest RR which had the VoLTE, so I followed the same procedure and added this RR to the queue instead of Abhishek's CM14.1 and it worked there too :laugh: :http://forum.xda-developers.com/redmi-note-3/development/rom-resurrectionremix-5-8-0-t3507433
Hope this helps!
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
#Henkate said:
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
Click to expand...
Click to collapse
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
I have the same problem …
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
SiiXFX said:
I have the same problem …
Click to expand...
Click to collapse
You must be on Lollipop to flash RR 6.0.1, just like CM13.
#Henkate said:
You must be on Lollipop to flash RR 6.0.1, just like CM13.
Click to expand...
Click to collapse
Thanks friend I will try.
Same Green Screen
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Vityy said:
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Click to expand...
Click to collapse
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
aytida4 said:
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
Click to expand...
Click to collapse
I flashed the 5.1.1 rom but still i get the green screen/lines at the boot. I always get bootloops when i flash any zip. Plz help
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ... ???
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
Which Custom Rom did you flash?
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
AndroiDTechi said:
Which Custom Rom did you flash?
Click to expand...
Click to collapse
not custom rom but kernel idk what the problem is so now i decided to have android backup in order to back again to my current system
---------- Post added at 06:46 AM ---------- Previous post was at 06:31 AM ----------
#Henkate said:
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
Click to expand...
Click to collapse
:good: i back to its current system now what i want is stock rom with customize and rooted system
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Flash 5.1.1 cynogenmod rom then install RR remix
Demicro said:
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ...
Click to expand...
Click to collapse
For those, who -as I did - don't really understand this (see the quote)...
I had the same issue when I wanted to install a custom Marshmallow ROM (6.0.1) over my stock Lollipop (5.1.1). The solution was to download and flash a new Bootloader and Modem with Odin. See tis:
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
https://forum.xda-developers.com/galaxy-j5/development/rom-resurrectionremix-v5-8-1-t3566035
iH8Ecchi said:
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
Click to expand...
Click to collapse
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
wrongwriter3 said:
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
Click to expand...
Click to collapse
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
iH8Ecchi said:
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
Click to expand...
Click to collapse
Yes.
Because it work only with 5.1.1 bootloader.
Hi guys, as you can see from the title, I just bought a new Redmi 2 LTE CN Dual-SIM (Unicom China) WT88047 - HM2014811. I flashed TWRP using Stock Recovery with stock rom (first I tried the 'fresh out of the box stock' and latest global developer rom) and succeeded to boot into TWRP. The problem is (using the 2 stock roms), my touchscreen doesn't work when I try to press or slide when I'm in TWRP. Touchscreen does eventually works after screen time out though. Successfully installed Custom ROMs and stuff, but everytime I boot into TWRP, to use it, I have to wait until the screen goes black (time out) and then the touchscreen becomes responsive. The question is, is this a bug (hardware level bug) or I did things the wrong way? Is there anyway at all to fix this? Because once I accidentally turned off screen timeout and had to flash stock via fastboot to wipe TWRP data. It's becoming pretty annoying. Thank you, please do reply ASAP.
ezrawk said:
Hi guys, as you can see from the title, I just bought a new Redmi 2 LTE CN Dual-SIM (Unicom China) WT88047 - HM2014811. I flashed TWRP using Stock Recovery with stock rom (first I tried the 'fresh out of the box stock' and latest global developer rom) and succeeded to boot into TWRP. The problem is (using the 2 stock roms), my touchscreen doesn't work when I try to press or slide when I'm in TWRP. Touchscreen does eventually works after screen time out though. Successfully installed Custom ROMs and stuff, but everytime I boot into TWRP, to use it, I have to wait until the screen goes black (time out) and then the touchscreen becomes responsive. The question is, is this a bug (hardware level bug) or I did things the wrong way? Is there anyway at all to fix this? Because once I accidentally turned off screen timeout and had to flash stock via fastboot to wipe TWRP data. It's becoming pretty annoying. Thank you, please do reply ASAP.
Click to expand...
Click to collapse
So according to your post....you flashed t.w.r.p by stock recovery .So let me guess.The t.w.r.p was from miui forum.I suggest you to flash t.w.r.p 3.0.2.0 by kumajaya sir (from XDA) by fastboot or rashr or flashify. And flash any custom ROM from here(XDA) and do a clean flash(though clean flash is not a magic wand)
raymond_bqg said:
So according to your post....you flashed t.w.r.p by stock recovery .So let me guess.The t.w.r.p was from miui forum.I suggest you to flash t.w.r.p 3.0.2.0 by kumajaya sir (from XDA) by fastboot or rashr or flashify. And flash any custom ROM from here(XDA) and do a clean flash(though clean flash is not a magic wand)
Click to expand...
Click to collapse
Yes exactly, you are correct, the TWRP was from MIUI forums. I did try flashing kumajaya's TWRP via fastboot and the results: Can't boot to TWRP (and this was before I found the post in MIUI forums, because it's been my habit to check XDA first before oem forums). Sorry I forgot to mention firsthand about this. Maybe it was because of my Redmi 2 model, it's got different soc parts or something, I'm not that well much informed about the differences between Redmi 2 models. What I did found out was that my Redmi 2 Prime (says the online shop that I bought it from) was not exactly Redmi 2 Prime, but it was the Redmi 2 China LTE Dual-SIM model with 16 GB's of ROM and 2 GB's of RAM (Wingtech 2014811 - Redmi 2 LTE Unicom China Dual-SIM).
I do have past experiences with Redmi 2 from a friend who bricked his Redmi 2, and I flashed kumajaya's (sir) TWRP with ease. No problems, perfectly booted to TWRP without any bugs or other problematic situations. Flashed custom roms and kernels, even reverted back to stock (vice versa).
I'm not totally shocked by the different variants of Redmi 2 (My past HH was a Zenfone 5, and yes A*SUS likes to ship HH with different SoC parts, it made me unable to unlock the bootloader), what makes me curious is the difference between KK bootloader and LP bootloader, the limitations and weird bugs that they offer. Why did Xiaomi suddenly implemented a different bootloader for Redmi 2, thats my main question so far.
*PS: I've tried to use nicknitewolfs Modded kumajaya TWRP, from the LineageOS 14.1 thread, and yes it booted, but the same problems exists.
I'll try once more to do a clean flash of TWRP. *fingerscrossed
ezrawk said:
Yes exactly, you are correct, the TWRP was from MIUI forums. I did try flashing kumajaya's TWRP via fastboot and the results: Can't boot to TWRP (and this was before I found the post in MIUI forums, because it's been my habit to check XDA first before oem forums). Sorry I forgot to mention firsthand about this. Maybe it was because of my Redmi 2 model, it's got different soc parts or something, I'm not that well much informed about the differences between Redmi 2 models. What I did found out was that my Redmi 2 Prime (says the online shop that I bought it from) was not exactly Redmi 2 Prime, but it was the Redmi 2 China LTE Dual-SIM model with 16 GB's of ROM and 2 GB's of RAM (Wingtech 2014811 - Redmi 2 LTE Unicom China Dual-SIM).
I do have past experiences with Redmi 2 from a friend who bricked his Redmi 2, and I flashed kumajaya's (sir) TWRP with ease. No problems, perfectly booted to TWRP without any bugs or other problematic situations. Flashed custom roms and kernels, even reverted back to stock (vice versa).
I'm not totally shocked by the different variants of Redmi 2 (My past HH was a Zenfone 5, and yes A*SUS likes to ship HH with different SoC parts, it made me unable to unlock the bootloader), what makes me curious is the difference between KK bootloader and LP bootloader, the limitations and weird bugs that they offer. Why did Xiaomi suddenly implemented a different bootloader for Redmi 2, thats my main question so far.
*PS: I've tried to use nicknitewolfs Modded kumajaya TWRP, from the LineageOS 14.1 thread, and yes it booted, but the same problems exists.
I'll try once more to do a clean flash of TWRP. *fingerscrossed
Click to expand...
Click to collapse
If he phone have a different SOC then I think no ROM in this forum will work(may be I am wrong,and I hope this) perfectly.If kumajaya Sirs t.w.r.p does not work then try Tesla ROM by miui forums t.w.r.p.I once flashed Tesla by miui forums t.w.r.p ,and it worked fine .But lineage by miui forums t.w.r.p never will work.
raymond_bqg said:
If he phone have a different SOC then I think no ROM in this forum will work(may be I am wrong,and I hope this) perfectly.If kumajaya Sirs t.w.r.p does not work then try Tesla ROM by miui forums t.w.r.p.I once flashed Tesla by miui forums t.w.r.p ,and it worked fine .But lineage by miui forums t.w.r.p never will work.
Click to expand...
Click to collapse
Oh yeah sorry, wrong words to put, just different parts I meant (Touchscreen, proximity, etc.). Okay thank you, I'll try MIUI's Tesla ROM. Thank you for the reply btw. :highfive:
ezrawk said:
Oh yeah sorry, wrong words to put, just different parts I meant (Touchscreen, proximity, etc.). Okay thank you, I'll try MIUI's Tesla ROM. Thank you for the reply btw. :highfive:
Click to expand...
Click to collapse
Not miui's Tesla.As u said t.w.r.p from miui forum worked in ur device.So I said try to flash Tesla @premaca (from XDA) by t.w.r.p(from miui forum).May be that will work.
raymond_bqg said:
Not miui's Tesla.As u said t.w.r.p from miui forum worked in ur device.So I said try to flash Tesla @premaca (from XDA) by t.w.r.p(from miui forum).May be that will work.
Click to expand...
Click to collapse
Oh so what you're saying is, "changing the zips original recovery.img (from MIUI) and replacing it with Tesla's TWRP from XDA? I'll try that! ", never mind that, I got it wrong, what you meant was install image right? I've done that before, and 'the situation below' happened.
Oh btw I tried flashing XDA Tesla's TWRP via fastboot commands, clean flashed it (fastboot format system, cache, userdata, fastboot erase recovery, fastboot reboot-bootloader and then flash recovery blablabla.img), it booted, but it made another bug. First, the same as before, touchscreen unresponsive, second when screen time out kicked in, my power button or even volume buttons couldn't wake TWRP up. I'm feeling so hopeless right now..
ezrawk said:
Oh so what you're saying is, "changing the zips original recovery.img (from MIUI) and replacing it with Tesla's TWRP from XDA? I'll try that! ", never mind that, I got it wrong, what you meant was install image right? I've done that before, and 'the situation below' happened.
Oh btw I tried flashing XDA Tesla's TWRP via fastboot commands, clean flashed it (fastboot format system, cache, userdata, fastboot erase recovery, fastboot reboot-bootloader and then flash recovery blablabla.img), it booted, but it made another bug. First, the same as before, touchscreen unresponsive, second when screen time out kicked in, my power button or even volume buttons couldn't wake TWRP up. I'm feeling so hopeless right now..
Click to expand...
Click to collapse
You got it wrong again....may be my fault.
I am trying to say that flash Tesla ROM by miui forums twrp.
raymond_bqg said:
You got it wrong again....may be my fault.
I am trying to say that flash Tesla ROM by miui forums twrp.
Click to expand...
Click to collapse
Oh I see!
Well which Tesla ROM are you mentioning above? The latest nougat build or the final MM build? Because right now I'm using the final MM build. What does flashing the Tesla ROM have to do on fixing my unresponsive touchscreen on TWRP?
ezrawk said:
Oh I see!
Well which Tesla ROM are you mentioning above? The latest nougat build or the final MM build? Because right now I'm using the final MM build. What does flashing the Tesla ROM have to do on fixing my unresponsive touchscreen on TWRP?
Click to expand...
Click to collapse
Rom compatibility with recovery.
I don't know if there are a tread about this I did not see one. Every time I flash android 11 I can't get the wifi to work any advice would be greatful thanks.
First give some info about Which rom or kernel you had installed, how you installed clean flashed or dirty flashed, flashed oos before flashing custom rom. Last have you followed flashing rule,p because of so many things are experiencing by people when flashing custom roms,
kmr168401 said:
First give some info about Which rom or kernel you had installed, how you installed clean flashed or dirty flashed, flashed oos before flashing custom rom. Last have you followed flashing rule,p because of so many things are experiencing by people when flashing custom roms,
Click to expand...
Click to collapse
I flashed latest oss to both slots reboot to the welcome screen then reboot to recovery flashed
[OFFICIAL] KekHunter-420 - A Pentesters ROM for OnePlus 6/6T format data reboot no wifi but about 90% of android 10 or 11 roms has no wifi
dude1981 said:
I flashed latest oss to both slots reboot to the welcome screen then reboot to recovery flashed
[OFFICIAL] KekHunter-420 - A Pentesters ROM for OnePlus 6/6T format data reboot no wifi but about 90% of android 10 or 11 roms has no wifi
Click to expand...
Click to collapse
Sorry to say this I think I remembered someone also have same problem, so better post it in that forums and ask for help from the developer, may be he will help, he is actually respond to each and every questions, so I think he can help you to solve this issue.
Best of luck.