Database Users

Error: "nandroid-mobile.sh restore" from console!

Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?

lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
Your Nandroid backup was on that SDcard...I don't suppose you saved it before formatting it?

lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
nah. The happens sometimes. Could be your nandroid backup got corrupted or you are low on battery power. Two most common causes. I would make sure the nandroid backup is on the sd card. if so, simply try plugging it in to a power supply. Let us know if you get it working.

All right... I did not want to admit it but I believe what you said is probably true, and I either corrupted or simply deleted the nandroid backup during all the flashing and repartitioning. I am not seeing it at all when I mount the SD card. It crossed my mind a little too late that I should have pulled it off the card.
What are my options here? On the one hand, it is working fine for now. I had just got the Hero earlier that day (did an exchange due to dead pixels and network issues), so it was not like I lost anything important. Is there an easy way for me to go all the way back, such as flashing the original ROM to the phone, and essentially starting over, like I just opened the box and turned the phone on? That way I can do it right from the very beginning. I just worry that in all my partitioning things got scrambled, and I am not seeing the repercussions from it yet, other than Google Maps.

ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
if at first you try and fail.... try try agian

Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?

lorsoblu said:
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
Click to expand...
Click to collapse
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence

johnsongrantr said:
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
Click to expand...
Click to collapse
All right, I am having issues already, from the very beginning.
The RUU ROM .exe will not recognize the HTC Hero. It throws an error 170 at the step where it is trying to pull information from the phone. I think this has something to do with ADB, and the fact the computer did not have the SDK on it. (I originally set up the root with my Mac.)
So, where do I go? I have a Boot Camp partition and another computer both running Windows 7, but my attempts to put the SDK on those computers and then have the phone drivers properly recognized failed on both, and the .exe still cannot complete. Is there something I am missing here, or can I somehow do this on the Mac side? I'll take anything!
Edit: Just cause I can see someone asking, yes, I tried to do this on both of my Windows 7 computers, not the Mac. I recognized that the .exe would not run on OSX pretty quickly.

can you put your phone into fastboot (power+vol down) and get to the point where windows basically sees your phone
what you are looking for is when you type adb devices it shows your hero
fastboot might not work because it's a seperate program but try custom recovery main menu.... enable usb.... or something to that extent
I appologize I don't have my main computer in front of me so I can't tell you EXACTLY where to go
once I do, I'll find which one to hit.... it does work though because I had to do the same thing with my godly preaching of backups :blush:
it's one of the recovery areas though i promise
fastboot will see the hero as the same device as adb will in fastboot
adb will see the hero as recovery device in custom recovery
attempt both of these I'm certain one of these work
if absolutely all else fails.... after you "install" sprint ruu search your computer for rom.zip it should be in your START>RUN>%TEMP% in here somewhere
rename rom.zip it to HERCIMG.ZIP and put it at root of your sd card and boot into hboot and it should automatically find it and press action to flash it

I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.

lorsoblu said:
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
Click to expand...
Click to collapse
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue

johnsongrantr said:
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
Click to expand...
Click to collapse
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!

lorsoblu said:
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
Click to expand...
Click to collapse
glad to be of assistance

johnsongrantr said:
glad to be of assistance
Click to expand...
Click to collapse
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?

lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
you'd think so.... but from my own experience if you do a backup on a partititon then convert it... it screws with the backup and you can't recover from it.... just in case... do 2 backups.... store the normal fat32 nandroid backup on your workstation (the entire nanddroid folder) and copy it back to sd after you convert it to fat32+ext2 .... you'll see what I'm talking about....
I don't quite understand why it does that... but for me I was only successful in recovering from a partition that I made a backup to not copied to (if that makes any sence)
also if you don't want to experiement yet... just leave it fat32... you can always change it later after you see it working (sorta confidence builder before tinkering)

lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
Think about it this way, you do a nandroid backup...it places it on the sdcard.
Then you go and change the format of the sd card (potentially blowing away or corrupting any data on it, including the nandroid backup you just made).
Thus why it's better to do it afterwards (besides, nandroid doesn't back up your sd card, just your phone's OS and such)

solved for me
i had that problem its cuz the back up is brocken get anthoer copy of it if u hav 1 then restore it again it worked for me

Make myTouch 32b Legal Up To Latest 1.6 DMD64

This is a Step-by-Step fool proof guide to getting your T-Mobile myTouch 3g (32b) back to factory firmware with the ability to once again receive all official T-Mobile OTA (Over-The-Air) Updates.
*Note* There are two files named updated.zip that are both needed. We will keep them seperated by two folders needed at two totally different steps during installattion.The fisrt gets us back to 1.6 and the other gets us the newer radios for1.6...and Yes it works. Files are official....Nay-Sayers! LOL
*Note*
Optional SD Card Format
From the settings menu of the phone, Scroll down to "SD Card & phone storage." Press "Unmount SD Card." Next press "Format SD card." If you go this route you will have to reinstall all media you had on the SD Card, i.e. pics, music...etc
STEP 1
Create a Folder named ANDROID on the desktop. In that create 3 sub-folders. Name the 3 sub-folders in this order: Cupcake, Donut Update 1, Donut Update 2
STEP 2
You need a copy of SAPPIMG.img. It puts the phone back to the "Cupcake" or 1.5 Firmware Version.
Download it from:
http://www.mediafire.com/?yezotmjyuww
Save it in the Cupcake folder you just created.
STEP 3
Plug your phone into your PC and click "USB Connected" on the Notification Tab, then mount image. Your PC can now read and write to your SD Card. Find your downloaded copy of SAPPING.img and copy it to your SD Card. Unmount, unplug and power off your phone.
STEP 4
Reboot phone into boot mode by holding down volume down key while pressing the power key. It should boot into HBOOT and automatically run the SAPPIMG.img you just copied onto the SD card Click. Follow the onscreen instructions to initiate the automated update. Use trackball to accept.
If it did not boot to HBOOT, read the screen and do what it says to "Reboot to HBOOT." From there everything else should once again be automated. Follow the onscreen instructions to initiate the automated update. Use trackball to accept. Once the update is done and it says "Installation Complete," reboot by pressing Home and Back buttons together.
STEP 5Once rebooted, do the initial setup. Once setup is complete, plug the phone back into the PC and re-mount the SD Card. It is safe to delete the SAPPIMG.img file from the SD Card now. You can also check to make sure the Firmware Version 1.5 is correct and installed by going to Settings-> About phone.
STEP 6You need to Download the second file needed named update.zip. It gets us back to Android 1.6
Download it from:
http://www.mediafire.com/?t3zlwdzzqqx
Save it in Donut Update 1 folder. Once download is complete, copy the file update.zip to the SD Card like before. Unmount, unplug, and power off the phone.
STEP 7Reboot the phone into recovery mode by this time holding down the Home and Power buttons together this time. A picture with tirangle and phone will show press Home and Power again to get to the actual recovery screen. You now have 2 options to apply this update...either or:
*Note* Use trackball to navigate the cursor in this new menu
1. Apply update.zip from SD Card. This option will leave all user data that you previously put on the phone after the SAPPIMG install, i.e. Contacts, Apps, Settings...etc.
2. Wipe/Factory reset. This option will completely remove all user data from the phone. A clean slate if you will. If you choose this option, when the reset finishes, Make sure you do Option 1 Apply update.zip from SD Card. Once the update is done and it says "Installation Complete," reboot by pressing Home and Back buttons together.
STEP 8
Once rebooted, if you chose option 2 in the previous step you have to redo the initial setup. Plug the phone back into the PC and re-mount the SD Card. It is safe to delete the update.zip from the phone now. You can also check to make sure the Firmware Version 1.6 is correct and installed by going to Settings-> About phone.
STEP 9
You need to Download the third file needed named update.zip. It gets us back the latest radios.
Download it from:
http://www.mediafire.com/?ojnnyrjzneg
Save it in Donut Update 2 folder. Once download is complete, copy the file update.zip to the SD Card like before. Unmount, unplug, and power off the phone.
STEP 10 = Finale
Reboot the phone into recovery mode by this time holding down the Home and Power buttons together this time. A picture with tirangle and phone will show press Home and Power again to get to the actual recovery screen. You now have 2 options to apply this update...either or:
*Note* Use trackball to navigate the cursor in this new menu
1. Apply update.zip from SD Card. This option will leave all user data that you previously put on the phone after the SAPPIMG install, i.e. Contacts, Apps, Settings...etc.
2. Wipe/Factory reset. This option will completely remove all user data from the phone. A clean slate if you will. If you choose this option, when the reset finishes, Make sure you do Option 1 Apply update.zip from SD Card. Once the update is done and it says "Installation Complete," reboot by pressing Home and Back buttons together.
Once rebooted, if you chose option 2 in the previous step you have to redo the initial setup. Plug the phone back into the PC and re-mount the SD Card. It is safe to delete the update.zip from the phone now. You can also check to make sure the Firmware Version 1.6 is correct and installed by going to Settings-> About phone. That is it!
Now you are good to go and are waitng for T-Mobile and their 2.0 or whatever other goodies they decide to throw or not to throw our way.

Didn't work for me. Step 4 did not install. Instead, it said "invalid signature"

Why was this posted? There are about a thousand other threads regarding how to 'unroot' your phone to factory defaults.

sombionix said:
Why was this posted? There are about a thousand other threads regarding how to 'unroot' your phone to factory defaults.
Click to expand...
Click to collapse
So go look at another post! Just that simple.

once you get to cupcake you can just wait a couple hours then you will get an ota update to update to doughnut and the newest radio so i dont see the point in doing all of this work when just isntall cupcake and wait

Great thread! This is much better than waiting for the ota updates!

no ota to 1.6
I have been on 1.5 for 24hrs and no ota back yo 1.6?

Then follow the steps to manually flash the updates from here that is what o did.
Technically I think the updates are only if you have internet with tmobile and can take up to 72 hours.
Sent from my T-Mobile myTouch 3G using XDA App

outlawnunn said:
I have been on 1.5 for 24hrs and no ota back yo 1.6?
Click to expand...
Click to collapse
M9x3mos said:
Then follow the steps to manually flash the updates from here that is what o did.
Technically I think the updates are only if you have internet with tmobile and can take up to 72 hours.
Sent from my T-Mobile myTouch 3G using XDA App
Click to expand...
Click to collapse
Never took me more than 24 hours.
Restoring data with mybackup or titanium backup can actually prevent the update from installing, so if you're not getting it, do a factory reset and don't install anything that isn't from the market until you've received your update.

Does this method also remove the Recovery?
Can I install just the stock rom but keep my recovery? If I do this, will it disable my ability to flash custom roms without re-exploiting the phone?

Thanks phate

I just did this but now I'm stuck at the green android welcome screen with no data service and I'm out of the country. Am I pretty much ****ed? Four corners trick doesn't seem to work. Tried it like a hundred times.

Well this did not work out so well.
Everything seemed to go fine. After the last step, rebooted the phone, and it came up with a picture of a box with an arrow, so I just let it sit there. Came back an hour or so later and the screen was off. No charging light or anything.
Pressed power button and nothing. Tried everything I can think of. So do you think I bricked the phone some how or did the phone just die.
Oh, Battery was fully charged, and it was plugged in while doing the downgrade from CM 6 back to stock.

ziggy34 said:
Well this did not work out so well.
Everything seemed to go fine. After the last step, rebooted the phone, and it came up with a picture of a box with an arrow, so I just let it sit there. Came back an hour or so later and the screen was off. No charging light or anything.
Pressed power button and nothing. Tried everything I can think of. So do you think I bricked the phone some how or did the phone just die.
Oh, Battery was fully charged, and it was plugged in while doing the downgrade from CM 6 back to stock.
Click to expand...
Click to collapse
If the phone refuses to boot you could always apply sappimg.nbh again and this time just let it download 1.6 ota. It only takes about a day or so.

Phateless said:
If the phone refuses to boot you could always apply sappimg.nbh again and this time just let it download 1.6 ota. It only takes about a day or so.
Click to expand...
Click to collapse
Phone won't power on or anything. When plugged in, there is no charging light.
It's just DEAD.
Edit: I've tried two other batteries and another charger also.

Anyone who has used this method to downgrade, or someone using stock firmware, could you enter the phone information menu by dialing *#*#info#*#* tell me what call redirect says, true or false? I want to verify something.

amazinglarry311 said:
Anyone who has used this method to downgrade, or someone using stock firmware, could you enter the phone information menu by dialing *#*#info#*#* tell me what call redirect says, true or false? I want to verify something.
Click to expand...
Click to collapse
I'm all stock but rooted with universal androot. Is that oem enough?

amazinglarry311 said:
Anyone who has used this method to downgrade, or someone using stock firmware, could you enter the phone information menu by dialing *#*#info#*#* tell me what call redirect says, true or false? I want to verify something.
Click to expand...
Click to collapse
Ok, downgraded two phones, one worked ok, the other I guess is bricked.
anyways on the one that worked, Call Redirect: false
And can anyone help with the other phone?
when plugged in to either computer or A/C, there is no charge light,
read a couple posts above for more info on the problem I am having.

amazinglarry311 said:
Anyone who has used this method to downgrade, or someone using stock firmware, could you enter the phone information menu by dialing *#*#info#*#* tell me what call redirect says, true or false? I want to verify something.
Click to expand...
Click to collapse
i did as your said and call redirect says
Call redirect: False
what were you trying to verify?

Mine is also false, I'm also curious to know what you are verifying?
Sent from my T-Mobile myTouch 3G using XDA App

[Q] Failing the pattern too many times

Hello
My brother has managed to get this message on his phone, and I don't find any solution to fix it. He don't remember his gmail account, since he has 2 or 3 for some reason and. So every account i have tried gets the same error : Wrong user og password.
Is there any solutions to this, hard reset?
On my own phone I can just use SEUS and reset the phone, but it does not seems like ZTE have a similar program.
Please help!

Is it rooted?

No it's not rooted. It's totaly stock

Ahh I think I know.
Press the Emergency call button and try type this: *983*57#
It's the code for hard reset.

k0zmic said:
Ahh I think I know.
Press the Emergency call button and try type this: *983*57#
It's the code for hard reset.
Click to expand...
Click to collapse
I've tried this, but it just says: call was not created, * 983 * 57 # is not an emergencynumber!

Bummer. The method below should work. Just make sure you put a custom ROM like Cyanogenmod on your SD Card.
I think this would work: http://android.modaco.com/content/z...-gen2-and-gen2-to-gen1-windows-flashing-only/
Please note this will wipe all the phone's data, change the partitions and upgrade the radio. There is a chance of bricking if you interrupt it midway. I did use it and it went well, it does for the majority of people.
The other alternative is go back to the retailer and try get a replacement.
If you're not 100% comfortable with that method above try go to the retailer.

k0zmic said:
Bummer. The method below should work. Just make sure you put a custom ROM like Cyanogenmod on your SD Card.
I think this would work: http://android.modaco.com/content/z...-gen2-and-gen2-to-gen1-windows-flashing-only/
Please note this will wipe all the phone's data, change the partitions and upgrade the radio. There is a chance of bricking if you interrupt it midway. I did use it and it went well, it does for the majority of people.
The other alternative is go back to the retailer and try get a replacement.
If you're not 100% comfortable with that method above try go to the retailer.
Click to expand...
Click to collapse
Thank you for the help it work perfect ^^

Nice, what ROM are you on now?

k0zmic said:
Nice, what ROM are you on now?
Click to expand...
Click to collapse
I installed Cm7 on it but it doesn't have market installed :S any reason for that?

HenningLang said:
I installed Cm7 on it but it doesn't have market installed :S any reason for that?
Click to expand...
Click to collapse
Oh you need the Gapps package: http://goo-inside.me/gapps/gapps-gb-20110307-signed.zip
It has the Market and stuff.
Flash via recovery.

[Q][Semi-Brick]Can't write to data and sd partition

Hey folks,
My SGS is starting to act wierd. Monday it started to use loads of energy, so I did a reboot. But then whas the problem, it started to hang on the kernel splash screen. I've tried to flash back with odin, but not much luck. Sometimes it boots, sometimes it doesn't. When it boots, it has no write acces to /data and /sdcard. This will render the phone useless.
Is anyone here that can say some solutions, because i'm out of options myself.
I've tried 2.2 and 2.3 stock roms, allso tried to flash ICS via CWM, but then I got the encryption error.
Hope someone here can help me. I have experience with the commandline in linux and windows. I have installed both OSes on my computer, so that is not a limitation.

joopykoopy said:
Is anyone here that can say some solutions, because i'm out of options myself.
Click to expand...
Click to collapse
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to differnt versions of Galaxy S

Thanks
Thanks for the reply.
I will check all the links, and will report back if it did work, or did not.
It did not work, so i've flashed stock back, and i'm going to a repair center in my city tomorrow. Hope they can fix it

how to enable Exfat for sd cards on Walmart Onn Tablet (10.1 inch w/ keyboard)?

Hi,
This is my first time trying to root a tablet but managed to unlock the bootloader and install magisk + Edxposed, but was unable to find a module that enabled exfat for the sd card.
Currently it only reads Fat32 formatted cards but I would like to load a 10gb file on there that the device can read.
Any ideas how to go about this? will flashing a custom kernel/ rom help me with this?
All help is appreciated.
Thanks in advance!

rachelld said:
Hi,
This is my first time trying to root a tablet but managed to unlock the bootloader and install magisk + Edxposed, but was unable to find a module that enabled exfat for the sd card.
Currently it only reads Fat32 formatted cards but I would like to load a 10gb file on there that the device can read.
Any ideas how to go about this? will flashing a custom kernel/ rom help me with this?
All help is appreciated.
Thanks in advance!
Click to expand...
Click to collapse
I believe you'd need something like vold-posix, along with a version of magisk modified to inject it
But vold-posix is for Android 8.1, although I believe there is a modified 9 build for Pixels.
I'm not even sure if anyone has gotten any custom roms working on any of these yet, but if they have, might be your only option.

Thanks!
As of now I think I bricked it....
I messed around and accidentally erased the system partition, tried to fix it by flashing the image posted here (https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227) and now the screen won't turn on, no recovery mode, no adb..... the device is still detected through the SP flash tools though.
I think the image I used wasn't complete - can anyone upload a complete working image (including a scatter file) I don't care if it's stock or custom, just need something working on the device.
Thanks all!

rachelld said:
Thanks!
As of now I think I bricked it....
I messed around and accidentally erased the system partition, tried to fix it by flashing the image posted here (https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227) and now the screen won't turn on, no recovery mode, no adb..... the device is still detected through the SP flash tools though.
I think the image I used wasn't complete - can anyone upload a complete working image (including a scatter file) I don't care if it's stock or custom, just need something working on the device.
Thanks all!
Click to expand...
Click to collapse
Uploading my WWR backup right now. Kinda slow internet at work so I'll post the link tomorrow morning. Probably around 10am EST. It also has the scatter.
Edit: https://www.dropbox.com/s/pmgbaik485pa9st/ONN%2010KB%20Tablet%20ONA19TB007.zip?dl=0

razredge said:
Uploading my WWR backup right now. Kinda slow internet at work so I'll post the link tomorrow morning. Probably around 10am EST. It also has the scatter.
Click to expand...
Click to collapse
Thanks so much! Will try flashing this when I get home later today

rachelld said:
Thanks so much! Will try flashing this when I get home later today
Click to expand...
Click to collapse
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.

rachelld said:
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.
Click to expand...
Click to collapse
Is it still detected by the computer? That's really all you need to flash the ROM. I would be careful not to overwrite or format the unit-specific data on the emmc, like nvram, proinfo, persist, etc. I hope those did not get corrupted on your device.

rachelld said:
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.
Click to expand...
Click to collapse
Is your computer still detecting it? What specific errors is SFFT giving you? Did you follow the guide HERE?

Appreciate all the help here! I did follow that guide but I believe I messed up when I deleted the internal storage so the flashing did not work...
Either way I have another one to play with as these were super cheap on black friday - does anyone have any ideas for my original question?
I don't mind flashing a custom rom if anyone knows of one that works with this device.

@rachelld, I don't understand what you mean by "deleted the internal storage" (I don't think you can delete the emmc chip ), but these tablets are basically unbrickable as long as you have a backup or at least the device-specific areas remain in the ROM. There is also no secure boot to speak of.

@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button

@rachelld, what about connecting it to the wall charger?

diplomatic said:
@rachelld, what about connecting it to the wall charger?
Click to expand...
Click to collapse
Nothing doing, no sign of life. Tested the charger with another device to make sure it's working

rachelld said:
@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button
Click to expand...
Click to collapse
Well no, if you did erase the emmc, then the stock Rom backups shared will not have enough data for you to fully restore from.
And it is not know what partitions can be shared between devices. For example. Secro has device specific data on it. Nvram , also.
So if you have multiple devices. Follow the wwr readback process and fully read back all the partitions from one that works. And flash it back to the bricked one.

rachelld said:
@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button
Click to expand...
Click to collapse
That's the factory mode, the clear eMMC option should just be another factory reset option.