Related
I was in the process of flashing TnT Lite v5.0.0 on my Viewsonic Gtab and all was going well. Got the Viewsonic screen, then the message that a recovery key was pressed and then booting recovery kernel image. Then the screen changed to a graphic of a package being updated with a progress bar.
Unfortunately, I let go of the Power and volume + key before the progress bar finished. When I realized I had to hold the key sequence longer, I quickly tried pressing both the Power and volume + key sequence again. This led to the screen turning black and then I got the familiar messages, "Booting recovery kernel image."
From that point it hangs indefinitely.
I did ensure I was using TnT build 3588 before I attempted flashing with TnT Lite 5.0.0.
Is there any way to recover from this state?
Any help is appreciated in advance.
Actually once the recovery starts you can release the buttons.
You're most likely going to have to use NVFlash to flash a stock ROM. Update that and then reflash 5.0.
sabre2002,
A number of folks have had problems with the 5.0.0 install. But the advice Cannibul gave you about holding the buttons only until the recovery starts is good.
You will need to use NVFlash to recover -- and that's not too bad except that you need to be prepared and understand the process.
First, go back to Roebeet's original 5.0.0 thread and read all the parts of the instructions about "what if problems happen" again.
Then go to the NVFlash Recovery thread:
http://forum.xda-developers.com/showthread.php?t=861950
and read it thoroughly. There are a couple of links in it to threads where several of us describe exactly how to get the stuff, set up and nvflash your
recovery.
Good luck to you. Know that a bunch of folks already have done the same thing,
so all is not lost.
Rev
P. S. -- There also is a thread I put near the top of the Developer Forum that provides additional info on the USB Drivers for the nvflashing if you need it.
Thanks, butchconner.
I found an earlier post of yours where you provide step by step instructions on using NVFlash to recover the G-Tablet to an old image.
It worked perfectly including getting the USB drivers for recognizing G-Tablet in APX mode (I was having difficulty with this last night).
Got the tablet up and running but had problems applying the TnT 3588 build update. However, I'll retry and re-read Roebeet's post as you suggested.
Thanks again for your help.
Update on progress
Ok ... I had a heck of a time getting the TnT build that was contained in the zip file from roebeet's post (http://forum.xda-developers.com/showthread.php?t=861950) to update to the necessary build 3588 in order to apply the TnT Lite v5.0.0.
I tried multiple times, but each time the 3588 build update would error and I would have to nvflash all over again.
After a couple of times with this error, I decided to try the TnT update.zip provided in another of roebeet's post:
http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
I copied all of the image files in the same directory where NVFlash was located on my Windows PC. It overwrote the bootloader.bin and the system.img and added 2 others (recovery.img and boot.img).
Ran the nvflash_gtablet.bat file again with the updated images and the gtab came back up as usual and it told me that it had been updated to build 3588.
However, don't believe it because when you check the Settings for the build number, it still shows an older build (2367 I think but don't quote me).
Clicked on the TnT Updates app and was prompted to download and install the build 3588 update again.
This time the update worked like a charm!
Not sure if this is really a useful workaround, but thought I would include it here just in case.
sabre2002,
When you do the nvflash as several of us have documented using Roebeet's files, your at the 2638 update.
Most of us have found that if you just activate the wifi on the 2638, VS Update almost immediately offers the OTA 3588 update from VS. Just let it download and install.
If not, the downloadable version of 3588 is in Roebeet's 5.0.0 thread I believe and you can put it and a new recovery/command file on your /sdcard and the power/volume- into recovery and install it.
Glad to hear you are on top of it all. Of course, I think all of us that "play" with these things really deep down inside know we are going to keep doing things and changing things around ------and some day something will happen again!
Rev
Loaded TnT Lite v5.0.0 successfully
I have TnT Lite v5.0.0 flashed on my Gtab now ... it's very nice. Much smoother than the stock TnT and access to the full Market is worth the price of admission.
Thanks for everyone's help ... it was fun flashing the new ROM and now I am familiar with nvflash in case I need it in the future.
I'm not expert enough to say this is the answer to a lot of people's problem -- but I'm going to throw it out anyway and hopefully some of the "really expert" people will jump in.
Several times when I have had major problems, I have found that the file structure/files/etc. on my tablet were messed up. Before I could reinstall, I had to re-partition, wipe caches, etc.
I read a lot of posts about people having major lockups or loops and then just trying to reload and reload software assuming that is the only problem -- and not getting good results.
It seems to me that if there is a serious enough malfunction to have to nvflash or do a major recovery -- it would be good to re-partition, wipe caches, etc. in case there is corruption or other structure problems.
What I think we need is for one of the gurus to make us a procedure for "Rebuilding the /sdcard File Structure" (or something like that. Repartition to 2048 and 0 --- and then what else? Which things need to be wiped, formatted, etc.
I'm pretty good a discerning what's wrong -- and I think some of these rebuilds are failing because of this problem.
Right? Wrong? Other ideas? Procedure?
Rev
P. S. -- Enough folks are having these problems right now that this could be an important help for them if I am right......
I PM'd, but the short version for the forum.
I've obviously seen a lot of issues with the TNT Lite 5.0.0, and I've whittled it down to two major problems. First off, not everyone reads instructions. This was fine pre-TNTL 5.0.0 as the instructions really were the same for every version preceding it. But 5.0.0 changed the playing field drastically. Which leads me to the my second point....
I think that some of us have been using mods for so long now that stock was no longer an option without an nvflash. Viewsonic, for example, had a bootloader update in December and I believe a recovery change with 3588. But since a lot of us have been using mods for months, we never got those updates. So, when the time came to revert back to stock, there were problems.
In some ways, TNT Lite 5.0.0 is almost like a tablet cleanup - it's the first update I've had where a stock pre-req was required, and the first one in a very long time where I added a stock bootloader and recovery.
nvflash and tnt 5.0
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Charles77 said:
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Click to expand...
Click to collapse
Not sure -- sounds like you did it correctly. nvflash to 2967, OTA to 3588 and then TNTL 5.00. You didn't install clockworkmod, correct? You need 3588 recovery for this to work.
oops yes I did. ok
Charles77 said:
oops yes I did. ok
Click to expand...
Click to collapse
That would do it. The reason why 3588 recovery is needed is because it updates the bootloader, whereas I believe clockwormod does not.
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
darthbubba said:
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
Click to expand...
Click to collapse
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Deleted dupe
FIXED IT!
jimcpl said:
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Click to expand...
Click to collapse
I FOUND A FIX!!!!
Link here: http://forum.xda-developers.com/showpost.php?p=12030351&postcount=14
I got my wish, now I'm back to status quo ante...
I sent tcrews a PM with this link, hopefully it'll fix his too...
darthbubba et all,
The files from otreblada that are in this download are the same files roebeet and others have provided -- just packaged together in one set.
To nvflash you have to have:
1. the files for the program nvflash
2. the .img, boot, etc. files
3. the USB driver files.
All of these are referenced and available in several places.
I am glad, however, that this might be a solution for some of you who seem to
have recurring problems.
Rev
(At the request of management). Even with all the unsticking / mod intervention and warnings up the wahzoo, there are still a lot of user problems. It may return in a week , but for now it is PULLED. The moderators have hidden the thread, at least for the short term.
For those of you on TNT Lite 5 / TTx, just keep using it and no worries. Once we know where VS is headed, I will have a plan to either ask you to downlevel or upgrade. Again, depending on what they do.
EDIT: For those of you who had issues, could you please write up the steps you used before it failed? It would help everyone to understand why there are so many problems with this 3991 stock / TNTL 5 / TTx. From the posts and PM's I've seen, the majority have been either:
1- The device was flashed with clockworkmod to 3991/TNTL5/TTx and gets stuck at the birds or
2- The device was being prepped to stock 3588 and recovery was broken, after the 3588 reversion.
But I'm hearing that others might have applied all the proper steps and still had problems. We're trying to gauge just where the problem lies with this 1.2 UAT of Viewsonic's.
From my own device, I know that clockworkmod flat-out does not work. That's because the BCT partition is being touched by standard recovery, which clockworkmod does not replicate (and seems to be required). But as long as I have a clean 3588 stock ROM running on my device, I have not had an issue upgrading to 3991/TNTL5/TTx, it has worked for me 100% of the time.
Stock 3991 / TNT Lite 5.xx / TTx .9x backout instructions:
There are two way I know of to back out of these:
- Flash to stock 3588. This assumes you have NOT added clockworkmod and have standard recovery. I have done this several times and never had a problem. Stock 3588 link: http://forum.xda-developers.com/showthread.php?t=842000
- nvflash using bekit's 1105 image: http://forum.xda-developers.com/showthread.php?t=861950. This is still the best way to back out, as far as I'm concerned. You can do a full erase first, to wipe user data as well, thread is here: http://forum.xda-developers.com/showthread.php?t=974422
NOOOOOOOOO. Hopefully VS will decide what they are going to do by the end of the month. I am enjoying TnT Lite 5.0 with no issues at all. Thank you for all your hard work Roebeet, it is unfortunate that so many have had problems with this.
Damnnn, was about to install it
Really sucks that people have had problems maybe people should read and then re-read instructions instead of jumping into things and just assuming devs and mods can help them out. They have a life and dont think that after putting in all the work in to create something they want to hear from whiny a$$, irresponsible people that probably caused their own problem
Now people, like me, that wanted to install cant. nice.
thank roebeet tho and all the other g tab devs
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
One of the obstacles I've had in the last 2 weeks is that this is a UAT, not a released firmware from Viewsonic - so its validity is in question (and understandably so). If they release it with the same bootloader and upgrade requirements, it's going to shake things up here a bit.
I still think the odds are that they will - from their standpoint, they are only supporting stock users so, as long as they can ensure that a user is on 3588 stock, then the upgrade should work. In our case, many of the issues were either getting from a mod to 3588 stock, or using clockworkmod by mistake. Viewsonic doesn't have to worry about either of those issues.
But, there's still the X-factor -- everything is 3588 stock and the upgrade still fails. That might be what's holding them back.
bkbrod said:
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
Click to expand...
Click to collapse
No, clockworkmod won't work (even the new one) - if you wanted to backout to old stock (3558, for example), you'd have to use Viewsonic's recovery. Clockworkmod will kill your device, trust me on that. nvflashing to bekit's 1105 also works, that's how I've been backing out to old stock.
Hmmm
In the last 24Hrs, my gTab v.9.02 just decided to go totally nuts. Constant FC's, lockups, lost sound. Tried every fix listed on XDA, wiped /data , re-downloaded apps from Market instead of restoring with TiB; wotked for a little bit, then the same FC's. And random loss of sound.
Going back to 3558 and CWM and 4.2.5.
We'll see what VS throws our way.
Keep up the good work Mr.Roe!!!
roebeet said:
The backout, btw, is the same -- run stock 3588 and it will downlevel you back to the old bootloader. BUT, make sure it's standard recovery and not clockworkmod.
Click to expand...
Click to collapse
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
TwoTapsX works great for me so far. Had TNT Lite 5.0.1 but it wouldn't run some apps correctly. Tried all the ROMS and they all had sleep of death problems. TwoTapsX works the best for me without giving any glitches.
TwoTaps .9.2
Thanks Roebeet for all you do here. I am finding this ROM easier to work with than any other. I have noted that periodically it will flash the home screen while I am working. Mostly this has been while in Dolphin Brower HD.
jholmes5 said:
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
Click to expand...
Click to collapse
Good point, since the other thread is hidden.
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
P00r said:
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
Click to expand...
Click to collapse
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It does not... if you install a custom boot animation it stay there... so it's not full even if after the unit doesn't even start (red text) it's not fully wiped...
I have used clockwork with the partition option, this seem to perform a full format with either the nvflash format or bekit recovery but I am not sure why we can't get this done tru the nvflash...
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It's in my first post, as well. Run that nvflash first to erase the device, then the bekit 1105 nvflash to complete the process.
What seems to happen is that the old stock / new stock user data setups are not compatible. When going to new stock, it's not so bad because new stock has a better recovery. But when reverting, old stock has a crappy recovery with no user data wipe options. Even Viewsonic understood the limitations which is why they changed their recovery in this UAT of theirs.
I mentioned to jerdog that I wanted to see if I could port their new recovery to old stock (using an old kernel). If that works, we could conceivably offer a "bekit 1105 enhanced" version that adds it. This is better than clockworkmod in that it's the vendor's own recovery and includes the ability to wipe user data, calibrate the device AND update / downlevel the bootloader. For the purposes of getting users backed out if needed, it might be a critical piece of the puzzle.
EDIT: No go. The recovery functionality is actually IN the kernel, my bad. So it can't be ported over. Oh well.
You guys are GODS at this. Simply amazing what you are all doing with this G Tab. So I guess I'm one, of some lucky few, that ACTUALLY READ the install instructions for 5.0 and 5.0.1.
Glad I did because I love the market on this thing.
Eagerly watching what happens with Viewsonic......Any chance they did this as a step to make a Honeycomb upgrade easier? I doubt it since the original G Tab with OTA updates is still crippled.
First off just want to give my thanks to roebeet and the devs here at XDA. I've been running TnT Lite 5.0 / TwoTapsX ??? since the day I bought my Gtablet on 3/11 with no problems. On Friday the 11th I was itching for a Xoom somehow managed to find out Staples had the Viewpad 10 but not in store and somehow managed to end up finding out that Office Depot had the Gtablet for $379.99 in store. I read roebeet's at the time TnT Lite 5.0 thread several times before walking to my nearest Office Depot and brought home a Gtablet within minutes of reading that thread.
Out of the box from 2967 I went to 3588 through stock recovery and not OTA; and then did the same thing to go to TnTLite 5.0.0
I have successfully backed out of TNT Lite 5 in two ways:
1- Re-run a stock ROM. Specifically, I tested 3588. STOCK is important, as the bootloader will be downleveled to the necessary revision.
2- nvflash, using bekit's 1105 image.
In the case of stock, you might get stuck in a boot hang due to the possible need to wipe user data. So, I would recommend running the update.zip off a microSD so you can install clockworkmod .8 (old version) to give you the ability to wipe data.
Once you have old stock back, you'll be able to install older versions of TNT Lite, VEGAn, zPad, etc. as the bootloader is downleveled again.
Click to expand...
Click to collapse
My question to roebeet or anyone who has gone from TnTLite / TwoTapsX back to 3588 using stock recovery. I could swear the above quote from roebeet had an additional line about using stock recovery to run the 3588 stock rom and then wiping user data from stock recovery. From TnTLite 5.0.0 can I go back to 3588 using the stock recovery and wipe user data with the stock recovery after running 3588 but before rebooting?
Android system recovery <3e>
Wipe Data/Factory Reset
Wipe Cache Partition
Click to expand...
Click to collapse
If it is possible to wipe user data after flashing back to 3588 do I need to just wipe data or do I need to use the 'wipe cash partition' as well.
edit: never mind my rambling probably better to wait until we know what Viewsonic is going to do and at that point roebeet will let TTx users know how to proceed from TTx to whatever comes down the pipe from VS
I did have a line (I think in the TwoTaps thread) about reversion and wiping data before you reboot into 3588 stock. But, I tried this once myself and it didn't work.
Maybe I should make a special 3588 "mostly stock" with clockworkmod, as a backout solution (so that, if you get into a bootloop situation post downgrade, you already have clockworkmod installed to fix it - that could work). It's the "wipe data" option, btw.
But first, lets see what the vendor does - if they stick with this new bootloader then TNTL5 / TTx users might already be one step ahead of everyone else - you may not want to backout.
Using it since first release with no problems. I always read the entire first post as well as user issues prior to updating. There are probably many users that try before reading which can lead to issues.
I think this is a great ROM.
Sent from my GTablet-TwoTapsX using Tapatalk
I'm one of the ones who ran into troubles getting this to load and I honestly believed I followed all the instructions when doing so. I've tried mostly all of the custom ROMs and was on the Vegan experimental before loading TTx. Not sure what the problem was but nvflashing with or without recovery didn't take. Kept getting stuck in APX mode. I wasn't really worried since I could always get the tablet to take the nvflash so I just kept playing with it until lo and behold, I was able to enter the TTx recovery mode. Been working fine since. I really like this ROM but I definitely feel like the disclaimer is justified - if you're not into tinkering this isn't something you wanna try.
The only problem I've run into so far is that when I recover my Angry Birds file and run the app it FC's. Runs fine if I just install either version, but when I try to restore my saves by using TB, the app refuses to run. Weird. Other than that, no problems. I don't really like the default browser, but understand that it's required at this point. FLash works fine and I haven't had any issues at all with the market. Even found a few apps that were supposedly only available with XOOM builds.
Many thanks Robeet and hopefully we can get a more "idiotproof" upgrade process.
T
roebeet,
Where can we obtain the bekit 1105 file?
I remember seeing the name somewhere but don't remember seeing the D/L source.
Rev
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
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.