Database Users

Read BEFORE flashing!!

Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.

+sticky
excellent write up. a must-read for anyone even thinking about flashing

Original Post updated to add my information

bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.

STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App

Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.

bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App

This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky

Bump Bump Bump
Great Info

Updated original post with extra info.

Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.

Thanks, great info.

FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.

+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App

Moving this to the top. More questions in QA that can be helped by reading these tips first.

I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.

Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.

Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!

thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom

I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.

[Solved] Mystery bricked tablet. Black "android systems" screen

I bought an Acer a500 tablet a few days ago not knowing how broken it is.
After loads of research and attempting different techniques I still haven't had any progress.
The software issue:
When booting up the tablet, it goes to the black screen with "android system" at the top and power off/ shutting down in the middle of the screen.
Fixes I've tried:
1.
Since I don't know anything about what operating system is on this tablet, I have been blindly flashing different "stock" (from Vache) versions of HC.
--The android logo with gears shows up, the green bar loads but freezes when it gets 1 cm away from finishing.
--After turning off the tablet and booting it up again, "updating bootloader shows up on the upper left hand corner of the screen. Then a message pops up saying "apk installer: all pre processes complete". Then it returns to the black screen.
2.
The tablet will not go into apx mode (using the reset botton at the bottom).---Fixed. I didn't execute the steps properly. Apx mode works fine.
3.
I plugged the tablet into an older windows laptop and the computer could not install the correct drivers to sync with the tablet. Again also my lack of knowledge. I installed drivers from Acer.com
4.
These two guides seem to be exactly what my problem is but I can't seem to make sense of them:
http://forum.xda-developers.com/showthread.php?p=24531880#post24531880
http://forum.xda-developers.com/showthread.php?t=1572622
This is as far as I've gotten.
Other complications:
--The battery is dead. I have to use it while plugged in by the charger.
--Most of the thread that I have looked at use Megaupload as the source of downloading their files.
--The original owner of the tablet will not help me out. As I stated before, I don't know what version android OS was on here before it was bricked and on top of that the original owner won't answer my questions. As far as I know though, this tablet is not rooted or has anything "non-OEM" installed in it. The story goes that this tablet was bricked when the owner tried to "update" it. Before that, it was functioning perfectly.
-----It looks like Darvis is having the same issue and frustrations I'm having but reading his threads makes me think that this tablet is a dead end.
http://forum.xda-developers.com/showthread.php?t=1427983&page=4
http://www.androidtablets.net/forum...32467-please-help-me-unbrick-my-iconia-5.html
If someone could point me in the right direction toward fixing this tablet, I would appreciate it very much.
Thank you for reading my Thread.

KiwiN said:
http://forum.xda-developers.com/showthread.php?t=1572622
Click to expand...
Click to collapse
First off......I hope u didn't pay much for the tablet.
Secondly the guide above looks pretty straight forward but maybe this is one of the ones that has files at megaupload?
I know that the ra recovery and timmydean's files are accessible as I have downloaded both of them.
Maybe someone who has done this previously will chime in and get you the other file if it is indeed unreachable.
Sent from my A500 using xda premium

I would suggest trying to connect the tab to a Windows 7 PC after installing the USB drivers from ACER. Then check if your device appears in the device manager. As long as you have its UID you can flash the tab from the PC with one of the EUU tools - check my signature on "how to revert to 3.0.1" or TimmyDean's thread which offers an EUU with rooted HC 3.2.1 (it's linked in my thread as well).
How exactly did you try to get into APX mode?
p.s. I have the EUU files if you can't access them from the threads links. I can send them to you.

getting into apx mode
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
I'm trying to follow the instructions from the root 3.2.1 v4 file.
I can't perform the first step where it instructs me to turn on Usb debugging. The problem is that I can't open the settings by clicking the clock. Nothing happens.
I realize that one complication of my tab is that it will not charge. The battery power is below 15% so none of these fixes might not be effective for me. That might be the ultimate problem?
CyaN1de-
I paid $100 for the tablet. As of this moment I feel like I paid too much.
Thank you both for you quick replies. I have to say that most of the problems that I'm having is because of my lack of experience but I'm learning. I hope I fix this tab soon.

if this dont fix it, i'll give you what you paid for it;0
someone posted a while back that a hard reset fixed the android systems screen error
not sure where you're at now but no harm in trying it
Try using hard reset:
1) Turn off your tablet,
2) Rotation lock s to your left;
3) Press Vol+ (which is next to rotation lock) and power on simultaneously
4) As soon as the tablet vibrates you can release the power on button and you
should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.

Thanks for the suggestion but I didn't accomplish anything by hard resetting it. I've done this many times and nothing has changed.
I haven't given up on unbricking this tablet yet and even though it's frustrating I'm learning from the process. If I decide to sell it, I'll contact you Dibb.

KiwiN said:
.....
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
Click to expand...
Click to collapse
i've seen the 2 methods u described but i've not seen anyone else have success with it apart from the OP'ers - seems OTT to me but hey if it works for ya...
I've used timmydeans method ALOT on HC it never failed to work and that includes reverting back to HC from ICS - if it doesnt work for your issue then id be tempted to use blackthund3rs APXFlash Tool and civato's HC_ICS_Bootloader zip to flash a new bootloader and rom package on yr tab - but for the moment we'll run with td'sv4 - if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
as i said this is worth a go,,,,how about the update.zip have u tried that.....
else the only other way i know is apx flash....ya still need to get into apx
mode and if u cant then ???? sometimes youll try something over and over
and then out of the blue it will work...you'll swear you never did anything different , it jsut worked this time.....
hope you find some joy

Thanks Dibb for your words of wisdom. I've put it aside for now but I'm going to pick it up in the morning.

As addition to what dibb_nz said - Windows 7 would do the trick - I'm almost 100% sure you'll be able to connect in APX mode with the drivers properly installed. Then use one of the EUUs.
Drained battery really looks like the ultimate problem now because as far as I know you cannot charge the tab in APX mode - haven't tried that. Eventually I would suggest to crack the tab open, remove the battery and charge it somewhere - I don't know alternative ways but...may be another tab or you own charger with proper connector ...
http://www.youtube.com/watch?v=xvXihNIdQ1M
p.s. 15% power ... seems enough to flash through the PC...but who knows - don't waste them and get everything you need before starting the procedure.

no probs m8 hope u have better luck tomorrow
if u wanted to try the EC method i have those files if you want them
good luck m8

dibb_nz said:
if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
hope you find some joy
Click to expand...
Click to collapse
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.

KiwiN said:
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.
Click to expand...
Click to collapse
do u get on yr tab the big 'PASS' in white leetters or "entering download mode" at all???
think we're beyond update.zip if EUU failed but you can try it -
you can get to apx which is a start - getting a new boot/recovery image on there is the main priority I think...as i posted earlier i've only ever seen a fix for this problem work for 2 people, so on new ground here....
But anyway check out the APXFlash method/walkthru in my sig....all the info is in there and the links to the required files ....do we know if you're on HC or ICS B/L????

I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
dibb_nz said:
yes if you're talking about the stock roms from vaches thread, you need the full rom package - you cant just use an 'update' package as they need a full rom to work properly....
for instance my original HC3.2.1 Stock build is 7.014.15_COM_GEN1
and theres no FULL Rom for 3.2.1, so i have to use the HC 3.2 FULL instead
.....Acer_A500_7.006.03_COM_GEN1.zip
Once flashed, thankfully I recieve the 2 small OTA Updates to get up to 3.2.1 again
Another couple of days the ICS OTA d/l'ed and installed with no probs....
is that clearer or am i making things worse????
Click to expand...
Click to collapse
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.

KiwiN said:
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen.
Click to expand...
Click to collapse
I could never get mine into apx mode with the usb cable plugged in. So try that if you haven't. And it is literally hold reset, then press power, without letting up on the reset, release the power button after 3 seconds (use a watch or timer!) then one more second before you release the reset... It does work, but the timing has to be close. It must have a tenth of seconds or less tolerance. Very picky... I've done it on 2 different a500s so far and I am heading to do another tonight. If it doesn't work I'll be right back!!!

KiwiN said:
I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.
Click to expand...
Click to collapse
Hi m8 Hwya goin - just got home - what's the lay of the land???
Holey motley we just had a good shake....thort was gonna carry on thank fk it stooped, phew, just been awhile since we had one like that, scary
Crikey just as I finished typing "....land"
Back to more important matters..... whr u at m8????

None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?

KiwiN said:
None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?
Click to expand...
Click to collapse
recovery mode???
u need a new boot and recovery image on that thing
the HC EUU based flash arent working even tho u got a PASS on screen after TDv4
So HC based methods arent up to it. You need nvflash/fastboot.
We need ICS with the unlocked bootloader it has access to another level below where HC worked because HC b/l is and always has been locked down.
If ICS cant fix it, I have no idea what will and my offer to buy is off the table!!!!
check out civatos guide and ready yourself for nvflash via zip files in that post or blackthund3rs APXflash tool, with a complete tutorial for using it, all links in my sig.
good luck

Just to chime in with a tip on getting google drivers to work.
When getting any device not recognized, or driver error, generally I go into windows device manager, select the unknown or offending device, update driver, only I choose which driver to use, and ignore the error message where it says "may not be compatible with your device", and use it anyhow.
I get that occassionally when swapping back and forth between devices.
Also, battery not charging and display errors, are usually a sign of EC Power control. So you were on the right track about that. Once you get a rom up and running, if the batt don't charge, then there are some EC flash's you can do from CWM.

Back at it again using BT's nvflash tool. And tablet is still bricked.
I've tried a few different bundles and none allow me to operate the tablet. Everything goes smoothly and I get "pass" at the end of the process. When I go to reboot the tablet, it gets stuck at the black start up screen.
Found another lead: http://forum.xda-developers.com/showthread.php?t=1579490
Sounds like he was in the same situation as I am but has a bit more skills and knowledge dealing with problem solving.

You say you were able to flash roms. So apparently recovery is working OK. Have you tried flashing civato's flexreaper? It has code that will detect whether you bootloader is HC or ICS. You may just be flashing a rom that doesn't match your bootloader... I know I'm jumping into the middle of this, but it's just a thought.
Also, when you did the hardware reset with the rotation lock switch did you get the confirmation that it was, in fact, being wiped?
Failing all that, I'd be willing to take it off your hands for spare parts...
Sent from my A500 using Tapatalk 2

[Q] Root Question

Hello,
I have read on the forum that the bootloader is unlocked.
And that therefore it is rooted base.
or there is t he a manipulation done to the root.
good day

pci130 said:
Hello,
I have read on the forum that the bootloader is unlocked.
And that therefore it is rooted base.
or there is t he a manipulation done to the root.
good day
Click to expand...
Click to collapse
Hi dude now i have the device i don't know how to root it due to the incompatibility with the usb plug in the pc
If we can make the mojo visible by the pc i think it will be really easy to root but now it's not possible so
i'm trying to make a signed zip with root enable based on the 110 firmware.zip

Yes, Mad Catz provided the actually firmware for the M.O.J.O, and in theory, it should be possible to pre root it and flash this thing.
But atm, the only known way to flash the firmware is the update tool on the device.
You can boot into the recovery, but only to the "lying android with exclamation mark". Haven't found a way to enter the recovery menu.
If your flash goes wrong, the recovery would be the only way to bring the device back in a working condition.
Rebooting to the bootloader didn't seem to work. Since the device has no external buttons to enter the mode. You can't even boot into a custom recovery to flash unsigned code.
I don't belive, that you can one of the external USB ports set from host to slave and that it will survive a reboot to access the device in recovery or bootloader.
They say, that the bootloader is open. But no one has provided any evidence about it.
Maybe you can catch the USB slave signal direct on the mainboard. But that would never be an option most would consider.
The device is advertised as "hacking friendly".
From Mad Catz side, till today there isn't released any documentation or tool to make it real.
Even the sourcecode of the device software isn't official released.
I really hope the things change to better in the next weeks.

scorpio16v said:
Yes, Mad Catz provided the actually firmware for the M.O.J.O, and in theory, it should be possible to pre root it and flash this thing.
But atm, the only known way to flash the firmware is the update tool on the device.
You can boot into the recovery, but only to the "lying android with exclamation mark". Haven't found a way to enter the recovery menu.
If your flash goes wrong, the recovery would be the only way to bring the device back in a working condition.
Rebooting to the bootloader didn't seem to work. Since the device has no external buttons to enter the mode. You can't even boot into a custom recovery to flash unsigned code.
I don't belive, that you can one of the external USB ports set from host to slave and that it will survive a reboot to access the device in recovery or bootloader.
They say, that the bootloader is open. But no one has provided any evidence about it.
Maybe you can catch the USB slave signal direct on the mainboard. But that would never be an option most would consider.
The device is advertised as "hacking friendly".
From Mad Catz side, till today there isn't released any documentation or tool to make it real.
Even the sourcecode of the device software isn't official released.
I really hope the things change to better in the next weeks.
Click to expand...
Click to collapse
Hum this is what i expected. I tried to plug the controler via usb and it's work so it's a possible way to boot into recovery by holding button of it
It's a shame to said that the mojo is unlocked but impossible to have usb adb !!!! Mad Catz your device have been released the 10 december and the playstore have maybe 1000 app compatible ( yes i know you gonna said this is because the device doesn't have screen but if you faked a hd screen it will simple work and i'm sure if 'im rooted i can do it ) and you doens't provided a keymapper so the one or 2 playable game aren't mapped correctly !!!!
I hope that a little genius can find a solution to root it but mad catz need to work on the firmware !!

Dead-neM said:
It's a shame to said that the mojo is unlocked but impossible to have usb adb !!!!
Click to expand...
Click to collapse
ADB access isn't a real problem, because we can connect over network. But bootloader and the fastboot tool needs definitely USB.
No, the worst thing is, that even via ADB, you can't get temorary root access. So, you can't even remount /system partition as writable.
Don't know if anyone with one of the older firmware versions on their M.O.J.O have tried if a remount of /system would work.

Not familiar with the root process but can something like was done for OUYA be used here?

Unfortunately no.
The M.o.j.o can't even get root and mount the /system partition over ADB. So, no chance.

cm 12.1 rom is fine but "System UI has crashed" ;-;

My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS

wifiwitch987 said:
My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS
Click to expand...
Click to collapse
I think first I'd replace the PC. If that's not practical, try to boot it to this .iso once you've burned it to CD:
http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso
Download the recovery.img to root's home, connect to the MOJO and turn it on, open a terminal and issue:
# fastboot -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
Should boot the MOJO into the recovery. If you can't get your PC to boot properly I think you're OOL. You might look into getting a used PC, one that's out-of-date or simply has a bad (or no) HDD, that you can pick up cheap, and use this simple Linux distro (Puppy Linux it is, with fastboot and adb binaries installed by me) for an OS. But be careful, Linux is addictive, and you may find yourself in the same predicament as I am: losing patience with the bloated domineering Windows OS.

Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude

wifiwitch987 said:
Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude
Click to expand...
Click to collapse
You can flash this (or most other linux live-CD .iso files) to a USB drive with a utility called Unetbootin. IIRC it's available for Windows, Mac, or Linux. I have no idea whether your Alpha is capable of booting to it, though. Any chance of borrowing another PC, maybe one a bit more traditional? Your little brother's old slow laptop maybe? FWIW I just finally managed to get fastboot and adb working on a Chromebook with an ARMv7 processor, but I doubt you want to go through that much work. Does the Alpha have an Intel processor?

How I Rooted Walmart Onn Tablets (No TWRP Needed)

I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time

I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.

Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse

Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!

Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please

CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too

mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.

CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.

EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!

byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it

CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.

no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.

Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.

'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that

KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?

I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.

will this root onn 8 inch tablet running android 9

soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.

installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes

when you mean patch boot img do mean to unzip file on onn 8