How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
toby1978 said:
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
Click to expand...
Click to collapse
I've got the same question. I know I'm an idiot that shouldn't have installed Gapps without having a clue, but unfortunately I did. I used the Victoria Antonio youtube video that says it does not root but does install Gapps about 4 months ago--May 2013. I'm now trying to figure out how to get the OTA update to 2.1, but I'm just lost, since it's been a while. I tried fooling around in TWRP, but again, didn't have any luck. Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
abbienormal said:
Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
Click to expand...
Click to collapse
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Thanks and sorry!
aicjofs said:
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Click to expand...
Click to collapse
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
abbienormal said:
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
Click to expand...
Click to collapse
If you followed any of the guides out there then you likely have gapps on your tablet(Google Play Store). If that is the case then it has modified/removed some system files. When the Nabi OTA does its thing in the "Android guy" screen(aka stock recovery) it finds files missing or modified and halts the OTA.
You have 2 options. 1) Use a modified OTA(that ignores those files), or
2) restore your backup you made during the Victoria video that has unmodified/removed files then do the OTA.
There is a caveat. The new 2.1.27 OTA uses up almost all the room on the system partition. Without removing something you cannot have a tablet with full gapps package and full Nabi 2.1.27 something will have to be deleted.
Start reading from post #1597 http://forum.xda-developers.com/showthread.php?t=1905674&highlight=nabi&page=160 it will make some more sense.
Update Nabi 2
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
rozibaby84 said:
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
Click to expand...
Click to collapse
Assuming you are on 2.0 right now?(2.0.5)? I'm going to base my description on that, if it's 1.9.37 or less there would be other steps.
If so you have a couple of options. I don't know which method you used to get playstore so it's a bit harder. There are 2 questions that you need to answer for yourself. Do you want Wings or the Playstore? Because as of right now it's difficult to fit them both on, and while we kind of have a method using symlinks it's not perfect yet.
So if you want to update and keep the playstore the first thing you need to do is figure out if you have TWRP installed(probably best to have version 2.6.1.0). WIth tablet powered off press and hold the vol+ and power key, navigate with the vol- key to recovery kernel and vol+ to select. If it boots to TWRP you can go on, if it boots to an Android guy you need to install TWRP. Once you have TWRP. MAKE A BACKUP! You can delete it later if you choose but make one now so you can get back to where you are if something goes wrong. I would use external SD for all of this because these are some big files.
After you have done that you can try to do this:
Download these
https://docs.google.com/file/d/0B024tOntNFbbaFJHcFRBRjVMUXc/edit?usp=sharing
http://home.comcast.net/~aicjofs/205to210libfix.zip
Copy them to the Nabi.
Boot in to TWRP and "install" both of these. You should be at 2.1 with Playstore and no Wings(You will still have one Wings app)
OR
You can restore a stock 2.1 if the above doesn't work
Download this:
https://docs.google.com/file/d/0B024tOntNFbbX1liUGN5eVU4UU0/edit?usp=sharing
Extract boot.emmc.win, system.ext4.win from the zip in to the TWRP folder on the device to internal storage(may not have room)
TWRP/BACKUPS/%serial%/2127
Or external SDcard
TWRP/BACKUPS/%serial%/2127
you will have to create the 2127 folder, and possibly the others(if you made a backup some of this will exist already) %serial% = whatever your device serial number is it's different for everyone.
Then boot to TWRP and "restore" checking boot and system only. Don't select data(it shouldn't be an option if you didn't copy data.ext4.win from the zip anyway)
This would leave you at 2.1.27 with Wings but no playstore. You can root it at that point but not install the Playstore unless you then deleted Wings.
The Product Version on the Nabi 2 tablet is 1.9.37. I am assuming that is what you were referring to when you asked if I was on 2.0 right now. I don't really care if I have the Play store or not anymore. At this point, I just want to be able to get the Nabi update and see if it addresses some of the other issues that I am having. I think that I made a huge mistake in doing all of this since I do not actually know what I am doing. I think the only reason why I got the Play store was for one specific game and I don't even remember what that game was anymore, so she will be ok without it.
I do not really understand what TWRP or anything like that is. Is there an easy way to just get rid of everything and pretty much start from scratch so that I can get the updates like normal? I know that the factory reset doesn't get rid of the rooting, unfortunately.
I am really grateful for your help! Thank you!
Error in /external_sdcard/...
I am not sure why I am getting his but I have tried every version of the Nabi2 ROM stock and custom 2.0.5 and above. It seems that I can only install previous versions to 2.0.5.
I have TWRP v2.3.3.0 installed and I am trying to get the latest 2127OTA build installed. If I revert back to stock ROM it boots fine but there a few odd going ons. One it always defaults to Mommy Mode even though I select Daddy Mode. WiFi never works even with WiFi fix. Tap sound does not turn off even though I selected to turn it off.
At this point I am fine going back to a full working stock mode as long as I will be able to get the latest OTA of the web or a working 2127OTA build.
Please advise,
Niles
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
marcusbaw said:
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
Click to expand...
Click to collapse
I have upgraded to the latest TWRP, 2.7, on my Nabi2 and was able to upgrade to 2.05, but I am still not able to upgrade to 2.10. Same error. Obviously some one was successful or they would not post the 2.10 file. Please advise.
Not sure if it will work for everyone, but....
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
How to Restore Backup?
78cherokeechief said:
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
Click to expand...
Click to collapse
How do I locate the backup file to restore it? I am hoping that I saved everything on my computer at home. I really just want to get rid of everything that I did to get access to the Google Play Store. I regret ever messing with it to begin with. I am trying to update my daughter's tablet, but it won't let me bc of whatever I did to get the Google Play Store about a year ago. I am almost 100% sure that I used the video by Victoria Antonio to root the tablet originally. If you are able to explain this process to me to fix it, I would greatly appreciate it. I like to think of myself as being pretty computer intelligent, but this was a big mistake!
Related
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
AtmaDarkwolf said:
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
Click to expand...
Click to collapse
really this is just an issue I have and nobody else has seen it? Nobody at all has had this problem and knows the fix? Well gee!
Another bump just incase, its happened again: Update yet nothings actually changed, had to 'swipe to fix' root permissions in bootlader menu.
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
AtmaDarkwolf said:
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
Click to expand...
Click to collapse
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
polobunny said:
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
Click to expand...
Click to collapse
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
AtmaDarkwolf said:
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
Click to expand...
Click to collapse
you cant update your phone if it is rooted you have to unroot for that or just temporary unroot the option is available in supersu /superuser
and some apps like root keeper and you have to be on stock recovery
AtmaDarkwolf said:
*snip*
Click to expand...
Click to collapse
Not trolling, the sub categories are there for a reason.
Good luck!
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Ste_J said:
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Click to expand...
Click to collapse
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Floralina123 said:
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Click to expand...
Click to collapse
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Ste_J said:
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Click to expand...
Click to collapse
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
[email protected] #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
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.
Ste_J said:
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.
Click to expand...
Click to collapse
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.
metalheadkicks said:
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.
Click to expand...
Click to collapse
Not yet. Waiting on 2.2 to be uploaded on the other thread. Hopefully the guy will get chance to upload over the weekend
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://forum.xda-developers.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.
aicjofs said:
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://forum.xda-developers.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.
Click to expand...
Click to collapse
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?
Ste_J said:
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?
Click to expand...
Click to collapse
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.
aicjofs said:
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.
Click to expand...
Click to collapse
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
Ste_J said:
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
Click to expand...
Click to collapse
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.
aicjofs said:
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.
Click to expand...
Click to collapse
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://forum.xda-developers.com/showthread.php?t=2041224&page=9
aicjofs said:
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.
Click to expand...
Click to collapse
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.
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.
MattP79 said:
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.
Click to expand...
Click to collapse
Floralina123 said:
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.
Click to expand...
Click to collapse
Have you tried this? http://forum.xda-developers.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.
I'm happy to say I will be an owner of a Kindle Fire HDx 7in.- lte/4g- 32 gb tablet. A Thor? Unless that is just the wireless one. I was contemplating an ipad for weeks, but what I wanted was easily $550- So when I saw the specs on this tablet at half the price, I pushed the button! Picked it up at Amazon's $100 off sale tuesday. $285 with tax. Minus $78 in amex points- grand total of $200 and change
My past modding was on the old white PDN e-reader that was turned into a touch tablet. lol. That had cupcake on it or was it donut??:silly: That's where I learned the basics of adb (I'm pretty bad at it but can follow directions and get the job done, at least 7-8 years ago. I'm pretty rusty at adb now. The toolkits that you guys put together spoiled me- but I did at one time do it the old fashioned way. I hope never again!!! I went cross eyed. Oh, forgot the huawei hs7 too- That took some doing too. That was after the PDN.
I graduated to the TF 101- rooted and rom'd that till it was replaced by the Nexus 7 original-I will never buy a new-never before released- product again after that one, Still have it, passed it to my daughter and she loves it. 3 months after I was one of the first owners, they dropped the price, doubled the storage space to 32 gb, and gave compensation to everyone in the world but us here in the USA. My relationship with Asus products is over. Somewhere along the way I got a nook wifi and hacked that too.
I moved next to samsung, modded the galaxy nexus, the orig. Note, a Note 8 wifi, have a Mega att version ( locked bootloader, and now unrootable on kitkat 4.4 2 so far. TR v. 1-2-3 does not work for it) Love the Note 8, but the screen is a bit fuzzy- so it was the ipad or the kindle hdx. The bargain won. With similar specs, I 'm giving it a try.
Along my history- Never had any trouble or lossed a phone or tablet due to bad flashing or modding. I read 3-4 times or more, and I follow directions pretty well to the letter.
Here is my question. Sorry if I bored you. ( Looked for an intro thread, but didn't find one.) When I get this tablet on Friday, I don't want it to auto update. I don't want to change the build prop. So after I make my adjustments, I want to make sure it doesn't update on me. Does it update over internet data connection, or just wifi?
Here is what I want to do. I Will not connect to wifi. Will check the build number I am on. If I have to, I will manually update to the best safest build by putting it in the root of the sd card, and going to update tool- not connected to the internet, and install. I have been reading all the threads here. What is the safest build if I want to possibly unlock the bootloader when it is released?? and of course root, and install google playstore?
Using the toolkit( v.0.94) I will:
1. Install driver.
2. Use TR v1 and root. Probably with the toolkit. @Faznx92- great job pulling it all together in one place. Thank you. Will by using Toolkit v.0.94.
3.. Install supersu.
4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
5. Block OTA updates with #4- Does this still work on the latest, safest build?
6. Install the exposed framework, and modules, and check appropriate boxes, Reboot in between installs.
7. Install the 4 google apks in the instructions- manager, services, store, framework- and reboot.
8. Check if OTA updates are indeed blocked looking for the OTA update failed!! :
9. turn on wifi and get tmobile free data started.
Is there any way to BU original firmware before installing HDxposed stuff and google apps? Without safestrap? ( I never used that before and it intimidates me a little I also understand it is a little iffy to remove it safely. Can you just re-install a manual update to recover if things go south? After reversing all the apks, modules, root, etc. after a factory reset?
To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
Does this sound like a good plan? It's what I picked up after reading for the last 24 hrs.- not straight of course!!:silly: Did I miss anything important?? Do I have anything backwards?? Would love some feedback. My first preference would be to leave it alone for a few weeks, but my priority is to avoid the updates, but be able to use and set up my tablet the way I want.
If the bootloader is ever cracked and released- Yes I have read the deed is done, but in testing- I would like to install a stable custom recovery, make good backups, and be able to reinstall if things go south any stable rom I have tucked away.
Thank you for your time if you read this whole post!!
sashusmom said:
I'm happy to say I will be an owner of a Kindle Fire HDx 7in.- lte/4g- 32 gb tablet. A Thor? Unless that is just the wireless one. I was contemplating an ipad for weeks, but what I wanted was easily $550- So when I saw the specs on this tablet at half the price, I pushed the button! Picked it up at Amazon's $100 off sale tuesday. $285 with tax. Minus $78 in amex points- grand total of $200 and change
My past modding was on the old white PDN e-reader that was turned into a touch tablet. lol. That had cupcake on it or was it donut??:silly: That's where I learned the basics of adb (I'm pretty bad at it but can follow directions and get the job done, at least 7-8 years ago. I'm pretty rusty at adb now. The toolkits that you guys put together spoiled me- but I did at one time do it the old fashioned way. I hope never again!!! I went cross eyed. Oh, forgot the huawei hs7 too- That took some doing too. That was after the PDN.
I graduated to the TF 101- rooted and rom'd that till it was replaced by the Nexus 7 original-I will never buy a new-never before released- product again after that one, Still have it, passed it to my daughter and she loves it. 3 months after I was one of the first owners, they dropped the price, doubled the storage space to 32 gb, and gave compensation to everyone in the world but us here in the USA. My relationship with Asus products is over. Somewhere along the way I got a nook wifi and hacked that too.
I moved next to samsung, modded the galaxy nexus, the orig. Note, a Note 8 wifi, have a Mega att version ( locked bootloader, and now unrootable on kitkat 4.4 2 so far. TR v. 1-2-3 does not work for it) Love the Note 8, but the screen is a bit fuzzy- so it was the ipad or the kindle hdx. The bargain won. With similar specs, I 'm giving it a try.
Along my history- Never had any trouble or lossed a phone or tablet due to bad flashing or modding. I read 3-4 times or more, and I follow directions pretty well to the letter.
Here is my question. Sorry if I bored you. ( Looked for an intro thread, but didn't find one.) When I get this tablet on Friday, I don't want it to auto update. I don't want to change the build prop. So after I make my adjustments, I want to make sure it doesn't update on me. Does it update over internet data connection, or just wifi?
Here is what I want to do. I Will not connect to wifi. Will check the build number I am on. If I have to, I will manually update to the best safest build by putting it in the root of the sd card, and going to update tool- not connected to the internet, and install. I have been reading all the threads here. What is the safest build if I want to possibly unlock the bootloader when it is released?? and of course root, and install google playstore?
Using the toolkit( v.0.94) I will:
1. Install driver.
2. Use TR v1 and root. Probably with the toolkit. @Faznx92- great job pulling it all together in one place. Thank you. Will by using Toolkit v.0.94.
3.. Install supersu.
4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
5. Block OTA updates with #4- Does this still work on the latest, safest build?
6. Install the exposed framework, and modules, and check appropriate boxes, Reboot in between installs.
7. Install the 4 google apks in the instructions- manager, services, store, framework- and reboot.
8. Check if OTA updates are indeed blocked looking for the OTA update failed!! :
9. turn on wifi and get tmobile free data started.
Is there any way to BU original firmware before installing HDxposed stuff and google apps? Without safestrap? ( I never used that before and it intimidates me a little I also understand it is a little iffy to remove it safely. Can you just re-install a manual update to recover if things go south? After reversing all the apks, modules, root, etc. after a factory reset?
To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
Does this sound like a good plan? It's what I picked up after reading for the last 24 hrs.- not straight of course!!:silly: Did I miss anything important?? Do I have anything backwards?? Would love some feedback. My first preference would be to leave it alone for a few weeks, but my priority is to avoid the updates, but be able to use and set up my tablet the way I want.
If the bootloader is ever cracked and released- Yes I have read the deed is done, but in testing- I would like to install a stable custom recovery, make good backups, and be able to reinstall if things go south any stable rom I have tucked away.
Thank you for your time if you read this whole post!!
Click to expand...
Click to collapse
Most of your questions have been answered before but I will try my best to re-answer them. I will try to clear up any misguided understanding you may have.
-Does it update over internet data connection, or just wifi?
+It updates over a internet connection.
-What is the safest build if I want to possibly unlock the bootloader when it is released??
+We don't know yet. Stay on the version you're on for now.
-4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
+If you don't know much about what it does it's best for you not to worry. Yes, it's fine to leave safestrap alone.
-5. Block OTA updates with #4- Does this still work on the latest, safest build?]
+Yes, it works. The only time it may change up is if Amazon pushes a update with different package names or functions.
-Is there any way to BU (Back-up?) original firmware before installing HDxposed stuff and google apps without safestrap?
+No. I'm not aware of any other way to backup the stock rom.
-Can you just re-install a manual update to recover if things go southafter reversing all the apks, modules, root, etc. after a factory reset?
+You can't re-install a update. You can factory reset it.
-To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
+There is no need to uninstall play store before a factory reset because the reset wipes it out. You should un-root via SuperSU and remove my ota block. (I reset while root but was unsure how safe it was. It did work out in the end without issue.)
Keep the wifi off once you undo the ota block and then factory reset so you don't update. Once the reset is done, re-install the blocker. I'm not sure if you need to remove safestrap before a factory reset.
To make clear:
If you install a ota blocker it's good to check that it works by being connected to the net and then going to Settings->Device->System Updates->Check now. If it says Last update failed it is working else it is not.
The current roms for the hdx require Hashcode's safestrap. But to get the rom's working you need a backup of the stock rom or you could use the backup he provided. Once a slot is made you would install the rom zip to the slot.
I believe safestrap works be emulating a new system/data/cache partition in a file as a full rom to the bootloader. I recommend blocking ota before you make a backup or installing a basic stock rom. If you create and install the stock rom to a rom slot without blocking ota, the amazon system files are still in place to call for a update and hand it off to the system and bootloader.
Safestrap is safe as long as you do not touch the stock rom but only to make a backup of it.
If you don't feel comfortable using safestrap then don't.
Quick word of advise, you should include the version of your device when asking questions for that version. I'm guessing your on 13.3.2.4, the current latest.
Also I highly recommend staying on your current version and not moving forward.
Last thing, give this a read.
I hope I answered your questions as clear as possible.
Anybody else please clear up anything I missed.
Also good luck with your device and play safe.
Thank you so much Faznx92 for reinforcing all that I read ( lots in a short time period). I didn't want to mix up the info I read from the beginning of the year to where this tab is now. You did clear up anything I was unsure about. Thank you! And safestrap- I am not comfortable with it at all- there is no safestrap for my Mega, all my other tech toys have unlocked bootloaders. So I have absolutely no experience with this custom recovery. I am used to CWM and TWRP. Totally comfortable with them, although I have to admit kitkat twisted my arm to try TWRP since that was the only way to flash those roms on a lot of tablets and phones. Now I am partial to that. So I won't say no to safestrap, just now when an unlock is so close. If a safestrap was released for my Mega, I would definitely give it a try.
Oh, I know to report what build I am on when asking questions- that's just polite and informative, right?? But I am not getting this tab till tomorrow, at least that's what tracking says. So I don't know yet. When I check the build I will post back and let you know what they are shipping now with. Hopefully it is still rootable and eligible for unlocking the bootloader when that is released. That is very exciting!
I give you credit for reading my epic long post, and thank you for taking the time to address my concerns. I appreciate it! I'll check back in tomorrow afternoon. Mail comes late where I am.
Your link was the First thing I read on this forum!!!! Which is why I am sticking with what I am comfortable with. Also, in my case I only learn by doing. But I have always realized that hacking leads to problems sometimes. My motto is stay calm, and reach out for help. Panic doesn't solve anything. And if you are hacking your only phone that you rely on, be prepared to go buy a cheap prepaid phone to bail you out till you straighten out your expensive semi brick! lol. I've gone from holding my breath when hitting go, to just being curious on how to do stuff and finding out how things work. I guess I'm living life backwards!! I can afford it at this point in my life.
Just received my kindle HDx 7 from Amazon.
So, I placed this order 1 am Wed. morning- the sale must have been on PST. Took free shipping- non prime. Received on Friday around noon. Way ahead of the promised date.
The build received was 13.3.2.1. Sim chip was installed and connected to the internet, so I took it out as a precaution even though it is not yet asso. with an account. Skipped wifi set up till I get OTA updates halted. Now it's time to play!
I Really like the size of this tablet.
@Faznx92, now that I know I am on build 13.3.2.1 do you recommend I update manually to 13.3.2.4 or can I stay on this one?
Thanks for your advice and help. Rooted, OTA blocked and confirmed, superuser installed, binary updated. I will hold off on google stuff for now and see how this OS works.
sashusmom said:
@Faznx92, now that I know I am on build 13.3.2.1 do you recommend I update manually to 13.3.2.4 or can I stay on this one?
Thanks for your advice and help. Rooted, OTA blocked and confirmed, superuser installed, binary updated. I will hold off on google stuff for now and see how this OS works.
Click to expand...
Click to collapse
I'm still on 13.3.1.0 and not moving any time soon.
13.3.2.1 is fine.
Stay on your version!
Also you will need to registered your device.
Faznx92 said:
I'm still on 13.3.1.0 and not moving any time soon.
13.3.2.1 is fine.
Stay on your version!
Also you will need to registered your device.
Click to expand...
Click to collapse
Thank you! I will hold where I am then. I guess since I bought it from amazon- an account I already had there- when I connected to wifi it sort of registered itself and associated it with my amazon account by Magic!!:silly:
I do have to say just using the native kindle OS, I am not a fan. I will be installing the HDxposed modules and google stuff. :fingers-crossed:
Yeap, magic brick lol Hopefully not for you though, you seem to have done a little homework. I would be thorough with your own research at least skim the threads of the modifications you wish to do just to see what problems other people have had may save you a lot of trouble. Good luck
jimyv said:
Yeap, magic brick lol Hopefully not for you though, you seem to have done a little homework. I would be thorough with your own research at least skim the threads of the modifications you wish to do just to see what problems other people have had may save you a lot of trouble. Good luck
Click to expand...
Click to collapse
Thanks jimyv Everything went as planned, couple hiccups that I solved by all the info posted here in this forum
The only thing I seem to have a problem with is sideloading apps now. It worked prior to downloading the google platform, but I can't seem to install from my sd card, app installers, or dropbox. I went back and checked that unknown sources is checked, and adb is turned on.
I had this same problem on my Note 8 on totally stock with just root applied and philz touch recovery. I fixed it by installing a stock hacked kitkat rom and that solved the problem.
Anyone have any ideas? Not too much of a problem since the play store/ market is up and running. I wanted to install samsung milk music that did install on my note 8 (not approved for that tablet). When sideloading was working for the hdx 7 I could load that apk, but it refused to install.
Now nothing will happen when I try to install any apk from dropbox or app installer. The buttons don't respond. If that's my only problem I can live with that!!
too much
sashusmom said:
Thanks jimyv Everything went as planned, couple hiccups that I solved by all the info posted here in this forum
The only thing I seem to have a problem with is sideloading apps now. It worked prior to downloading the google platform, but I can't seem to install from my sd card, app installers, or dropbox. I went back and checked that unknown sources is checked, and adb is turned on.
I had this same problem on my Note 8 on totally stock with just root applied and philz touch recovery. I fixed it by installing a stock hacked kitkat rom and that solved the problem.
Anyone have any ideas? Not too much of a problem since the play store/ market is up and running. I wanted to install samsung milk music that did install on my note 8 (not approved for that tablet). When sideloading was working for the hdx 7 I could load that apk, but it refused to install.
Now nothing will happen when I try to install any apk from dropbox or app installer. The buttons don't respond. If that's my only problem I can live with that!!
Click to expand...
Click to collapse
If you are trying to install into system it may be too crowded
Personally I use titanium back up and it shows the size of the ROM I only have like 34 MB left of room after installing gapps. And if you are using safestrap by chance you need to remake your slot delete the slot first then go to remake it it will show available space. I increase that cache by 200 MB then use the rest of my available space up in the data partition then create slot .
jimyv said:
If you are trying to install into system it may be too crowded
Personally I use titanium back up and it shows the size of the ROM I only have like 34 MB left of room after installing gapps. And if you are using safestrap by chance you need to remake your slot delete the slot first then go to remake it it will show available space. I increase that cache by 200 MB then use the rest of my available space up in the data partition then create slot .
Click to expand...
Click to collapse
No safestrap. I have a 32 GB. Is the internal partition for installing apps tiny on this tablet? I got the 32 gb so I wouldn't have this problem. Stock other than being rooted and having the HDxposed modules with google market installed. That might be taking up the room.
I have 1.1 GB of apps, system apps are close to 397 mb. I have 21 GB free.
************************************************************************
Must have been a space problem. I deleted AngryBirdsSpace and was able to install Adobe flash and Cerberus. Milk music still will not install, so don't think that is the issue with that one. It did install last week on my Note8 and my Mega so maybe because it's a samsung app??
Will Titanium BU work for moving apps to the sd card on this device? And free up space that way?
I can't seem to find the move to sd card on a long press with tit.BU, so I guess not.
Alright XDA Community. I need some help. Desperately. So I had plans on rooting my tablet (TF201) to install a custom ROM. Being that I have version 4.1.1 installed I would looking for something a little newer and modern. That did not go as planned from the beginning. Since the first step was rooting it, I looked for a ROM. So I searched the web, including XDA and found KingRoot to root my device. Either KingRoot was a terrible choice or something did not go right with the process. Now when I turn on my device I get random pop ups for for stupid garbage that I don't want installed like What's App and UC News. Everything functions as it should but I get random messages that Settings stopped working. I get random apps being installed on a regular basis. I could be in an app and I get a blank / black box on top of something trying to open or install. This very frustrating and I am completely over my head now. So here is what I would love help with;
1. I would like to UNROOT my device to ALL stock settings and firmware. Completed
2. I would like to ROOT my device PROPERLY. Completed
3. I would like to install a custom ROM with Android 6.x or 7.x (Something plain and vanilla)
4. I would LOVE this help if at all possible in plain English Step by Step with pictures if possible. I would like it dummy proof.
Thank you very much for any and all help. It will be very much appreciated.
PS. I do not need to back anything up. It was a fresh reset recently and I do not have anything to backup.
Step 1 is complete. I used Kingo Root to UNROOT my device.
Step 2 is complete. I used Kingo Root to ROOT my device.
Have you unlocked the bootloader using the Asus supplied software?
NP
No. I downloaded it and installed it but when I go to run the APP it asks for my Google Credentials but it does not accept them. I use the credentials every day so I know my username and password but it does not work.
Delete you google account then run the bootloader unlocker again.
NP
Nektopoli said:
Delete you google account then run the bootloader unlocker again.
NP
Click to expand...
Click to collapse
Thank you very much. That did the trick. Here is the problem though. I think I am way over my head on this. I did a Davlik Wipe and a Factory Reset but there is something still not right. I did both a Dalvik wipe and Factory reset last night before bed. I did not touch it once complete but on a regular basis I get pop ups about Android System stopped working or UC News. I cannot get rid of either of these on my tablet.
Any idea what I can do?
Now that you have the BOOTLOADER unlocked next step is to ROOT the TF201, I used MOTOCHOPPER. Check out this thread;
https://forum.xda-developers.com/showthread.php?t=2230763
NP
That worked. I was able to Root my device without issue. Actually that was a great tool. Nice and easy to work with.
So here is my next stop. What ROM do I pick? I was looking at 6.x or 7. It looks like KatKiss is pretty good but I am not sure.
https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
No reason not to go straight to 7.1.2 just make sure you flash the correct TWRP.
NP
And this is the part I don't understand. I have downloaded TWRP and ROM Manager from ClockWork. I have copied the ZIP folder to my SD card and placed it in my TF201. From here I don't know what to do.
I follow the instruction from 5.1 here: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-5-1-tf201-22-t3080892
using the 7.1 files from here: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
NP
Yeah. So now the tablet is stuck at the Asus Splash Screen. Been for the last 48 hours or so. I completely drained the battery but when I filled it back up, no difference.
Can you get into the TWRP recovery console?
NP
Nope. I can't do anything with it. I have power cycled it many times over holding different buttons but no difference.
Hi Interweb!
I was wondering just how many people were still "in the know" on the topic of rooting, unlocking bootloader and general Android development for the Tesco hudl2 [HTFA4B] tablet. Obviously with Tesco's little trick of shutting down the servers, two thirds of us were left with Kitkat, and having had enough of it, I decided to root. Everything went fine. I booted back into Android KitKat (stock) and then installed Xposed Framework. Presumably the installation failed, as upon rebooting, the tablet booted straight into stock recovery. I have been seeing this for two months now, having removed the battery several times, refitting it and trying to reinstall android with the ROM form this link:
hudl2_ota_rel.android-build.20150803.092218_to_rel.android-build.20150917.142239.zip | GEM-FLASH Firmware
firmware.gem-flash.com
Either way, I am now faced with a soft brick. Does anyone know how to fix? The exact text displayed in Stock Recovery is down below.
To be clear, I occasionally DO see the "powered by android" screen before booting into recovery, but not every time.
A possible solution would be if there is a fastboot mode I can access, I may can use Odin and flash a Custom ROM onto the tab. Or, alternatively, if anyone has, or knows someone who may have Tesco's key signature, that too would be useful in building a ROM.
I've had this tablet since I was 7 years old, and it's been part of my life for many years now. If anyone can help please do
Many Thanks.
[TAGGING SOME PEOPLE WHO MAY BE ABLE TO HELP]
@Rickav
@droident
People not on XDA who may can help:
Kirwan Lyster - Head of Facebook's Android department and former head of Tesco Connected Devices (hudl) software team. [email protected]
The Guardian Consumer Champions
BBC Watchdog
Martin Lewis - Money Saving Expert.
Android system recovery <3e>
K0T49H.rel.android-build.20151102.170607 release-keys
Volume up/down to move highlight:
power button to select.
reboot system now
wipe data/factory reset
wipe cache partition
apply update from ADB
apply update from external storage
apply update from cache
[ANDROID WITH OPEN BELLY]
No Command.
Click to expand...
Click to collapse
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Rickav said:
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Click to expand...
Click to collapse
Thanks @Rickav . Presumably you saw my DM.
All three come out with:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:end of footer from /tmp/update.zip not 0xFFF (File exists)
E:signature verification failed
Installation aborted
once adb sideloaded in stock recovery (all I have access to).
Is there any chance of you making a nandroid backup zip using the CWM fastboot custom recovery in "hudl2 root stuff.zip" on MoDaCo? I know it's asking a lot. @paulobrien might send me a system image and couple of OTA zips and other assorteds for a start which may help. Before I attempted Xposed I was trying to get Lollipop but the OTA server has been decommissioned (confirmed by Kirwan Lyster, head of hudl2 software), so if I can do that by other means that'd be great. Fist priority though: get it running. You can see by the video what is happening.
Many thanks,
Cessna
If can't do this, may need to try to unlock bootloader. Any ideas, also useful.
@Rickav I really appreciate your assistance, but going by this link:
New update Sept 15
www.modaco.com
It looks like my tablet is dead. What do you think of this?
Hi,
In case anyone is looking for clear instructions on how to overcome the problem after a factory reset of the Tesco Hudl 1 & 2 you will find them here (works for Hudl 2 as well). Use a date between 27 June 2019 and 26 June 2020 :
HUDL bricked after factory reset and how to fix it - Hey Munky!
I did a factory reset on my HUDL and bricked it. Here's a quick step-by-step guide on how to unbrick it after a factory reset.
www.heymunky.co.uk
Or the same with pictures but remember to use a date between 27 June 2019 and 26 June 2020 :
Rob's stuff - Hudl - Fix
Update 23 May 2023: This mechanism for recovery of a factory reset Hudl 1 no longer works. Due to the Tesco server at https://device.tesco.mobile.com/ no longer responding correctly to requests this technique no longer works and will fail after Step 18. As far as I know my Custom ROM is now the
rob.themayfamily.me.uk
(If this date solution ever fails then another option is to create a new user in the settings menu and reboot into it.)
Post if it works for you
I am going to try and update my hudl 2 to lollipop android 5. ADB sideload fails so i need to update from sdcard or from cache folder, just a case of where the cache folders are and how to add to them.
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Did yours brick before or after you installed xposed?
CessnaBroon said:
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Click to expand...
Click to collapse
Did yours brick before or after you installed xposed?
ushilives said:
Did yours brick before or after you installed xposed?
Click to expand...
Click to collapse
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
CessnaBroon said:
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
Click to expand...
Click to collapse
Ah OK thanks. I'll have a read more into it Rather than using recovery
Please do. Just check for me please, does it still boot? If yes, what have you attempted so far? Thanks