[Q] How to get dynamic storage (/sdcard ->/data/media) on One S, "Insufficient Space"
Ohh, I'm getting so fed-up with seeing "Insufficient Space on Device" errors in the Play Store. What good is Android if I can't download any games or apps?!
I'm running CyanogenMod 12.1, latest nightlies. But the ROM thread isn't the right place to put this, because it's a device/partition-level issue.
I've got hboot 2.15 and S-OFF, and from what I've seen, hboot 2.16 brings with it the "dynamic /sdcard" feature that creates one big partition out of /data and uses part of it for a "virtual SD". What I have now seems to be a fixed /data size and a huge, almost completely unused /sdcard partition. I keep running into "Insufficient space on device" errors all the time, without even downloading new apps - just trying to update the apps I have. Nothing big, either - the biggest app I have is freakin' Candy Crush. It appears that I'm only given a 2GB /data partition, and 1.1GB of that is Dalvik-Cache, and 900MB of it is apps & data. Yeah, the dalvik-cache is bigger than the damn apps it's caching!
I'd be willing to wipe it all out again (sigh... SIGH) if I can get dynamic /data to work, perhaps by updating to hboot 2.16. I'd even go S-ON again if need be - the only reason I'd gone S-OFF is to try to get more stability out of the glitchy radio firmware constantly dropping the internet connection, but those problems still persist too...
Well, I dug really, really deep and discovered that hboot 2.16 is what brings the "dynamic /sdcard" to the One S. You can follow along with much more information in my replies here: http://forum.cyanogenmod.org/topic/113169-storage-space-running-out/#entry535206
The key is to install hboot 2.16 from this post: http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266
I'm hoping - hoping and hoping* - that I can restore my TWRP backup into the new /data partition. To get it working, I had to use TWRP's "repair/change filesystem" on both /cache and the /data partitions (though strangely, /system was left intact and valid, apparently because the sector location didn't change). This means that all USB storage (/sdcard) and internal storage (/data) will be lost, so be sure to backup and transfer to your PC before updating to hboot 2.16! You also lose the ability to mount internal storage as USB (using USB Mass Storage mode), because /sdcard is now a virtual drive, no longer FAT formatted. In my opinion, this is a very worthwhile and acceptable tradeoff... because /data is now 12 GB!
* - edit: I'm full-on freakin' ecstatic right now.
"Internal storage - Total space: 12.06 GB -- Available: 7.63 GB"
And not a single thing was lost or changed. Booted right up as if I'd just switched the thing off and back on.
Hey FalconFour,
Thanks a lot for sharing your progress with us.
As you saw in my thread, I'm facing the same annoying storage issues like you (and a lot more people on the internet...).
I'll give your solution a shot during the next couple of days and report back as soon as I have some results.
My status quo: HTC ONE S / CM 12.1 / S-ON / HBoot 2.15
Do you have any advice for me before I start?
Urds said:
Hey FalconFour,
Thanks a lot for sharing your progress with us.
As you saw in my thread, I'm facing the same annoying storage issues like you (and a lot more people on the internet...).
I'll give your solution a shot during the next couple of days and report back as soon as I have some results.
My status quo: HTC ONE S / CM 12.1 / S-ON / HBoot 2.15
Do you have any advice for me before I start?
Click to expand...
Click to collapse
** Crap -- I just realized you said you're S-ON. See the bottom of the post for advice on that. **
1) Backup. I used TWRP 2.8.7.0.
2) Earlier versions of TWRP seem to have a bug in "Mount USB storage" function - on mine, it was horribly, unusably unreliable to actually present the "linux file gadget" USB device or whatever it was. 2.8.7.0 seems to fix that. It mounted reliably after the update, and I backed up all the files on the "internal SD" - including the backup I just made.
3) Grab hboot 2.16 and apply it per the fastboot commands in that thread.
4) For safety, I ran "fastboot oem erase_phone_storage" from the new 2.16 bootloader (fastboot mode).
5) Before rebooting, I reflashed TWRP 2.8.7.0 with "fastboot flash recovery" just in case it changed.
6) Reboot to TWRP recovery.
7) Under "Wipe", "Advanced", use "Repair/change filesystem", and I applied F2FS to /data and /cache, since at least /data will now be unformatted (or corrupt) due to the partition layout change. Since ext4 isn't designed for Flash storage and I'd like my phone to last as long as possible, I figure the bit (a few hundred MB) of "wasted" storage space on F2FS' logs is totally worth it, now that I have 12GB of storage available between /data and /sdcard combined.
8) Enable MTP mode in TWRP (under Mount) and transfer all my SD card contents back to the phone.
9) Now, I restored my backup - excluding /system and /boot. It warned me about the backup being made with ext4, but worked fine.
10) Now, the phone will boot as if nothing had happened -- but your /sdcard will not be accessible, due to the change in structure. You need a new kernel image that's compatible with hboot 2.16's partition layout. I did this by updating my ROM to the newest (9/1) snapshot of CM12.1 - here: http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266 -- so I applied that zip, the newest GApps, and the SuperSU zip.
That's it! Just like it was yesterday, but with practically infinite room to move. :good:
Update -- for S-ON, I think you need to get S-OFF in order to modify "hboot". I'm not actually sure. If you get to step 4 and you do NOT see hboot 2.16 installed, you should grab Rumrunner and let it work its magic. It's a very condescending and often frustrating program at first, but it gets quite genuinely hilarious in its status messages as it runs. As long as your environment is clean (ADB driver matches the ADB version bundled inside rumrunner's executable, which you can check while it's running by examining the files in a hidden folder it creates when you run it), it'll work its magic and you'll become S-OFF. Backing up is a good idea before embarking on rumrunner, of course. Also -- I've used Moonshine before as well, and it seems like Rumrunner was created to fix a lot of program-logic bugs in Moonshine - does a much better job of recovering from unusual conditions that hang up Moonshine. Rumrunner > Moonshine. :victory:
Thank you very much for your summary. I really appreciate your work here!
At the beginning I was really excited after going through your posts... Now, after my first attempts, I'm back to reality ^^
At first I tried to flash the bootloader while staying S-ON. During the update process I received the following error: remote: 99 unknown fail.
I can't really define what causes the error but I thought it could be related to S-ON. That's why I decided to go for S-OFF.
After using rumrunner and moonshine (which both failed) I found out, that apparently I need to go back to a stock rom. Switching to S-OFF and having cyanogenmod installed seems to be not supported.
At this point, being tired and bugged, I stopped for a rest...
Urds said:
I can't really define what causes the error but I thought it could be related to S-ON. That's why I decided to go for S-OFF.
After using rumrunner and moonshine (which both failed) I found out, that apparently I need to go back to a stock rom. Switching to S-OFF and having cyanogenmod installed seems to be not supported.
At this point, being tired and bugged, I stopped for a rest...
Click to expand...
Click to collapse
Hah, yep, I can relate... it's a HUGE pain in the rear to find the right RUU to get this thing fully stock again. But I think I've mastered the process, and I'll pass that along here as well.
Even through all this, once you get it S-OFF'd and updated to hboot 2.16, you can restore TWRP (or your preferred recovery) and restore your ROM just as it was before - most likely. Performing "S-OFF" also allows recovery to flash the "boot" (kernel) partition, instead of needing to use "fastboot flash boot" separately from installing the ROM.
For my RUU, I believe I used a package called (*deep breath*... may need to remove spaces) RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe - which contains every iota of data that the phone consists of - bootloader (it will S-On your phone again), radio firmware, kernel, system storage, partition layout, *everything*. So definitely back up your ROM and the resulting internal /sdcard contents before doing it.
When you run that, it'll pretty much do everything on autopilot, though you may want to launch it from Fastboot mode (Power+VolDown from powered-off state). I found that it only works reliably in a system with an older OS, though - I had trouble with Windows 8 and obviously Windows 10 as well, as they wouldn't detect the bootloader device. Windows 7 may be compatible, but I did it on a Server 2003 (Windows XP) system myself.
Then, you can Rumrunner it, then (may need to) unlock it again (HTC method), verify you're at hboot 2.16 (perform steps above if needed), restore your recovery, restore /sdcard, restore your ROM using MTP mode, and should be good to go!
FalconFour said:
(Instructions omitted)
Click to expand...
Click to collapse
Hey @FalconFour,
Just wanted to express my thanks for writing your OP. Earlier today I found it when I was looking for a way to increase my data partition. Thanks to you this was a totally effortless process. Thanks! :victory:
voidzero said:
Just wanted to express my thanks for writing your OP. Earlier today I found it when I was looking for a way to increase my data partition. Thanks to you this was a totally effortless process. Thanks! :victory:
Click to expand...
Click to collapse
Thanks @voidzero! It'd be awesome to gain some +rep for it :laugh::good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
update: Oh! I see you already did, LOL. Sorry! Well, for anyone else passing through these internet tubes, then! Crap, now I wish I could delete.
Related
This is a guide that I created for a friend of mine. Since originally putting it together I have found myself going back to it often as a quick reference guide on how to perform certain procedures. I figured that I may as well share it for others that might find it useful. I will do my best to keep it as up to date as possible.
Gain Root
Koush put together an excellent guide for this here:
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Recovery
Rom Manager to install either clockwork recovery or amon ra recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rom Manager
Click to expand...
Click to collapse
Backup
In either recovery you can do a nandroid backup. Do a full backup in case anything goes wrong you can restore phone to its previous state. If you have apps2sd running you will want to select the option that does ext backup as well. Basically its best that every time you have your system working the way you like it to do a nandroid backup so you always have the most recent restore point for your phone.
Alternately, if you simply want to backup applications or system settings individually download MyBackup or Titanium backup You can opt to save application data so that all of your application settings and such are saved as well.
MyBackup
Titanium Backup
Click to expand...
Click to collapse
Flash Radio Update
**NOTE** It has been brought to my attention that it can be unsafe to flash Radio or SPL via recovery (result in brick). Fastboot is much safer. I completed this via recover without any issues. However, I am not responsible if something happens. I will be adding instructions for fastboot shortly. Haven't touched it since I first got my phone way back so need to relearn the procedures. Info HERE**
http://forum.xda-developers.com/showthread.php?t=640535
Download - http://www.mediafire.com/?zgnzmex2mrj
Copy to SD card
In recovery apply zip
Click to expand...
Click to collapse
Flash Danger SPL
**NOTE** It has been brought to my attention that it can be unsafe to flash Radio or SPL via recovery (result in brick). Fastboot is much safer. I completed this via recover without any issues. However, I am not responsible if something happens. I will be adding instructions for fastboot shortly. Haven't touched it since I first got my phone way back so need to relearn the procedures. Info HERE**
http://wiki.cyanogenmod.com/index.php/DangerSPL
Download - http://sapphire-port-dream.googlecode.com/files/spl-signed.zip
Copy to SD card
In recovery apply zip
Click to expand...
Click to collapse
Partition SD
In recovery partition SD
~500 ext
64 swap (only do swap if you intent to use it; read info on swap below before you decide)
*These are my settings. You can adjust as you wish
Click to expand...
Click to collapse
Flash Newest CyanogenMod Rom (5.0.7 Stable)
http://forum.cyanogenmod.com/index....magic-mean-lean-pastry-machine-v507-05252010/
Download - http://www.kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-signed.zip
Download - http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
Copy all to SD card
If first time installing CM 5.0.7 do a wipe in recovery
In recovery apply update zip
In recovery apply gapps zip (not necessary if already running previous version of 5.0.7)
*Note
Go into settings
Application settings
enable unknown sources and aps2sd
Click to expand...
Click to collapse
Optional Addons Must be completed after every rom flash to retain effects.
Enable Swap
**Note** Each location on a flash memory card can only be written to so many times before it stops working correctly. Since swap will cause the swap partition to be written to frequently, there is a potential issue of wearing out part of a flash memory card. If a card wears out while using swap, your system will malfunction and crash.
Wear leveling is a mechanism that distributes write wear uniformly over the entire memory card by dynamically remapping logical memory blocks to different physical memory blocks over time. This largely alleviates the issue of card wear when using applications such as swap that tend to write to the same memory blocks over and over.
Anecdotal reports on the 'net indicate that most Class 6 microSDHC include hardware wear leveling, while Class 4 and lower cards typically don't. A-Data and Transcend Class 6 cards were specifically cited as having hardware wear leveling. Many people have used these cards for swap without issue. In the end it is your decision on whether you want to take the risk of running swap. Many respected developers here recommend you not use it.
http://forum.cyanogenmod.com/index....swap-partition/page__view__findpost__p__30130
Download - http://dl.dropbox.com/u/5702285/G1/86swapon.txt
Edit 86swapon.txt (default at 30 swappiness)
Copy to SD card
In terminal:
su
mount -o rw,remount /system
cp /sdcard/download/86swapon.txt /system/etc/init.d/86swapon
chown 0:2000 /system/etc/init.d/86swapon
chmod 755 /system/etc/init.d/86swapon
sync
reboot
*Verify by typing "free" in terminal (swap will show values instead of "0")
To disable swap do the following:
su
mount -o remount,rw /system
rm /system/etc/init.d/86swapon
sync
reboot
Click to expand...
Click to collapse
Enable JitFix
http://forum.cyanogenmod.com/index.php?/topic/2910-jit-installeruninstaller-script-507t3-updated/
Download - http://dl.dropbox.com/u/5702285/G1/JIT-Install.zip
Extract JITFIX folder to SDCard
In terminal:
su
sh /sdcard/JITFIX/install
after installation is complete you will be asked if you want to install the fix as well
just type Y and hit enter
the next line will ask where your dalvik-cache is located
Type S for SD card
*verify by typing "dalvikvm -h" in terminal (last line will contain "WITH_JIT")
Click to expand...
Click to collapse
Enable OverClock
http://forum.xda-developers.com/showthread.php?t=679033
Download - http://fromhindsight.com/crap/overclock_update.zip
In recovery apply zip
Download SetCPU
Open and set auto detect.
Set max to no higher than 652800
Min works good at 480000
*These are general settings. You can find a more in-depth conversation about what good settings are at the link above.
SetCPU
Market link above for donate. Free for XDA members here
Click to expand...
Click to collapse
Facebook Account Sync
http://forum.xda-developers.com/showthread.php?t=679572
Facebook from market breaks sync for Market users. Firerat has posted a great patch file for fixing this issue.
Download - http://forum.xda-developers.com/attachment.php?attachmentid=325544&d=1273702838
Copy to SDCard
In terminal:
su
sh /sdcard/fr-patch132.txt fb
Go into Facebook app and edit settings for sync
Click to expand...
Click to collapse
Thanks for this guide!
What's this for?
echo 255 >/sys/class/leds/blue/brightness;
yokonunz said:
What's this for?
echo 255 >/sys/class/leds/blue/brightness;
Click to expand...
Click to collapse
Led will turn blue after settings swap on startup. (Will be reset later in the startup process)
Enable Facebook Sync
To enable Facebook sync use firerats script: http://forum.xda-developers.com/showthread.php?t=679572
su
sh /sdcard/fr-patch132.txt fb
Click to expand...
Click to collapse
fonzie123 said:
Led will turn blue after settings swap on startup. (Will be reset later in the startup process)
Click to expand...
Click to collapse
As Fonzie stated, it makes your led turn blue during startup. This lets you know that the script file is being run. You can safely remove that section if you do not need to notification. I just like having it there.
fonzie123 said:
To enable Facebook sync use firerats script: http://forum.xda-developers.com/showthread.php?t=679572
Click to expand...
Click to collapse
Thanks for that. I'll add it to the guide.
Should be on Cyanogenmod wiki where it belongs
xaueious said:
Should be on Cyanogenmod wiki where it belongs
Click to expand...
Click to collapse
I can throw it on there as well, but I think it belongs here as much as it does there. xda-dev forums are here to help all, and have a much larger user base. A large number of g1 users here use cyanogen. And besides a lot of this can be used for other roms as well. It's simply a quick reference guide to help people out.
To be safe, if you already have the newest radio 2.22.23.02, I say DOWNGRADE to 26i. That way when you're flashing the Danger SPL you decrease your chance of getting a brick.
I know thins because I accidentally bricked my friends G1 because he had the newest radio(2.22.23.02) when I flashed Danger over it..
I wouldn't know how to write out the steps so if you kindly would.
And if you already have 26i whoopy dooo for you less work.
AustinAce said:
To be safe, if you already have the newest radio 2.22.23.02, I say DOWNGRADE to 26i. That way when you're flashing the Danger SPL you decrease your chance of getting a brick.
I know thins because I accidentally bricked my friends G1 because he had the newest radio(2.22.23.02) when I flashed Danger over it..
I wouldn't know how to write out the steps so if you kindly would.
And if you already have 26i whoopy dooo for you less work.
Click to expand...
Click to collapse
That advice is false.
What does prevent accidents when flashing radio is flashing in fastboot
xaueious said:
That advice is false.
What does prevent accidents when flashing radio is flashing in fastboot
Click to expand...
Click to collapse
I'm talking about the SPL. When I flashed Danger over 2.22.23.02 I bricked my friends phone.
What xaueious means is that flashing a radio or SPL through recovery has been proven dangerous. We don't fully understand why, but we do know that you run close to 0 risk if you flash through fastboot instead. Danger has been shown running on old 1.x radio's before, only if they are flashed through fastboot.
mejorguille said:
What xaueious means is that flashing a radio or SPL through recovery has been proven dangerous. We don't fully understand why, but we do know that you run close to 0 risk if you flash through fastboot instead. Danger has been shown running on old 1.x radio's before, only if they are flashed through fastboot.
Click to expand...
Click to collapse
Oh hahaha alright I get it thanks for clearing that up for me.
Sorry! Process System is not responding
i don't know what i have done to the phone. since i flash cm5-t5, i get warning "Sorry! Process System is not responding" everytime I reboot the photo and then unlock it. I did try to wipe and flash back to cm5-t4, i still get the same warning.
xaueious said:
That advice is false.
What does prevent accidents when flashing radio is flashing in fastboot
Click to expand...
Click to collapse
Thanks for the info Xaueious. I looked more into this and found the following:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader
I will be updating my reference guide here shortly to reflect this information.
Great guide i just placed it in the bible
Royalknight6190 said:
Great guide i just placed it in the bible
Click to expand...
Click to collapse
Thanks Royalknight. I figured some people could get some use out of it. And it helps me update my procedures as people kindly let me know of better ways to do things.
sagementor said:
i don't know what i have done to the phone. since i flash cm5-t5, i get warning "Sorry! Process System is not responding" everytime I reboot the photo and then unlock it. I did try to wipe and flash back to cm5-t4, i still get the same warning.
Click to expand...
Click to collapse
So you had test 4 running good, and flashed test 5 over it correct? No other changes? Upon booting up when you attempt to unlock you get the above error message?
i don't remember. i can eliminate the problem by swipping the ext partition. however after i add back some apps, the problem appears again.
UPDATE: Posted more info in the Misc Android Development section - here.
Hi all, sorry if this is the wrong place to post but hopefully someone else with a rooted Sharp ADS1 can test this out, or even find this usefull - its been working for me for a few days so far and I'd like to share for testing.
I extracted the stock recovery image, used the clockworkmod builder site and have a (mostly) fully working CWM 6 for that device. I've been using it for about a few days, and it works nicely. It wont mount the USB storage on mines, the device was rooted with SuperOneClick.
Started when I saw a youtube video on how to get it into the stock recovery screen (hold Power and Sym while booting).
I was able to make a nandroid backup of my image, I already removed some bloatware from the device. I'm working on a CWM flashable zip of what I have, maybe someone else can do a fully stock image (mines is missing a few bits for a factory-reset).
I also extracted images of the all partitions on the device. I'm working on getting CyanogenMod (working with CM7 at the moment) running on this thing, still trying to figure what to compile it as lol. I managed to get the Kernel to compile, but I'm working on getting a Gingerbread ROM to use with this device.
Specs I noticed on this:
MSM7227/MSM7x27 cpu
Adreno 200 GPU
512MB RAM, 512MB ROM (200-ish accessible by user)
Hardware Keyboard
WiFI/Bluetooth/etc..
Wondering if theres a similar device I can try using their ROM and testing the zImage I compiled.
QUICK N DIRTY INSTRUCTIONS:
-Device must be rooted (use SuperOneClick 2.3.3)
-Copy the flash_image and CWM recovery image for the ADS1 onto the root of your SDCARD (to make things easy for now)
-Using ADB I remounted the sdcard by running the following (otherwise, you'll get permission denied even with/as root)
Code:
mount -o remount,exec /dev/block/vold/179:1 /sdcard
-I used flash_image from my sdcard (pushed it with ADB in Ubuntu), I took the CWM recovery.img file and also pushed that to the sdcard.
Code:
cd /sdcard
./flash_image recovery /sdcard/recovery.img
reboot
-As the phone reboots, hold Power and Sym and it should take you to the CWM Recovery screen after it blinks once.
Now you can do backups/restore images, clear dalvik, battery stats. Only thing that didnt work for me was mounting USB mass storage via Advanced menu. Once you get it installed, do a nandroid backup asap!
LINK TO CWM FILE (contains stock recovery.img, flash_image and clockworkmod in the CWM folder).
here
file is packed with 7zip.
I have more info on my findings on this lil device incase anyone is interested including partition mounting, etc.. root info recovery and system dump info also some random notes on the kernel.
I'm using this as a learning experience/hobby, and I'd like to share incase anyone was wondering what makes this thing tick lol. Have a nice day all!
EDIT:
heres a pic of mines booting into CWM for inspiration
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
system and nandroid backups
Didnt wanna wait to edit, but heres img files for all partitions on froyo - and here's a nandroid backup (should boot, but do a factory reset/wipe data/cache and dalvik in CWM and you''re like new).
Also, the new boot.img and splash,img flash when I put em in a CWM zip however no boot with a "quick" ported GB CM7 rom (still waiting for repo sync to finish ) - flashed a zte v9 as the hardware was similar (even running the grab proprietary files grabbed almost EVERYTHING - there were a few that were off). Hopefully someone can find this interesting for the device. There's a few others that looked promising, I'm taking a break for now tho lol
UPDATE:
Tried using a ROM kitchen to play with the stock rom, didn't work too well lol. I managed to restore a nandroid, but WiFi keeps showing as an error (think it may have had something to do with an option for tethering/wifi that I thought I said No to in the Kitchen's menu...). Also , the signed ROM from the Kitchen seemed to BJork the SuperUser/Root - gonna try flashing a SuperUser CMW zip (3.x)
Also, even with experimenting different roms - CWM is typically accessible via Power + Sym combo. No luck with ro.secure=0 in the stock boot.img - hopefully someone with more experience can help get something running on this lil thing. I'll keep moving forward anyways, have a few ideas of things to try out - albeiit somewhat limited, it's a start . Hope this is usefull to anyone trying to mod this sucker.
UPDATE:
Wifi's back, typing from the device. Restored to a old backup using CWM, on reboot toggled airplane mode and was able to see and join my SSID.
(another) UPDATE:
Looking at other models that seem to have similar hardware, Commtiva Z71, Spice MI300 and ZTE v9 (they have the MSM7227 600MHz/Adreno 200 GPU combo - other specs are very similar). Not sure what they have for sensors, etc.. but I found the ones on the ADS1
Code:
Sensors:
BMA150 Acceleration Sensor: 0.2mA by Bosch Sensortech
MS-3C (YAS529) Magnetic SEnsor: 4.0 mA by Yamaha Corp
MS-x Orientation Sensor: 0.0 mA by Yamaha Corp
ISL29011 Light Sensor: 0.0 mA by INTERSIL
ISL29011 Proximity Sensor: 0.0 mA By INTERSIL
random info from the "features" of the phone (build.prop related?)
Code:
Features:
android.hardware.location.network
android.hardware..wifi
android.hardware..telephony
android.hardware..location
android.hardware..touchscreen.multitouch
android.hardware..sensor.compass
android.hardware..camera
android.hardware..bluetooth
android.hardware..sensor.proximity
android.hardware..microphone
android.hardware..sensor.light
android.hardware..location.gps
android.hardware..camera.autofocus
android.hardware..telephony.gsm
android.hardware..sensor.accelerometer
android.software.live_wallpaper
android.hardware..hardware.touchscreen
glEsVers=2.0
Build Info/Kernel Config from Device.
I've attatched the system.info.gz and config.gz for the stock kernel dumped from my own device.
As far as some ROM testing I did earlier, CyanogenMod 6 for the Z71 (using the Sharp ADS1 boot.img) actually makes it past the Sharp logo and goes to the CyanogenMod boot animation, it stays there but its trying to load something lol. (Luckily I have a few nandroid backups, so flashing back to my previously rooted setup seems to work).
Maybe if I can find something that can work with this setup, then I can look at that device for something to base off to work with CM7. Fun learning experience so far. Going to try a ZTE V9 rom with the Sharp boot image and see what results from that (just trying to see what makes it past the initial boot logo). Might try swapping the build.prop in and see if that does anything lol (using the CM6 keys in their build.prop).
I'm guessing for the CM7 source (or AOSP), I'd have to find a device/manufacturer/device that I can base off for a working sharp/ads1 folder grabbing the needed proprietary files and libs.
Sharp fx plus no clockworkmod
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
rrkevon said:
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
Click to expand...
Click to collapse
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
AmauryRR said:
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
Click to expand...
Click to collapse
Thanks. I'll see if i can
rrkevon said:
Thanks. I'll see if i can
Click to expand...
Click to collapse
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
AmauryRR said:
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
Click to expand...
Click to collapse
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
rrkevon said:
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
Click to expand...
Click to collapse
From what I remember, the recovery itself had to be modified to allow unsigned roms to work - Signing it yourself, I'm not sure if it'll give the recovery the "signature" its expecting.
nstewart said:
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
Click to expand...
Click to collapse
Yeah, I had to drop my site for a while - I host it myself as a hobby with whatever I have to spare, and unfortunately funds weren't right. Just started a new job, so hopefully I'll be able to get my old site back up.
If you're running linux, IIRC you have to make sure the udev(?) permissions are correct for the device/user. Been a while, so bear with me lol (haven't had this phone in a while, since sharp wasn't helping with the source) - alternately, I think you can try running adb as root (sudo adb kill-server, then sudo adb) and it should recognize the device in terminal.
I can host the stuff for you if you want.
Sent from my SHARP-ADS1 using xda app-developers app
NabiRootXD v2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible
Weeee more Easter goodies haha.
thanks aicjofs
Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time
Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?
aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?
I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.
ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?
i am trying to get this tablet to use my network opendns settings and web filters
Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.
Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.
yup getting the dead droid
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse
aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.
This thread intends to be a general thread for all things about the NuVision Tablet. The aim is to help other users of this tablet to be able to root their device, get a temporary recovery and to unbrick their device. I will add the guides for the following posts below in time. This would not have been possible without help from @andrei_kr.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Technical Specifications:
Display: 8-inch IPS HD capacitive touchscreen
Resolution: 1280 x 800
Operating System: Android 4.4 Kit Kat
Processor: Intel® Atom Processor
Memory: 1GB DDR
Storage: 16GB
Micro SD Card Slot: Yes, expandable up to 64GB
Camera - Rear: 2MP
Camera - Front: 2MP
Audio: 3.5mm stereo jack with microphone
Wireless: Wi-Fi 802.11 b/g/n
Bluetooth: Bluetooth 4.0
Battery Type: Rechargeable lithium-ion
Battery Life: 6+ hours; results will vary based on usage and settings
Port: Micro USB
Sensor(s): Accelerometer
Backup/Root/Recovery
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
How to backup of your stock ROM, install CWM and Root your device.
Requirements
ADB/Fastboot Drivers
Intel Android USB Drivers
SDcard (8GB of higher)
Temp recovery script
SuperSU
Steps
Download and unpack IntelAndroid-FBRL-07-24-2015.7z
Power off tab.
Hold Vol+ and press Power on the tab 5-10 seconds
You can see logo about 10 sec and after that DROIDBOOT will load
Connect USB cable to PC
Run launch.bat from IntelAndroid-FBRL-07-24-2015 folder
Type ACCEPT and press Enter
Type 5 and ENTER (cwm.zip)
Type T3 and ENTER (or T4)
CWM will load after 10 sec.
Select backup to external sd card.
After the backup is complete, copy it to the PC to ensure it's safe.
Follow steps 1-10 again and go to install zip from sdcard or external and select the SuperSU zip file and flash it.
NOTE: DO NOT FLASH ANY ROMS WITH THIS RECOVERY IT IS ONLY TEMPORARY. I DID NOT TEST XPOSED SO BE CAREFUL.
Credits
@andrei_kr
@social-design-concepts
@vampirefo
@Chainfire
Unbrick your Tab!
To unbrick your device all you simply have to do is go back to the CWM and restore your backup that you created earlier. If you don't have one, here is a copy of a working backup ---> Google Drive. Credits to @andrei_kr, say thanks!
How to fix touch!
If you unbricked your tablet and your touch isn't working, there is no need to worry. @andrei_kr has provided a guide on how to fix that touchscreen. Credits to him.
NOTE: If your touch is working then do not try this, it will mess up your touch!!
You probably got this touchscreen issue by flashing a different kernel with incorrect drivers.
Now your configuration is likely to differ from the native. You can view the konifig in command prompt or in the terminal :
Code:
cat /proc/gt9xx_config
(only mtk) or using the gtp_tools apk (it is in the attached file below).
It starts with the byte sequence: 0x41 0x1C 0x02 0xC0 0x03
0x41 - 65 version
0x1C 0x02 - 540 horizontal resolution
0xC0 0x03 - 960 vertical resolution
Touch must somehow work to press the button, if there is support otg, then it's easier, you can connect a mouse.
1. Install the gtp_tools_v2.6_20140126_special.apk
2. Go to the option Firmware update. Click refresh, see IC Version: 913_1020 then touch GT913 firmware and 1020.
3. Go to the option Config Settings, press read, the data were considered. Under Normal Config we have:
65 version
540 horizontal resolution
960 vertical resolution
4. Click browse, select click browse to the native config.
5. Native configuration take from your device, in the same paragraph, press the save (saves the backup config file). Native configuration for Fly IQ446 in the attached file. Press send.
6. If nothing has changed, look at the version you have and native config. Then change the version of the file in the native config in your hex.
Example: 0x41 = 65 home, a stranger 0x49 = 73 => replace the 0x41 to 0x49.
Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk (711.77 KB)
Number of downloads:
11,141,690 in total · 8,610 in the last 24 hours
MD5 checksum:
de4f0dc569f96dbcc5668d40fa76040b
Uploaded on:
Tuesday, May 20, 2014 - 21:59
Changes:
- Fixed a crash with some apps (Disa, Rdio)
- Some minor UI improvements
- A few translation updates
Now either use an android terminal emulator or ADB and run these commands
1. su
2. echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
3. chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
Now you can install the Xposed framework.
max0r4axor said:
Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk .
Click to expand...
Click to collapse
Thanks for report.
First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?
Jingbadguy said:
First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?
Click to expand...
Click to collapse
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?
kirito9 said:
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?
Click to expand...
Click to collapse
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...
Jingbadguy said:
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...
Click to expand...
Click to collapse
Oh I thought they were working. Follow the procedure above to fix.
NuVision TM101A510L
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry
Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...
ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)
williamglick said:
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry
Click to expand...
Click to collapse
I think the models numbers are specific so I can't say for certain that this will work with your tab. Try the fastboot/rooting procedure first and then maybe you can just restore the system partition only not corrupting the boot/kernel.
Unidave199 said:
Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...
Click to expand...
Click to collapse
You're welcome. I waited months also before finding a working backup.
Jingbadguy said:
ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)
Click to expand...
Click to collapse
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?
kirito9 said:
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?
Click to expand...
Click to collapse
ill let you know just as soon as i can get back to working on those devices... im prety sure if memory serves correctly, that I was getting some errors regarding unable to mound sd or ext sd. I could be wrong but thats what comes to mind.
Im up to my neck in jobs on other devices. (rooting galaxy S5, changing imei on another S5, IMEI change on a LG Stylo 2 plus, Galaxy Tab 2 system issues need to diagnose, and several screen and lcd replacments)
STUCK
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?
after ive flashed super su, when i go to restor the working backup i see a list of backups... including yours but when i select it i always get :
checking md5 sums...
md5 mismatch!
what now?
(i tried just flashing the boot but even that comes back with same error)
I know on other devices the recovery is an img file any the one you provide is a rar... i extracted to my desktop and was gonna try flashing with abd/fastboot but since its not an img file, im thinking it wont work...
any thoughts?
Im still unsure how to flash the recovery that u supply in the section for fixing bootloop....
Jingbadguy said:
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?
Click to expand...
Click to collapse
The too many links error is common for this device. Touch doesn't work with TWRP on this device so CWM is out only go. You can root and using cwm like any other root method.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Proudly Presents
Another Exclusive Release
Supported Model
UMX U696CL
Recoveries
TWRP_11 Recovery
Roms
GSI Roms - Arm32 Binder64 Required
AssuranceRom Custom Stock * WIP *
-AIO ToolKit Prerequisites-
1- Linux: Linux Mint Cinnamon Suggested
2- Python 3
Rom Notes/Disclaimer/Warning
* WIP *
Contributors
@gregeerg / BVK - for using his device as a ginuea pig to make this happen
@AndyYan - for his GSI knowledge and wisdom
@deadman96385 - for uploading dumped files to github
@Jet! - for flashing twrp and dumping stock super image
Big Thanks To The Folks In My A-Team Telegram Group
Big Thanks To The Folks Who Have Come To The A-Team Telegram Group To Help Test
Device Downloads
UMX U696CL Downloads
Recovery Device Trees
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions
-Updates-
5-18-2022- Initial AIO ToolKit v0.01 Release
I don't have telegram, is there anywhere else I can download some of this stuff from?
Thanks..
karl615 said:
I don't have telegram, is there anywhere else I can download some of this stuff from?
Thanks..
Click to expand...
Click to collapse
No sir, I don't put out untested stuff. I've gotten 0 feedback on the toolkit
How do we get feedback if no one can download here? we are not forcing anyone to install tiktok whatsapp instagram facebook telegram or any other crappy pipapo, keep development on xda-developers. Think about it
aIecxs said:
How do we get feedback if no one can download here? we are not forcing anyone to install tiktok whatsapp instagram facebook telegram or any other crappy pipapo, keep development on xda-developers. Think about it
Click to expand...
Click to collapse
I left a download link, unsure what you mean. If XDA would allow me to upload a 1.7gb 7zip file I would but that's not reality. I need stuff tested and chat to be fluid and prompt. That's not possible on a forum. In reality, If I had the device, I could test in 1 day what it would take a week to do on Telegram or 3 months to do on XDA forum. So for getting things done in a timely fashion, Telegram is my go to. I've been a member of XDA since 2012, I've done my time. If people don't want the toolkit or if joining telegram is too much, that's fine, not the people I want to help me test my software then anyways. The people who just want to grab a download and go can wait for the rest of the backend process. Again, I don't even have this device. So why am I even doing this is what i'm now wondering. I guess next time someone comes to me with a untouched device I won't help and use my resources to get something going....
it's alright though, you can consider this project shelved as I have a different hands on device I've already moved on to. Enjoy the twrp I built for you guys!.....
PizzaG said:
I left a download link, unsure what you mean. If XDA would allow me to upload a 1.7gb 7zip file I would but that's not reality. I need stuff tested and chat to be fluid and prompt. That's not possible on a forum. In reality, If I had the device, I could test in 1 day what it would take a week to do on Telegram or 3 months to do on XDA forum. So for getting things done in a timely fashion, Telegram is my go to. I've been a member of XDA since 2012, I've done my time. If people don't want the toolkit or if joining telegram is too much, that's fine, not the people I want to help me test my software then anyways. The people who just want to grab a download and go can wait for the rest of the backend process. Again, I don't even have this device. So why am I even doing this is what i'm now wondering. I guess next time someone comes to me with a untouched device I won't help and use my resources to get something going....
it's alright though, you can consider this project shelved as I have a different hands on device I've already moved on to. Enjoy the twrp I built for you guys!.....
Click to expand...
Click to collapse
Appreciated..
Update: flashed the recovery using 'fastboot flash recovery /path-to-.img' and the recovery works fine as far as I can tell, but the system is gone. Or something is up anyway, I can't get it to boot normally.. only to recovery. What did I do wrong?
Sorry Pizza i havent had the time to give feedback on it but i have the same issues booting. please dont let one person ruin it for everyone. i will hyu on telegram later today
PsYk0n4uT said:
Sorry Pizza i havent had the time to give feedback on it but i have the same issues booting. please dont let one person ruin it for everyone. i will hyu on telegram later today
Click to expand...
Click to collapse
Actually i havent had the time to get my linux machine setup correctly because of a memory leak issue that kept crashing my system but i finally got it running stable. i tried using relive on virtualbox but couldnt get it working properly due to driver issues in the host OS on this windows machine and for some reason i had more than one python version installed causing me conflicts. i ended up just using adb to flash the images and the phone no longer boots. i want to test it on a native linux os first
Well, folks...I'm about to give this a go....I still have a BLU View 3 to root today. Much gracias for all the effort
Cinephile 74 said:
Well, folks...I'm about to give this a go....I still have a BLU View 3 to root today. Much gracias for all the effort
Click to expand...
Click to collapse
Well I seem to have faux pas along the way.... bootloader unlocked easy-peasey. But I can't get fastboot to flash TWRP no matter what directory I use....RELP!
Is this the ROM or the bootable zip?
I'm back and about to try this again with an actual thumb drive with the ReLiveDVD on a thumb drive now that I have one
I downloaded A-Team-UMX_U696CL_AIO_ToolKit-v0.01.7z from the tg group and here's my feedback. I don't mean to sound ungrateful but:
Root does not work. I opened Main_Menu.sh and the root option literally does nothing. The lines are commented out and the image it was supposed to flash doesn't exist. Bootloader unlocking works (seems to literally be a single fastboot command i.e. "fastboot flashing unlock", seems like the new "oem unlock") and TWRP does work, but only once. If I flash it in fastboot and immediately reboot to recovery from there, I can get in. If I try to go to recovery after restarting, I get the dead android with the red ! triangle saying "no command". TWRP won't mount data (I think it said it couldn't decrypt, but I don't even have a lock code on it) so you need a micro sd to store the boot.img in order to patch it in Magisk. It would've been nice if you included it, though it seems you intended to but haven't gotten around to it since it's only v0.01. Still, it's not much of an all-in-one if it can't do the primary thing most people will want from it. I do fortunately have micro sd cards so I was able to save (manually in TWRP terminal using dd, annoying as hell on a touchscreen, can't even type "=" without going through 2 keyboard menus) and patch it in Magisk and now do have root working.
I don't understand why this requires Linux. The AIO doesn't do anything you can't do in Windows. The Python file is just an ASCII logo that makes you wait 10 seconds for no reason. It would have more user friendly as just a bunch of separate partition IMG uploads and instructions. I wish I had actually looked at the shell scripts beforehand instead of downloading a Linux distro and booting it as a live cd. If you make a new version, consider just including a portable adb/fastboot with it and skipping Linux/Python since it's not necessary.
After googling the "no command" screen, I held down power and pressed volume up and got into the regular Android recovery. So despite the bootloader being unlocked, it appears TWRP got overwritten by the default recovery. I flashed TWRP at least 3 times, immediately entering TWRP each time afterward, but it never stuck.
I'm attaching my Magisk'd boot.img in case anyone else gets stuck at that part. If anyone chooses to use it, MAKE YOUR OWN BACKUP FIRST, obviously. I'm not responsible for anything that happens using that file.
Eric janaika said:
TWRP does work, but only once.
Click to expand...
Click to collapse
proof that TWRP works for you, anything beyond is usage problem.
aIecxs said:
proof that TWRP works for you, anything beyond is usage problem.
Click to expand...
Click to collapse
I got twrp to stick but could not do anything with it since I didn't have an SD card before I misplaced the phone. Yes the scripts unfinished but as stated above somewhere, the dev did not have a device to test on.
If you wanna help, and it's probably the only way anyone else who isnt so knowledgable as many visiting xda seeking a way to root their device is gonna get this finished as well, please consider joining the telegram chat and contribute to this forum whatever you learn. Maybe Pizza will still be interested in helping. I tried but somehow misplaced the phone in the middle of filling in my huge gaps of knowledge on the subject.
I could not mount or wipe /data in twrp and even flashing the super.imgwould not allow me to boot because I was unable to do anything with the data partition. Had to flash the stock recovery to get it to boot period.
Maybe twrp will get you root if you patch your boot image with Magisk and flash it in twrp.
I'm not sure what else could be done. And not even sure that would work without being able to mount /data.
It's really hard for anyone working on a device they don't have to finish the work without some feedback from people who have enough knowledge to give them useful feedback.
The unlock bootloader option and the flash twrp recovery options work.
Script could be finished but I doubt there's much motivation for them since th3y don't own the device.
But the script is there. Most of the work on that part is done.
would only take some contributions by interested people.
PsYk0n4uT said:
I got twrp to stick but could not do anything with it since I didn't have an SD card before I misplaced the phone. Yes the scripts unfinished but as stated above somewhere, the dev did not have a device to test on.
If you wanna help, and it's probably the only way anyone else who isnt so knowledgable as many visiting xda seeking a way to root their device is gonna get this finished as well, please consider joining the telegram chat and contribute to this forum whatever you learn. Maybe Pizza will still be interested in helping. I tried but somehow misplaced the phone in the middle of filling in my huge gaps of knowledge on the subject.
I could not mount or wipe /data in twrp and even flashing the super.imgwould not allow me to boot because I was unable to do anything with the data partition. Had to flash the stock recovery to get it to boot period.
Maybe twrp will get you root if you patch your boot image with Magisk and flash it in twrp.
I'm not sure what else could be done. And not even sure that would work without being able to mount /data.
It's really hard for anyone working on a device they don't have to finish the work without some feedback from people who have enough knowledge to give them useful feedback.
Click to expand...
Click to collapse
what do you need a script for? read any random TWRP install guide steps are more or less same
- unlock bootloader
- patch avb/dm-verity/vbmeta
- install TWRP
- makesysrw super.img (optional)
- disable encryption (optional)
PsYk0n4uT said:
The unlock bootloader option and the flash twrp recovery options work.
Script could be finished but I doubt there's much motivation for them since th3y don't own the device.
But the script is there. Most of the work on that part is done.
would only take some contributions by interested people.
Click to expand...
Click to collapse
Agreed. PizzaG has done a bang up job with his UMX U696CL offerings, and his knowledge is extensive regarding custom ROMs and recoveries.
Eric janaika said:
I downloaded A-Team-UMX_U696CL_AIO_ToolKit-v0.01.7z from the tg group and here's my feedback. I don't mean to sound ungrateful but:
Root does not work. I opened Main_Menu.sh and the root option literally does nothing. The lines are commented out and the image it was supposed to flash doesn't exist. Bootloader unlocking works (seems to literally be a single fastboot command i.e. "fastboot flashing unlock", seems like the new "oem unlock") and TWRP does work, but only once. If I flash it in fastboot and immediately reboot to recovery from there, I can get in. If I try to go to recovery after restarting, I get the dead android with the red ! triangle saying "no command". TWRP won't mount data (I think it said it couldn't decrypt, but I don't even have a lock code on it) so you need a micro sd to store the boot.img in order to patch it in Magisk. It would've been nice if you included it, though it seems you intended to but haven't gotten around to it since it's only v0.01. Still, it's not much of an all-in-one if it can't do the primary thing most people will want from it. I do fortunately have micro sd cards so I was able to save (manually in TWRP terminal using dd, annoying as hell on a touchscreen, can't even type "=" without going through 2 keyboard menus) and patch it in Magisk and now do have root working.
I don't understand why this requires Linux. The AIO doesn't do anything you can't do in Windows. The Python file is just an ASCII logo that makes you wait 10 seconds for no reason. It would have more user friendly as just a bunch of separate partition IMG uploads and instructions. I wish I had actually looked at the shell scripts beforehand instead of downloading a Linux distro and booting it as a live cd. If you make a new version, consider just including a portable adb/fastboot with it and skipping Linux/Python since it's not necessary.
After googling the "no command" screen, I held down power and pressed volume up and got into the regular Android recovery. So despite the bootloader being unlocked, it appears TWRP got overwritten by the default recovery. I flashed TWRP at least 3 times, immediately entering TWRP each time afterward, but it never stuck.
I'm attaching my Magisk'd boot.img in case anyone else gets stuck at that part. If anyone chooses to use it, MAKE YOUR OWN BACKUP FIRST, obviously. I'm not responsible for anything that happens using that file.
Click to expand...
Click to collapse
Did you flash this from fastboot or from twrp?