FORUMS

NVIDIA Launches SHIELD Android TV at Google I/O

Since Android TV was announced at Google I/O 2014, there has been very little activity … more

Devs Beware – Automatic Backup Privacy Risks

One new feature of “Android M” (speculation on potential names welcomed … more

Android M to Bring New App Drawer

It has now been seen that Android M will receive a new app drawer as part of the stock … more

Which IO Announcement Are You Most Excited About?

The keynote we had all been waiting for has just ended and it’s time to enjoy … more

[REF] Nexus 7 Stock OTA URLs

Thanks Meter: 2,754
 
By oldblue910, Recognized Contributor / Archivist-in-Chief on 1st July 2012, 11:58 PM
Post Reply Subscribe to Thread Email Thread
13th February 2013, 01:36 PM |#271  
oldblue910's Avatar
OP Recognized Contributor / Archivist-in-Chief
Flag Durham, NC
Thanks Meter: 2,754
 
Donate to Me
More
Quote:
Originally Posted by osm0sis

Really? Sh*t didn't know that. Stupid issue since it shouldn't affect the OTA reading the build.prop but somehow it does, eh? Apologies folks.

My advice still stands for all file asserts, however. If it's failing on a file, use the methods I posted above. And please don't post until you've at least tried.



Yeah that's really weird because that's not how getprop in edify is supposed to work. You mount system first and it's supposed to grab those from the build.prop.

As for having an actual image for tilapia. Shouldn't 6.0.2.3 work?
download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.2.3-tilapia.img

and he's using TWRP, so same difference?
techerrata.com/file/twrp2/tilapia/openrecovery-twrp-2.4.1.0-tilapia.img

Yes those should work. People ran into that same issue back when JOP40D rolled out 3 months ago. People were using grouper recoveries and the asserts were failing when checking device. I'll bet you dollars to donuts his recovery was designed for Grouper. All he should need to do is flash a tilapia recovery and he should be all set.
The Following User Says Thank You to oldblue910 For This Useful Post: [ View ]
 
 
13th February 2013, 01:38 PM |#272  
osm0sis's Avatar
Recognized Developer / Recognized Contributor
Thanks Meter: 15,718
 
More
Again, frigging weird if you know how getprop works. Thanks for the info!

Oh, about the nakasig bootloader, I can pretty much guarantee it will also be 4.18, since I checksummed 4.13 for both devices when I was writing my BootUnlocker Script guide and they were exactly the same.

Edit: There we go!
Last edited by osm0sis; 13th February 2013 at 01:43 PM.
13th February 2013, 01:41 PM |#273  
Member
Flag N E Wales
Thanks Meter: 9
 
More
Quote:
Originally Posted by oldblue910

Can someone who has updated a 3G Nexus 7 to 4.2.2 do me a favor? ......

Baseband 1231_0.17.0_1205

Bootloader 4.18
The Following User Says Thank You to Ydnaroo For This Useful Post: [ View ]
13th February 2013, 01:42 PM |#274  
oldblue910's Avatar
OP Recognized Contributor / Archivist-in-Chief
Flag Durham, NC
Thanks Meter: 2,754
 
Donate to Me
More
Quote:
Originally Posted by Ydnaroo

Baseband 1231_0.17.0_1205

Bootloader 4.18

Thanks buddy!
13th February 2013, 02:14 PM |#275  
Member
Thanks Meter: 8
 
More
If anyone is curious and it may have been mentioned, but I used the tool ( not wugs) in development thread to flash stock then downloaded the 4.2.2 patch and ran it and am running 4.2.2 just fine. Though o was willing to flatten my device completely with tool, I had all my pics and music in cloud. Hope this helps. 4.2.2 runs quite a bit faster then 4.2.1 and faster then I remember 4.1.2. Happy flashing.
13th February 2013, 04:15 PM |#276  
jaysus145's Avatar
Senior Member
Thanks Meter: 33
 
More
Quote:
Originally Posted by Johnassel

I got this error, too.
I fixed it by downloading the factory image from here https://developers.google.com/androi.../images#nakasi and extracted the file with this tool: http://forum.xda-developers.com/show....php?t=1921399
Then I copied it with RootExplorer to /sytem/bin, chmodded it with 755 and after that the update worked.
I've attached the extracted debuggerd - so only the last step is necessary.

Thank you sir! I appreciate the leg work.
13th February 2013, 05:31 PM |#277  
tdizzle404's Avatar
Senior Member
Flag North Georgia
Thanks Meter: 1,101
 
Donate to Me
More
Re: [REF] Nexus 7 Stock OTA URLs
I had the error and the easiest way I found to get 4.2.2 to flash was to use wugs toolbox from his sticky in development and just flashed the stock image.
You can also back your device up with his program So DO THAT and I also backed up my internal storage because this method wipes every thing, But any ways flash stock then root. Boot phone ,set up phone update super su app and busy box installer then flash twrp via goo then download ota keeper and remove root. Boot into recovery and flash the update zip that is posted in the op. Reboot and your good.
You will have to update sdk if you want to use adb.
Stock 4.2.2 is really amazing so far.
And thanks for the help guys

Sent from my SGH-T999 using xda app-developers app
13th February 2013, 06:41 PM |#278  
ALD3's Avatar
Senior Member
Flag OC, Florida
Thanks Meter: 155
 
More
Re: [REF] Nexus 7 Stock OTA URLs
Updated SDK and still unable to see device......not just adb, I mean the computer does not see my nexus 7. 3 desktops, 1 laptop all with win7 32 or win7 64. They all see all my other android devices, I know its weird. Does anyone one know how I could get back to another version, so I could start over? Tablet works fine, its just with no USB and no micro sdcard is hard but I do use several cloud devices.
Even having trouble using xda on nexus
Sent from my SAMSUNG-SGH-I957 using xda premium
Last edited by ALD3; 13th February 2013 at 06:43 PM.
13th February 2013, 06:50 PM |#279  
mustbepbs's Avatar
Senior Member
Thanks Meter: 298
 
More
Anybody get ApplicationsProvider.apk Status 7?

I'm on JOP40D stock deodex with root, stock kernel. Is the deodex causing issues? Flashing with CWM. Grouper.
13th February 2013, 07:09 PM |#280  
Member
Flag Kota Bharu
Thanks Meter: 2
 
More
Confirmed, Nakasig 4.2.2 still has "swipe-bounce-back" issue and no tethering either! Disappointed!
Overall feel smother tho...
Sigh~
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Nexus 7 General by ThreadRank