yashsingh1/xdaforums huggingface dataset:
[Fuhu Nabi 2] Floralina123:
Hi Ste_j, thanks for the reply. I unrooted it already, or so I thought using nabilabs but it looks like twrp was removed and gapps remains - which I'm happy about seeing as I can't update it using ota update with google playstore- that could have been a disaster.

Here is my question I posted -

I Apologise for my ignorance in android in general.

I have rooted a Nabi 2 successfully installing Gapps etc using Nabilab, which was a pleasure to use. Now that the new OTA update is available which includes the Googleplaystore I would like to unroot and get the OTA updates. I thought I had unrooted it - using Nabilabs (twrp would not work, can't remember why but I think the touchscreen part wouldn't work for me). I returned to stock using (option 1. -1.9.37. Android can boot.) recovery using Nabilabs. I think I did a factory reset after that -sorry but it was weeks ago. Anyway, I suspected something wasn't right when I still had Gapps. I don't have TWRP on it now.

When I do the OTA update I get the dead android on reboot. Nabi is working fine apart from that. I read a lot of pages on this website but it ended up confusing me more than helping me unfortunately as I'm not android savvy.

I just need someone to tell me exactly what to do to properly unroot the Nabi so that it is truly back to original so I can use the OTA updates. I have no need to root the nabi again as the google play store is now officially available. And I've got a UK Nabi 2.

Ste_j,

I assumed I had a Uk nabi because I'm in Ireland. I don't know how to check this as it doesn't say uk here but the

model no is NABI2-NV7A-IE

Android version 4.0.4

Kernel version 3.1.10-00298-ge08b99f

MID@keenhi-desktop #2

SMP PREEMPT Tue Feb 26 17:21:35 HKT 2013

Build no IMM76L

Product version: 2.0-release-keys

I don't want to unroot any further unless I can get the latest ota update that gives me the google play store. I would rather leave it as it is now(gapps still on it) until you get yours working successfully ;) I will gladly follow your lead from start to finish then. I just hope someone in the know replies with the solution. I too had been reading the nabi forum but cannot post there.

Tnx
[Fuhu Nabi 2] Ste_J:
Sounds like one of my recent 1am going on for 2 adventures in nabi land!

Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
[Fuhu Nabi 2] metalheadkicks:
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
[Fuhu Nabi 2] Ste_J:
Not yet. Waiting on 2.2 to be uploaded on the other thread. Hopefully the guy will get chance to upload over the weekend
[Fuhu Nabi 2] aicjofs:
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?

In theory restoring either of these(2.0 stock or 2.1 stock) http://xdaforums.com/showpost.php?p=50158865&postcount=67

should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.

Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.

A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.

Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
[Fuhu Nabi 2] Ste_J:
Thank you. I have restored 2.0 from that post

Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
[Fuhu Nabi 2] aicjofs:
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.

Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi. ;)
[Fuhu Nabi 2] Ste_J:
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
[Fuhu Nabi 2] aicjofs:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?

I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
[Fuhu Nabi 2] Ste_J:
That was going from 2.1 to 2.2

And yes i appear to be cross threading at the moment. Grabbed the 2.2 update and just spent the last hour trying to get past the stuck nabi screen. Got back to 2.1 eventually. Fastboot and Nabilab with just enough time to fire over previous TWRP and get back to the restore

Any ideas on how to update the boot loader?

Moving back to the other thread http://xdaforums.com/showthread.php?t=2041224&page=9
[Fuhu Nabi 2] MattP79:
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:

Finding update package. . .

Opening update package. . .

Verifying update package. . .

Installing update. . .

Verifying current system. . ,

assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")

E:Error in /cache/nabi2-update.zip

(Status 7)

Installation aborted

So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
[Fuhu Nabi 2] Floralina123:
Uk nabi update - leaving nabi as is until it's solved

I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
[Fuhu Nabi 2] aicjofs:
Have you tried this? http://xdaforums.com/showpost.php?p=50431606&postcount=98

It has to be done manually but should get a UK Nabi to complete stock version 2.2.

In case you need to know for some reason in the future that is a SHA1 hash not md5.
[One (M7) Q&A, Help & Troubleshooting] topbanana4:
Hi,

My orange EE UK phone is on version Android 4.2.2 ,It is rooted etc with clockworkmod installed I have a update to 4.3, this won't install and have been told that I should flash back stock recovery .

I downloaded the 4.3 OTA file and copied the file onto my laptop from my phone.

I have read somewhere the within the 4.3 Zip file there is the stock recovery file that I need , is this true ?? if so where in the zip file will I find the recovery file.

If when I get the stock recovery file will I be able to flash it with the software (One_M7_All-In-One_Kit_v1.0 ) if not what software would I need to download.

I hope I've made my self quite clear and hope somebody can help me.

Take care everybody and thanks for all your help over the years
[One (M7) Q&A, Help & Troubleshooting] mb_guy:
You will need the stock recovery from your 4.2.2 version, not the 4.3. If you have that ruu you can extract from the firmware folder. If you don't have, try this link. Be sure to get the version for your current OS ie: 3.x.x.x

http://xdaforums.com/showthread.php?t=2545227

The toolkit should work for you but select your recovery , or just use adb directly (fastboot flash recovery recovery.img)
[One (M7) Q&A, Help & Troubleshooting] topbanana4:
my version is 2.24.61.1

I cant find this version anywhere
[One (M7) Q&A, Help & Troubleshooting] mb_guy:
I think any recovery from a 2.24.xxx.x will work, but wait and see if someone else comments.

the recovery from this zip, would likely work. I used a Telus one for my Rogers device.

http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
[Xperia Z1 Q&A, Help & Troubleshooting] arjun.vinoth:
Guys while updating Android 4.3 14.2.A.1.136 firmware via PC companion on Z1(India), I got stuck at step 2, it says preparing sofware and the bar is nearing its end and it takes 5 mins and then the process window closes and again my pc companion shows a new software upgrade is availble for your phone and if i repeat the process again i get the same issue................even i installed SUS, but while opening SUS it says an error has occurred your apllication will shutdown......any help can be appreciated....thx :)

I also tried reinstalling my pc compnaion and also SUS but, I face the same issue. Can you guys tell me any solutions?????
[Xperia Z1 Q&A, Help & Troubleshooting] eclyptos:
Flash via Flashtool.
[Nexus 5 Q&A, Help & Troubleshooting] hg3atintin:
Hi, I am using a metrans wireless charger mwt03 for my nexus 5.

During charging the battery temperature is beween 40-44,5 degrees celcius.

Is this too hot for the phone?

Sometimes it will go to 45 degrees where the phone will still charge but state (overheat) as a status (instead of health: good).

Should I look for another wireless charger?
[Nexus 7 (2013) Q&A] chadhoard:
For some reason, I can no longer boot into recover when using the power/vol up buttons. Can I re flash a recovery to fix or use an app every time I want to get into recovery?
[Nexus 7 (2013) Q&A] Jhall8:
Yes, you can use apps like Goo Manager and ROM Manager for these functions. Also, Cyanogenmod 11 has a setting in Developer Options to allow reboot to recovery from the power menu.
[Nexus 7 (2013) Q&A] Jhall8:
Forgot to add this picture
[Nexus 7 (2013) Q&A] charesa39:
As JHall8 stated, you can use ROM Manager for this. Or, Gravity Box has an advanced power menu option that will allow you to reboot into recovery as well. It works perfectly.
[Xperia Arc Q&A, Help & Troubleshooting] mshipXZ:
Good day to all of you. I would like to tell you my vision for Arc S improvements. Firstly in Gaming. MUST support GB ROM PLEASE!

In-Gaming there should be at least:

- Screen Resolution adjuster: ARC S is way better in 640X480 Resolution (MUST SUPPORT FIT TO SCREEN SO NO BLACK AREAS). Most apps will run at 30FPS stable or more (Dead Trigger, Subway Surfers, etc)

- Screen Resolution for apps: This will set your selected games to run at most at least 640X480 instead of 854X480. (MUST SUPPORT FIT TO SCREEN SO NO BLACK AREAS)This app will set your games resolution to desired resolution when launch.

- More Kernels that you can made to make further improvements or ask DoomLord's or Wedgess permission to continue their GB kernels or ICS or JB.(If existing)

This is my vision. Thanks for taking time to read this. Good day. :) I don't mean any harm if you think that.
[Xperia Arc Q&A, Help & Troubleshooting] Someguyfromhell:
I see your point, however I seriously doubt changing resolution from 854x480 to 640x480 gives any major performance boost (I have no idea, where are you taking it from).

Secondly, fitting the image with size of 640x480 to 854x480 screen will just end up quite stretched.
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
Well if you have such a vision you can start by learning Android programming and development instead of sitting there and telling the whole world your vision.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] mshipXZ:
I tried it. Since The time I used SJB rom Subway Surfers since it lags massively on JB. I had an 26 FPS on normal 20 on Heavy. But when I set res to 640X480 the FPS increase to 33-38 FPS which is great. So it worked that well. But the resolution won't fit the whole screen. It will be stretched but not much. :) In Emulators epsxe normally on Arc S Crash Team Racing has 54/60 on Selecting character on Adventure mode. While I gained more speed when reducing to 640X480. I can run it at 60/60 at 640X480. :) Thanks for noticing my idea since I don't have any money to go to oher devices. This Arc S was originally an Arc (secondhand) given to me by aunt. Then I swap to Arc S.
[Sony Xperia Z Ultra] YoungSkeezy:
Stationed in Italy, want this phone, can I just go to the store this week and start using all the tools in the dev thread?
[Sony Xperia Z Ultra] fastest83:
Yes, the version sold here in Italy is the C6833, which is one of the LTE versions.

When you use any of the mods, make sure you choose the ones marked "C6833" and not "C6802" or anything else.

Roms and ftfs for the international version work on the C6833 as well, but you'll lose the 4G (or LTE).

And if you want to save a lot of money, go on the glistockisti site, they sell it for 599 euros... ;)
[Nexus 7 (2013) Q&A] imablackhat:
My og 2012 n7 I changed dpi and it put it in tab mode where status bar and nav keys become one at bottom. Is there a ROM or way to do this with 2013?

twitter/instagram : [MENTION=258995]imablackhat[/MENTION]
[Nexus 7 (2013) Android Development] TheDarkDefender:
Reserved

Screen shots :
[Nexus 7 (2013) Android Development] TheDarkDefender:
Reserved
[Nexus 7 (2013) Android Development] TheDarkDefender:
one more!
[Nexus 7 (2013) Android Development] aamitabh28:
Wow.. Thanks for bringing this to flo mate !
[Nexus 7 (2013) Android Development] TheDarkDefender:
Just couldn't resist once I flashed it on my mako! :D

Sent from my Nexus 4
[Nexus 7 (2013) Android Development] MidnightDevil:
Can I kindly ask what this build consists of, regarding other CM builds?

Difference in tool chain, optimizations, cherry picks... ?

Thanks for this!
[Nexus 7 (2013) Android Development] aamitabh28:
Visit the link in the OP
[Nexus 7 (2013) Android Development] TheDarkDefender:
All the info is in the OP. Check the links for the complete list. Pulling out each n every feature and listing it in the OP is tedious. That is why we ask you to check it out yourselves :)

Sent from my Nexus 4
[Nexus 7 (2013) Android Development] jaybizza:
Awesome work guys!! I'm using this on my T-Mo Note 3!! I see there are a bunch more add ons with the Flo build!! Thanks for all the hard work and will post my findings soon!
[Nexus 7 (2013) Android Development] MidnightDevil:
Flashed it and so far so good. It's smooth, all functions are working fine and it's pretty smooth. I love the Omni addies.

Flashed Glitch kernel (CAF) version and it's working perfectly well :)

I love the CM base with these cherry picks.

Thank you for giving to us flo users :)

I'll report in case I find some little bug.
[Nexus 7 (2013) Android Development] TheDarkDefender:
Added a video in case anyone wants to take a quick peek at the features.

https://www.youtube.com/watch?v=QJ2wrpolSWc&feature=youtube_gdata_player

Sent from my Nexus 7²
[Nexus 7 (2013) Android Development] MidnightDevil:
Very much appreciated. I find it useful to know better what we're about to flash (could you add it to the OP?).
[Nexus 7 (2013) Android Development] TheDarkDefender:
Done.

Sent from my Nexus 7²
[Nexus 7 (2013) Android Development] RyLoS2000:
My Nexus7 arrives tomorrow and i will unlock and flash this baby...just one question:

I wanna install glitch kernel, what version i need to flash, AOSP or CM?
[Nexus 7 (2013) Android Development] TheDarkDefender:
CM. :)

Sent from my Nexus 7²
[Nexus 7 (2013) Android Development] aamitabh28:
Loving the Rom man! Seriously very very cool.. Thanks alot
[Nexus 7 (2013) Android Development] aftermath85:
Caught my eyes

Ok this is it! i always love temas work back in the optimus 2x days.. :good:

before flashing, is the elemental x compatible with this rom? :) PA gapps too?
[Nexus 7 (2013) Android Development] TheDarkDefender:
PA gapps yes. Elementalx no. Only Glitch,AK kernel or any cm / caf kernel are compatible, for now.

Sent from my Nexus 7²
[Nexus 7 (2013) Android Development] nikr123:
This ROM is awesome together with glitch, thanks.
[MDA III, XDA III, PDA2k, 9090 General] mg-max:
I get an error on my XDA2s, when I try to start the camera:

"Failed to initialize camera. Please reset the hardware. 36001:1:100:2"

I did this, but still no joy.

I tried to search for a CAMERA cab on here, but can't find anything that works.

My device is WM2003.

Can anyone help?

I have seen other ppl with the same error, but no fix.

Max
[MDA III, XDA III, PDA2k, 9090 General] aprmike:
I had this issue after updating the ROM. I needed to update the operator software to fix it (in this case from orange). You may also find that media player wont load as it cannot find any skins. Let us know how you get on.
[MDA III, XDA III, PDA2k, 9090 General] mg-max:
Tried.. failed

I re-flashed.

What a drag.

:(
[MDA III, XDA III, PDA2k, 9090 General] rio1981:
flash

was it easy to flash? and did it sort out the problem?
[MDA III, XDA III, PDA2k, 9090 General] willpower102:
it's easy to flash.

Read the wiki

wiki.xda-developers.com
[Android Apps and Games] youssef badr:
Hello XDA

How are u guys ? i hope you are okay , because surely Droid bird will make u ' not'

I decided to mod Flappy bird to make it a little less Birdy but it's still flappy of course ;) :highfive:

ScreenNshots

Downloads ;)

Just Download the Apk from here

P,s : to install it remove flappybird :fingers-crossed:

Credits :

My teammates

Flappy bird developer

Okay guys so that's it Don't forget to press the thanks button if u like it

Find us on facebook

fb,com/Androidworld9​
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] *SHB*:
Dear Friends

It is possible to downgrade from Android 4.3 to Android 4.1.2 via Mobile Odin 3.85.apk

Don't use windows Odin program for downgrade

Just download Mobile Odin 3.85.apk from Internet ( registered apk version from torrent )

and download android Jelly bean 4.1.2 from www.sammobile.com

and copy your stock rom md5 file in your Internal Memory and SD Card

and Flash through Mobile Odin 3.85.

I have done it successfully

its not removed knox bootloader but we can downgrade to Android 4.1.2 and its working smoothly.

No problem at all.

Try it on your own risk !!! I got success coz I Love risks. :P
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] sham79:
And if you go into download mode do you still see the Knox flag?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] *SHB*:
Yes knox flag is there and I already have knox 0x1 warranty void

but i have rooted my SGS3 successfully and super su installed on my Android 4.1.2 which not possible on Android 4.3 coz of knox interference so I think knox side effect will end by flash via mobile odin.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Lerpzu:
:D You made my day! Thanks, but people allready knew that it was possible to downgrade to 4.1.2.

They are looking for a solution to downgrade the bootloader, not the firmware.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] kamikaze702k:
knox is a pain in the backside!!

i had many S3 devices, luckily all are still on the old bootloader!! bought an S4 mini few months ago, luckily that was on the old bootloader also, so no knox for any of them, few weeks ago i decided to get the S4, came with knox! sold it, found an old firmware S4, was on 4.2.2 but somehow had the knox bootloader, sold it, bought 4 S4 devices in the space of 2 weeks, all with knox bootloader, ive now given up on S4 and Samsung all together!! ive since then gona back to my old rooted knox free S3 and S4 mini,

no longer will i be buying any more Samsung devices in the future, they can stick it with knox!!

if your reading this thread its probably too late to downgrade your bootloader but i highly advise DO NOT UPGRADE YOUR FIRMWARE!!!

if your rooted keep your old stock firmware thats knox free and keep using custom roms instead!!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] shayind4:
I have S3 i9305 on 4.3 Knox flag 0x0. If i use mobile odin to downgrade the firmware, will it trigger Knox flag 0x1?

Thanks

---------- Post added at 08:37 PM ---------- Previous post was at 08:29 PM ----------

You are right. Knox is a real pain!!! However, i did manage to root S4 i9505 4.3 and Note3 4.3 by doing a factory reset to clear any security updates, and avoided setting up wifi (which will automatically download new security updates)/avoided auto security updates downloads in settings, and use Kingo for rooting.

Like you said, it's not advisable to upgrade at this time.

---------- Post added at 09:20 PM ---------- Previous post was at 08:37 PM ----------

I believe root is required for Mobile odin pro. Were you rooted then before downgrading with mobile odin? I have been unable to root my SGS3 4.3 MKC without triggering knox flag. It seems that i cannot use mobile odin to downgrade the firmware and then root afterward.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] shucrut:
At least for me, was not possible to root 4.3 without triggering knox ans to use mobile odin you need root access, so.. If you succeed rooting without triggering knox, you will have flag 0x0 at the end with mobile odin.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] xclub_101:
What are you saying here? Mobile odin normally works only when you are already rooted ???
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] mervingeo:
remove or reset knox counter

so is it possible to reset knox counter or remove it?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] *SHB*:
No Knox isn't remove
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] shayind4:
Knox counter cannot be reset at this time.