Database Info

00028002: Not able to downgrade to RC7 on Singapore HTC dream

OK, after 3 hours investigation, I stopped trying.
My Phone is a Singapore HTC dream(SingTel), with version:
Model Number: HTC Dream
Firmware version: 1.1
Baseband version: 62.33.20.08U_1.22.14.11
Kernel version: 2.6.25-01845-g85d4f0d [email protected] #27
Build number: dream_stg-user 1.1 STG-RC8 128394 ota-relkeys,release-keys
I have tried:
- Format SD(the default 1GB Transcend micro sdcard) to Fat32, both on Mac OSX leopard and Windows XP;
- copy the RC7 DREAIMG.nbh on the sdcard. (also tried different case combination, like DREAMIMG.NBH, DREAIMG.NBH; and tried the similar step using RC29)
- restart using Camera + POWER(with the USB connected, and without the USB connected)
- I saw the rainbow screen, after 1~2 seconds, I saw message "loading", then "checking", then get 2 messages in red: "00028002", "Not Allow"
I've checked thru nearly all the related posts here, and Google. It seems that I am the only fool who face this problem...I hope this is stupid problem that could be easily fixed by a small typo...
Any one experience same issue and overcome successfully? I just want to upgrade to Cupcake 1.5 and get stopped at the very first step...

you cannot do so because that RC29 is for US G1s.. Read the thread on the Singapore user group for the specific step by step instruction for you to get root access for your Singtel Dream.
http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2

u can check the latesr comment in this post. i followed this guide, and running on ADP1.5Hr3 now
http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2

Thanks chuazy and sencorde. I am trying that solution now.

Read this thread: http://forum.xda-developers.com/showthread.php?t=485364
The Transcend 1GB microSD card that comes with the SingTel Dream is crappy. I couldn't write the goldcard.img onto the card without making it unreadable and requiring a format again. It seems that many SingTel Dream users seeking to root their phone faced this issue (see hazeline's post). Everything went without a hitch once I tried the procedures stated in the above thread with a new microSD card (Kingston 4GB Class 4, S$19.90).

ok, I stopped here...Will go to buy a Kingston microSD tmr...
My the other side question is, why is so crappy to downgrade a Singapore based HTC dream? it seems that (in this forum) the US/UK based phone can skip this 27 steps approach to make a downgrade and get rooted...

It is because there are no previous firmware versions of the Singtel build that you can recover to, and they are not rooted. Previous firmware of US and UK G1 are rooted (anything before UK RC8 and US RC30) so you can go into recovery mode and recover previous rooted firmware for that region (and then do whatever you want with it).

wonder if anyone in SG provide rooting service , me is a noob lol
dom't mind paying a norminal sum

kaninabu said:
Read this thread: http://forum.xda-developers.com/showthread.php?t=485364
The Transcend 1GB microSD card that comes with the SingTel Dream is crappy. I couldn't write the goldcard.img onto the card without making it unreadable and requiring a format again. It seems that many SingTel Dream users seeking to root their phone faced this issue (see hazeline's post). Everything went without a hitch once I tried the procedures stated in the above thread with a new microSD card (Kingston 4GB Class 4, S$19.90).
Click to expand...
Click to collapse
Hi I used the Transcend 1GB microSD card that comes with the SingTel Dream to root my phone, no issue at all.

mechiland said:
ok, I stopped here...Will go to buy a Kingston microSD tmr...
My the other side question is, why is so crappy to downgrade a Singapore based HTC dream? it seems that (in this forum) the US/UK based phone can skip this 27 steps approach to make a downgrade and get rooted...
Click to expand...
Click to collapse
Hi, when i first started to root my Singtel set, I had faced the same issue as yours. It took me 3 days to figure out whats wrong. AT first I suspected the sdcard but I was wrong. Make sure u following the "27 steps approach" from http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2. The goldcard procedure etc... Its important.
An extra point to take note which is not stated is to copy the DREAMIMG-RC7.zip to your sdcard and extract the file from your sdcard to your sdcard.
Hopes the above helps. If not I will try my very best to help u again. Do let us know your results. GOOD Luck and have fun

mechiland, I'm facing the same issue. I'll try the 27 steps tonight when I get home, and post results.

OK, let's take a breath. a deep breath.
IT WORKS! IT WORKS! IT WORKS!
IT WORKS WITHOUT A NEW microSD CARD AND JUST USE THE OLD 1GB Trancent!
Thanks everyone give the warm-hearted help...we SingTel HTC users are not alone.
I exactly followed the 27 steps tutorial this morning for the last time before I went to e-market. And suddenly everything went so smoothly.
One tip I can share:
It's kind of tricky that to get the CID using the terminal, and manually write down the 32 characters is error prone. If you like me, have the latest Android SDK installed, you can use adb shell to get the CID:
Code:
// make sure that the devices is connected (Check USB Debug option on your HTC Dream)
$ adb devices
List of devices attached
HT92DKV01647 device
// go to shell
$adb shell
$cd /sys/class/mmc_host/mmc1
$ls
uevent
subsystem
device
power
mmc1:0002 // <-- you see
$cd mmc1:0002
$cat cid
1b534d303030303010b144ddde008cb8 // <-- it's your cid...
Just copy and paste the CID to QMAT(Thanks), and follow the steps from 4.

will appreciate you guys thank pk for his detailed instructions for the singtel dream on http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.3 =)
pls post any of your tips/advise there, as that is the thread which most Singtel users referred to.

Disco_Stu said:
mechiland, I'm facing the same issue. I'll try the 27 steps tonight when I get home, and post results.
Click to expand...
Click to collapse
Tried, and worked
Cheers!!

YAY! more singtel users joining the hacking party XDXD. However i did not did an extra step in using my another 1gb micro sd brand.
What i did was get my cid code from terminal emulator, then i reversed it using the qmat trail programme and used the hex editor, reading from a windows mobile device did not work for me. I got stuck when downgraded to RC7 because i did nt have a data plan but stupidly i went to activate my data plan in the middle of the night and waste money but thanks to xda community there is a method to skip over the registration.

step 3 i already got problem, might need to get need memory card to try again

No luck
ok, so I tried this process. Didn't get any errors, but still get the 'not allow' message when I try to reboot and downgrade to RC7. Any ideas what might be going wrong? I have an Aust Optus Dream with RC8.
After copy and pasting the info from goldcard.img, I have to reformat my card. Is this undoing the copy?
Thanks
Greg

gjlamb said:
ok, so I tried this process. Didn't get any errors, but still get the 'not allow' message when I try to reboot and downgrade to RC7. Any ideas what might be going wrong? I have an Aust Optus Dream with RC8.
After copy and pasting the info from goldcard.img, I have to reformat my card. Is this undoing the copy?
Thanks
Greg
Click to expand...
Click to collapse
Hi,
I didn't use the original 1GB card that came with the set, the gold card method doesn't seem to work on that, I bought a new 4GB and it works like a charm, running Ravenge R7 now. If after copying the goldcard.img on it, and you are asked to format the card, it means the card cannot be used to convert to a gold card or you had the steps in converting that card wrong (yes the numerous numbers and alphabets got me the first time too)...

gjlamb said:
ok, so I tried this process. Didn't get any errors, but still get the 'not allow' message when I try to reboot and downgrade to RC7. Any ideas what might be going wrong? I have an Aust Optus Dream with RC8.
After copy and pasting the info from goldcard.img, I have to reformat my card. Is this undoing the copy?
Thanks
Greg
Click to expand...
Click to collapse
Foramtting the card means it's wiping it and re-writing the filesystem, so it will delete everything on the card.

Unique problem on rogers HTC dream
Guys
here is the story,
-> i got rogers HTC dream
-> used DREAIMG.NBH to downgrade to RC29, it went smoothly
-> i did factory reset
-> it wont boots up, stucks at G1 screen
-> i pressed CAMERA+POWER button and i got
{
"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"
}
but instead of DREA100 or 110 i got DREA210 (which is for rogers)
-> i formatted card to FAT32
-> loaded again DREAIMG.NBH
-> go to boot mode
-> it says "Not Allow 00028002 Error"
-> i asked big dad (google), n i found that itz carrier ID (CID) mismatch
-> as there is no LEAK of DREAIMG.NBH for canada (rogers), hw can i make my DREAM work??
-> i tried gold card method but same thing
-> i tried DREADIAG.NBH but same thing
-> how can i communicate with my HTC dream through USB cable?? i have original stock SPL of G1...
any ideas??
Thankssssssssss in advance..

[Reference] Stock G1 to Newest CM (5.0.7 Stable)

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.

[Q] How to get dynamic storage (/sdcard ->/data/media) on One S, "Insufficient Space"

[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.

NuVision TM800A510L- General Info (Root, Recovery, Unbrick)

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.

[ROM] ZTE Grand X View 2 (K81) Root and Stock firmware

Stock firmware
Rogers B05 Firmware
https://www.androidfilehost.com/?fid=1395089523397891291
Separate Firehose download
https://www.androidfilehost.com/?fid=1395089523397891292
ZTE Kernel source mirror (We are codenamed Helen)
https://www.androidfilehost.com/?fid=1395089523397891289
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash just boot or recovery use the tool in the 2nd post it is a lot easier

Warning
This is a dangerous tool. It can render your device permanently unusable. If you use it, your warranty will likely be void. You accept all responsibility for the consequences.
Acknowledgments
Special thanks to @tdm for taking the firehose I got and creating the k81tool with it!
Note Well
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Preparation
Download magisks patched boot.img from here.
Download k81tool from here.
Setup your computer.
Setup for Windows
Download zadig.
Boot your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so cancel.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Reboot your device and rerun steps to go back to EDL mode
Booting in EDL mode
Code:
adb reboot edl
Usage
Code:
k81tool.exe <read|write> <boot|recovery> <filename>
Example:
Code:
k81tool.exe read boot stock-boot.img
Code:
k81tool.exe write boot patched_boot.img
Multiple Operations
This is a "one-shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish to perform multiple operations (eg. backup, flash), simply re-enter EDL mode.
Common Problems
Device was not found
First enter EDL mode, then run the tool.
Device is visible in device manager but cannot be found by the tool.
Connect directly to the PC, not through a hub.
Windows says bad file descriptor
The WinUSB driver is not installed.
Once you flash the patched_boot.img all you need to do is install the magisks manager and you will have root enjoy!
Proof of root:
{
"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"
}

Place Holder for TWRP

bad links??
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
edit - I have a couple of questions -As you have been the first to root the device there are obviously no custom firmware builds available so we stick with stock, correct? We will be able to remove the bloatware on stock because it's rooted though, correct? I also use tasker and the AutoApps suite for automation and I need root for some of my tasks so this is a huge step in the right direction. Lastly in order to root the device do we need to do follow all steps in the first post and then complete the steps in the second post? Or is the second post just a different way to do what was done in post 1? I'm excited to root this so thanks for fixing those links! Thanks again for all your work.

ryanoc75 said:
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
Click to expand...
Click to collapse
Sorry about that somehow the links broke, I have updated them so now they are proper.

Hey guys. Having a little trouble. I keep on running into "Failed: unknown error" when I try to flash the patched boot.img that was provided. I managed to read the stock boot image with no problems, but writing just runs into this error.
Thoughts?
I am using the Bell variant so I hope that isn't the source of it

Post Root questions
Hi
I'm about to try to root the device, assuming it goes according to plan, can we then install SuperSU? Do we need a TWRP for the device if we want to install another ROM and are there generic ROMS out there that would work on this tablet? Sorry if these are noob questions, I've been an apple jailbreaker for years and just bought and rooted and installed a custom ROM on a Samsung Galaxy S4. I installed a new android tablet NAV in my BMW and I needed a device to act as a hotspot, so I use Tasker and AutoApps with it to automate the process and it works really well. When I rooted the Galaxy S4 there are a ton of ROMS available for every variant so it was easy to follow the instructions. However, this is totally new territory for me. This device isn't nearly as popular so I wondered what options are available to us once we have it rooted?

same issue failed unknown error
Hi
I am using the Rogers K81 and I am encountering the same failed unknown error when I try to write the patched boot file. I also was able to read the firmware file without issue. I rebooted into edl mode and then tried to write the patched file -
NB - for those who have yet to try, move the k81tool.exe and the patched boot file to your c drive and make sure your at the root of c and then remove the B05 in the patch file name so that it can find the file if you are just cutting and pasting the command line instructions above, otherwise you'll get an error that it can't find the file. If the k81tool.exe isn't in the current directory you are in you will get an error saying k81tool.exe is not a known command ..etc.etc. This might seem obvious to some but for those with little command line experience, it will save you from having to post questions about your errors.

There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?

huaji2333 said:
There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?
Click to expand...
Click to collapse
A friend of mine has the k92, and currently it has a locked bootloader even with the firehose and all. So he is working to find an exploit to allow it to be unlocked. But no ETA at this time.
Sent from my iPhone using Tapatalk

Thank you for providing this. I have the Virgin Mobile device currently. Just a question before I try this. My past experience with a tablet from Rogers a few years ago was that whenever you put a different sim card in, it would force you to reset the entire device. To get around this, I was lucky that there were other generic firmware available for that device. Does the Rogers firmware that you provide force a reset if you change the sim? I'd ideally like to have the option to change sims when traveling. Thanks.

I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?

wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
bridonca said:
I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?
Click to expand...
Click to collapse
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code

Online Gravy said:
wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code
Click to expand...
Click to collapse
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!

bridonca said:
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!
Click to expand...
Click to collapse
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk

any chance of getting Pie GO installed on this thing, mine lags to even tap and the stock settings leave only 400mb free of ram

I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?

s_021 said:
I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?
Click to expand...
Click to collapse
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.

Decided to try the k81tool to just root instead, but I'm getting the same Failed:unknown error as others have posted.
(Using VM stock firmware)
---------- Post added at 11:20 PM ---------- Previous post was at 11:14 PM ----------
If you put in a Rogers sim, does it attempt to do a hard reset or just the usual reboot?
thanks
deadman96385 said:
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse

deadman96385 said:
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.
Click to expand...
Click to collapse
Deleting the files also fails. The error is {ERROR: handleProgram:8615 'ddr.img' not found. You could possibly try --notfiles=ddr.img,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
Adding back ddr.img, the error is
{ERROR: handleProgram:8666 Filesize is 0 bytes. This is usually a mistake!! Please check 'C:\ZTE\rogers\ddr.img'