Database Users

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.

Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?

Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.

Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]

I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.

PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)

Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)

Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.

just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..

Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.

hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!

Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started

i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off

astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??

Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little

U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App

all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^

How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link

Looks like you are not having much luck. Did you try to factory reset?

astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

A500 wont get past boot logo or CW recovery

I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!

Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
That's what happens when you run stuff from Dev's that don't adhere to GPL. Undoubtedly some leftover code from whomever it was taken from and "somebody" didn't bother to clean it out all the way. FYI, Team Rogue did ICS development for the Xoom tablet, and also some early CWM work. Guess we know where "somebody" got some code from
Ok, back to your current issue at hand. For starters, you're probably still on an HC Bootloader and probably running a really old version of CWM recovery. If you are going to run ICS or JB roms, I highly suggest you upgrade your bootloader to the patched ICS Unlocked bootloader. Also, I would update to the latest version of CWM. You can get it at his site.
I believe your next rom may be able to run on an HC bootloader, or so I've heard, but your CWM needs to be updated, and that's what probably threw out the errors.
You can find a guide for the unlocked bootloader installation in the Dev Forum. It's stickied.
Hope this fixes your issue. If not, post back.
MD

Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
All I can say is WOW!!

linuxsociety said:
All I can say is WOW!!
Click to expand...
Click to collapse
Yeah, its strange but doesn't surprise me.
OP, your partitions are also undoubtedly messed up as well. I suppose you didn't by chance write down your UID number did you? You may be able to get by with installing an ICS full update zip. Maybe.
MD

Soo...nothing. is it just a piece of junk now?

Staples01 said:
Soo...nothing. is it just a piece of junk now?
Click to expand...
Click to collapse
I wouldn't think it is 100% bricked, but I'd definitely ask on tegraowners.com since it is from one of their recovery/roms. Guess you may have already asked Thor about the issue though?

I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.

Staples01 said:
I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.
Click to expand...
Click to collapse
Are you trying to manipulate the A500 from a Windows PC or Linux? Notice you said Dotnetdetector, sounds like windows, but not familiar with it exactly. Maybe you could try using a live linux distribution (such as Ubuntu or Fedora) to try to get fastboot/adb and reflash the recovery partition with a known working recovery for A500. The teamrogue thing still puzzles me and I'm just curious if bits of Team Rogue's code has been pieced in with the A500 recovery you are trying to use, or if you may have got a hold of a recovery that was for a different device ? I'm not trying to say that you are a nub and flashed a recovery for the wrong device, but there is a possibility depending on where you obtained the rom from, that it could have been mis-labeled for your device ( but been for a different one) If it was for a diff device it would make sense why you can't do anything with it.
Let me get it straight how this happened.
1. You had CWM installed for A500 and recovery was working fine
2. You used CWM to try to flash a Thor ROM, in which the installation failed.
3. After reboot you have nothing but the Acer logo
4. When you boot back into recovery, it is no longer CWM, but a Team Rogue logo is displayed, and that is all you see?
That's the way I interpret the issue you are having anyway. Can you please send me a link to the ROM that you tried to install that triggered all of this. That way I can see exactly what the installer script attempted to do (because it very well could have tried to flash a diff recovery to your device and failed on something else)
Hope we can get things straightened up for you. Good luck again bud

Help please! :( need to nflash b70 device.

Hello, need some help please.
Had my 101 with JB Nightlies rom and wanted to try another rom. I've downloaded super wipe for samsung galaxy S3 and run it in my CWM.
The process didn't finish and the tablet restarted giving me an endless message saying to wait a few moments and that it was deleting everything.
The problem is that this process does not stop and i can't get in CWM again. It just stays there... tried to restart and the message comes again and no CWM.
I figure it out that i have to nflash my device but i never did it. I found Wheelie on this link: http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/.
But i just don't know how to do it on linux... just installed Ubuntu.
Can anybody help me please? :crying:

SWEagle said:
Hello, need some help please.
Had my 101 with JB Nightlies rom and wanted to try another rom. I've downloaded super wipe for samsung galaxy S3 and run it in my CWM.
The process didn't finish and the tablet restarted giving me an endless message saying to wait a few moments and that it was deleting everything.
The problem is that this process does not stop and i can't get in CWM again. It just stays there... tried to restart and the message comes again and no CWM.
I figure it out that i have to nflash my device but i never did it. I found Wheelie on this link: http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/.
But i just don't know how to do it on linux... just installed Ubuntu.
Can anybody help me please? :crying:
Click to expand...
Click to collapse
First don't run scripts that are made for other devices, especially a super wipe script, not only that, some roms done need a super wipe, refer to the install directions on each ROM page.
Second,using olife though terminal is probably one of the more dificult methods to use to do what you need.
Try this
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=tool+one+click+stock
It's basically a simplified package instead of you using terminal, it's really straight forward but ask if you need help.

Great software m8 this is probably what i need!!!
The funny thing is that i've been here for 2 hours clicking on vol + and power button and i can't get in to APX mode and i know that i have the correct drivers installed because after the problem append i successfully connected to APX once

SWEagle said:
Great software m8 this is probably what i need!!!
The funny thing is that i've been here for 2 hours clicking on vol + and power button and i can't get in to APX mode and i know that i have the correct drivers installed because after the problem append i successfully connected to APX once
Click to expand...
Click to collapse
Are you clicking like a short press or actually holding them down.
To get into apx you need to hold both of those buttons down while the power is off, usually for about 5-10 seconds.
If it's boot-looping try holding the power and volume + button for like 30 seconds to 2 mins.
I've gotten stuck in a boot loop before and I just had to hold the buttons down for a while before it did anything.
Keep trying, good luck!
Btw is the script you're running on the internal storage or on an SD card?
If it's not even letting you boot android or recovery I think APX mode is your only hope.

nvflash for b70+ devices: http://androidroot.mobi/2012/05/31/wheelie-for-windows-beta/
edit: oh I didnt saw you already have that

fauxsoul said:
Keep trying, good luck!
Btw is the script you're running on the internal storage or on an SD card?
Click to expand...
Click to collapse
It was from the sd card.
I think my problem is my cable because before this happend to me i tried to copy a rom from the computer to the tablet and it wouldn't connect. I've order another cable from Ebay yesterday and let's see what will happens.
This program is very easy to use so i think i will not have a problem. :good:
Will report when i get the cable
Thank you very much!!!

Well, i tried on another computer and i got in APX mode and used the software to nvflash... it totally worked.
Thank you very much fauxsoul for your help :good:
This means that my tablet will never have anymore problems again despite the fact that is a b70 device except if i drop it on the floor! eheheh
Cheers

SWEagle said:
Well, i tried on another computer and i got in APX mode and used the software to nvflash... it totally worked.
Thank you very much fauxsoul for your help :good:
This means that my tablet will never have anymore problems again despite the fact that is a b70 device except if i drop it on the floor! eheheh
Cheers
Click to expand...
Click to collapse
Nice glad that worked out for you!

[Q] I broke my Tf101

Hello everyone This is my first time posting so I hope this is in the correct spot.
I have a Transformer TF101.
I rooted it months ago and can not remember what method I used.
I installed CyanogenMod 10 and everything was fine.
I did an update to one of the nightly builds and now my Transformer is stuck in CWM.
When I plug it into my Windows 7 pc it comes up with a unknown device code 43. I have tried it on several other devices having vista and xp and the same thing happens.
For the heck of it I tried placing the stock FW on the SD card but the transformer does not see it.
I tried placing it in adb mode but the pc still comes up with unknown device.
I have factory reset, wiped cache, and delvik, it is just stuck on CWM.
Can anyone help me with this or did I just totally break the thing? Thank You.

what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager

Broke my TF101
scottyf79 said:
what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager [/QUOTE
Thank You Scotty: That did get me back so it boots up. None of my computers will see it. Wondering if maybe the cable took a dump. I did use rom Manager. At this point I would like to bring everything back to stock and start over. Any suggestions on how to bring back to stock with sync cable not working?
Click to expand...
Click to collapse

best just to get the sync cable and use one of the tools available to make sure it gets done right.
just dont use rom manager bud.....:good:
try this to see if you can fix the recovery loop
Recovery Loop fix with terminal emulator

[Q] A500 Boot Issues...need assistance

I've searched and found a few similar (not identical) problems that people were having, and tried some of the solutions, and none have worked.
I'm trying to fix this stock Acer A500 for a friend. It will boot up part way, goes past the acer screen and android screen, but then stops at a black screen with 'android system' in the upper left corner, the home and back buttons in the bottom left, and the time, signal, and battery life logos in the bottom right. Then there's the Power Off thing in the center of the screen, and it says shutting down but it never shuts down.
I boot into the stock recovery mode, and it says in the upper left on the acer screen:
erasing cache before SD update
SD update cmd: recovery
--update_package=sdcard:update.zip
booting recovery kernel image
then it shows the android with the turning gears, then goes straight to the android with the warning symbol.
Since I can't get into the OS, i have no idea which version or specific model this is, but i downloaded a few different honeycomb update.zips, and put those on the SD card, and when i tried booting with those, the loading bar pops up under the android logo, and it goes to about 1/3 of completion before switching back to the warning symbol.
I tried downloading what im pretty sure was a full version of jellybean for this tablet, and it went straight to the warning symbol, no loading bar. same when i tried renaming the file update.zip >.>
im clearly very new to all this, but i'd really like to get this thing working.
is there a way to do a factory reset without booting all the way into the OS?
im not sure because it seems like the only file its looking for in recovery mode is update.zip.
if anyone has any bright ideas, id appreciate the help.
Also, not sure if this is relevant, but when i boot it normally, and it goes to the 'shutting down' screen, the battery level indicator says its almost dead, but i can leave it plugged in for hours and nothing changes at all.
EDIT: Also, it won't even boot if the power cable is not connected.

Similar issue hope there is a solution
I have a similar problem. Tablet was working fine, sitting on docking station. Returned to it the next day and when I went to wake it, it would not wake. Rebooted it but will not reboot. Sits on the ANDROID screen after the ASUS title screen indefinitely. If I try and boot into recovery it fails at "update.zip" and I see the broken Android image laying there.
Is there a means to restore it from PC via the usb cable and can someone please post a very noob friendly walk through step-by-step?
Greatly appreciate any positive advice!

Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD

zardoz99 said:
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
So, dead chip? So soon? Nice.

NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
Yep.. 14 months old in my case. Contacted Acer and said "what about a fix?" They said, "no chance unless you cross our palms with lots of silver."
So, bought a Samsung Note 10.1 instead. Acer can "stuff it". I won't be buying a tablet from them again. Considering that I bought their "flagship" product of the A501 with the 64GB memory, this is truly unacceptable.
I was incredibly careful with it and certainly never did anything to void the warranty. But, you only get 12 months and then it's over.

NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?

skurtov said:
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
Click to expand...
Click to collapse
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!

NoOneSpecific said:
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD

skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
I'll have him PM you when he is able.
Thanks!

skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!

coluwyvurne said:
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
Click to expand...
Click to collapse
You are quite right sir, however the button combination I am most familiar with is holding the power and the reset button (the one you have to stick the paper clip in) when you first start it up. It should then either say APX mode on the screen or be blank, either way the computer will identify it as a APX device and automatically install the drivers.
Going into APX MODE manualy
You enter APX mode by holding down the Reset button(with paper clip). Do not release it. Hold down power for 3 secs and then release it. After another second, release the reset button.
Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
The screen of your tablet is black.
Quoted from Civato
Click to expand...
Click to collapse
The next course of action is to get the SBK, from what it sounds like the tablet didn't write a partition properly and that's why it's not booting. So what you can do is wipe out the partitions and install a custom bootloader and recovery. Not only does it fix things but it also opens up his world to custom roms . Okay, back to the matter at hand, I don't know if he has his SBK or not, and if he does skip the step to find it and just run babsector below. If not then follow the next step.
You'll have to pull the UID from the tablet using this method described here:
http://git.pappkartong.se/?p=a500/apxuid.git;a=snapshot;h=HEAD;sf=tgz
There's a readme
After getting the UID and calculating your SBK you'll just go to the next step.
All credit goes to user eppeP.
Click to expand...
Click to collapse
Run this file hosted here:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
And this file basically rewrites and formats the partitions out installs a custom bootloader and recovery
Credit goes to Danny2 for finding this and posting it.
Click to expand...
Click to collapse
Once this is done, pick a new rom. I prefer the Civato ones, load it on a SD, boot to recovery, erase dalvik cache, cache, do a factory reset wipe (from the recovery menu!), then wipe system, flash the rom and go on your merry way

Many thanks for the reply.
As per your instructions, I have booted the tablet into APX mode. However, as I do not know the UID of the device, I've had to try to run the utilities to create a driver for the device and then pull UID from the tablet...
I am able to create the driver for the device and install it with driver signing off in Windows, but I can't figure out how to run the script to get the UID. I notice the file in the package you directed me to contains an .SLN file, which would indicate it is a programming solution file. I have Visual Studio on my system but it cannot open this particular .SLN file.
How would I run what's in the package to pull out the UID of the tablet?
Any help getting past this hurdle would be much appreciated!