Hi
I made this post below, but didn't get a reply, so I'm not sure if I'm making it in the right area, or if it isn't being seen, or just no solutions. Anyway, here it is again!
Hello guys
I have an HP 10 tablet(similair to slate 7) running 4.4.2. It is rooted, but it hasn't updated due to the ota not recognizing the root scripts. I wanted to update to lollipop(Android 5), but couldn't find specific roms for may model. I saw some HP touch stuff though, but not sure if that would work. This tablet is a quad core 1.2ghz, ARM v7 processor rev 3 (v71). Since rooting, it no longer keeps its state, and if it goes dead, is turned off, or reboots, it defaults back to factory settings, and I have to start all over with installing my back up (via titanium). It is time to update and make it more stable. any help?
Hi, thank you for using XDA Assist. Since 5.x OTA's will fail on rooted devices. I'm not sure if this is the right forum but see if anyone can help you here, http://forum.xda-developers.com/hp-touchpad
Related
hello everyone,
I have a peculiar problem with my rooted TP. well before i put forward i will provide a brief history. i Had with me webos updated version before i attempted to root my TP. I SUCCESSFULLY rooted my tp to cyanogenmod 3 android system and everything worked as it intended. Then i updated to 3.5 cyanogenmod and then a clean install to xronified version. my problem now is when i ask the system to shutdown from xronified version it reboots again while when i ask to reboot it shutsdown and have to manually restart. it there something wrong with the booting sequence.? i know the limitation of both versions of android but i am happy with the excellent work put up by both versions. i thought it would be better to question this issue in developers thread but as being new to THIS forum i am not able to.(minimum 10 posts).
I don't think I could've make the title any blander really could I?
So, to the issue.
I've had a hefty prowl around the forum and i've found threads that hint at the information I need (i.e. Letting me know the information exists), but not one thread that actually answers my question.
So without further ado, here it is:
How exactly did the 'nand' block association for CWM recovery change between 4.0.3 and 4.0.4?
I ask because my tablet ran 'Christian Troy's A10 CWM 6.0.1.2' perfectly on 4.0.3, but when i upgraded to my manufacturer's new 4.0.4 rom, it suddenly didn't work. That's not to say that the install-recovery.sh stopped working, but that after applying it, a reboot automatically brought me into recovery, even if I wasn't holding down Vol+. Then, after exiting, the unit stopped loading, and wouldn't even go back into CWM. Effectively, the unit seemed 'bricked'.
I resurrected the unit using Livesuit, and tried multiple other applications, and CWM versions to no joy, and then I found a thread detailing that the dev/block/nandg was no longer valid on 4.0.4, and this is why flashing CWM was causing the unit not to boot.
However, nowhere have I found which block to change it to, or what other developers have had to do to get CWM to work stably on 4.0.4.
Any ideas?
My device's specs are as follows:
Sumvision Astroplus (Astro+) 7 inch tablet.
Stock ROM Android 4.0.4
Arm A8 1.2Ghx Processor
Mali 400 GPU
The unit is known by the following names, but I'm sure there are many more:
Ployer Momo 9
Funbook
IVIEW 760TPC
Does anyone have an idea at all?
I've conected this your post here,
[rom] Unofficial CyanogenMod 9 for many AllWinner A10 tablets, post # 398-400
http://forum.xda-developers.com/showthread.php?t=1760929&page=40
investigating this problem..
Hey guys, been a long time lurker here and just encountered my first issue, so made an account to hopefully get some advice.
I received the note 10.1 8010 (UK) as a gift for Christmas. I was disappointed to see it was running 4.0, when devices like the Nexus 7 are already on 4.2. And Germany had the 4.1 update for over a month. Samsung as always refuse to give a solid answer.
I followed a guide to install the German 4.1.1 update. I first installed the German version of ICS via Odin. I then applied the update.zip from here:
HTML:
d-h.st/lLB
Prior to this, I rooted the device, but I believe the above process removed the root anyway.
After my device rebooted, the S Pen isn't working at all. It recognises when I take the pen out, but I cannot use it. It doesn't do a thing. I've read about 1,000 forum threads and cannot find an answer, as to how I can get it working again.
I tried deleting cache and user data, then reapplying the update.zip to no avail.
When I boot up in to recovery mode, it does come up with a message about CSC and then the little drop falls over and I have the usual options.
Any idea what I need to do, to get my S Pen working again? Or what I've done wrong?
Many thanks
This is how I rooted the device.
HTML:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
I have a feeling this is the "root" of the issue. I'm not sure how to remove it.
I know previously I wasn't able to change my CSC via CSC switcher, but I am now.
So I guess installing the German ICS and then update.zip, hasn't completely undone whatever rooting it above did.
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Tehkseven said:
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Click to expand...
Click to collapse
This a pretty bummer situation. Sorry you're dealing with it.
I find this interesting, as I followed the exact same procedure to root as you. I haven't experienced any pen issues though.
Could it be the 4.1 you flashed?
This is one of my fears too, so I really hope this can be solved.
I finally managed it.
I downloaded a different German ICS from a different guide and this time it worked no problems.
The one that worked, had a file name: N8010XXALI3_N8010OXAALI3_DBT
Update.zip worked first time after I installed the above ICS.
Hope that helps.
Hey community,
after updating my 5.0 LTE 32 Shield Tablet some month ago and rooting it, I came to the conclusion that I don't really need root, but would like to continue receiving OTAs and have a device that just works.
Prio1:
Have a tablet with the latest updates installed.
Prio2:
As 1, but rooted.
I have made a apps+sysapps backup with Titanium.
What do you recommend as the next step?
Thank you very much.
All the best, Esshahn
Some additions:
1. I noticed I'm actually having 5.0 on my Shield. It's the 5.0.1 update plus the nVidia stuff that comes up all the time in the notification center.
I really just want to undo all root and whatnot actions and have a right out of the box experience on my Shield. I already did some stupid stuff (factory reset) and therefore lost my personal data anyway, so there's nothing to lose.
I noticed this forum isn't really active. If anyone doesn't know the answer, but could point me to the right forum for help that would be nice too.
Thank you
flash the full OTA through recovery: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
then reinstall supersu through recovery, no factory reset needed
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Esshahn said:
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Click to expand...
Click to collapse
you can flash the full OTA through TWRP or CWM, no idea why it won't work with stock recovery though
the update supposedly fixes the graphics glitches that appear in various apps on update 2.1, that might be a good reason to update
Thank you!
Actually, since I didn't have CWM installed anymore, I just sideloaded the latest OTA, which worked nice.
hi there,
i have a SM-9005( Australian Telstra) which i bought used a couple of weeks/ about a month ago. NOT KNOWING WHAT I WAS DOING i tried to install android 5.0 via odin but, the thing that i did'nt realise was that it was the hong kong firmware after installing it i encountered a problem something like " binary (number) < (number) i figured that it was because when i decided to install it the storage was about 95% full and it only had like 300mb left so i just went into recovery and restored the phone. after successfully installing 5.0 i noticed that the phone was starting to be glitchy as in system would'nt respond (lag) no sound and camera and mic and calling wouldn't work. so i decided it was best to just roll back to the old os 4.4.2 and thats what i did. after doing so i realised that the same problems were still there "no in/outgoing call, no sound, no Google Now, no S-Voice, no camera, slow lock screen and slow settings" after trying to research and not finding anything that would help me ( mainly as my phone is Australian variant) i decided to install a custom rom Cyanogenmod, although this fixed the camera the other problem were still there and after trying to even restore from a nandroid backup via twrp recovery the problem has still not been resolved and well....:crying:
Hi, thank you for using XDA assist. Start here, http://forum.xda-developers.com/showthread.php?t=2439633 Also see this which is your device specific forum, http://forum.xda-developers.com/galaxy-note-3
thanks, but?
jd1639 said:
Hi, thank you for using XDA assist. Start here, http://forum.xda-developers.com/showthread.php?t=2439633 Also see this which is your device specific forum, http://forum.xda-developers.com/galaxy-note-3
Click to expand...
Click to collapse
thanks, but i have no idea what to do with this information neither do i know what to call the problem (name for problem would be good). as for what phone model mine is, it is the same as the one in the link it is 32gb telstra aus vrs.
Thread closed.