[Q] Rooted 3G Xoom - Trying to Update to 3.1 - Xoom Q&A, Help & Troubleshooting

Ok, so here's my dilemma (And btw, I am not new to this, but it seems as though Motorola is a bit trickier than Samsung when it comes to Rooting IMO. Maybe it's just me.
I recently, through the help of a couple Online Video Tutorials created by SleeplessNinja (Whom btw, is bad ass!!! For all the work he has done!!! I have learned more from him and his Video Turtorials about ADB, fastboot, and Command Prompt in these last few weeks, than I have in all of the short time that I have been working with Android.) I reverted my 3G Xoom back to its ORIGINAL state, like it was the day I took it out of the box, fresh from the HoneyComb 3.0.1 Farm. After doing so I then followed this up by installing a version of CWM (made by Solarnz) through fastboot/ADB. The CWM version is "recovery-Tiamat-R4c-100611-1150-cwm". I then Rooted my Xoom as well with the Universal-Xoom-Root.zip file. In this process, I also flashed a new boot.img, system.img, userdata.img that were all required in order to gain the precious Root that I so badly wanted, rather, needed!​So here I am, with my Xoom freshly rebooted, and smiling with it's now huge Rooted Smile! And what do you think happened next? Oh what do we have here? But an OTA update for the wonderful HoneyComb 3.1! Oh what to do? Do I risk losing my recently gained Root? That, which I went through so much to achieve? Or do I bite the bullet and go for it? Well, instead, I immediately turned off my Xoom, before it could even start downloading the update. I then sifted through countless pages upon pages here in the XDA Forums (Which btw, is the absolute greatest place ever!!! I just had to throw that out there) in the Xoom section, all of which describe ways to update your Rooted 3G Xoom running HoneyComb 3.0.1 to HoneyComb 3.1 they just seem to do it different ways, and some enable you to keep Root, and some you have to lose Root, and then ReRoot once finished.​What I can see is that for the most part it looks as though to go from 3.0.1 to 3.1 one would have to do a similar download of the required boot.img, system.img, recovery.img, as well as the required 3G radio files, and push them through by way of either ClockWorkMod Recovery, or by pushing it through ADB/fastboot. Only thing is, all of the files, or links to files, and I DO MEAN ALL OF THEM, seem to be DEAD links. They either take me to a page that says forbidden, or they take me to an iLivid download page?​Finally, just now, just a few minutes ago, I said screw it and bit the bullet. I decided to download the OTA update and try and just ReRoot after this process finished. Well can you guess what happened when my Xoom restarted? It went into recovery mode for some reason. And at the moment, I am not really sure why?​
I received an Error message that says the following:
ClockWorkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
E:Can't open /dev/block/mmcblk1p3
(No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I am including picture to the Recovery screen so that everyone can see exactly what it looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope that someone can help me out. I just want to be able to update my Xoom to 3.1 as well as have my Root. I know that there are plenty of ways to do so, and I am fairly comfortable with pretty much every method. Whether it be Command Prompt(ADB/fastboot) A SuperOneClick Method, or installing a modified Recovery and modded System and Boot .img's. Please Help!

I don't know if I got what you mean, but let's see...
First you have to reinstall the Stock Version, the problem is that you'll lose your root access and your data will be formated. After you install the Stock Version again don't root and receive the updates, if I am not wrong you have an Everest Xoom, so you can update until Android 4.0.X, after you update check the FAQ to reroot your Xoom
Wish you all the best!
"This Story Ends Where It Began" - Octavarium (Dream Theater)

XxLordxX said:
I don't know if I got what you mean, but let's see...
First you have to reinstall the Stock Version, the problem is that you'll lose your root access and your data will be formated. After you install the Stock Version again don't root and receive the updates, if I am not wrong you have an Everest Xoom, so you can update until Android 4.0.X, after you update check the FAQ to reroot your Xoom
Wish you all the best!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Click to expand...
Click to collapse
Thank you very much XxLordxX, all input is welcomed, and very much appreciated, but unfortunately that's not quite it. Allow me to try and simplify:
I am not concerned at all about formatting, and losing any data.
1. What I want to know is, what do these Error messages that I'm now receiving every time I boot into my Custom Recovery mean? Does anyone think I should go about re-installing the Custom Recovery again? The one that is currently installed, the one that I originally installed when I Rooted the Honeycomb 3.0.1? Or should I just go ahead and install a more current version of CWM?
2. Also, why do you suppose that after the OTA download of the Honeycomb 3.1 update was completed and the Xoom restarted, it booted into the Recovery and started giving me those Error messages? I personally think that there is an issue with the OTA Honeycomb 3.1 update, and how it syncs up with this Custom Recovery that I have installed that was created by Solarnz. (Whom by the way does bad ass work!!! It was working flawlessly up until I decided to try and update. LOL. So I want to be clear that I am NOT placing blame at ANYONE but MYSELF as to why I am receiving these error messages. LOL. I just had to add that last line in case somebody took anything I have previously stated in any way offensive.
I just am hoping that someone hear can possibly help me out with correcting the issue/issues at hand.
I may end up just re-installing everything back to stock, and then doing like XxLordxX and just updating my 3G Stingray Xoom through OTA, until I get to the desired OS. Decisions decisions....

DannyShane said:
Thank you very much XxLordxX, all input is welcomed, and very much appreciated, but unfortunately that's not quite it. Allow me to try and simplify:
I am not concerned at all about formatting, and losing any data.
1. What I want to know is, what do these Error messages that I'm now receiving every time I boot into my Custom Recovery mean? Does anyone think I should go about re-installing the Custom Recovery again? The one that is currently installed, the one that I originally installed when I Rooted the Honeycomb 3.0.1? Or should I just go ahead and install a more current version of CWM?
2. Also, why do you suppose that after the OTA download of the Honeycomb 3.1 update was completed and the Xoom restarted, it booted into the Recovery and started giving me those Error messages? I personally think that there is an issue with the OTA Honeycomb 3.1 update, and how it syncs up with this Custom Recovery that I have installed that was created by Solarnz. (Whom by the way does bad ass work!!! It was working flawlessly up until I decided to try and update. LOL. So I want to be clear that I am NOT placing blame at ANYONE but MYSELF as to why I am receiving these error messages. LOL. I just had to add that last line in case somebody took anything I have previously stated in any way offensive.
I just am hoping that someone hear can possibly help me out with correcting the issue/issues at hand.
I may end up just re-installing everything back to stock, and then doing like XxLordxX and just updating my 3G Stingray Xoom through OTA, until I get to the desired OS. Decisions decisions....
Click to expand...
Click to collapse
I suppose those errors messages is because you aren't on Stock Recovery, however you can't just install the Stock Recovery, because custom ROMs doesn't support it. I think there's no problem with the OTA Package, although the recovery is a problem, because it's custom. As you told you're not concerned about formatting your tablet, do it and install Stock again, then you update until the version you want, after that you root again
For more info about restoring to Stock and Rooting visit the FAQ
(BTW, are the same DannyShane from U|A? Because I'm the same XxLordxX as the one at U|A lol)
"This Story Ends Where It Began" - Octavarium (Dream Theater)

Related

Got a OTA for my ADP1!

Just received update notification (running jf's adp)
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.
Its adp's update. No its not cupcake lol
Uh oh, if it's a new bootloader, could this mean trouble for us in the future?
doesn't sound good to me
Just installed the bootloader without the "complete system update" and... surprise. The original T-Mobile G1 bootloader (RGB). After seeing that i downloaded hard spl, then installed it and that's all. I'm not going to complete the full update, because there is a chance after the update to be stuck to normal bootloader, and I don't want to prove it
Good morning!
I was just checking out the market when I got a popup message on my ADP1 (v1.1) telling me a baseband update was available.
I cant remember which version I had before, but it my Baseband version is now:
62.33.20.08H_1.22.12.29
Anyone have the same thing?
Untouchab1e, what was the use of reporting this post? it's only to report Spams, advertisments and other abusing stuff to the Mods and Admins, please use it wisely the next time or you'll get a ban!
yes you called
we came running....please use the report button as it should
thank you
My apologies? I either clicked the wrong button or I dont know, as I cant remember clicking any report button (havent noticed any report button at all really)..
Anyhow, sorry for the trouble
EDIT: A second update is being installed now, described as a "Full system update".. will be interesting to see what it is!
EDIT2: Its apparantly the ADP1 equivalent of the RC33. Latitude, Voice Search.. its all there!
Thank you Google
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the Report Post Button its right besides the post number
ADP OTA update = no more Wifi Tethering??
I go ahead and did the update.
I checked the bootloader and it's still the modded one.
although, there's other problem. I can't do wifi tethering from the terminal emulator. I don't know if the OTA update take out Root access or not. is there a way to check root status without using Terminal emulator? (I know on the terminal emulator you just type su for superuser to get root, and # on the prompt means you have root access)
So, When I typed "tether start" after running the .tar file from the terminal emulator, I got this message
Code:
insmod: init_module '/system/lib/modules/wlan.ko' failed (file exists)
then when I typed tether stop, I get this message:
Code:
rmmod: delete_module 'wlan' failed (errno 11)
any info on this probleM? I need the tether function because it is the only internet access for my laptop at home because my cheap ass aunt disconnected the DSL for the house.
please be nice to me as I am a linux noob and has fairly little understanding using the terminal command line.
Edit: Nevermind. I found the problem. I had the Wifi radio on before I run the terminal code for tethering. Sorry for freaking out guys.
mony87 said:
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.
Click to expand...
Click to collapse
I just got this exact same update notification (im in the netherlands), im also running JF's ADP1 1.41 but im doing so on a devphone......... I really dont want to install anything on my phone unless i know specifically what it does or changes.....
mony87 said:
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.
Click to expand...
Click to collapse
I got it too, and I'm not even running a TMobile data plan. It came in over wifi on JF ADP1.1. I did not install it. It's very annoying to say no to the update every time my phone wakes up from screen lock, however.
EDIT: JF's got a new release to fix this problem: http://forum.xda-developers.com/showthread.php?t=475381 (or check out the top sticky post).
Did it...
... i also got this message and i did the update.
Nothing changend after update. Everthing is the same.
Does this mean, we are all getting ota-updates in the future, even if we are on JF (RC33 or RC8)?
I thought JF deactivated this in his versions...???
kanisdragon said:
I got it too, and I'm not even running a TMobile data plan. It came in over wifi on JF ADP1.1. I did not install it. It's very annoying to say no to the update every time my phone wakes up from screen lock, however.
Click to expand...
Click to collapse
Here's the news....
First part of the update was no problem, all still worked..
Second part installed, phone rebooted, got the nice little blinking android and nothing happened for 15 min :S SO i got bored and tried to turn if off but this didnt work, pulled the battery and the same thing happened; phone hangs on bootup..... So its fooked haha, ill update to JF 1.42ADP1.1h, see what happens. I do need to find a way to disable this update stuff 'cuz its annoying!
So BEWARE when using these 'ota' updates on modded firmwares!!
[edit] And no, i do not have anything Tmobile on my phone because Tmobile sux! [/edit]
...same..
after the second update (part 2) my phone got stucked too.
What can I do now?
Hanneskitz said:
after the second update (part 2) my phone got stucked too.
What can I do now?
Click to expand...
Click to collapse
You can pray my friend, pray!
No, seriously i do have a solution but its not a pretty one...... I wiped my phone completely and had to reinstall the whole lot. Seems to work fine now but i just hope i dont get the freakin annoying update window again because that would seriously piss me off!
I dont know how easy this will be on non-dev phones tho....
maarten82 said:
You can pray my friend, pray!
No, seriously i do have a solution but its not a pretty one...... I wiped my phone completely and had to reinstall the whole lot. Seems to work fine now but i just hope i dont get the freakin annoying update window again because that would seriously piss me off!
I dont know how easy this will be on non-dev phones tho....
Click to expand...
Click to collapse
It sounds to me like this update was sent by Google only to dev phones. Couldn't you also do a nandroid restore if you made a backup?
kanisdragon said:
It sounds to me like this update was sent by Google only to dev phones. Couldn't you also do a nandroid restore if you made a backup?
Click to expand...
Click to collapse
Probably..... but setting back the complete backup(s) would not fix anything because you would still get the annoying update window telling you to install the stuff that will in turn crash you phone back to where you started
But then from your old backup you could try to install JF1.42 without wiping, that might work!
maarten82 said:
But then from your old backup you could try to install JF1.42 without wiping, that might work!
Click to expand...
Click to collapse
The JF1.42 update worked for me without wiping. I haven't been offered the Google update in the last hour.

EVO OTA is here

take a look guys
http://androidforums.com/htc-evo-4g/90893-ota-update-1-32-651-6-a.html
Interesting...
I am running Flips "stock" rom, and no prompt for this...
Did a "firmware" update... none found.
Did a HTC Software Update... found it.
post the zip so flipz and toast can have a look at it
extrafuzzyllama said:
post the zip so flipz and toast can have a look at it
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used the search function in Root Explorer, but found neither "OTA_Supersonic" or "update.zip"
It must be in one of those folders that need root to view (right now I'm stock no root) like /data or something
DO NOT ACCEPT THE UPDATE FOR NOW ...MORE LATER FROM Matt, Ozzeh,Joshua and zule...
https://twitter.com/unrevoked
There's an OTA update we just got on the #EVO that breaks the root. Don't install it if you want to root.
Click to expand...
Click to collapse
Well that sucks...
upload it so the devs can see whazzz up!
Here's a copy of the sprint hero ota that I got at the same time and it supposedly (not gonna test it) breaks root. I'm pretty sure it's really a super cool update to make are phones ten times better
Just got back home. Super glad I saw this thread. I had the guy at radioshack cancel the update when it came up (he had to turn phone on to complete activation, he said).
He mentioned that for the other 6 phones he did that morning, he let the update install
GumboChief said:
Just got back home. Super glad I saw this thread. I had the guy at radioshack cancel the update when it came up (he had to turn phone on to complete activation, he said).
He mentioned that for the other 6 phones he did that morning, he let the update install
Click to expand...
Click to collapse
99% of the population is better off with the update due to the storage fix. Rooters are a tiny group of people, relatively speaking.
The guy at Sprint almost ran the update since they do have to turn the phone on to activate it, however since I didn't need anything else he just told me to make sure to update and told me how and even offered. I told him I'd get right on it as I go outside. But yea the OTA is probably best for most consumers buying this device (especially after the conversations that took place this morning) as just about everyone else there this morning just wanted to get the phone switching from various carriers from T-Mobile and ATT and just wanted it to work. There was like one other guy there who was pretty knowledgeable buying the phone outright like I was, but he claimed again he just wants the phone to work no jumping through hoops and knows about rooting but has no intentions to. The guy in charge was emphasizing to his staff to make sure to push the update. I just happened to luck out.
anyone got pre and post ota version numbers so I can confirm my unit hadn't been updated before handing it over? Thanks
FuManChuu said:
anyone got pre and post ota version numbers so I can confirm my unit hadn't been updated before handing it over? Thanks
Click to expand...
Click to collapse
1.32.651.1 ->Shipping
1.32.651.6 ->OTA
I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.
princem131 said:
I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.
Click to expand...
Click to collapse
That sounds promising. Look at the rom version in the about section of settings. Does it end with a 1 or a 6?
princem131 said:
I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.
Click to expand...
Click to collapse
are you able to type su thru adb shell or connectbot on the localhost after applying the OTA while stil using flipz stock with root ROM?
um i tested... OTA applied... Rooted, recovery, NAND backup... it all worked...USB debugging Enabled on plugin. Installed 64bit ADB drivers and boom!
no problem to fear the root loss
um crap... nvm apparently i didnt update...
i swear I downloaded, installed, restarted the phone to allow install... but it shows software number 1.32.651.1.
maybe because I did a factory reset? then that would mean that this update is rather a patch (ie like a cab fix)??
or did the update not apply?
Tilde88 said:
um i tested... OTA applied... Rooted, recovery, NAND backup... it all worked...USB debugging Enabled on plugin. Installed 64bit ADB drivers and boom!
no problem to fear the root loss
Click to expand...
Click to collapse
But does that retain the update fix for the sdcard?
damn i updated what am i supposed to do now ?

Next8P12 (Big Lots 'Black Friday Edition' Nextbook)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm seeing a lot of confusion on the forums about the Nextbook Big Lots released on Black Friday so I see it worth making a thread over.
This Nextbook does *not* use the Rockchip RK2918. If you look at the build info and do a little research (http://yifang.en.made-in-china.com/...-4-0-Tablet-with-Amlogic-8726-M3-M805MC-.html) it's got an Amlogic 8726-M3 under the hood. That's the M3 chip people keep mentioning here.
I have gathered much information on this 'new' Nextbook and posted it here. I have found what I think to be a jtag mode where, as people described, "M3-Chip" shows up in device manager. That forum thread has an Android System Info dump posted and for the sake of space I won't be reposting it here so go there and check it out. I only omitted non-relevant personal info and replaced with a [Removed] tag.
I would really like to see some genius minds at work getting this tablet rooted and the 'ROM Train' chugging. I have donated my talents of information gathering. I'm calling for someone to pick up the torch and work it from here. I've noticed at least two people that said they bought at least 3 of these so maybe someone can work with someone on donating a device to a cause and XDA can add another 'rooted knotch' to it's seemingly infinitely long belt'
---
[Update]
Here is the chip MFG's original source code to include kernel and all the toppings. This should be good starter info: http://openlinux.amlogic.com/wiki/index.php/Arm/Platform_Info/Information_for_8726M/Build_system_for_8726M_Howto. Also I've brought Slatedroid in the loop on this one so hopefully we can get the ball moving quickly.
What's up...just got one of these as well and of course like other people I was surprised to find out this wasn't rk29 as I was super ready to root this thing...I have absolutely no idea if this will help any and you may have already come across this site but it seems that the admin here (finless) knows how to work with these devices.
I don't know if that would go for this particular version with the m3 chip but anybody else who can get this rooted would be of great help. I wish I knew how to do it myself because I would but I'm only good for graphics...glad I came across this thread and to see you gathering much needed info, I'll stay tuned and if I stumble across anything that can help I'll be sure to post it here.
I have one of these units as well and would like to get it rooted. Just chiming in.
therealrayzzor said:
What's up...just got one of these as well and of course like other people I was surprised to find out this wasn't rk29 as I was super ready to root this thing...I have absolutely no idea if this will help any and you may have already come across this site but it seems that the admin here (finless) knows how to work with these devices.
I don't know if that would go for this particular version with the m3 chip but anybody else who can get this rooted would be of great help. I wish I knew how to do it myself because I would but I'm only good for graphics...glad I came across this thread and to see you gathering much needed info, I'll stay tuned and if I stumble across anything that can help I'll be sure to post it here.
Click to expand...
Click to collapse
Thanks for the info! I have made some progress. Here's a thread on Slatedroid that has the M3-Chip driver and low level flash utility: http://www.slatedroid.com/topic/39037-amlogic-low-level-flashing-tool/
I am tinkering with it a little but I'd encourage someone smarter than I to have a look at it as well in case I fail. To get the tablet in the proper mode do vol up + plug in usb with device powered down. I'll go ahead and attach related files here for convenience. You will need to disable driver verification to get the driver installed.
My first attempt I think I might have bricked the tablet. I'll give more info as I get it.
Yeah I fu-barred it. Anyone with experience w/ AmlogicBurningTool -or- someone who can extract the firmware so I can flash; I think I wiped my device tinkering with this utility. Any help would be appreciated as I'm dead in the water until I get the device bootable again.
[Update] I contacted Nextbook on this issue. The sup seemed pretty pissed when I let him know what I was attempting to do but for being forthcoming he agreed to see about getting me the original firmware zip file. As per usual I will update should I get any info.
Nice job! Thanks for all the work on this. I've got one I'm willing to hack on too. Not sure how to get the firmware off of it but I'm willing to try anything. I've been looking around and I supposed I'd need to run the burning tool with the device in IPL (not sure if that's what it's called) to take the firmware off? Let me know how I can help.
I'm on a thread now with Finless on FreakTab and he said he can build a rom for us to get root...he just needs the stock rom to work with...I'm waiting on some type of instructions in case I need to take it from my tab and give to him.
Maybe this could be the break we're looking for.
therealrayzzor said:
I'm on a thread now with Finless on FreakTab and he said he can build a rom for us to get root...he just needs the stock rom to work with...I'm waiting on some type of instructions in case I need to take it from my tab and give to him.
Maybe this could be the break we're looking for.
Click to expand...
Click to collapse
I sure hope so.........this stock rom sucks! I've been trying to mess around with it and install some apps from SDcard but having absolutely no luck. Now mine wont even boot. Going to have to reset to out of box.
mascondante said:
Yeah I fu-barred it. Anyone with experience w/ AmlogicBurningTool -or- someone who can extract the firmware so I can flash; I think I wiped my device tinkering with this utility. Any help would be appreciated as I'm dead in the water until I get the device bootable again.
[Update] I contacted Nextbook on this issue. The sup seemed pretty pissed when I let him know what I was attempting to do but for being forthcoming he agreed to see about getting me the original firmware zip file. As per usual I will update should I get any info.
Click to expand...
Click to collapse
If they provide you with a copy, Finless can root it for sure.
shaunmt said:
If they provide you with a copy, Finless can root it for sure.
Click to expand...
Click to collapse
That would be awesome. My folks are getting me a Google Nexus 10 for Christmas. If I can get this one working I might be tempted to spend that money on something else. I feel really really dumb for wiping the NAND just because it was in Chinese and I clicked a random button. I thought surely it'd give some sort of popup warning to alert me I'm being an idiot first. But it happily wiped the thing no questions asked. So, when we get to the point of flashing a firmware in; If we have to use the low level flash tool be really freakin sure you got it in English and you read the instructions thoroughly before flashing. It's not normally like me to do something that dumb but I've not been getting good sleep and I've been in a real big rush to get this project done.
Lesson of the day:
So no one has been able to install google play on it so far ?
kristibaee said:
So no one has been able to install google play on it so far ?
Click to expand...
Click to collapse
That would require root access which has not yet been obtained. Once someone successfully roots it, installing market will be easy. Stay tuned.
No go on a ROM from TS
I opened a ticket with tech support to try to get the ROM from this thing and they said it's not available to consumers... I figured I'd get some response like that but just thought I'd give it a shot. +1 for a customer "needing" the ROM on their end.
So your tab is still not booting mascondante?!?
tread_water said:
I opened a ticket with tech support to try to get the ROM from this thing and they said it's not available to consumers... I figured I'd get some response like that but just thought I'd give it a shot. +1 for a customer "needing" the ROM on their end.
So your tab is still not booting mascondante?!?
Click to expand...
Click to collapse
nope after i wiped the nand it fails at the first phase of flashing
Still haven't heard back from Netbook.
Sent from my Nexus 10 using XDA Premium HD app
Still hoping someone will root this thing and make a decent ROM. Please?
My Ramos W13Pro AMlogic was pre-rooted in a way. I was able to ADB to it and type su and got the # prompt back.
What we need for sure is uImage dump (boot.img is the same). This will give us the kernel and boot which is the most important part!
Get Android Terminal Emulator. Run it and at the $ prompt type su
If it returns with # it means you have root access.
If you do not get # it is not pre rooted. However you can do this command without root I think
cat /proc/mtd
This will show the mounted blocks. We need to dump those to SDcard using DD command.
Bob
Nextbook ADB access
Bob, I've been lurking for a while on XDA and on your own Freaktab site trying to get this Nextbook 8p12 / 8SE with amlogic chip rooted as a christmas present for my son. I've managed to get the market and google services framework installed on the thing but they force close due to other necessary files missing. I saw your post above and jumped right into ADB on this thing, but got a permission denied error on the DD command trying to copy the bootloader. Any suggestions? Many thanks!
We may have a breakthrough over at freaktab.com!
Stay tuned...
eegorr: Could you link the discussion so folks from here can have a look at the progress?

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Shield Tablet

Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
Sorry for the question... but how is the process to root a Nvidia Shield Tablet? It supports update 2.2.1?
Thanks!!
tux_topo said:
Sorry for the question... but how is the process to root a Nvidia Shield Tablet? It supports update 2.2.1?
Thanks!!
Click to expand...
Click to collapse
I'm working on a step-by-step written guide, but the toolkit will guide you through the steps to root as well. The toolkit does support the 2.2.1 update. :good:
Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!
tux_topo said:
Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!
Click to expand...
Click to collapse
+1.
not looking to install custom recovery, just root. Looking forward to the progress of this toolkit. Thanks @WindyCityRockr
Sent from my 1+1
tux_topo said:
Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!
Click to expand...
Click to collapse
Mojar7070 said:
+1.
not looking to install custom recovery, just root. Looking forward to the progress of this toolkit. Thanks @WindyCityRockr
Sent from my 1+1
Click to expand...
Click to collapse
Unlocking the bootloader WILL erase all data. I don't know if you could achieve root without a custom recovery but if you plan to flash a custom recovery you will need to unlock the bootloader.
While this tool worked for me, it didn't work well with step 2. It did flash the recovery but I had to manually reboot to recovery for it to work. Selecting yes/next to reboot to recovery after flashing it through the tool only took me to fastboot. That was the only thing I noticed but other than that, everything else worked perfectly. For clarification as well, I did it on newest firmware available right now (2.2.1).
gqukyo said:
While this tool worked for me, it didn't work well with step 2. It did flash the recovery but I had to manually reboot to recovery for it to work. Selecting yes/next to reboot to recovery after flashing it through the tool only took me to fastboot. That was the only thing I noticed but other than that, everything else worked perfectly. For clarification as well, I did it on newest firmware available right now (2.2.1).
Click to expand...
Click to collapse
The reboot option after the recovery flash is supposed to reboot you back to Android because the next step in the toolkit is to push SuperSU, which requires ADB.
WindyCityRockr said:
The reboot option after the recovery flash is supposed to reboot you back to Android because the next step in the toolkit is to push SuperSU, which requires ADB.
Click to expand...
Click to collapse
Well in my case, it didn't do that either, mine ended up in fastboot. In any case it everything works as it should. thanks!
Worked flawless.
After flashing TWRP where it asks to reboot, it does reboot the tablet but the program seems to get stuck on "Rebooting......" even after the tablet have booted.
I tried waiting a min to see if it changed but I had to remove and attach the USB again before it realized it was connected and said "Move to step 3".
I'm happy though because anything that can be done smoother than ADB (even though it is really easy) is appreciated.
Wow, this looks super useful and easy. I was just thinking of rooting my shield again cause I'm sick of adds and just dropped in to see how things were progressing on the development side.
Glad I did now, might give this a whirl today
Edit: This is awesome! I was contemplating rooting my 2nd shield (after my first one blew up after 5 days) and have been putting it off for a while.
I'm used to rooting n'stuff so I don't find it to difficult but this just made things so much easier! I had it unlocked and rooted in a couple of minutes.
Big thank you for your effort and hard work.
I can't seem to get adb working. What do I need to do to get the program to recognize my shield tablet?
Sent from my Nexus 6 using Xparent Cyan Tapatalk 2
Ensure you have installed the drivers.
And don't forget to use an USB 2.0 port! USB 3.0 ports generally do not work.
Is there any way to do this with Ubuntu?
Thank you for this! It looks like an amazing tool, just what I was looking for. I had a Kindle Fire HD and it was a hell lot of trouble to install TWRP and flash roms, and when I saw my brand new shield had a hell of a process to get rooted in Lollipop the Kindle nightmare just flashed before my eyes (I had bricked it once so my heart practically stops every time an android device of mine reboots, in fear it won't turn on again). It's such a relief to see everything automated.
If you read what I had written there before (some questions about how to use the toolkit) never mind me, I found the instructions
i can't get this to work, it keeps saying OFFLINE. i installed everything it requested when I opened the .exe
Unlocked bootloader.
Installed Twrp.
But when i go to recovery mode on my lg watch r it STILL boots to the stock recovery???
Am i doing something wrong?

Rooting and getting the latest custom ROM for Transformer TF300T?

I just pulled this device out of a closet where it's been stored for the past four years or so. Still boots up to the latest JB 4.2.1. Hardware still looks almost new and seems a waste to just get rid of it. If possible, I'd like to bring it up to the latest Adroid OS that the hardware can handle, and use it in the kitchen to look at cooking videos online (it's bigger and easier to see than my phone, LOL). However the device is still locked, and the Asus Unlock app, according to the Playstore, isn't compatible with my device. (I probably need an older version than what's in the Playstore now). I've rooted Samsung phones before, but never done anything with a tablet. Also it's been a while (last phone I rooted was a Samsung Galaxy S5), so step by step of where I need to go from here would be much appreciated. Thanks!
TechieSophie said:
I just pulled this device out of a closet where it's been stored for the past four years or so. Still boots up to the latest JB 4.2.1. Hardware still looks almost new and seems a waste to just get rid of it. If possible, I'd like to bring it up to the latest Adroid OS that the hardware can handle, and use it in the kitchen to look at cooking videos online (it's bigger and easier to see than my phone, LOL). However the device is still locked, and the Asus Unlock app, according to the Playstore, isn't compatible with my device. (I probably need an older version than what's in the Playstore now). I've rooted Samsung phones before, but never done anything with a tablet. Also it's been a while (last phone I rooted was a Samsung Galaxy S5), so step by step of where I need to go from here would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi! You need to download the Unlock App from Asus Support Site.
Go to Asus Support-Product Tablets - Transformers - TF300T - And under Utilities download V8 Unlock App (Use expand all if you don't see it)
figazin said:
Hi! You need to download the Unlock App from Asus Support Site.
Go to Asus Support-Product Tablets - Transformers - TF300T - And under Utilities download V8 Unlock App (Use expand all if you don't see it)
Click to expand...
Click to collapse
I have downloaded the software to my laptop, and will transfer it to the tablet by emailing it to myself, then open the email on the tablet. Thank you so much!
Sophie
After that you'll need an SD to install TWRP and a the custom OS you want to flash (I'm not an expert, just repeating what I've been reading here).
I couldn't get past installing the Unlock App. I always get a "network connection error" and I've been trying to fix that
figazin said:
After that you'll need an SD to install TWRP and a the custom OS you want to flash (I'm not an expert, just repeating what I've been reading here).
I couldn't get past installing the Unlock App. I always get a "network connection error" and I've been trying to fix that
Click to expand...
Click to collapse
Oh, I think I read something about that issue, and the people had to call Asus to fix it. I suspect maybe they have taken down the server that responds to that connection by now. That would be a drag if I have to call them. But I'll give this a go and see. Thanks again!
TechieSophie said:
Oh, I think I read something about that issue, and the people had to call Asus to fix it. I suspect maybe they have taken down the server that responds to that connection by now. That would be a drag if I have to call them. But I'll give this a go and see. Thanks again!
Click to expand...
Click to collapse
The same question, the customer service said that it can only be sent for repair
look forward to your progress
lihgt2000 said:
The same question, the customer service said that it can only be sent for repair
look forward to your progress
Click to expand...
Click to collapse
Well, I'm stuck at trying to get the Unlock App to work too. Keep getting the same error message that everybody else was getting. I've tried getting help from Asus and got stuck in their Knowledge Base loop. Couldn't get a hold of any live person, not even a chat. I have a feeling that's how it is during COVID-19 pandemic. I'm going to put this project on hold for now and revisit it again when Asus has more support staff available.
Thanks again for all the help!
TechieSophie, i know how to root Asus Tf300t, you need to use the vroot (chinese) then you need to install Super SU to change the language, that works on me, but still having the problem to unlock the bootloader, im working on that, maybe in a few days i will get it! regards​
Same here... No luck unlocking the device. Android has latest updates that were available... Ver 4.2.1
I've tried the following...
Tried UnLock_Device_App_v7 and v8
Tried the above after removing all accounts
Tried the above after System restore
Registered the Tablet with proper serial number on Asus website and tried again
Created a new account and tried again
All I get from the unlock tools is the network error everybody gets (I think it's not supported any more) and someone needs to come up with a new utility or custom decipher utility that considers what the Asus website used to feedback to the utility after you supply the serial number. Not sure if this is unique code for every serial number or not?
Tried connecting with AsusSync and using RootDebugfs... It sees the Tablet, restarts it and stuff, but long story short it cannot push the files over (denied or whatever)
With AsusSync and RootDebugfs I'm not sure if I need or even can root the device which would then give me permission to push files to the root folder?
As of yesterday I emailed Asus support, however, I doubt anybody who has emailed about this topic as of recent will get any kind of clear response like "We cannot and will not give unlock support for this device any more" or "If you registered your device our network tool connection will be fixed shortly".
I've searched for updated videos that have been created in the last year or two but there is only a few and in another language
If anybody has a more resent successful method step by step it would be appreciated...
such as 1) Root and method 2) Unlock bootloader and method 3) etc. etc.
Thanks, I know a lot of people are trying, reading, and awaiting a successful method for devices that had not been previously unlocked and or rooted in order to upgrade.
I Don´t know if you want to keep the original ASUS system. Or try a new one.
I Guess that ASUS stopped developing the system for TF300T, This is why there is nothing above Android 4.
I've been using KatKiss for about 4 years now on my TF300T, and it is great.
The system is based on Android 7.1.
Early this year I changed the Google pack (Wich is pretty heavy) For the MicroG also. the tablet is running smoothly, but there is no Play Store.
On this thread, there is info on installing KatKiss and MicroG (microG is on the latest messages on the thread)
[ROM][N 7.1.2] [ KatKiss - Nougatella #039 ]
KatKiss ROM Nougat 7.1 Release Asus TF300T Please note that this version is made for and tested on the TF300T model. This rom is an aosp based rom with my own additions on top of it. The main motto of the rom being Kiss. Even...
forum.xda-developers.com
[GUIDE/TUTORIAL] Asus Transformer Pad TF300T Any version to Android 7.1 Nougat
[GUIDE/TUTORIAL/HOWTO] Asus Transformer Pad TF300T Stock to Android 7.1 Nougat with 2022 Bootloader unlock This detailed step-by-step guide helps you transform your Asus Transformer Pad TF300T with Android 4.2.1 to a powerful one with Android...
forum.xda-developers.com
On this Thread, the Step-by-step to install Katkiss is more accurate.
There are NO solutions including the tutorial above that's currently working for people who cannot Unlock Bootloader...
September of 2021
Screenshot of where I and others get stuck:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This part is a key note:
The year is 2021. Get the same network error that other people are getting while trying to use v7 or v8 of unlock tool. Tried other unlock tools. Tried Rooting. Tried delete user accounts. After using Kingroot / Kingoroot / and other "root" apps tried method of copying the modified DMClent app to replace the stock one... but will not copy new file even after being able to rename the original in the /root directory, Tried creating new user account, Tried factory reset, retried all the above in different orders. Registered on Asus. Tried again, and again. Researched more and tried their links. Tried unlock for other Asus Transformers that people says worked for their TF300T... NOTHING. Still get the network error and cannot unlock Bootloader to proceed.
Here is my reply from Asus:
So... Unless I'm wrong, I believe that unless somebody has some NEWER (Last 2 or 3 years?) custom unlock tool that simulates whatever Network response the tool(s) wants to unlock the Asus Transformer TF300T or some Brute Force unlock, or something then myself and everybody else that is stuck at the network error (Last 2 or 3 years?) cannot upgrade this device?
Thank you all... Look forward to some new news or even closure. It would be a shame to toss this nice tablet... I just need to get ANY Android version stock or custom higher than 4.2 because a lot of newer apps are requiring it
try with mitmproxy ( windows or linux). i unlocked the device last week. ( see in tf700 forum)
zebetti said:
try with mitmproxy ( windows or linux). i unlocked the device last week. ( see in tf700 forum)
Click to expand...
Click to collapse
Thanks, I will look into that as soon as I get a chance and respond my results.
im in the Same boad, i pulled my old tf300t out to hopefully turn into a kids tablet, the unlock tool is where i run tino problems, i see there is a post titled how to root in 2020 but it says to root with kingo root which i was unable to install, if anyone has the ability to put together a couple steps needed to unlock for the tf300t i would appreciate it or really any help as im lost RN
TYIA
I found my TF300t and would like to bring it back to life. Can someone send me a detailed guide to be able to use?

Categories

Resources