Hi all,
As you might already know, MediaPad touchscreen is kinda noisy. You can't get a simple touch consistently, because sometimes it will be recognized as a swipe. And when you put your finger down for sometimes, the touchscreen will start moving by itself. That makes it harder for precise finger work.
So I was thinking to implement some kind of filtering to reduce touchscreen noise. The result is quite good in my experience. No more tap misrecognized as a swipe. Touchscreen is still when holding finger down. Now I have one less reason to dislike my wife's MediaPad.
I'm sharing the boot.img I've built using HWMOD C232B005 boot.img as a base. Those who interrested can flash it using fastboot:
Code:
fastboot flash boot boot.img
boot.img:
http://www.mediafire.com/?qanekyco31c0a3e
Source:
http://github.com/arkusuma/mediapad-kernel-ics
Update:
Because this filtering thing is kinda subjective, I modify the driver to export filtering parameters to user. The parameters can be accessed from inside /sys/t1320 directory:
filter_radius only do filtering for samples inside filter radius. (default: 40 pixels = 95)
touch_thres minimum movement before a touch will be considered as a swipe, increase this value if you still have unrecognized tap. (default: 4 pixels = 9)
swipe_thres minimum movement between swipe. (default: 1 pixel = 3)
min_sample minimum sample that should be collected before filtering begin. (default: 5)
sample_size maximum sample that should be kept in history. (default: 10)
filter_radius, touch_thres, and swipe_thres are specified in touchscreen unit, that is 2.365 per pixel. (e.g filter radius of 100 pixels is 236).
Modifying these parameters can be done via console, for example:
Code:
echo 2365 > /sys/t1320/filter_radius
echo 12 > /sys/t1320//touch_thres
Feel free to experiments. And please share your findings about the best values for you.
Credits: hwmod & after_silence for their attempt on hacking MediaPad ICS kernel
Regards
support o/c ??
Nope, this is plain from Huawei source.
really nice, it is a great improvement!! the touch is not "jumpy" anymore, thanks a lot for this patch
I can not flash it, when I hold power+volume down, I get this text: "Enter into fastboot mode, press power for 10 seconds to reboot", and when I try to flash it I got "waiting for device" in fastboot CLI.....what drivers I have to install? I have installed HiSuite from virtual CD ROM on mediapad
441Excelsior said:
I can not flash it, when I hold power+volume down, I get this text: "Enter into fastboot mode, press power for 10 seconds to reboot", and when I try to flash it I got "waiting for device" in fastboot CLI.....what drivers I have to install? I have installed HiSuite from virtual CD ROM on mediapad
Click to expand...
Click to collapse
Have you turn on Fast boot in ICS Settings? Driver for fastboot supposedly installed automatically from Windows Update. If not, try replugging the USB cable while on fastboot menu. (But I'm not sure, I don't use Windows for this)
i have fastboot OFF in settings, Have I to enable it?
441Excelsior said:
i have fastboot OFF in settings, Have I to enable it?
Click to expand...
Click to collapse
Yes, please try enabling it. And reboot into fastboot menu.
when I enabled it and tried to boot into fastboot, device booted into OS very fast, it looks like hibernation mode
441Excelsior said:
when I enabled it and tried to boot into fastboot, device booted into OS very fast, it looks like hibernation mode
Click to expand...
Click to collapse
While inside OS, press the power button until a popup appear with Shutdown and Restart options. Press the volume down button (the one near the power button) while selecting Reboot. Keep pressing the volume down button until you enter fastboot.
problem was that I was missing files "AdbWinApi.dll" and "AdbWinUsbApi.dll" in same directory with fastboot.exe, now it is working, thanks for fix
after flashing this, it System information, it says Kernel-version "unavailable". Does that mean I run your boot image? The touch behavior seems better but this could be just imagination
taronas said:
after flashing this, it System information, it says Kernel-version "unavailable". Does that mean I run your boot image? The touch behavior seems better but this could be just imagination
Click to expand...
Click to collapse
Yes it seems so. Try pinch zooming a website, hold it for a while, and pinch zoom again. You'll see the difference
arkusuma said:
Yes it seems so. Try pinch zooming a website, hold it for a while, and pinch zoom again. You'll see the difference
Click to expand...
Click to collapse
Installed a multitouch tester and saw the difference immediately. It tells me touch point size is 7px now instead of 2, will see whether this is small enough to not cause issues.
thank you!
Great that here is still someone alive from developers
Great job! Using it myself and it really helps a lot.
arkusuma, may be you can make a commit with a patch to my github sources? I wish to unite all developers to work on one version of cm9 for mediapad to make it perfect.
Oh, ok, i see that you have uploaded your patches to your github.
can you make also fix for light sensor bug? (unable to auto decrease brightness, only auto increase works)
Had two reboots since flashing. Could be coincidence, or not.
Is there a kmsg_last on the device? where to find it?
after_silence said:
arkusuma, may be you can make a commit with a patch to my github sources? I wish to unite all developers to work on one version of cm9 for mediapad to make it perfect.
Oh, ok, i see that you have uploaded your patches to your github.
Click to expand...
Click to collapse
Hi, I've create a pull request to your repo on Github for this patch.
Related
I would like to give credit to everyone who has worked on the android roms, and other guides. I have taken some of the info for this guide from the WIKI
It seemed we were due for a friendly how to guide on how to load a NAND rom on a RHOD device. I decided to write a step by step guide to help people out. This guide does provide a very basic ADB setup, but it is just enough to get you up and running. If you want to do advanced things you should get the full ADB, and learn more about it.
This guide is written for a RHOD400, Android GBX0*+3.4.26 rom, and a Win7 pc, but should be almost identical for the rest of the RHOD family, other versions of Windows, and most other roms.
It is assumed that you have unlocked your phone for custom rom loading in the past at some point. This is not the same as unlocking the sim card. This is 100% required. Please read here and/or here, and/or here if you need help with unlocking your phone.
This guide assumes that you know what a command prompt is, how to load windows drivers for a device, and can open zip files. If these things are not within your skill sets I would recommend that you find someone who understands these things to assist you.
Things you need.
1. A RHOD phone.
2. A micro SD card that is at least 512mb in size.
Tip: I suggest a sd card that is less than 4gb in size. There tends to be less compatibility issues with non SDHC cards. SDHC cards usually work, but if you have trouble this is a good thing to change. The SD card does have to be less than 64gb in size as the phone can not read cards larger than 32gb.
3. A usb based micro sd card reader. A usb based card reader is need to be compatible with the HP format tool. Some built in ones are usb based others are not. If you have one, you can try it and see if it works. It is not recommended to use your phone's sd card reader for prep work.
4. A usb cable that is known to work. Test it in WM first. On rare occasion I have seen cables that did work with WM and not Android. If you have issues, this is also something good to swap out during trouble shooting.
5. A windows based pc. *DO NOT USE USB 3.0 PORTS* Many reports about have come in about them causing issues.
The procedure.
1. Back up anything you want to keep from your phone. Everything on the phone will be wiped during this process.
2. Put the micro sd card into your USB card reader and format with the HP format tool. It needs to be a full fat32 format. Windows format is known to have issues on occasion, and this step is a work around for that problem. It is not 100% required, but if you have trouble it is 100% required during trouble shooting.
3. While this is formatting you can download the recovery (recovery_cwr_6.0.1.3.img) ***It has been found that the 6.0.1.3 recovery does not make backups correctly, resulting in md5 errors. You may use it if you are not planning on using the backup feature, or the older one by acl works fine. You can rename it to use the included scripts if you wish.***, rom (GBX0*+3.4.26 Full) , the boot loader, the needed usb android drivers, and the adb files.Gapps is optional.
4. Make sure your battery is at least 50% charged. I recommend a 100% charge. A dead battery in the middle of flashing can brick your phone.
5. Copy the RHODIMG.NBH, rom (GBX0*+3.4.26 Full), and the gapps (optional) files to the sd card and put it in your phone with the phone turned off.
6. Press the hold down the volume down button while pressing the power button. This will bring up the tri colored screen. It will then automatically go to the white rom update screen.
7. Follow the directions (press the power button on the RHOD400) to start the update. This should take less than 1min.
Troubleshooting tip:
If the phone sits at loading 0%, and never moves after 10 min you may not have unlocked your phone or there is an issue with your RHODIMG file. Verify that you have unlocked your phone (you can try loading a WM custom rom), format the SD card, re-download the RHODIMG file, and try again. Also try another SD card and SD card reader.
8. If the phone reboots automatically, that is fine. Otherwise when the phone says Update Success you can pull the battery to shut it off.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
11. Install the USB/fastboot driver for the phone. On Win 7 the phone showed initially as android device under other folder in the device manager. After the driver is installed it should be called My HTC.
12. Open the ADB Tools zip file, and put the platform-tools folder on c:\
13. Open a command prompt and go to c:\platform-tools\.
Once there type:
Code:
fastboot devices
You should get a response similar to this:
C:\platform-tools>fastboot devices
HT04TM300704 fastboot
If this is not working stop now and troubleshoot.
14. Now to wipe the phone in prep for loading (or reloading) the android rom.
There is a wipe.bat file I have included. You may run it, or you may type the following commands.
Code:
Fastboot erase recovery
Fastboot erase boot
Fastboot erase misc
Fastboot erase system
Fastboot erase userdata
Fastboot erase cache
15. Place the recovery (recovery_cwr_6.0.1.3.img) file into c:\platform-tools.
16. Now load the recovery image. If it is named recovery_cwr_6.0.1.3.img you may use the reload_recovery.bat or type:
Code:
fastboot flash recovery recovery_cwr_6.0.1.3.img
to load the recovery image then
Code:
fastboot boot recovery_cwr_6.0.1.3.img
to boot the recovery image.
17. Install the rom.
Using the volume keys highlight 'Install zip from sdcard' then press the call button to select it.
Highlight 'choose zip from sdcard' and press the call button to select it.
Highlight the rom file (GBX_3.4.26_Full.zip) and press the call button to select it.
Highlight yes and press the call button to select it.
The rom will now install. This will take a few minutes.
18. (optional) Install Gapps.
Using the volume keys highlight 'Install zip from sdcard' then press the call button to select it.
Highlight 'choose zip from sdcard' and press the call button to select it.
Highlight the gapps file (probably gapps-gb-20110828-signed.zip) and press the call button to select it.
Highlight yes and press the call button to select it.
Gapps will now install. This will take a few minutes.
19. Press the back arrow, and select reboot system now.
The phone should reboot into the Android rom now. It will take about 10min the first time. If you have waited more than 30 something has gone wrong. You should troubleshoot and try again.
At this point you have the basics all in place, and can start using your phone.
If you want to do basic ADB tasks (along the lines of installing apps remotely/side loading or pushing/pulling files) you will need to install the adb windows driver.
20. Press the thanks button if you liked this guide.
P.S.
If you have issues getting adb to work later, download and use USBDeview.exe to remove the HTC driver entries and then install pdanet for android to get the correct adb drivers installed.
So is my RHOD500 not supported by this Rom ?
denva said:
So is my RHOD500 not supported by this Rom ?
Click to expand...
Click to collapse
This is a guide, not a rom...
wizardknight said:
This is a guide, not a rom...
Click to expand...
Click to collapse
I know Is a guide . But need to know why my device keeps restarting at startup :crying:
denva said:
I know Is a guide .
Click to expand...
Click to collapse
Then why ask if your phone is supported by this rom?
denva said:
But need to know why my device keeps restarting at startup :crying:
Click to expand...
Click to collapse
Well if you have not listed all your trouble shooting steps, you will not get help from anyone. Our physic abilities are lacking these days.
Also posting specific questions in the thread about the rom you are trying to install will have a higher chance of getting useful feedback.
wizardknight said:
Then why ask if your phone is supported by this rom?
Well if you have not listed all your trouble shooting steps, you will not get help from anyone. Our physic abilities are lacking these days.
Also posting specific questions in the thread about the rom you are trying to install will have a higher chance of getting useful feedback.
Click to expand...
Click to collapse
Am refering you to this thread HERE av done all necessary things but still i get my device rebooting
http://forum.xda-developers.com/showthread.php?t=870081
denva said:
Am refering you to this thread HERE av done all necessary things but still i get my device rebooting
http://forum.xda-developers.com/showthread.php?t=870081
Click to expand...
Click to collapse
Well if you have done all necessary things, then your phone must not be compabtiable.
Maybe if you provided a list of your troubleshooting steps we might be of more help... Otherwise we have no choice, but to bow to your knowlage of having done all necessary things.
wizardknight said:
Well if you have done all necessary things, then your phone must not be compabtiable.
Maybe if you provided a list of your troubleshooting steps we might be of more help... Otherwise we have no choice, but to bow to your knowlage of having done all necessary things.
Click to expand...
Click to collapse
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
denva said:
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
Click to expand...
Click to collapse
Ok. I see the standard steps outlined in the guide that you have done. Now what troubleshooting have you done?
denva said:
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
Click to expand...
Click to collapse
Sounds like you just need to flash CWM... the CWM recovery image doesn't go on your SD card, you flash that from your computer using the "fastboot flash" command...
You can also try "fastboot boot <recovery.img>" - w/o the < >. Remember, this is done on your computer. That's why you need the fastboot drivers...
arrrghhh said:
Sounds like you just need to flash CWM... the CWM recovery image doesn't go on your SD card, you flash that from your computer using the "fastboot flash" command...
You can also try "fastboot boot <recovery.img>" - w/o the < >. Remember, this is done on your computer. That's why you need the fastboot drivers...
Click to expand...
Click to collapse
Ok Can you guide me how to do this on the P.C. ?
denva said:
Ok Can you guide me how to do this on the P.C. ?
Click to expand...
Click to collapse
It's in the guide, is it not...? Please read the guide. It walks you through everything necessary...
Edit - following the guide, you should be on step 9 at this point. Please continue with the guide.
arrrghhh said:
It's in the guide, is it not...? Please read the guide. It walks you through everything necessary...
Edit - following the guide, you should be on step 9 at this point. Please continue with the guide.
Click to expand...
Click to collapse
You Mean This .
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
My Phone doesn't bring this window
denva said:
You Mean This .
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
My Phone doesn't bring this window
Click to expand...
Click to collapse
You described this screen (scrolling text, blue background?) I remember you said you got it to fastboot, no?
Where is your phone getting to?
edit: nevermind fiddled with it, dont know what i did but it worked
I have a rhod400. I have been messing with OMGB as my daily phone OS since July 2012 and just installed this one about a week ago.
I have two questions/issues
1) Every time I try to reboot, it freezes. When I try to power off, it sometimes freezes, but usually reboots.
2) I can't seem to make persistent changes to the hosts file. After every reboot, it's set to the same old generic "127.0.0.1 localhost"
During boot, does the OS unpack a .img or something with the hosts file packed inside it? If so, where is it?
Thanks, guys. Other than these 2 issues, this flavor of android for rhodium is pretty solid. i like it.
jdoggsc said:
I have a rhod400. I have been messing with OMGB as my daily phone OS since July 2012 and just installed this one about a week ago.
I have two questions/issues
1) Every time I try to reboot, it freezes. When I try to power off, it sometimes freezes, but usually reboots.
2) I can't seem to make persistent changes to the hosts file. After every reboot, it's set to the same old generic "127.0.0.1 localhost"
During boot, does the OS unpack a .img or something with the hosts file packed inside it? If so, where is it?
Thanks, guys. Other than these 2 issues, this flavor of android for rhodium is pretty solid. i like it.
Click to expand...
Click to collapse
Please put rom specific questions in that rom's thread.
If you are running a newer than.27 kernel the reboot and power off functions do not work properly in any rom.
I believe that the host file is overwritten by the ram disk/boot.img on boot every time. Any changes will not stick.
There is a chance these issues may be fixed on the next release of GBX, but no promises.
arrrghhh said:
You described this screen (scrolling text, blue background?) I remember you said you got it to fastboot, no?
Where is your phone getting to?
Click to expand...
Click to collapse
My Device always restarting after passing through all the tutorials
denva said:
My Device always restarting after passing through all the tutorials
Click to expand...
Click to collapse
This isn't enough information to help you.
If you're not going to provide detailed information on what is happening, no one will be able to help you.
Perhaps NAND is not for your device. Flash back to WinMo.
arrrghhh said:
This isn't enough information to help you.
If you're not going to provide detailed information on what is happening, no one will be able to help you.
Perhaps NAND is not for your device. Flash back to WinMo.
Click to expand...
Click to collapse
Yeah sir i think so , bcz av search all ova the net only rhod400 is ok
Unlucky for rhod500 am waiting maybe nxt update
anyway thank you arrrghh and wizardknight for your help :good:
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
knismaps said:
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
Click to expand...
Click to collapse
why do you want to enter the bootloader? and have they made any roms or cwm recovery for these types of generic android tablets?
[RESOLVED] finally, ROOT for Neutab N7 pro tablet.
knismaps said:
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
Click to expand...
Click to collapse
Having been looking for this information myself i'm sharing real quick here what i've found. Scouring the net all over i've found NOTHING specific for these Chinese tablets but after finally getting on the scent of VROOT I downloaded and tried iROOT essentially a one-click rooter the .APK **DID NOT WORK** but the PC version **DID** can be found by googling iroot or vroot.
RE: bootloader, i've still found no way or any good info on entering the bootloader AFAIK this is locked and may not be possible without some good hard hacking on the firmware, I DO KNOW that if you try entering the "bootloader" with a reboot manager on the device u will find yourself at the "NeuTab" welcome screen and stuck. Fortunately at least in my experience, letting the tablet battery run down low you can boot back into it and root condition is still good.
Hope this helps somewhat I know its an old post but a lot of people have been looking for this info have yet to post on authors site confirming that the NeuTab also works with his software.
peace.
VE3UND
BTW I forgot to mention the site and the software (ALTHOUGH IT STATES OTHERWISE) is in Chinese. A leap of faith needed there I know but i confirm this method works. l8z
BTW^2 ALSO the android version was KitKat as received from the mfg, also have been told that Jellybean will install on the tablet after rooting and maybe is now included with device but don't quote me on that.
all in all a really nice tab for the price, especially now we have root biggest missing option: GPS but you can tether to another device with gps if you need to. Also no built in USB HOST MODE. //out
I've got the NeuTab N10 and can't get ADB to see it at all. How did you get ADB to work with your N7, were you able to find NeuTab ADB drivers somewhere?
So i recently came across this tablet in my stuff... something i picked up for the wife a few years back.
I also came across this website.... http://neutab.com/info-detail.php?InfoId=11
It has all the tools and programs that the company uses. includes all files for development of their entire line of tablets.
Thought this may be useful. just click on the link that says pheonixtools.zip and it will take you to a back end file server... This tablet is about as open sourced as it gets... so... this leads me to ask a question i have been struggling with for the last 2 years of being a member on this website...
can anyone... please... help me develop my first recovery and custom rom for this tablet? I just have never done it all the way... i have set up a couple things here and there... figured out how to strip the stock recovery and boot... but never got further than that.
Thanks for the help.
• Unzip phoenix tool.zip you just downloaded; (to open a .zip file, download WinRAR)
• In the folder of phoenix tool you just unzipped, depending on your system specs, select "drvinstaller_X64", "drvinstaller_x86" or "drvinstaller_IA64" to install tablet driver; Or you can run all three driver installer and at least one will work;
• Run "PhoenixSuit.exe", select "firmware" tab;
• Click on "Image" button, choose the firmware you just downloaded;
• Turn your tablet completely off (by press and hold power button for 20 seconds), press and hold "volume -" button, connect tablet to computer via usb cable, keep volume button held, press power button 10 times repeatedly；
• The phoenix tool should recognize the tablet. On pop-up dialog window, select if you want to format and wipe out everything on your tablet；
• The phoenix tool will start flash the firmware to the tablet. Wait till it is done；
• When upgrade is finished, disconnect your tablet from computer, press and hold power button for 10 seconds to quit upgrade mode. then press and hold power button for 2-4 seconds to turn tablet on；
Congratulations! Your tablet is now refreshed.
Ok so I have a NueTab Air 7 Android and I have talked toto their customer support which did neurologist absolutely no good. I have been trying to hard reset my tablet and do a factory reset by holding down the volume up and down keys and the power keys until it gives me the option of rebooting. However, there is no option for a factory reset. Only a Recovery mode, Fastboot mode, and Normal mode. I tired the Normal and Recovery an both sent me back to enter password that I can't rremember, which isthe why I'm resetting it lol. Finally I chose the Fastboot option and now it is stuck on that option and has been for almost an hour. It willwas not let me power off, try to hard reset, it is literally stuck. And it is a hundred percent charged. I do jot hav the optiontime to connectbe the tablet to acall Windows computer at this timetime, as the forums I have read say can possibly fix the issue. And what a surprise the customer service phone number for this specific tablet does not know how to fix it!!!!! Not surprised at all. If anyone at allthe has any ideas or knows what to do or howsomething to fix it please help meme. I'm very frustrated to say thethat least and in desperate need of help. Anything would be immensely appreciated. ~Melissa
How to identify the exact firmware of the N7 after this page (Oficial NEUTAB), I have 3 options but that IMEI series is nowhere in the table.
---------- Post added at 11:35 PM ---------- Previous post was at 11:35 PM ----------
this page http://neutab.com/info-detail.php?InfoId=11
n7s root
therealtaynak said:
So i recently came across this tablet in my stuff... something i picked up for the wife a few years back.
I also came across this website.... http://neutab.com/info-detail.php?InfoId=11
It has all the tools and programs that the company uses. includes all files for development of their entire line of tablets.
Thought this may be useful. just click on the link that says pheonixtools.zip and it will take you to a back end file server... This tablet is about as open sourced as it gets... so... this leads me to ask a question i have been struggling with for the last 2 years of being a member on this website...
can anyone... please... help me develop my first recovery and custom rom for this tablet? I just have never done it all the way... i have set up a couple things here and there... figured out how to strip the stock recovery and boot... but never got further than that.
Thanks for the help.
Click to expand...
Click to collapse
I would love to root this tablet purely because it's my daughter's and some of the games she likes has some real funky permissions That they want! A custom rom would be nice but I will be satisfied with being able to revoke some of the permissions that the apps want to have access to.
n7s software download issue
therealtaynak said:
• Unzip phoenix tool.zip you just downloaded; (to open a .zip file, download WinRAR)
• In the folder of phoenix tool you just unzipped, depending on your system specs, select "drvinstaller_X64", "drvinstaller_x86" or "drvinstaller_IA64" to install tablet driver; Or you can run all three driver installer and at least one will work;
• Run "PhoenixSuit.exe", select "firmware" tab;
• Click on "Image" button, choose the firmware you just downloaded;
• Turn your tablet completely off (by press and hold power button for 20 seconds), press and hold "volume -" button, connect tablet to computer via usb cable, keep volume button held, press power button 10 times repeatedly；
• The phoenix tool should recognize the tablet. On pop-up dialog window, select if you want to format and wipe out everything on your tablet；
• The phoenix tool will start flash the firmware to the tablet. Wait till it is done；
• When upgrade is finished, disconnect your tablet from computer, press and hold power button for 10 seconds to quit upgrade mode. then press and hold power button for 2-4 seconds to turn tablet on；
Congratulations! Your tablet is now refreshed.
Click to expand...
Click to collapse
I have yet to be able to download the zip or the firmware software. i got root with kingo pc version but that's pretty much it and I can't change the route manager because once I delete that then I don't have root anymore and can't add another one. Also I have yet to been able to get into or see download mode on this either. It just stays on the screen with the name on it and that's pretty much it. no bootloader unlock either
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Conrad-007 said:
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Click to expand...
Click to collapse
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
aicjofs said:
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
Click to expand...
Click to collapse
Thanks for your reply, aicjofs.
In my case it happens always, no matter if charging or not... and it's annoying.
Would rooting and installing a custom ROM solve the problem? If yes, is there a custom ROM dedicated to kids, similar with the stock one?
Conrad
Wrong Section Buddy !!!
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
and why ???
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
:thumbdown:
Ignore this guy. I have a friend with the same power on issue with her Nabi 2, and I'm interested to read the solution here.
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Conrad-007 said:
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Click to expand...
Click to collapse
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Conrad-007 said:
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Click to expand...
Click to collapse
The latest TWRP should have a section under the wipe menu where you can repair the file system which is probably easiest, although you need to be careful what you are doing in there as it is called the "wipe" tab for a reason. Should be able to go to wipe menu, select data partition checkbox, select change or repair filesystem(don't swipe to wipe, click the words check/repair etc) and select check in the next screen.
To do a filesystem check the partition can not be mounted so you do it from recovery not in Android. Since stock recovery you can't use ADB you pretty much need TWRP one way or another.
If you don't want to use the graphical interface in TWRP you can do it over USB with ADB and use e2fsck on the partitions after unmounting them, but it's going to be doing the same thing you will just see a more verbose version if you do it over adb.
Thanks a lot, aicjofs.
I will try to root and install first TWRP, as my Nabi is still untouched.
One thing I remarked: at the moment, when I go in the (stock) recovery and want to do a "Wipe data/factory reset", 2 lines are displayed before "-- Wipping data...": "E: missing bitmap stage_empty (Code -l)" and "E:missing bitmap stage_fill (Code -l)". After that, the wiping process seems to run normal, as I get the message "Data wipe complete." at the end.
Do you know what that lines are meaning? Could those lines help to debug the main problem ?
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Conrad-007 said:
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Click to expand...
Click to collapse
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Conrad-007 said:
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Click to expand...
Click to collapse
I dont have Nabi2's anymore but both my kids tablets did the same thing. I never really found a solution. I did buy a cable from Nabi store that has the orange braid covering. It seemed to make a difference, but it still happened from time to time.
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
... aicjofs, please... help
Conrad-007 said:
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
Click to expand...
Click to collapse
You can't repair the partition table from adb/TWRP. It's read only. You could through nvflash but I don't think the partition table could possibly cause the issue. I think you are meaning fix super blocks and inodes of the filesystem? Even that is a stretch if it's happening how you describe it but with a try. Did you try repair filesystem like we talked about earlier? If not backup all the data and try a wipe data. That will make sure to blow away and reformat the data partition.
It could be hardware. I know for sure the charging system causes it when plugged in but not about the first boot stuff or when it's not charging.
Thank you aicjofs for your answer,
yes, I did attempt to repair the system, data, cache and it was successfully. I did it several times. I also wiped everything a few times and installed the Nabixus ROM afterwards. Nothing helped. It's like the operating system needs to "get warm" somehow, because I have to try to power on the system many times, until I get it work... but after that, if the Nabi goes in standby, I have to start the whole thing over
How can I check for damaged blocks, etc.? If I can do it and find some, could they be marked as "bad" and isolated? Would it make sense?
I m able to got call but I can't see anything on screen it is just 1 month old....what to do now?? I see some scratch...
You rooted? Or like DarkAlpha.Sete asks:
DarkAlpha.Sete said:
What did you do before it stopped working?
(Did you make an update, tried unlocking bootloader, installing a custom recovery or custom ROM?)
Click to expand...
Click to collapse
If there's something that you are modifying, this could introduce bugs.. if you are stock unrooted, and if you can get download mode booted, just plug it into your pc and flash stock again.. moto I'm not as familiar with versus samsung, but I'm sure you can flash stock
sj
Sent from my rooted SM-G920P on stock Nougat 7.0 using [email protected] Pro
ZeroVirus said:
I m able to got call but I can't see anything on screen it is just 1 month old....what to do now?? I see some scratch...
Click to expand...
Click to collapse
What did you do before it stopped working?
(Did you make an update, tried unlocking bootloader, installing a custom recovery or custom ROM?)
No it's comes out from my pocket
ZeroVirus said:
No it's comes out from my pocket
Click to expand...
Click to collapse
Sorry but I don't understand what you mean by "it comes out from my pocket". Could you please explain in another way?
Also can you enter download/fastboot mode? Press and hold the power button and volume up(or down, I don't know what is your device) to enter it.
I see clear crack on LCD...i feel vibrate but I can't see anything
ZeroVirus said:
I see clear crack on LCD...i feel vibrate but I can't see anything
Click to expand...
Click to collapse
Well, sorry if I am wrong, but if you have a clear crack, and you don't see anything when you turn it on(but it vibrates), probably the problem is the LCD.
You can try following the steps that I wrote to enter fastboot. If you can enter it and make the last step show the serial number, but still don't see anything on the screen, then there is a high chance that the problem is the LCD.
Firstly, install the ADB and Fastboot drivers (if you already have them, skip this). The easiest method I know to install them is by using this installer
Make sure the device is powered off(holding power button by around 15 seconds should force a shut down if it is on)
Hold power button and volume down key to enter fastboot (or try?) until it vibrates
Now, connect the device to your PC with an USB cable
On the folder where you have the drivers, open a command window. (Shift + Right Click, then "Open command window here")
Type
Code:
fastboot devices
If a serial number is printed, then, the problem is the screen and not the device itself
I have attached a screenshot with an example(my device output).
If this doesn't work, then I'm sorry but I don't know much more to do.
I say again: I'm not any professional, all of this is my knowledge... I can be wrong
ZeroVirus said:
I m able to got call but I can't see anything on screen it is just 1 month old....what to do now?? I see some scratch...
Click to expand...
Click to collapse
Did what I said worked? You didn't reply for a long time...
Im hoping Im posting in the correct area for this and that someone will catch this and know how to help me out....
I have a Rand McNally OverDryve 8 Pro, OD8Pro, that I would like to extract the boot.img file from the stock ROM so that I can use it to install seemless Magisk.
My issue is that i cannot obtain the boot.img without TWRP or existing root access. There is currently no build of TWRP available for this device obviously because its kind of a neiche device, though very good.
Does anyone know of any guarunteed way of extracting the boot.img file from an Android 5.1.1 device with any other way?
I;'ve tried a bit of basic adb commands, but without being able to open shell command with existing su privilage I get access denied when trying to copy out a /dev/block/... with cat or dd commands.
I can get into fastboot mode, but nothing helpful there as fastboot is only remove and write commands mostly and cant read/copy as far as I'm aware, not without a su shell maybe....
If anyone can help me out, it'd much appriciated, I'd like too get magisk installed seemless without pre-rooting and switch because I previously have rooted another OD8Pro using dr.phone, which works and gives you the SuperUser app, but it makes changes to files within the system install-recovery.bin file and this breaks everything for any updates from Rand McNally, and it does NOT backup the original file, so even after unroot within SU app, the file remains broken and fails md5 hash checks when rm_services goes to preform updates.
Ultimately, I'd like to get a port of TWRP or attempt to build it myself for this device, but I'm just a novice and learning on-the-fly about setting up a TWRP build, and having issues syncing my repo within linux. But eventually I'll get things working, and I'll need, or at least it would be helpfull, to have root access when building my TWRP and testing it, not too mention I would like to force Open GApps into the system which is currently not installed in any capacity, not even nano version, and then the Magisk Modules, seemless root, magisk hide, speak for themselves.....
So ya, basically, if anyone knows a way too pull the boot.img or even an entire device partition copy, without existing root or TWRP in any capacity, or is able to BUILD me TWRP that I could use in fastboot boot TWRP.img for example and use TWRP too pull the /dev/block required for the boot.img
Thanks XDA
Anyone know how to get into fastboot on this device?
I can load the bootloader menu, but when i select fastboot it just hangs on RM logo then reboots normally.
I assume i meed too do somthing more, like when selecting the recovery mode instead, you ha e too hold both VOL buttons or it just reboots...
Anyone know the keys too load fastboot?
To be honest, i cant get fastbott too recognize via ADB either now.
I thought i had it working but it does that same as you, just goes into bootloader menu or reboot normally.
Does anyone else have any experience with the OD8PRO?
Im hoping this isnt a dead listing and someone out there can help with this....
Im going too post more detailed device info; If anyone knows where I can go online too find the information required for either a stock boot.img or a wiki for devlopment of this device, it would be much appriciated.
Firstly, I posted before accidently in the forum about the other Rand McNally TND series looking for this information, and I want too start this thread off by making it clear, that too my understanding, the TND series is an AllWinner brand device and there is some limited information for rooting that already available, but the OD7/OD8 series devices are, I believe, Foxconn Devices, with Nvida boards, and MacAllan chipsets, accorinding too the droid info report im posting below. Which means they are not done in the same way.
From what I have done to where I'm stuck now;
I have enabled Developer options
I have enabled OEM Unlock
I can use "ADB reboot ....." command, BUT
No matter which "adb reboot" command I send, recovery, bootloader, fastboot, RUU, RRU..... the command "fastboot devices" does not register after the reboot, nor any other fastboot command.
The device simply reboots one of two ways;
It either;
1. Reboots into the "bootloader" or "recovery", which i've discovered is not the bootloader or recovery modes, but acctually a Rand McNallly Engineering Menu, and gives the options for "recovery mode" "fastboot mode" "forced reset".
When you select ANY of these options, if you do nothing but select the option, the device simply restarts, hangs on the RM logo for about 30secs, and then continues too boot the system normally.
2. the device skips the Engineering Menu entirely, hangs on the RM logo, then boots normally.
I have learned that too enter the "Recovery Mode" after selecting it from the engineering menu, you have too follow these directions;
1. Power off the tablet by pressing the power button for 3-5 seconds and selecting “Power Off” on screen. If the device has frozen and will not respond to screen commands press and hold the POWER BUTTON for 10 seconds to force the tablet to shut down.
2. PRESS and HOLD the VOLUME UP BUTTON AND POWER BUTTON simultaneously. The tablet will then boot into the Engineering Menu.
3. Press the VOLUME DOWN BUTTON and highlight the “Android Recovery Mode” option and press the POWER OR VOLUME UP BUTTON to select.
The tablet will then show the Android Robot with a Warning Sign and display “No Command”.
4. Press and hold the VOLUME DOWN BUTTON and HOME BUTTON for no less than five seconds then while still holding them down press the VOLUME UP BUTTON at release all buttons. The tablet should display the Recovery Menu.
If it does not repeat this step until it does. If the screen goes black, start back at Step 2.
5. Using either of the VOLUME BUTTONS, highlight the “Wipe data/factory reset” option and Press the POWER BUTTON to select.
6. Using either of the VOLUME BUTTONS, highlight the “Yes – Delete all user data” and press the POWER BUTTON to confirm. The screen will indicate that the Data and Cache partitions were formatted.
The tablet will return to the Engineering Menu.
7. Using either of the VOLUME BUTTONS, highlight “Reboot System Now” and press the POWER BUTTON to select.
8. Wait for the tablet to complete its reboots.
The tablet will then be reset to factory state
Its the same for fastboot too my understanding, EXCEPT there is a snag I cant figure out;
When you follow step 1 & 2 and get too the Engineering Menu, and try too follow step 3, but selecting "Fastboot Mode" instead of Recovery Mode, you get nothing. either the screen just refreshes and you have too click it again, and the it reboots too the RM logo, hangs and then boots normally, or it just reboots too the RM logo skipping the screen refresh, and then boots normally after about 30 secs.
I assume, like in step 4, where you have a button combo press, like holding two buttons for 5 secs and then clicking a third while holding them at the Android logo, to actually enter proper stock android recovery mode; that there must but somthing I have to do, ether while its rebooting after selecting fastboot mode, or while it shows the RM logo for a few seconds before booting normally, to get it too actually boot into stock android fastboot mode where adb commands will register and I can send the fastboot oem unlock command.
If there is anything I missed, Ill try too add it, but I think thats about it for the current state of my issues.
Below, as mentioned, are the more detailed specs for the device, like I said, if anyone knows where and can point me in the direction of the stock files for this device, or a foxconn or Nvidia wiki or somthing covering this device, it would be BEYOND appriciated.
Thanks everyone!!!
DROID INFO REPORT
DEVICE
Model: OD8Pro (OverDryve_8)
Manufacturer: FOXCONN
Baseband Version: Not Available
RIL Version: Not Available
Build Number: LMY49I.N8_1_2_180328_363
Build Fingerprint: RandMcNally/OverDryve_8/VTAB8:5.1.1/LMY49I/N8_1_2_18
0328_363:user/release-keys
Bootloader: 20180328.07:54
Java VM: ART 2.1.0
OS Version: Lollipop MR1 (5.1.1)
SDK: 22
DISPLAY
Resolution: WXGA, 800x1280 pixels
Software Density: 213 dpi (tvdpi)
Refresh Rate: 50 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 2 (v7l)
Board: N8_NvT4
Chipset: macallan
Cores: 4
Clock Speed: 1810 MHz - 1810 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: interactive
Kernel Version: 3.4.66
Kernel Architecture: armv7l
GRAPHICS
Renderer: NVIDIA AP
Vendor: NVIDIA Corporation
OpenGL Version: OpenGL ES 2.0
RAM
Total: 1915 MB
Java Heap: 192 MB
This report is generated by Droid Info Android app.