I tried to install the omnirom build and it really messed up the ouya. I think it's because it tried to upgrade to lollipop 5.1.1 and it changed the directory structure. The only thing I could get working again is the ouya image however there is no spot for download anymore. Instead there is a 0/download. Anyway to flash firmware so that the box is completely back to ouya. Right now it is saying there is no external storage. Can anyone help me out of this problem?
Related
My N7 16GB WiFi, rooted but stock, updated successfully to 4.3 some time ago. Basically, I used Voodoo OTA to save the root, let the OTA do its work, then restored root using Voodoo OTA. It's worked flawlessly since then.
Suddenly, after weeks with no issue, it started insisting it had to install 4.3 from a downloaded file. It nags constantly, which makes it hard to use the tablet. I've got CWM as the recovery so whatever file it's trying to install won't work from there. The only way I can find to go back to stock recovery involves wiping the tablet. I don't want to do that, unless there's no other alternative.
I looked for the update.zip file in the location that the tablet insists its stored at (root of SD card), but there's no file there by that name that I can find. It only shows up if I allow the nag screen to try and install it. Of course, CWM says that it can't verify the file and aborts the install. Which puts me right back at the ever-present nag screen.
Just to be clear, I am already running 4.3. This whole situation came up months after I'd upgraded. Is there anything I can do to stop the upgrade notices, short of running a factory reset and having to set up the tablet again from scratch?
May have found an answer. Used Wug's toolkit to force-restore the standard recovery. Had to do some old ADB driver removal for a bunch of other Android devices first. Appears to have deleted the unnecessary update file as part of the process. Will keep an eye on it going forwards, but think it's good.
Nope -- didn't work. Had to do a full factory reset/restore to out-of-the-box condition to get it to stop constantly trying to re-upgrade to 4.3. Annoying.
Just downloaded the 5.0 OTA File for N10:
3f896c6158a5b8a2ebf8e85462a6fb9f6ebc8523.signed-mantaray-LRX21P-from-KTU84P.3f896c61.zip
Have rooted KTU84P installed, original recovery
Issued "adb sideload 3f896c6158a5b8a2ebf8e85462a6fb9f6ebc8523.signed-mantaray-LRX21P-from-KTU84P.3f896c61.zip" as Admin.
File loads but then this Error: /system/app/maps.apk has unexpected contents
See Screenshot
Any Ideas ?
Did you ever solve this problem? Getting the same thing on my Nexus 7.
I have the same problem, update for 5.0.2.
I also have this maps.apk issue while trying to update to 5.0.2 from 4.4.4 on a 2012 Nexus 7.
Why not flashing factory images?
Sent from my Xiaomi MI2s
same problem
brossow said:
Did you ever solve this problem? Getting the same thing on my Nexus 7.
Click to expand...
Click to collapse
same here
Initially I was able to sideload 5.0 and then 5.0.2 update by installing just the stock 4.4.4 system.apk (IIRC) over the top of my existing 4.4.4. It "worked" but was incredibly slow, and the total storage space on my 32GB device was only showing as 6GB. To resolve both of these issues, I ended up wiping the whole thing and installing from scratch using Wugfresh's tool. Tablet is much quicker now than it had been under 4.4.4, but likely because of the reset rather than because of the new Android version. I'm still getting odd issues even with minimal third-party apps installed where the tablet just freezes up for several (or more) seconds, then eventually goes about its business like nothing happened. (Sometimes instead there are FC messages about the system or Chrome not responding, but all of that is beyond the scope of this thread.) Long story short: my solution was a complete wipe and fresh start. Not a great solution, but it's working mostly well. Looking forward to the rumored 5.1 update next month.
If you want to read the below learning experience you may gain some knowledge but at this point I believe my method may have flaws. While it seemed fine at first the problem listed directly below could not be fixed without using Odin to flash a stock ROM back onto the phone. It had checked the hidden menu settings for MTP and ADB and PDA, CP etc and all were correct (I have another good working S5 to compare these values to). I tried an earlier restore of a TWRP backup and that just blew up with all sorts of FC's on boot. So thank goodness for Odin. After flashing the stock rom it booted fine and I can now write files from the PC to the phone again via USB. In the process right now of re-rooting, installing TWRP and doing a restore of my last backup.
Note : I have found one problem I am currently working on after using this method. I can hook up the phone to the PC and get a link, open folders on the phone and can copy file from the phone to the PC but can NOT copy files from the PC to the phone. More later .....
I've got a Samsung Galaxy S5 from US Cellular. Other than a few people in the Motorola subforum here trying this I haven't seen this exact method described here so apologies if I missed it somewhere - tried many searches. It seemed so easy - maybe it is just considered SOP for some - don't know so I'm going to run the details by here anyway in case it saves anyone some trouble. Do read my warnings below though before you attempt this.
1 - You want TWRP installed (or Philz CM Touch will probably work too - seems a bit more complex though) If you are flashing ROM's having TWRP or some other custom recovery is always a good idea and I'm sure most people have one of them.
2 - Always do a complete backup with TWRP before flashing anything new. You did a backup before going to Lollipop didn't you?
3 - So you are tired of the white screen, battery sucking, quirky Lollipop or maybe that Cyanogen Lollipop mod didn't quite work for you and you want the old Kitkat back. So fire up TWRP, go into Advanced wipe and wipe Dalvik Cache, System, Data and Cache. You aren't done wiping yet though. After you swiped to wipe those go back to the previous page and Swipe to Factory Reset. That may not actually make any difference but I just did it for good measure and my method worked great.
4 - Now without out even needing to reboot find your latest backup of Kitkat 4.4.2 that you have on your Internal SD or External SD card (you do keep one there don't you in case your phone glitches on you while you are out and about?)
5 - Do a Restore of everything - Boot, Recovery, System, Data, Cache.
6 - Reboot. You are done.
Firstly I need to add that I had flashed Cyanogen Mod 12.1 (Lollipop 5.1) after following directions here in the main Cyanogen subforum to flash that on my KitKat 4.4.2 Galaxy S5 phone. What may be noteworthy is that after flashing CM 12.1 I ran the App PhoneInfo Plus (made mostly for Samsungs) and the OS version showed as Lollipop 5.1 but some of the build numbers to my recollection showed 4.4.2. So this was not a stock Lollipop OTA - it was the Cyanogen mod of Lollipop made by developers here. I just assumed they started with Lollipop to make that latest 5.1 build but I haven't followed the Cyanogen mod much at all so I don't know if they have borrowed bits and pieces of Kitkat in their builds. If they have done that then this downgrade method may not work the same for an OTA Lollipop.
Another warning - I noticed in the Motorola subforum here that some people bricked their phone trying this type of downgrade with TWRP however I believe that is because they had Verizon phones with locked bootloaders and that is not the case for my phone (US Cellular) or any other phones beside VZ as far as I know. If you have a Verizon with locked bootloader beware! I will also add that on my first boot after restoring Kitkat 4.4.2 that the second the home screen was up I started quickly scanning through my app pages and the phone rebooted itself. I believe it wasn't fully done loading the OS and it just was a hiccup. It has not happened since after trying all sort of things. Everything is working great.
I saw most people recommending to use Odin to flash a stock Kitkat firmware back on the phone in order to downgrade from Lollipop. Then you need to re-install all your apps or maybe do a restore of a recovery but with this method using TWRP you bypass most of that and get it all done in one TWRP session.
Another note about what I read people having a problem with upon downgrading - some were losing their IMEI when using Odin to flash the original firmware. I still have my original IMEI with no problem. That is another reason I think this method may be better than using Odin for this downgrade. I'll add that there are a lot of people around here with a whole lot more knowledge about flashing and custom ROM's than me so don't take my ideas as hard fact without doing your own research for your particular phone and particular situation.
I can copy FROM the internal and external SD card to PC but not PC to either internal or external SD card and the permissions seem to be correct for the folders I'm trying to copy into. Anyone have any ideas on that? However I was able to use AirDroid (Wifi) to copy files to the phone from the PC - no real surprise there but it reaffirms that I can write to those folders - just not with the USB cable.
More info. I just decided to run the App KitKat external SD Card patch. It failed. I believe I ran that before flashing Lollipop and it worked but now it fails. ?? I don't know if it is related to this problem since both internal and external SD are having a problem - but only via USB.
I tried another Galaxy S5 with same computer and cable and that one works fine to copy to the SD cards so that eliminates the cable or computer. AirDroid - Wifi works but only a problem one way with USB - WTF?
droidzer1 said:
I tried another Galaxy S5 with same computer and cable and that one works fine to copy to the SD cards so that eliminates the cable or computer. AirDroid - Wifi works but only a problem one way with USB - WTF?
Click to expand...
Click to collapse
Well thanks to TWRP AND Odin all is well once again in Androidland
Hi,
So I have a Note 3 N900W8, Stock 4.4.2, rooted with SuperSU & the usual xposed & busybox config.
I had TWRP working fine but I hadn't gone to recovery in a while, probably a few months or so & when I went a few days ago somehow recovery had reset to stock recovery.
I usually download TWRP off their website & install using a terminal on the phone itself. But the TWRP website wasn't working so I couldn't download the file, so I installed TWRP (the latest version for hltecan) from TWRP Manager which is on the PlayStore.
It got installed just fine & TWRP loads up perfect. Right after that I wiped my cache & dalvik/art. That also went just fine.
But since then, my internal SD card has been going nuts. The phone turns on perfect, everything works, apps still function for the most part. What isn't working is, SD card is not entirely readable I think & definitely not writable through apps.
ES explorer shows the sdcard as blank in every location (not a single folder).
Titanium backup doesn't even load up, just stuck at loading screen says loading app data.
Lucky patcher says SD card not mounted
Camera doesn't work, can take pictures but they of course don't get saved & videos say recording failed.
I'm guessing a factory reset would probably fix it, or not. But before trying that I want to know if there's any other way?
Please help!
Thanks!
Cheers!
Personally, I would flash the latest stock ROM from sammobile.com, set up the phone to make sure everything works, then flash TWRP and a custom ROM of your choice.
audit13 said:
Personally, I would flash the latest stock ROM from sammobile.com, set up the phone to make sure everything works, then flash TWRP and a custom ROM of your choice.
Click to expand...
Click to collapse
Hey yeah, exactly my thoughts, unfortunately sammobile hasn't been working for a while I think, their free servers are down :/ But 5.0 is finally available for the Canadian Note 3s! Should get on that!
But anyhow, I found the fix, there's this app on the PlayStore; Int-SdCard Write Fix (https://play.google.com/store/apps/details?id=com.vinny.intsdfixer&hl=en), does the trick! I'm guessing it's just a small bit of code but bloody brilliant!
After I updated my N7 from 4.4.4 to 5.1.1, it got so slow that it's unusable. Can I go back to 4.4.4 somehow?
Or should I install a custom ROM? And if so, is there a good guide for that?
sure... well... before I say for certain, it all depends on if Google still hosts the AOSP images. I suspect they do. Grab whatever official release you want to fall back on and fastboot install it per their instructions.
Any other feedback anyone?
Hi, I was in the middle of downgrading my N7 from 5.1.1 to 4.4.4
It failed to take the flash and now I can't turn it on, (tried the button thing) also now the PC and adb won't connect. Looking on this forum for someone who knows there way around the N7 and can get my 7" brick back to life. p.s. also tried unplugging the battery trick, no luck here either.