Hi All,
I recently purchased a Nexus 7 (2013). Its my first Android device and so far I've been really enjoying using it.
I managed to root it and installed Multi-rom. I have two roms on it. Stock 4.4.2 and another Kali based rom.
Anyway recently I saw an update for 4.4.3 and I tried to install it from my stock 4.4.2 rom ( I'm thinking this was a mistake?)
Anyway it download and the booted into recovery mode. I wasn't sure what to do and I just rebooted it again and opened up my Stock image.
The issue is now I cannot turn on Wifi for some reason. From the Wireless conections page it just says 'turning on wifi' but never does. If I boot into my other rom wifi works fine.
The version of Android on the stock rom still says 4.4.2. My Kernel version is 3.4.0-g80964c2 and the build number is KOT49H.
I'm kind of new to all of this and don't know how to proceed. If anyone could help me it would be very much appreciated.
Cheers.
MarcG
Just use this: http://forum.xda-developers.com/showthread.php?t=2389107
It will even download the correct images for you.
k3lcior said:
Just use this: http://forum.xda-developers.com/showthread.php?t=2389107
It will even download the correct images for you.
Click to expand...
Click to collapse
Thanks k3lcior!
I guess I can use this to get back to a clean known state with the 'Flash Stock + Unroot' option.
However I was wondering is there a way to update my internal ROM when I've got multirom installed? Trying to update from within 4.4.2 seems to have gotten me into this mess in the first place, so I'm trying to learn how I should update my internal stock rom in the future?
cheers.
I have no idea as i've never used MultiRom so dont want to speculate.
Hello everybody,
even after 4hours of google and searching I was not able to get an answer. Why is the new Recovery Partition, which was announced three months ago, not used somehow? http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/
I want to use latest CM and somehow, since a few days, a seperate recovery image is available http://download.cyanogenmod.org/?device=amami
So in the end, I am totally confused, there is no "clean" installation method, even the CM wiki tells me to flash boot.img with recovery included while sony annoueced seperate recovery partition 3 months ago, and I am not able to find a recovery.im to flash... Is it not working well or why still the old way is used?
I want to go to latest stock, then unlock bootloader (without saving TA-partition), and then I wanted to use the seperate recovery partiiton I am used to work with on my other Android devices.
So please any hint or thread or anything which might help me I am really lost...
best regards and I wish all a nice weekend
Hello all - I've been working for a few weeks (off and on) trying to get my old Incredible 2 in a working order to use as a wifi media device. To get he newer apps I needed to upgrade to at least ICS. I went through htcdev to be able to flash roms and then decided to downgrade and try to get to s-off - at which point I discovered revolutionary was down....I've since been able to get back to the htcdev unlocked bootloader process so I'm s-on with hboot .98. I'm using TWRP 2.6.3. I've tried three different roms - two cm10.2 and one cm11 and while they flash I'm not able to get past the boot screen (past the HTC one). I've done wipes before each flash and I've flashed the correct boot.img each time. I've tried each one of them at least twice to no avail. Is there any other settings or things to try??
My ultimate problem is that I was able to get to Android 4.2.2 but the app that I need to play my music from the cloud is Microsoft Groove which due to a recent change is no longer working with 4.2.2 (kind of like the perfect timing I had with revolutionary being down) - so I'm trying to get to something higher than that...Any other ROM ideas might help too???
Thanks. I've learned so much following this forum over the last few weeks - I just can't seem to get past this one by myself.....
Well thankfully I was able to solve my own problem...Figure I'd update here in case anyone else comes across the same issues. I basically did not have the best TWRP version installed - you need to have TWRP 2.7.0.0 installed. Once I installed that recovery I was able to flash each and every rom and the phone is starting up fine (after also flashing the correct boot.img file). We'll now see if I can get past the app issue itself that I was having but I'm definitely past the boot screen issue.
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.
Hello everyone,
A few weeks ago, I bought a reconditionned OnePlus 5T and installed /e/ on it. Now, I would like to install back OxygenOS.
My problem is that I can’t manage it.
As I couldn’t access to recovery (TWRP) anylonger (don’t know why, maybe something to do with the fact I flashed the 5.1.7 firmware a few days ago, I don't have a clue), I flashed an early Blu Spark one (3.2.1 as the 3.3.x ones won't work on my device). And it worked, I can access recovery through this one.
But when I try to install any OOS zip, via recovery Install menu or by sideloading it (downloaded from the OP website (the most recent one, or from the mirrors referenced on this xda forum, I tried several zips but don't really know which one is really relevant), it fails.
And the only thing I can do is installing back /e/. I tried several ways of doing it, following several guides but even the ones for the ultimate guide available on the One Plus Forum won't work (can't make it recognised by any device manager, maybe the fact that I'm running Ubuntu and not Windows).
So that, for the time being, I’m stuck with /e/OS (based on a LineageOSrunning Android 8.1).
There surely is a step or a file I missed, but which one... Any idea anybody ?
I finally got it working. Through the*********** 's guide.
donatienb said:
I finally got it working. Through the*********** 's guide.
Click to expand...
Click to collapse
Hi !
Im interested in going back to OxygenOS from /e/os because the new builds are on android 11, and my current /e/os build is on android 8.1
The idea is to get OxygenOS back, upgrade using OxygenUpdater, and then install de latest android 11 /e/ build.
So what was the name of that guide ?
Thanks