Hello,
I Just got a new TV Box X96 Max with a Amlogic X905X2 processor - Android 8.1 Oreo - U211 Board. I had some old PS3 Controllers laying around, so I wanted to set it up as a retro gaming station.
There is an app for a sixaxis conroller, but it requires root. So after reading thousands of articles about rooting and recovery, I felt confident enough to start (also have enough technical/programming knowledge to understand what I'm doing).
As i understand the easiest way would be to install TWRP, so I can easily make backups and restores and maybe later even tinker with the rom to customize it and/or add drivers etc. Interesting
Set up USB Debugging.... check
Get adb and fastboot... check.
Connect the box with PC through USB....... and here the problems started..
I can't seem to get my PC to see the device, neither Ubuntu nor Windows, doesn't even pop up in device manager etc.
Here's what I tried:
I installed almost all drivers for android / adb / fastboot / amlogic devices on the pc that I could find, with no result.
I tried different male to male usb cables (Even made one of my own) / different port combinations., with no result.
I opened the device to see if there is any other hidden USB connector, and if all the hardware was present, but no hidden USB found.
So I figured letś see what other options I have.
Rootkit apps... hmm letś try...:
SuperSu (multiple versions)... Nope
Kingroot.... Nope
KingoRoot... Nope
Magisk... Nope
Another few nonamed rooters.... Nope
De device was reset to factory via recovery (including wiping cache and dalvik) between tests, and also tried combinations. of rooters.. still nothing
So what's next?
Connecting ADB over TCPIP, now this is interesting... it works. even adb root works.
But.... when booting to bootloader/fastboot the Logo just stays on screen.
Hmm maybe I have to unlock the bootloader????
I checked in the Developer Settings(And all other settings that I could find), but Allow OEM Unlock doesn't exist anywhere.
And to do it via CMD, I need fastboot which requires USB... ahhhmm right so what's next...
Let's seee... owww I seems I can boot from SDCard... let's try to format the card (FAT) putting a recovery.img for s905X on it and put it in the device....
Nothing happens. the sdcard is not being read... let's try to boot to recovery (holding the pin in the AV port)... it just gets into the stock recovery.... as it seems, the Cardreader is not working.
Tte hardware is all there, but it seems the drivers werent installed or something.
As the cardreader is a USB device, I figured, letś try to boot from a USB stick. so I formatted it and put a recovery.img on it and booted to recovery. now it didn't run into recovery, not even stock, but it hanged... so I figure the USB device is being read by the bootloader. maybe a wrong img????
After a long time reding and trying everything I could think of I came accros this post : https://forum.xda-developers.com/an...ers/amlogic/opensource-amlogic-tools-t3786991
Where Ricky Divjakovski,made his Amlogic tools available : https://forum.xda-developers.com/devdb/project/?id=26925#downloads
He made a tool for flashing Amlogic boards with adb tcpip. now that´s great, my problems are solved I can finally do something with the box, right?
So I dowloaded AMLogicTools_5.5.0, installed the drivers, started the AMLogicFlashTool, clicked connect, and I was connected.
Looking Good until now...
Letś make a backup first...... Backup failed... owww nooo
Letś Port TWRP to the recoveryIt starts, goes up to 40% and then hangs the whole system. doesn't look good.
I used : adb pull /dev/block/recovery recovery.img to try TWRP porting to file... didn't work either.
So basically, I can access the box over tcpip, even restart adb in root mode, mount system rw
But Iḿ lost on what my options for rooting / TWRP / Recoverable Custom Roms are.
I read a lot and tried a lot, but maybe I'm missing something
Is there anyone out there who can poiint me in the right direction or has any ideas?
Thanks
Hi, I am about the get one such box and just want to know any new progress you did. As such I am new and interested to know the firmware version and did you got any OTA update. Beelink GT1 Mini is similar hardware and they have posted new firmware in their site. May be you can patch that and use in your device to get what you are looking for.
I have a working TWRP I created for this box. I can share it. Just saw this. The Resolution is a bit garbled, I am trying to fix it so its clear, but it works as of now. - https://mega.nz/#!BAkAyYgS!FvpS0xNJtvLYkb2y3SSfGQp4yY-m_Lkz-BwfIlUTHvU
anyone has tried this box with atv experience rom?
X96 max ethernet fix
I bought the x96 max and the box came with an internet problem both over ethernet cable both over Wi-Fi ..
My home net is working properly ... I do the cable speed test and the box gives me the maximum values ... Then I will see some stream or download and simply do nothing ... How can I solve this problem
CyberSolid said:
Hello,
I Just got a new TV Box X96 Max with a Amlogic X905X2 processor - Android 8.1 Oreo - U211 Board. I had some old PS3 Controllers laying around, so I wanted to set it up as a retro gaming station.
There is an app for a sixaxis conroller, but it requires root. So after reading thousands of articles about rooting and recovery, I felt confident enough to start (also have enough technical/programming knowledge to understand what I'm doing).
As i understand the easiest way would be to install TWRP, so I can easily make backups and restores and maybe later even tinker with the rom to customize it and/or add drivers etc. Interesting
Set up USB Debugging.... check
Get adb and fastboot... check.
Connect the box with PC through USB....... and here the problems started..
I can't seem to get my PC to see the device, neither Ubuntu nor Windows, doesn't even pop up in device manager etc.
Here's what I tried:
I installed almost all drivers for android / adb / fastboot / amlogic devices on the pc that I could find, with no result.
I tried different male to male usb cables (Even made one of my own) / different port combinations., with no result.
I opened the device to see if there is any other hidden USB connector, and if all the hardware was present, but no hidden USB found.
So I figured letś see what other options I have.
Rootkit apps... hmm letś try...:
SuperSu (multiple versions)... Nope
Kingroot.... Nope
KingoRoot... Nope
Magisk... Nope
Another few nonamed rooters.... Nope
De device was reset to factory via recovery (including wiping cache and dalvik) between tests, and also tried combinations. of rooters.. still nothing
So what's next?
Connecting ADB over TCPIP, now this is interesting... it works. even adb root works.
But.... when booting to bootloader/fastboot the Logo just stays on screen.
Hmm maybe I have to unlock the bootloader????
I checked in the Developer Settings(And all other settings that I could find), but Allow OEM Unlock doesn't exist anywhere.
And to do it via CMD, I need fastboot which requires USB... ahhhmm right so what's next...
Let's seee... owww I seems I can boot from SDCard... let's try to format the card (FAT) putting a recovery.img for s905X on it and put it in the device....
Nothing happens. the sdcard is not being read... let's try to boot to recovery (holding the pin in the AV port)... it just gets into the stock recovery.... as it seems, the Cardreader is not working.
Tte hardware is all there, but it seems the drivers werent installed or something.
As the cardreader is a USB device, I figured, letś try to boot from a USB stick. so I formatted it and put a recovery.img on it and booted to recovery. now it didn't run into recovery, not even stock, but it hanged... so I figure the USB device is being read by the bootloader. maybe a wrong img????
After a long time reding and trying everything I could think of I came accros this post : https://forum.xda-developers.com/an...ers/amlogic/opensource-amlogic-tools-t3786991
Where Ricky Divjakovski,made his Amlogic tools available : https://forum.xda-developers.com/devdb/project/?id=26925#downloads
He made a tool for flashing Amlogic boards with adb tcpip. now that´s great, my problems are solved I can finally do something with the box, right?
So I dowloaded AMLogicTools_5.5.0, installed the drivers, started the AMLogicFlashTool, clicked connect, and I was connected.
Looking Good until now...
Letś make a backup first...... Backup failed... owww nooo
Letś Port TWRP to the recoveryIt starts, goes up to 40% and then hangs the whole system. doesn't look good.
I used : adb pull /dev/block/recovery recovery.img to try TWRP porting to file... didn't work either.
So basically, I can access the box over tcpip, even restart adb in root mode, mount system rw
But Iḿ lost on what my options for rooting / TWRP / Recoverable Custom Roms are.
I read a lot and tried a lot, but maybe I'm missing something
Is there anyone out there who can poiint me in the right direction or has any ideas?
Thanks
Click to expand...
Click to collapse
foremost ,you need a suitable recovery.img for your device. then , flash it via adb command: "adb shell cat /sdcard/recovery.img > /dev/block/recovery"
CyberSolid said:
Hello,
I Just got a new TV Box X96 Max with a Amlogic X905X2 processor - Android 8.1 Oreo - U211 Board. I had some old PS3 Controllers laying around, so I wanted to set it up as a retro gaming station.
There is an app for a sixaxis conroller, but it requires root. So after reading thousands of articles about rooting and recovery, I felt confident enough to start (also have enough technical/programming knowledge to understand what I'm doing).
As i understand the easiest way would be to install TWRP, so I can easily make backups and restores and maybe later even tinker with the rom to customize it and/or add drivers etc. Interesting
Set up USB Debugging.... check
Get adb and fastboot... check.
Connect the box with PC through USB....... and here the problems started..
I can't seem to get my PC to see the device, neither Ubuntu nor Windows, doesn't even pop up in device manager etc.
Here's what I tried:
I installed almost all drivers for android / adb / fastboot / amlogic devices on the pc that I could find, with no result.
I tried different male to male usb cables (Even made one of my own) / different port combinations., with no result.
I opened the device to see if there is any other hidden USB connector, and if all the hardware was present, but no hidden USB found.
So I figured letś see what other options I have.
Rootkit apps... hmm letś try...:
SuperSu (multiple versions)... Nope
Kingroot.... Nope
KingoRoot... Nope
Magisk... Nope
Another few nonamed rooters.... Nope
De device was reset to factory via recovery (including wiping cache and dalvik) between tests, and also tried combinations. of rooters.. still nothing
So what's next?
Connecting ADB over TCPIP, now this is interesting... it works. even adb root works.
But.... when booting to bootloader/fastboot the Logo just stays on screen.
Hmm maybe I have to unlock the bootloader????
I checked in the Developer Settings(And all other settings that I could find), but Allow OEM Unlock doesn't exist anywhere.
And to do it via CMD, I need fastboot which requires USB... ahhhmm right so what's next...
Let's seee... owww I seems I can boot from SDCard... let's try to format the card (FAT) putting a recovery.img for s905X on it and put it in the device....
Nothing happens. the sdcard is not being read... let's try to boot to recovery (holding the pin in the AV port)... it just gets into the stock recovery.... as it seems, the Cardreader is not working.
Tte hardware is all there, but it seems the drivers werent installed or something.
As the cardreader is a USB device, I figured, letś try to boot from a USB stick. so I formatted it and put a recovery.img on it and booted to recovery. now it didn't run into recovery, not even stock, but it hanged... so I figure the USB device is being read by the bootloader. maybe a wrong img????
After a long time reding and trying everything I could think of I came accros this post : https://forum.xda-developers.com/an...ers/amlogic/opensource-amlogic-tools-t3786991
Where Ricky Divjakovski,made his Amlogic tools available : https://forum.xda-developers.com/devdb/project/?id=26925#downloads
He made a tool for flashing Amlogic boards with adb tcpip. now that´s great, my problems are solved I can finally do something with the box, right?
So I dowloaded AMLogicTools_5.5.0, installed the drivers, started the AMLogicFlashTool, clicked connect, and I was connected.
Looking Good until now...
Letś make a backup first...... Backup failed... owww nooo
Letś Port TWRP to the recoveryIt starts, goes up to 40% and then hangs the whole system. doesn't look good.
I used : adb pull /dev/block/recovery recovery.img to try TWRP porting to file... didn't work either.
So basically, I can access the box over tcpip, even restart adb in root mode, mount system rw
But Iḿ lost on what my options for rooting / TWRP / Recoverable Custom Roms are.
I read a lot and tried a lot, but maybe I'm missing something
Is there anyone out there who can poiint me in the right direction or has any ideas?
Thanks
Click to expand...
Click to collapse
So, any news? Did you manage to flash custom recovery and root this device? If not. Maybe here you may find something or someone helpful: https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
Cross fingers. I just bought same box and would appreciate if someone could write tutorial how to do it. I just newbie in this matter. Cheers.
TWRP 3.2.2.0 S905X2 x96max
https://4pda.ru/forum/dl/post/14664327/TWRP_AML_3_22_X96MAX.zip
https://drive.google.com/file/d/1nJYas5bZZhtut0KWpd31_uGEpdWSxuR8/view?usp=drivesdk
partition table:
# mount point fstype device [device2]
/boot emmc /dev/block/boot /dev/block/mmcblk0p11 flags=backup=1;display=Boot
/recovery emmc /dev/block/recovery /dev/block/mmcblk0p6 flags=backup=1;display=Recovery
/param emmc /dev/block/param /dev/block/mmcblk0p10 flags=backup=1;display=Param
/system ext4 /dev/block/system /dev/block/mmcblk0p16 flags=backup=1;display=System
/vendor ext4 /dev/block/vendor /dev/block/mmcblk0p14 flags=backup=1;display=Vendor
/data ext4 /dev/block/data /dev/block/mmcblk0p17 flags=backup=1;display=Data
/cache ext4 /dev/block/cache /dev/block/mmcblk0p3 flags=backup=1;display=Cache
/bootloader emmc /dev/block/bootloader /dev/block/mmcblk0p1 flags=backup=1;display=Bootloader
/reserved emmc /dev/block/reserved /dev/block/mmcblk0p2 flags=backup=1;display=Reserved
/env emmc /dev/block/env /dev/block/mmcblk0p4 flags=backup=1;display=Env
/logo emmc /dev/block/logo /dev/block/mmcblk0p5 flags=backup=1;display=Logo;flashimg
/rsv emmc /dev/block/rsv /dev/block/mmcblk0p12 flags=backup=1;display=RSV
/tee emmc /dev/block/tee /dev/block/mmcblk0p13 flags=backup=1;display=Tee
/crypt emmc /dev/block/crypt /dev/block/mmcblk0p9 flags=backup=1;display=Crypt
/misc emmc /dev/block/misc /dev/block/mmcblk0p7 flags=backup=1;display=Misc
/odm emmc /dev/block/odm /dev/block/mmcblk0p15 flags=backup=1;display=ODM
/dto emmc /dev/block/dto /dev/block/mmcblk0p8 flags=backup=1;display=DTO
/external_sd auto /dev/block/mmcblk1p1 flags=wipeingui;storage;removable;display="External SD"
/usb-otg auto /dev/block/sda1 flags=display="USB OTG";removable;storage
A.S._id said:
https://4pda.ru/forum/dl/post/14664327/TWRP_AML_3_22_X96MAX.zip
partition table:
# mount point fstype device [device2]
/boot emmc /dev/block/boot /dev/block/mmcblk0p11 flags=backup=1;display=Boot
/recovery emmc /dev/block/recovery /dev/block/mmcblk0p6 flags=backup=1;display=Recovery
/param emmc /dev/block/param /dev/block/mmcblk0p10 flags=backup=1;display=Param
/system ext4 /dev/block/system /dev/block/mmcblk0p16 flags=backup=1;display=System
/vendor ext4 /dev/block/vendor /dev/block/mmcblk0p14 flags=backup=1;display=Vendor
/data ext4 /dev/block/data /dev/block/mmcblk0p17 flags=backup=1;display=Data
/cache ext4 /dev/block/cache /dev/block/mmcblk0p3 flags=backup=1;display=Cache
/bootloader emmc /dev/block/bootloader /dev/block/mmcblk0p1 flags=backup=1;display=Bootloader
/reserved emmc /dev/block/reserved /dev/block/mmcblk0p2 flags=backup=1;display=Reserved
/env emmc /dev/block/env /dev/block/mmcblk0p4 flags=backup=1;display=Env
/logo emmc /dev/block/logo /dev/block/mmcblk0p5 flags=backup=1;display=Logo;flashimg
/rsv emmc /dev/block/rsv /dev/block/mmcblk0p12 flags=backup=1;display=RSV
/tee emmc /dev/block/tee /dev/block/mmcblk0p13 flags=backup=1;display=Tee
/crypt emmc /dev/block/crypt /dev/block/mmcblk0p9 flags=backup=1;display=Crypt
/misc emmc /dev/block/misc /dev/block/mmcblk0p7 flags=backup=1;display=Misc
/odm emmc /dev/block/odm /dev/block/mmcblk0p15 flags=backup=1;display=ODM
/dto emmc /dev/block/dto /dev/block/mmcblk0p8 flags=backup=1;display=DTO
/external_sd auto /dev/block/mmcblk1p1 flags=wipeingui;storage;removable;display="External SD"
/usb-otg auto /dev/block/sda1 flags=display="USB OTG";removable;storage
Click to expand...
Click to collapse
Link is dead. Could you explain what are those strings for? Did you manage to unlock bootloader, flash working recovery and root this device? Thx
rsteelion said:
Link is dead.
Click to expand...
Click to collapse
just check - link is OK. you need to be registered to download from 4pda.
you may try second link from google drive instead (which is Ok too)
ayaromenok said:
just check - link is OK. you need to be registered to download from 4pda.
you may try second link from google drive instead (which is Ok too)
Click to expand...
Click to collapse
Thank you for second link. Could you tell what those strings from your first post are...? Forgive my ignorance...
Hi, i m not easy with forum and post by for hardaware x96max_v311 4gb ram 64gb intern and gigabit just new:with issues but last firmware no updates.
1/ gigabit wired port, link with the switch in place of old one h96+(3gb/32gb), the box stay info disconnect no gigabit port can communicate and menu Network and internet have no entry for setup cable wired, only wifi, all my infrastructure works fine.
2/ wifi 2/5 ghz works but onlyN can connect, 5 GHZ registreted never connect, but used my laptop and phone, 5ghz AC out order
3/ remote poor , power can be parameter but never wake up.
4/ menu interface poor, nedd change , and down new
my experience with no solution for gigabit
Thanks for your info correction for this product ( put my old in place and works )
I just posted a TWRP 3.2.3-0 build for the GT1 Mini (S905X2) that uses the same Amlogic u211 reference board, so it will likely work on this device too : twrp.u211-3.2.3-0.img
It's built with the twrp-8.1 minimum OMNI branch and is using a prebuilt 112N0 GT1 Mini kernel. Source is in the twrp-8.1 branch of my TWRP for Amlogic repository.
Systemdown666 said:
I bought the x96 max and the box came with an internet problem both over ethernet cable both over Wi-Fi ..
My home net is working properly ... I do the cable speed test and the box gives me the maximum values ... Then I will see some stream or download and simply do nothing ... How can I solve this problem
Click to expand...
Click to collapse
I am also having the exact same issues with the X96 Max TV Box 4GB/64GB.
Has anyone else come across this and found a fix?
Hello, I discover that the X96 max 4G/64/G is 8.1 android 32bit ! after issue on ethernet gigabit et wifi 5ghz OUT it s a big waste.
no original rom (name u311 is a 211 board too )can be found on web and no patch
It s a new plateform interresting but just the OS made quick for business , not to be full functionneley
It s direct now to the bin !
stock a firmware X96 Max - S905X2
Hello!
I have problem with may tv box, it is stuck on boot screen logo.
I tried to reset the box but it doesn't help.
I want stock firmware pls
best regards
ahmaduk8 said:
Hello!
I have problem with may tv box, it is stuck on boot screen logo.
I tried to reset the box but it doesn't help.
I want stock firmware pls
best regards
Click to expand...
Click to collapse
http://www.mediafire.com/file/ga6qtrj6df6cpsx/X96MAX--4+32G+4+64G.img
credit to
http://4pda.ru/forum/index.php?showtopic=925461
hello, the link does not work, can you resurrect it? Thank you
https://chinagadgetsreviews.com/download-android-oreo-8-1-firmware-for-x96-max-tv-box.html
Hi all, ive seen few posts where saying that libreelec can be flashed by using reset button placed behind AV connector, i'm really not sure if that applicable for amlogic s905x2 and 4gb ram
Anyone owning x96 max willing to test some of libreelec roms?
If anything stated wrong or u know the answer already, please tell
Btw im thinking about to get one x96 max, but just for having libreelec as standalone os there
Thanks
Related
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
dwelch77 said:
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
Click to expand...
Click to collapse
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
aicjofs said:
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
Click to expand...
Click to collapse
Exactly. I can not navigate the options at all. Volume - doesn't do anything, Volume + doesn't do anything.
OK scratch all of that. So while I was messing around with it this morning I accidentally dropped the tablet. After "impact calibration" the keys worked and I was able to get into TWRP. And Nabi Lab recognized it was plugged in. I was able to get it set all the back to factory with the factory boot recovery in place as well. As of right now update 2.1 is downloading and I'm keeping my fingers crossed that it will work.
The only thing I can think of is something on the board might have a broken solder connection, so as of right now I'm touching it as little as possible until the updates are done. I'll post back here when I have more information.
Nabi 2 Bricked ?
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Dowmole said:
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Click to expand...
Click to collapse
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
aicjofs said:
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
Click to expand...
Click to collapse
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Dowmole said:
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Click to expand...
Click to collapse
So what exactly did you do again? It was an original Nabi2 on ICS, and you "wiped" it. What exactly did you wipe? All the partitions not showing up is usually I sign of the wrong TWRP build but you said you tried both. Plus I have never seen where you can't mount the MicroSD
In the terminal app in TWRP(both versions) what does it say if you type
cat /proc/partitions
does it look like this:
major minor #blocks name
179 0 7766016 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 823296 mmcblk0p3
179 4 481280 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 1536000 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 65536 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 4485120 mmcblk0p11
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
or more like this
major minor #blocks name
179 0 7766016 mmcblk0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
Thanks for your help on this aicjofs I really appreciate it
It shows :-
179 0 31166976 mmcblk0
179 1 1 mmckblk0p1
179 5 31164416 mmcblk0p5
The whole "short" story was....When I received the Nabi 2 just over a year ago I had to somehow get Google Play Store on it. As we know that wasn't possible until recently so I followed the guide by Victoria (I think from memory) on Youtube. This then did not allow me to do further Nabi updates. I managed to get this back to stock from your guide and then update bit by bit to the latest update (wit Jellybean). All was great until I realised that the wrong one of my children had been setup on it. I removed the user (from the parent portal on the Nabi website). This then stopped me using the external SD card (media errors stopping it)
So stupidly (in hindsight) I took it upon myself to wipe the Nabi from within Jellybean and re-boot, thinking that it would be a straightforward re-setup. But it wasn't. It seemed to have un-mounted everything. So now within TWRP I cannot mount data, system, cache, external sd card. and therefore cannot wipe those folders and start again (from TWRP that is). I have tried to mount those folders from terminal but am getting nowhere
Thanks
Dowmole
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Dowmole said:
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Click to expand...
Click to collapse
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Radmatazz said:
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Click to expand...
Click to collapse
I had a similar issue -- I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Your solution was awesome!
2girlzdad said:
I had a similar issue -- I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Click to expand...
Click to collapse
-----> My issue was EXACTLY the same, I used your solution and viola, it is fixed, it even auto asked me to install root before I rebooted! THANK YOU... as a rank amateur, I feel I should share the finer details of my solution to help anyone else out that also has this problem.
I did a couple things different from this, that I should share so that all will benefit.
I use NabiLabGUI. The TWRP that comes with it does NOT work with my build. I searched for the TWRP that comes with it,
Found at my 'C:\Users\Spam\AppData\Local\Apps\2.0\7J1BHCKA.8HM\5YTQ71XH.YAP\ then 2 sub directories,
nabi...exe_3432fd94fe885e67_0001.0002_none_141f851fecdb6e30 and
nabi..tion_3432fd94fe885e67_0001.0002_f75a67d47ecb93e2
since I have a nabi 2 NV7A, for my daughter, I opened the subdirectory '2' in each replacing the 2\recovery\new\recovery.img with the one from twrp-recovery-JBNV7AUS-263.zip (note you must rename it to 'recovery.img')
I then ran nabilabgui, simply selecting the recovery installer, to easily load the recovery image, booted into the now version 2.6.3 TWRP, and loaded the 'twrp-recovery-JBNV7AUS-263.zip'
No boot/softbrick
I am unable boot beyond the bootloader screen. I cannot gain access via Nabi Lab GUI with ADB but I can via Fastboot. So my issue is how do I fix my Nabi 2 via Fastboot? I need commands and where and what files to get back to stock.
Thank you,
Niles
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Doozeman said:
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Click to expand...
Click to collapse
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
aicjofs said:
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
Click to expand...
Click to collapse
Thanks very much for the reply. I did have PDANet installed and my computer couldn't see the tablet. I will try again soon later. I think my problem has arisen since i followed a procedure from this link http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98 and I may have messed up flashing this file http://forum.xda-developers.com/showpost.php?p=50356162&postcount=91 too early!. Ultimately I wish to have this file http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85 on the tablet and it being up and running with no problems.
First things first though I need to get the tablet seen by the computer.
Do I need to uninstall my Nexus 7 and Samsung Galaxy S III drivers first before installing PDANet? Once installed how do I get fastboot installed?
Many Thanks in Advance,
Doozeman
Okay I now have found how I can install TWRP via your command but I'm still unable to install an OS on the tablet. NabiLabs refuses to see the tablet and I am now stuck. Tell you what like this is a steep learning curve for me! Why can't this tablet be as easy as the Nexus 7 to flash or recover?
Have you any more suggestions as to how I can proceed? Is there another way I can push installation files? I have tried copying stock restore files (as supplied by Nabilabs) to a micro sd card using the following layout TWRP/BACKUPS/"My Device Number"/restore but no matter the version of TWRP installed there are no files shown to restore.
*Update* I have tried to install the latest TWRP via flashable zip but it won't install because of the missing folders as there is no OS installed. I get an error status 6. Unable to mount /data, /system, /cache etc.
I'm beginning to fear that I have killed this tablet
I'm tearing my hair out here!!
Many Thanks in Advance
Completely and totally stumped
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
sandrewmorrison said:
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
Click to expand...
Click to collapse
Usually a sign u flashed ICS TWRP instead of JB.
aicjofs said:
Usually a sign u flashed ICS TWRP instead of JB.
Click to expand...
Click to collapse
Can you tell me the version numbers of each version? I believe I have tried both. Both have told me I have no OS installed, cannot mount any internal anything, can't format it, and doesn't show any internal storage space. It comes up as 0mb.
Hi All,
I have purchased a leagoo lead 1 http://www.leagoo.cc/c51181.html (slick design and under 150$) but now I'm trying to get it rooted.
I've tries Kingo root, V Root, Shuame, Towel root, Framaroot and none of it is working.
The phone operates on 4.4.2 with an MTK 6582 processor..
When holding Vol up + power I get a fastboot option though.
Would extracting boot.img and rework it mean something? or has anyone usefull tips?
Thnks in advance.
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
boyanpa said:
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
Click to expand...
Click to collapse
First of all .. I managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingosoft one click root, (www.kingoapp.com) Mobile uncle tools
Start sony bootloader unlocker and run it with your phone connected.
It will restart your phone to fastboot and then it remains idle.
Keep your phone plugged in, switch it off and boot manually into the fastboot (power + vol up)
From here the unlocker will proceed unlocking.
Step 1 done.
Now open kingosoft root connect the phone and let it do its thing.
At restart of the phone kingosoft will show on screen a message like "checking root status"
Launch mtk uncle and enter engineer mode.
Go to log and debugging tab ans select user2root
Select Root.
Now kingosoft will tell you that root is succesfull and restarts the phone.
That's that. Phone is rooted. For recovery see the posts 22 and 24 from Vampirefo who did the real hard work in creating 2 flavours of recovery. [emoji106][emoji106]
Non linux users can also flash the img through MTK uncle from sdcard if that doesn't work. See post 40 for flashing recovery via SP tools
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
de vetnek said:
First of all ..Looks like I (accidentaly) managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingo soft one click root, Mobile uncle tools
I Downloaded from kingosoft the sony bootloader unlocker.
It puts the phone in fastboot mode and then it hangs. I unplugged my phone, switch it off (keep the unlocker running) and manually booted into fastboot (vol up+power) the bootloader unlocker then proceeded untill finished.
Next I installed this root tool and started it while the phone was still in the fastboot mode. after a couple of restarts it says checking for Root, then I decided to start MTK uncle tools and scroll to "log and debugging" and select User2Root. then clicked Root and all of a sudden the phone was sucessfully rooted.. Smiling Smiling I don't know what exactly sparked the root access but It's rooted and works!
If anyone can reproduce this in a correct order. please feel free to share.
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
Click to expand...
Click to collapse
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
vampirefo said:
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
Click to expand...
Click to collapse
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
de vetnek said:
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
Click to expand...
Click to collapse
Thanks, GPS was working great on my phone out of box.
vampirefo said:
Thanks, GPS was working great on my phone out of box.
Click to expand...
Click to collapse
Mine wasn't but probably due to a factory reset from recovery? OR it wasn't fit yet to see the dutch sky
Managed to root the thing?
Yes mine is rooted also, Similar to the way you rooted yours.
I used Linux and wine to run the bootloader tool from there, I had to use another tool to get temp root, then I pushed su and set permissions.
The bootloader tool you used works via wine but the root tool doesn't.
Sent from my Leagoo Lead1 via taptak.
So we can carefully state that the (accidental) rooting method works.
Btw. I figured out that /system is ro and not rw
Also with adbd insecure it remains ro. Means it has to be scripted to rw at every boot or.... Can try to run framaroot exploit.
System is supposed to be ro this is normal, to get rw add busybox and then remount rw.
Also you can edit the boot.img and make a insecure boot.img and flash, I have done this myself, this enables adb remount, you can add a script to /system/xbin, to force rw or ro.
I wouldn't want rw all this time, as this can cause instability use ro until you need rw, es filemanger with root also allows you to mount system rw as needed.
Added some pics of phone showing it's rooted.
http://postimg.org/gallery/6ol04a9i/
Sent from my Leagoo Lead1 via taptak.
Check
Noticed that the 1GB Rom quickly runs full if you are not keen on the installation location of apps.
Facebook though can't be moved to SD card.
libvc1dec.sa.ca7.so has text relocations . This is wasting memory and is a security risk. please fix
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
vampirefo said:
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
Click to expand...
Click to collapse
Below shows data is now 4GB, as I am running data from sdcard, I can of course make data any size I want, only limited by size of sdcard, I think this phone supports 64GB, so data could be 64GB.
Code:
[email protected]:/ # busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 481.6M 128.0K 481.4M 0% /dev
none 481.6M 12.0K 481.5M 0% /sys/fs/cgroup
tmpfs 481.6M 0 481.6M 0% /mnt/secure
tmpfs 481.6M 0 481.6M 0% /mnt/asec
tmpfs 481.6M 0 481.6M 0% /mnt/obb
/[email protected] 885.8M 819.2M 66.6M 92% /system
/dev/block/mmcblk1p3 4.0G 999.8M 2.8G 26% /data
/[email protected] 123.0M 4.1M 119.0M 3% /cache
/[email protected]_f 8.8M 4.1M 4.8M 46% /protect_f
/[email protected]_s 8.8M 4.1M 4.8M 46% /protect_s
/dev/block/loop0 1.5M 1.5M 0 100% /mnt/cd-rom
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
tunglethanh90 said:
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
Click to expand...
Click to collapse
No ideal what you are saying, Have you rooted your leagoo lead1? if so by what? what is VOcano? Post more details, you say you root but not done, what does that mean?
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
de vetnek said:
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
Click to expand...
Click to collapse
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
vampirefo said:
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
Click to expand...
Click to collapse
Things just got worse hehe.. Did the whole link2sd thing and linked a couple of apps and voila. playstore, facebook, whatsapp gone.. and nowhere to be found back........... doubting whether a factory reset would fix the thing? So in short.... nope.. link2SD does not work.
wouldn't posting the repacked recovery and flashing it to another phone be possible?
Yes the recovery can be flashed on another rooted tablet, but there is more to getting data on sdcard that just flashing a recovery.
I just now modified cwm recovery to work on leagoo lead1, cwm recovery is bigger than my packed stock recovery, but I am able to squeeze in it, lol.
In Utopia..... This would be a good solution for the Leagoo too
http://forum.xda-developers.com/showthread.php?t=2020677
Don't know exactly how they fixed it.. but..... there you also went from 1 to 2.5 GB internal...
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
jmmac said:
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know nobody has talked about it on here except you.
Depending on what kernel patches or android security fixes it has you might be able to try some root programs. There certainly will not be a clockworkmod or TWRP for it yet.
If none of the root methods work it might be possible to use the Dreamtab TWRP.(http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917) If it's like the previous Nabi tablets the bootloader will be unlocked, and you could try booting from that TWRP. The screen and the landscape/portrait might be messed up but it could work. In the last software update to the dreamtab they locked the bootloader so the BIG TAB might be as well. It could be unlocked by
Code:
fastboot oem unlock
^^^ This will ERASE all the data on the tablet.
If you want to try the TWRP way let me know but of course there are dangers involved.
If you try it alone be aware that if you try the dreamtab TWRP load it by
Code:
fastboot boot recovery.img
and NOT
Code:
[STRIKE]fastboot flash recovery recovery.img[/STRIKE]
or you will overwrite your current stock recovery.
also interested! any further info would be great!
schlager said:
also interested! any further info would be great!
Click to expand...
Click to collapse
Do either of you have one? Or just asking?
aicjofs said:
Do either of you have one? Or just asking?
Click to expand...
Click to collapse
i plan to buy one in the next few weeks. mainly need it so i can have two sheets of music in front of me. if there is another tablet that can do that, let me know.
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
codest3r said:
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
Click to expand...
Click to collapse
I have no idea about the BigTab but if it's like the DreamTab it will update when you boot it up. It's hard to get around it. If it does it will likely patch a lot of the more recent exploits that can gain you root. There is the option to try the dream tab recovery like I said above but be really careful with that.
Also one of the Dreamtab updates locked the bootloader. This isn't a big deal as it was unlockable via fastboot. However, if you let the kiddoz, or you start installing a whole bunch of stuff, when you unlock the bootloader you will wipe the tablet back to factory(normal behavior). Best to unlock it as soon as possible.
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
You could download and try a rooting apk like towelroot framaroot or z4root if it has a low android firmware like 2.3.6 or something but only for z4root
I already got it rooted using Kingo root, these tablets are new on the market running kitkat 4.4.4, the end goal I am trying to achieve is making a custom rom but a neassacery first step is to get a working custom recovery so I can backup my stock rom just in case I blow up my tablet =)
lmortal said:
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
Click to expand...
Click to collapse
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
aicjofs said:
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
Click to expand...
Click to collapse
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
lmortal said:
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
Click to expand...
Click to collapse
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
aicjofs said:
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
Click to expand...
Click to collapse
I sent you a pm with a drop box link with my files in the mean time gonna try compiling with your suggestion and see what happens.
---------- Post added at 04:17 PM ---------- Previous post was at 03:36 PM ----------
I tried compiling with:
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
/dev/null /sdcard fuse datamedia,recoveryonly defaults
It compiled successfully and I was able to flash it, the sdcard showed up in the mount menu but was not mountable still.
---------- Post added at 05:10 PM ---------- Previous post was at 04:17 PM ----------
Okay so my latest build using:
/dev/block/sda1 sdcard fuse defaults nonremovable
Allowed backup to the sdcard of everything with the exception of /data got "Error while making a backup image of /data!"
Also still unable to mount sdcard under the mounts and storage menu.
I believe the reason for the error while backing up data was due to available space when I restarted the tablet there was only 99.59MB available and I think the data would have needed more space then that.
I kept running into problems with CWM recovery but with the help of aicjofs I was able to compile a working TWRP with usb drive support, I don't yet have enough post to make an outside link so if some one can pm me I can give the link to be posted here with the recovery I made.
Working TWRP 2.8.1.0 for Nabi BigTab 20
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
aicjofs said:
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
Click to expand...
Click to collapse
Fixed an error where /addon was not mounting. re uploaded recovery image to the above link.
I can't unlock my bootloader.
lmortal said:
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
Click to expand...
Click to collapse
I've ben trying to root my Big Tab 24". You said you had to unlock the bootloader. I can't get it into bootlad mode or unlock the bootloader. I tried fastboot. I tried every button combination I could think of. (not too many considering it only has three physical buttons) I tried rooting it with Kingo without unlocking the bootloader. Nothing is working. Please help. What am I doing wrong or not doing right?
Fastboot is the boot loader make sure you have USB debugging enabled and connect the tab to a PC you can then use the command "adb reboot-bootloader" the command to unlock is "fastboot OEM unlock"
Q&A for [TOOL][NABI2] NabiLab - Root, Play, Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][NABI2] NabiLab - Root, Play, Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
State of Nabi 2 Root as of 12/14?
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Eyebolt said:
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Click to expand...
Click to collapse
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).
katinatez repackaged it for jellybean here:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
jaxbierley said:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477
http://forum.xda-developers.com/showthread.php?t=1905674&page=248
Stock Restore
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Firepants said:
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Click to expand...
Click to collapse
What version of software? Use Nabilab2015 http://forum.xda-developers.com/showpost.php?p=59073456&postcount=2544
It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
Hacking Nabi2 to Allow Data2SD
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you don't have the time to do all these steps, I have the modified boot file attached here.
Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:
Code:
fastboot flash boot new_boot.img
Nabi2 not found
Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
Swipe to restore
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Aytul said:
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Click to expand...
Click to collapse
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
n3wt said:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
Click to expand...
Click to collapse
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Aytul said:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Click to expand...
Click to collapse
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
n3wt said:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
Click to expand...
Click to collapse
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Aytul said:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Click to expand...
Click to collapse
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
n3wt said:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
Click to expand...
Click to collapse
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Aytul said:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Click to expand...
Click to collapse
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
n3wt said:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
Click to expand...
Click to collapse
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately
Hi all,
got myself a Chinese tablet, a UnisCom MZ85-4G with MT6735 running Android 6.0. There is pretty much no software at all preinstalled, esp. no Google Play Services/Store. To install a GApps package, I need a custom recovery, which does not (yet) exist for this device. So I am trying my best to compile one on my own, even though I am completely new to Android development.
I started by using the AIO TWRP Compiler script, but this needs the recovery.img of my device which I am not able to get in any way. What I know/found out:
Guess what, there is no manufacturer's support site offering any downloads or sources for the product.
The developer options allow me to unlock the bootloader, but no root access.
I can get into stock recovery and also fastboot mode.
In "adb shell", I cannot get into the /dev/block directory tree. Actually, issuing "ls" in /dev already yields "opendir failed., Permission denied". Funny as /dev's mode is 755. Other directories with mode 555 like /proc work perfectly.
I can however use shell auto-completion to peak into /dev. There is no /dev/recovery, as might be expected on MediaTek devices.
There are no /proc/dumchar_info or /proc/emmc files. The best hint on the recovery location I got was from /etc/recovery.fstab:
Code:
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p5
/misc emmc misc
[B]/recovery emmc recovery[/B]
/sdcard vfat /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p3
So I expect the recovery to be at /dev/block/platform/emmc/by-name/recovery (or similar), but currently I have no chance of getting there, not speaking of dd-ing it.
I am stuck now. Any hints on how to proceed?
Regards,
Eric
After lots of reading and fumbling around, I managed to solve my problem on my own. It turned out to be quite simple in the end. I'll post a brief here for reference:
1) get physical address and size of the recovery image from the scatter info in "MTK engineering mode"
2) extract recovery image from the phone using the readback mode of SP Flash Tool and the parameters from step 1
Now only the hurdle of compiling TWRP remains.
Regards,
Eric
What commands do I have to type in adb to do this?
There is no adb involved (in those first two steps, at least). The MTK engineering mode is an app available in Play Store. In my case it was actually pre-installed and could be opened by tapping multiple times on the "Model number" item in the "About phone" settings menu. SP Flash Tool is freeware, available for Win and Linux; just google it.
I managed to pull recovery and boot img using spft and wwr mtk, if your device is mtk chip give it a try.
No root and custom recovery needed, just PC and adb.
***forum.hovatek.com/thread-21970**** search this one for the tutorial
can you help me extract recovery.img i got root on my realme phone