Related
Guys I really need some help here
I have managed to get the new cwm on the ouya and then installed the bootloader with different options to enable installation of cm11, but it keeps going right to failsafe mode.
Am sure its this part I've done wrong:
......"if you are not using a custom rom you will need to relocate your bootimage (read: kernel) to /system/boot.img manually"..........
Can somebody PLEASE tell me how to do this bit
Have asked a few times (so sorry moderators) and nobody here has helped me
I know I'm not the only one with this issue.....
Please guys........
The cm nightlies should put everything in the right place. Certainly I didnt have to move anything post install. Installed cwm, installed cm11, installed google apps..Ouya boot quite happily. Im wondering if you have actually installed cm11?
I' m guessing you haven't installed cm11 yet. You're going to needto install it through the recovery menu. It will not install through the failsafe. Once installed you may also need to do a factory reset to get cm11 to boot properly. I'm running the April 11 nightly and it is awesome. Much better performance than my neo x7. Good luck, once you get it installed it works very well and is very stable.
Largewoodenspoon said:
Guys I really need some help here
I have managed to get the new cwm on the ouya and then installed the bootloader with different options to enable installation of cm11, but it keeps going right to failsafe mode.
Am sure its this part I've done wrong:
......"if you are not using a custom rom you will need to relocate your bootimage (read: kernel) to /system/boot.img manually"..........
Can somebody PLEASE tell me how to do this bit
Have asked a few times (so sorry moderators) and nobody here has helped me
I know I'm not the only one with this issue.....
Please guys........
Click to expand...
Click to collapse
If you have the newest CWM installed, if not then install the newest CWM, you can then sideload CM11 to your Ouya, as well as the latest GAPPS. I used sideload after I completely wiped the whole Ouya, then used CWM to sideload the Bootloader and then CM11 & GAPPS.
This might be a good way to go if you've already got knowledge of ADB, and can't get it working any other way.
Hello,
Today, I tried to install Visi0nary's kernel, I first unlocked bootloader, "unlock pass" on phone and "OKAY" appeared on teminal. Then, I installed the kernel, and ended up in a bootloop. I reinstalled my rom and thr problem was solved. However, I tried again with tiltkernel, and the same problem appeared. Same with nexus rom, which contains Visi0nary' 12.1. Eragon and stock rom work just fine, so I'm thinking this happens when I'm flashing a kernel, but I have no idea why and how to resolve this.
I appreciate any help you can provide.
How you try installing the kernel ?
I'm using flashify from Play Store to install the kernel and have no problem with that.
Gesendet von meinem Elephone P8000 mit Tapatalk
Usually I use flashify too. However, both flashify and rashr failed this time. Even fastboot flash boot xxxxx.img which is the safest method IMHO to flash a kernel since I started to play with android phones.
To describe more precisely the error, I can't even see the ROM logo, it's stuck on boot logo for around 30 seconds then reboots and boot logo again etc...
I have the same problem. I flashed nexus with PhilZ as well a visi0nary with flashtool. Stock Kernel is working of course.
psychonael said:
Hello,
Today, I tried to install Visi0nary's kernel, I first unlocked bootloader, "unlock pass" on phone and "OKAY" appeared on teminal. Then, I installed the kernel, and ended up in a bootloop. I reinstalled my rom and thr problem was solved. However, I tried again with tiltkernel, and the same problem appeared. Same with nexus rom, which contains Visi0nary' 12.1. Eragon and stock rom work just fine, so I'm thinking this happens when I'm flashing a kernel, but I have no idea why and how to resolve this.
I appreciate any help you can provide.
Click to expand...
Click to collapse
I have got the same problem and tried several methods, which all did not succeed in getting custom kernels to run on my phone (P8000 gold version).
You may also look in the respective thread where I posted my issues; post 180 onwards in the visionary thread:
http://forum.xda-developers.com/showpost.php?p=63601502&postcount=180
So far no solution has been discovered for this bootloop problem. I really wonder what could possibly be wrong with the affected devices.
GalaxyFan88 said:
I have got the same problem and tried several methods, which all did not succeed in getting custom kernels to run on my phone (P8000 gold version).
You may also look in the respective thread where I posted my issues; post 180 onwards in the visionary thread:
http://forum.xda-developers.com/showpost.php?p=63601502&postcount=180
So far no solution has been discovered for this bootloop problem. I really wonder what could possibly be wrong with the affected devices.
Click to expand...
Click to collapse
Thanks, I will check it out That's really strange though.
Fixed in my latest release. There was a specific LCD driver missing that Elephone added with their kernel update.
Yup, just flashed it and it works, thank you BlueFlame4 for your hard work
All I want..... Is an S3 with AICP on Sprint's network.
Two weeks ago I bought an S3 for $50, started playing with it, easily flashed AICP and TWRP 2.8.7.0 Recovery. Everything was awesome, until Sprint couldn't activate it. I flashed back to stock through Odin, Sprint still couldn't activate it (problems with programming). There was no Sprint boot screen, so assuming that was the main problem I found "SPH-L710_ND8_Full Restore_UNROOTED.exe" that restored the Sprint boot logo and viola! I had Sprint 4GLTE and talk and text.......... But now, this little devil S3 won't flash Roms that are 5.0 or newer. I have tried AICP, PAC-ROM, Vanir, Exodus.... all just boot to the boot logo and stay there, but when i try Gummy 4.4.4 it boots and works fine.
I always wipe cache, dalvik, & use correct gapps. Using TWRP 2.8.7.0 and have tried two other recoveries with same result. Tried flashing L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5 through Odin and then reflashing recovery and retrying ROM, same result.
Right now its working fine with gummy 4.4.4 but I want 5.1-6.0 because that's the only way I will feel ok about having an S3 I'm sure I'm forgetting some details as this has been a two week off and on thing trying to get this phone to work, so if I am please forgive me and have pity (I'm using a blackberry Q10)
Why will lollipop roms not boot?!?!?!
Please..... help me obi wan kenobi...... you're my only hope
Papa Z said:
All I want..... Is an S3 with AICP on Sprint's network.
Two weeks ago I bought an S3 for $50, started playing with it, easily flashed AICP and TWRP 2.8.7.0 Recovery. Everything was awesome, until Sprint couldn't activate it. I flashed back to stock through Odin, Sprint still couldn't activate it (problems with programming). There was no Sprint boot screen, so assuming that was the main problem I found "SPH-L710_ND8_Full Restore_UNROOTED.exe" that restored the Sprint boot logo and viola! I had Sprint 4GLTE and talk and text.......... But now, this little devil S3 won't flash Roms that are 5.0 or newer. I have tried AICP, PAC-ROM, Vanir, Exodus.... all just boot to the boot logo and stay there, but when i try Gummy 4.4.4 it boots and works fine.
I always wipe cache, dalvik, & use correct gapps. Using TWRP 2.8.7.0 and have tried two other recoveries with same result. Tried flashing L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5 through Odin and then reflashing recovery and retrying ROM, same result.
Right now its working fine with gummy 4.4.4 but I want 5.1-6.0 because that's the only way I will feel ok about having an S3 I'm sure I'm forgetting some details as this has been a two week off and on thing trying to get this phone to work, so if I am please forgive me and have pity (I'm using a blackberry Q10)
Why will lollipop roms not boot?!?!?!
Please..... help me obi wan kenobi...... you're my only hope
Click to expand...
Click to collapse
If you the original Sprint S3 and not the new Sprint Triband S3 then you should not have any problem at all! How long are you waiting on it to boot? I had the new Triband model and I had and I thought the lollipop roms wouldn't boot either but I had to give it 5-10mins sometimes on the 1st boot!
RootSuperSU said:
If you the original Sprint S3 and not the new Sprint Triband S3 then you should not have any problem at all! How long are you waiting on it to boot? I had the new Triband model and I had and I thought the lollipop roms wouldn't boot either but I had to give it 5-10mins sometimes on the 1st boot!
Click to expand...
Click to collapse
I have let it sit overnight a few times now.... just to make sure. With the Gumy 4.4.4 Rom it only took about 2 minutes which I was shocked by.
I feel like I have literally tried everything.
Papa Z said:
I have let it sit overnight a few times now.... just to make sure. With the Gumy 4.4.4 Rom it only took about 2 minutes which I was shocked by.
I feel like I have literally tried everything.
Click to expand...
Click to collapse
Yea Kitkat roms don't take very long on 1st boot anymore. But as for lollipop what all roms have you tried flashing?
There's only 2 reasons I can think of that they might not be working. 1st is your model SPH-710T or SPH-710 and 2nd are trying to flash a custom kernel with it?
Another thing I feel like is worth mentioning.... When I first flashed the AICP Rom I played with it for a few days so i had all my stuff installed. Realized I had to flash to stock to activate on Sprint so i made a Nandroid backup of my AICP 5.1 setup. When i restore this backup it boot loops as well.
Tried restoring everything except data, wiped dalvik and cache, all using the same twrp recovery. So strange...
RootSuperSU said:
Yea Kitkat roms don't take very long on 1st boot anymore. But as for lollipop what all roms have you tried flashing?
There's only 2 reasons I can think of that they might not be working. 1st is your model SPH-710T or SPH-710 and 2nd are trying to flash a custom kernel with it?
Click to expand...
Click to collapse
I have tried AICP, PAC-ROM, Vanir, Exodus.... all just boot to the boot logo and stay there. Mine is the SPH-L710 not the triband 710T. The Roms I tried to install, as far as I know, come with the kernel in the ROM zip. I have tried AICP and the pac-rom with just the rom zip and gapps, as well as with a few custom kernels just to see if it would change anything.
Ah another thing, may be unrelated because I only get this when flashing AICP and Pac, it says "unmount of /system failed; no such volume" and then flashes boot img and seems to be successful.
When I flashed exodus and Vanir it does not say this, and all seems to go perfect..... buuuuuut still boot loops/gets stuck at boot animation
Even tried flashing rom and gapps via adb sideload
I have a bad esn l710 in really poor condition. Just flashed the same recovery, same AICP rom, same gapps, all from the same SD card, and this one is working fine. Boots up in just a few minutes.
So i have to be missing something or something is wrong with the one I can actually activate.
EDIT: So "unmount of /system failed; no such volume" error doesn't matter, same thing happened on the bad ESN device that booted up fine.
Update (if anyone cares lol): I flashed both devices completely to stock with the "SPH-L710_ND8_Full Restore_UNROOTED.exe" and then did the exact same thing to both devices, twrp>aicp rom>gapps>dalvik>boot, the bad ESN crap device boots AICP fine, the good condition good ESN one boot loops forever.
I am at a loss here, both devices are exactly the same SPH-L710, flashed to stock completely, but the one with a good ESN that would actually work will not boot lollipop roms. I disassembled both devices to look for hardware differences of any kind, they're identical (with no signs of damage). The only difference is the bad esn one is a slightly deeper shade of blue. I'm pulling my hair out.
I even tried using the force, but my midichlorian levels have never been that good.
Who knows man
I've seen this only a couple times. One guy had luck. When it was stuck, he just kept randomly hitting the power button and eventually long pressed until it was about to reboot (screen freezes for a second) and when it shut off, held home and volume up so it booted recovery when it came on. Then just rebooted system, and this time it booted. Also, sometimes when going back and forth between KitKat and lollipop, you need to wipe internal storage. Make sure you have the latest twrp too (2.8.7.0).
Just shots in the dark, but you never know.
I saw one member who was never able to boot lollipop roms, you would be the second. So its pretty rare.
Well you now know 3 people that cant flash lollipop roms on an l710 NON tri-band.... Ive tried all of them including a couple of Vanir 6.0 roms and the ONLY one i could get to take was a BeanStalk 5.01 rom and a Candykat only after flashing its KitKat predecessor... All KitKat roms work just fine.. Curious,, as I also used the same odin non- rooted rom to get back to stock and after that had trouble flashing lollipop roms period.. Maybe something with the symlinks in that un-rooted rom??? I'm at a loss myself...
madbat99 said:
I've seen this only a couple times. One guy had luck. When it was stuck, he just kept randomly hitting the power button and eventually long pressed until it was about to reboot (screen freezes for a second) and when it shut off, held home and volume up so it booted recovery when it came on. Then just rebooted system, and this time it booted. Also, sometimes when going back and forth between KitKat and lollipop, you need to wipe internal storage. Make sure you have the latest twrp too (2.8.7.0).
Just shots in the dark, but you never know.
I saw one member who was never able to boot lollipop roms, you would be the second. So its pretty rare.
Click to expand...
Click to collapse
As the only possible solution I have not tried, I will attempt to randomly press/long press the home button as it boots and then boot recovery..... lol
What's even weirder is it worked fine with AICP lollipop just about a month ago, before i had done anything to it. but I repeated all the things i did to it on another s3 and that one still worked fine with lollipop roms.
nexusdread13 said:
Well you now know 3 people that cant flash lollipop roms on an l710 NON tri-band.... Ive tried all of them including a couple of Vanir 6.0 roms and the ONLY one i could get to take was a BeanStalk 5.01 rom and a Candykat only after flashing its KitKat predecessor... All KitKat roms work just fine.. Curious,, as I also used the same odin non- rooted rom to get back to stock and after that had trouble flashing lollipop roms period.. Maybe something with the symlinks in that un-rooted rom??? I'm at a loss myself...
Click to expand...
Click to collapse
I used that same unroooted Odin rom on a bad esn s3 and it works fine with lollipop roms. So strange
Edit: no idea what symlinks are
I have similar probl.
After 4 months with CM12.1 I'm flashing NJ2 and upd. to OH1.
After THAT - I cant to flash anything ROM lollipop and higher.
I dont know, what is it.
I was waiting for 4 hours, 8 hours, 12 hours, a day!
I dont know, I dislike TW roms, help anyone!
CyanogenMod 13.0 D2SPR
...I dunno, wanna start from scratch?
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-13-0-t3248561
- Use the Sprint-made TWRP .img in the OP with Flashify (from the Play Store)
- Flash a CM 13, add GApps (from OpenGApps), and a recent SuperSU.
I'm a bit of a half-no0b, so I may be talking out me pants.
Bonne chance!
DavidovDI said:
I have similar probl.
After 4 months with CM12.1 I'm flashing NJ2 and upd. to OH1.
After THAT - I cant to flash anything ROM lollipop and higher.
I dont know, what is it.
I was waiting for 4 hours, 8 hours, 12 hours, a day!
I dont know, I dislike TW roms, help anyone!
Click to expand...
Click to collapse
I'm glad I'm not the only one. Someone has to know how to fix this.... somewhere.
Papa Z said:
I'm glad I'm not the only one. Someone has to know how to fix this.... somewhere.
Click to expand...
Click to collapse
Yep!:crying::crying::crying:
I had the same problem. Try this. It worked for me today.
I have a d2spr (originally from sprint). It is now activated with boost. L710VPUDOH1 bootloader and baseband. CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 flashed with odin for root. twrp-2.8.7.0-d2spr.img.tar.md5 flashed with odin as recovery. I backed up Apn's with "APN Backup & Restore" app. I wiped system, cache, dalvik, data. Flashed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip... . Flashed pa_gapps-modular-full-5.1-20150315-signed.zip. I Wiped Dalvik. The device booted smoothly within approximately 7 minutes. I had full function as far as I could tell. Everything worked well. Ran this setup for about a month. I decided to restore a stock w/root backup made with twrp2870. Bootlooped until I learned to wipe internal sd when going back to 4.4.2. I wiped the internal sd and successfully booted stock w/root backup. When I tried to go back to cm 12.1 backup, I ran into the same problem... boot loop for hours. Multiple times. Backups and different nightly zips. I found and flashed every custom recovery I could find for this device to try to make it work. Eventually... while I had twrp-2.8.7.2-d2spr.img as my recovery (not sure if it makes a difference or not). I found this...
(apparently the link is not allowed due to my lack of posts with this forum)
im pasting from another page at this point...
Ha! Got it! Visited the #cyanogenmod channel on freenode irc and there were some VERY helpful people there. So I've got a few instructions.
Flash the latest TWRP recovery via ODIN. (2.8.7.0-d2spr at the time of writing).
Flash your CM 12 zip file
On your PC (with adb installed) run the command "adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img"
Then run "adb pull /sdcard/persist.img" (This will give you a backup of the persist partition in case anything goes wrong)
Run the command "mke2fs -t ext4 /dev/block/platform/msm_sdcc.1/by-name/persist"
Run the command "adb reboot"
If it boots into OS, great! Reboot into recovery and install the lastest gapps package.
I did it from adb in a Cygwin64 Terminal. The device booted my cm12.1 backup the first time I tried. I think it would work just as well with adb from a windows command prompt. I only found this on another page. Credit goes to someone from "#cyanogenmod channel on freenode irc". Hope it is as much help to all of you as it was to me.
HouseHG said:
I have a d2spr (originally from sprint). It is now activated with boost. L710VPUDOH1 bootloader and baseband. CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 flashed with odin for root. twrp-2.8.7.0-d2spr.img.tar.md5 flashed with odin as recovery. I backed up Apn's with "APN Backup & Restore" app. I wiped system, cache, dalvik, data. Flashed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip... . Flashed pa_gapps-modular-full-5.1-20150315-signed.zip. I Wiped Dalvik. The device booted smoothly within approximately 7 minutes. I had full function as far as I could tell. Everything worked well. Ran this setup for about a month. I decided to restore a stock w/root backup made with twrp2870. Bootlooped until I learned to wipe internal sd when going back to 4.4.2. I wiped the internal sd and successfully booted stock w/root backup. When I tried to go back to cm 12.1 backup, I ran into the same problem... boot loop for hours. Multiple times. Backups and different nightly zips. I found and flashed every custom recovery I could find for this device to try to make it work. Eventually... while I had twrp-2.8.7.2-d2spr.img as my recovery (not sure if it makes a difference or not). I found this...
(apparently the link is not allowed due to my lack of posts with this forum)
im pasting from another page at this point...
Ha! Got it! Visited the #cyanogenmod channel on freenode irc and there were some VERY helpful people there. So I've got a few instructions.
Flash the latest TWRP recovery via ODIN. (2.8.7.0-d2spr at the time of writing).
Flash your CM 12 zip file
On your PC (with adb installed) run the command "adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img"
Then run "adb pull /sdcard/persist.img" (This will give you a backup of the persist partition in case anything goes wrong)
Run the command "mke2fs -t ext4 /dev/block/platform/msm_sdcc.1/by-name/persist"
Run the command "adb reboot"
If it boots into OS, great! Reboot into recovery and install the lastest gapps package.
I did it from adb in a Cygwin64 Terminal. The device booted my cm12.1 backup the first time I tried. I think it would work just as well with adb from a windows command prompt. I only found this on another page. Credit goes to someone from "#cyanogenmod channel on freenode irc". Hope it is as much help to all of you as it was to me.
Click to expand...
Click to collapse
I flashed mine back to stock and sold it.... got a good deal on an S5 and flashed MOAR to it.
I found this thread a while back and attempted to do what it says to do, but I couldn't get it to work for me. What exactly does running those commands do that suddenly makes it work?
I think it either reformats or converts the persist partition to ext4. I'm not 100% sure yet bc I haven't had time to look into it.
Sent from my SPH-L710 using Tapatalk
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
EDIT: I see that Puddi Puddin beat me to it.
Puddi_Puddin said:
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Click to expand...
Click to collapse
tnsmani said:
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
Click to expand...
Click to collapse
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
tnsmani said:
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
Click to expand...
Click to collapse
I am using the newest (twrp-3.1.1-2-oneplus3.img) but the problem is that I can't see anything in recovery or elsewhere :/
Peybro said:
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
Click to expand...
Click to collapse
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Puddi_Puddin said:
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Click to expand...
Click to collapse
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
Renosh said:
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Click to expand...
Click to collapse
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Peybro said:
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Click to expand...
Click to collapse
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
I can give it a try later (and in the future when everything works again) but I do not think (at least I can't imagine) that the problem I have comes from recovery.
I know the reason!
I found other people who also had a static screen and they said they could fix it by pressing the screen back on its contacts...
I did so and it worked!... A bit... For a few minutes...
So the static definitely wasn't the result of rooting and stuff but the repair company's fault.
I hope they accept their mistake and fix it. Thx for everyone here trying to hel me!
P.S.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
And as soon as I can I will try this TWRP
-------------------------------- Edit: --------------------------------
(Just in case people get same problem)
[after Mega Unbrick Method 2 finally worked (I put the stock zip in the tool's folder)]
This morning I restarted the phone just because and I could see what was going on on the phone - but the display was still crazy with yellow tint and colorful stripes etc.). After setup it asked me to download & install newest stock rom; I did and after reboot everything was fine again....
Don't know what happened here but it seems to work again.
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Wow.. Not one answer. What happened to the days where you ask a question, you get ridiculed, then many come out of the woodwork to get you on track...
Oh well........
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Make sure you have the latest TWRP by Bluspark, it just works flawless for me and alot of other people.
Take a full backup. Wipe system and both cache partitions. Then flash the latest Experience ROM. For the open beta releases I should stick with stock kernel. Otherwise Franco and Flash kernel would be interesting. For root I should go with Magisk. Everyone uses it nowadays and the modules are super handy.
Twrp issues
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
wascapsfan said:
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
Click to expand...
Click to collapse
Boot into fastboot, then connect it to your pc and use fastboot flash recovery. Get the latest TWRP.
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
wascapsfan said:
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
Click to expand...
Click to collapse
You may have to flash the original recovery by oneplus , you can find it on one plus downloads in google , make sure before you do anything that you backup anything important like photos , videos to a computer , then download the ROM of choice along with the correct gapps for that ROM and the correct firmware ( most ROMs will include the recommended firmware in their post ) , also download the latest twrp recovery from twrp.me and magisk ( if not included in the ROM ) then its just a matter of wiping system , data , cache and dalvick whilst in twrp , install the ROM with the gapps let the ROM boot and setup a few of your settings then go back into twrp and flash magisk manager and you should be good to go , good luck and make sure you fully read the instructions on the ROM page that you want ...