Database Users

[3g STOCK .IMG] VZ WIRELESS MX600 5/3/2011

Here are the .IMG files that Motorola has posted on their MOTODEV site. .
ATTENTION: DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
These files are from Motorola's Development site but I take no liability with anything that happens with your device if something goes wrong.
Official HRI39 Motorola .IMG files:
http://www.multiupload.com/9XP1B8LSWC
Official HRI66 Motorola .IMG files:
http://www.multiupload.com/POUDJY1255
The following are the steps from the MOTODEV site
1. Extract files into android sdk /tools folder.
2. Start command prompt/ terminal from the android sdk tools folder. (How this is done on Mac I do not know, Windows: shift+left click and select "open command window here")
3. adb reboot bootloader
4. fastboot flash boot boot.img
5. fastboot flash system system.img
6. fastboot flash recovery recovery.img
7. fastboot flash userdata userdata.img
8. fastboot erase cache
9. fastboot oem lock
The device will lock and reboot.
You are now back to out of box state. However I do not know if it is still detectable by VZ Moto if you have unlocked the device after doing this.
Also fyi the sbf file is still an option but you will have to go in and do the fastboot oem lock after it completes

u mispelled cache

Fixed. Thanks had a long day and missed that at proof reading

Thanks for the files, does seem a lot simpler to just use the sbf file though.

bwcorvus said:
Thanks for the files, does seem a lot simpler to just use the sbf file though.
Click to expand...
Click to collapse
Its always good to have more options and the Xoom gives us many and hopefully soon sdcard support will provide the final key piece, the CM recovery!
In the meantime it is very good to have all of the official files at our disposal.
If anyone is wondering what the the reflash file from the first leak is, it is an SBF format installation of the stock boot image and a blank user data image to wipe data and return to stock via RSD Lite without touching the system partition.
This provides yet another way to reset that should be examined, especially if it works over a modified system partition.
We also may be able to use any or all of these files to build our own SBF files and other one step solutions for recovering and or modifying the Xoom. This can be very valuable and must also be thoroughly explored along with the NVM so we can really start to tak better control of the radio functions.
Lots to look at...

I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.

jmc2543 said:
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
Click to expand...
Click to collapse
Yea having these images is one BIG step...now we just need sdcards

Just finished doing this. I'm back at stock. Of course no I'll b the last to get an update. And by the same time tomorrow I'll be unlocking and re-rooting.

by doing this does it erase everything on your xoom?

bishop72 said:
by doing this does it erase everything on your xoom?
Click to expand...
Click to collapse
Yes it would. Itll bring it back to what it was like when you first bought it.

For those that updated, were you able to reroot?

17akota said:
Yes it would. Itll bring it back to what it was like when you first bought it.
Click to expand...
Click to collapse
I saw multiple threads about Titanium backup not working with the Xoom. Are there alternative apps that will save all my configuration like home screen layout etc? It was a lot of work B-)
Sent from my Xoom using Tapatalk

It is just Android 3.0
3.0.1 is HRI66

Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?

Aaron636r said:
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Click to expand...
Click to collapse
Oh no. I did the "fastboot oem lock" and now I get "Failed image LNX 0x0002". Cant boot past Dual Core logo screen.

Ok, re-unlocking it fixed it.

Ok so we have the original flash so we can get the OTA thats great. And Moto confirmed on their forum they will upgrade devices that have been unlocked and rooted. If they cannot install the software they will ship it back with just the new hardware. Can't wait to see what people can really start doing now.

For those of you that are like me and hate having to using mega upload and crap to download things here is a direct link on my web server to the file released by Moto.
DMCA Noticed by Moto
This was taken directly from the Moto Dev site myself.
If you browse the directory, which I think I left on for this one... There is also the sbf archive and RSD there to download. If anyone needs a place to store some files let me know. I have unlimited storage and bandwidth. When some of the OG Droid releases came out I was pumping over 11GB a week in downloads with no issues. It's the least I can do to help the community.

I got to be honest I don't know what the hell i should do to get the update and what will cause me to either have a clean install or lose root

All reports so far indicate it will not break root and rooted users have been getting the notification. They are also probably doing a controlled rollout if you have not yet gotten the notification. My XOOM is at home right now which sucks I won't be able to get my hands on it for about 6 hours and see what I can all do.

S.O.S. bricked my Toshiba Thrive need a stock(or rooted) boot.img

I attempted to flash the Motorola Xoom rooted boot.img on my Thrive.
It didn't work.
I have been unable to find a stock(or rooted) version of the Thrive boot.img so I can unbrick my device.
Can someone please
1.Provide a working boot.img
or
2.Instruct me on how to extract it from an intact Thrive?
I guess its safe to assume anyone working on rooting would have a copy of it
I would really appreciate the help!
Edit: I have been looking for hours for information on how to extract the boot.img from a device like this and have been having no luck.

Can someone please help me?
I realize what I did was idiotic...
I'll never mess with anything that says "boot" again unless I really know what I'm doing.

This is why we need a dev forum!

someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please

In the meantime, I'm getting a call back from level 2 tech Toshiba support in an hour. Trying to convince them to give me a copy of the recent firmware update. So "I can see what they changed, as there was no changelog".
Odds I succeed?

what is the exact model of the thrive?

Toshiba AT105-T1032
P/N PDA01U-00501F

lol while your at it ask for the sbk

joe ferreira said:
lol while your at it ask for the sbk
Click to expand...
Click to collapse
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?

joe ferreira said:
someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please
Click to expand...
Click to collapse
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""

Well, 2nd level tech support never called me back. Called back tech support and they PROMISED they'd call me back this time, in 2-3 hours.
Here's hoping this lands us an OTA update file

Natolx said:
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""
Click to expand...
Click to collapse
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682

Natolx said:
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?
Click to expand...
Click to collapse
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?

btw root is a part of the system.img not the boot.img
boot.img is the kernel

joe ferreira said:
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?
Click to expand...
Click to collapse
yes, that's how I bricked my tablet, by using fastboot to flash a xoom rootboot.img. Fastboot and recovery are available from simple menu by holding down power and volume up when booting up.
The fastboot is completely unlocked from the factory, you don't even have to issue an unlock command.

Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.

D3MN5PWN said:
Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.
Click to expand...
Click to collapse
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/

Natolx said:
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/
Click to expand...
Click to collapse
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).

D3MN5PWN said:
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).
Click to expand...
Click to collapse
My recovery is fine, its just the kernel.
My level 2 tech support discussion was a mixed bag. The guy essentially said it was extremely odd that the firmware update wasn't on the website and that they hadn't even heard about it. He sent an e-mail out to his entire department to find out what's going on. Hopefully that gets sent up the pipeline and it shows up under thrive downloads on the support website.

joe ferreira said:
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Looks like none of the oneclick roots work, someone on thriveforums posted this in response to my request.
"Sorry, I tried both the gingerbreak and psneuter versioins, neither worked.
Oh, and I also ran the "Check Drivers" and it said no issue found.
Also found z4root on theunlockr.com and tried it, appears to have hung up my Thrive."

New Brazilian firmware

Hi guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
AS my comes from Brazil, i saw that fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz is avaliable. But my question is: how can i flash this kinda if files since they arent RSD lite type and are fastboot ones? Do i need unlocked bootloader?
If someone can help me, i appreciate a lot!

AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file

waiflih said:
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
Click to expand...
Click to collapse
Thanks my friend! But do uo have the steps for this? Cause i couldnt found any specific to Moto X.
As i unzip the tar file, i have these files as attached.

I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards

waiflih said:
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
Click to expand...
Click to collapse
Thanks again!
Any ideas?

Do you have the phone in fastboot mode and connected to your PC while running the BAT file?

xitake said:
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
Click to expand...
Click to collapse
No,but as the programa asks, i don have a JTAG flex?

xpc21 said:
No,but as the programa asks, i don have a JTAG flex?
Click to expand...
Click to collapse
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go

xitake said:
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
Click to expand...
Click to collapse
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.

Flahing stock SBF
xpc21 said:
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Click to expand...
Click to collapse
Try this maybe it'll work
1. Connect your Moto x, make sure developer options is enabled and tick usb debugging.
2. open command window on the folder including the new extracted firmware.
3. Type adb devices to confirm that Moto X is detected by your computer.
4. Type adb reboot bootloader, Moto X will reboot in fastboot mode.
5. Run the batch file flasfall.
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.

kkhadr said:
Try this maybe it'll work
...
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
Click to expand...
Click to collapse
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?

Anyone else?
[email protected]

xitake said:
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Click to expand...
Click to collapse
If this version includes the camera patch then it won't be rooted, but I flashed TMO 4.3 the test build it's working great but off course I lost root, and I'm sure in a few days it will be rooted again, so nothing to fear.

this is the OPs 3rd post about the same topic. One under q&a, one under dev that got moved to q&a, and now one under moto x general. Someone needs to teach him a lesson because he has gotten responses on all three threads. Really frustrating. Won't be getting anymore help from me...

Looks like fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz have the same camera app as in ATT, TMO, Sprint after OTA (with improved camera). Camera app in new Brazilian firmware have version 3.0.211 - the same as in TMO rom with OTA installed.

Kind of straight forward
You just need to unpack the tgz container. Inside the folder there is a bunch of files.
I'm my case since I'm using OSX I just ran flashall.sh and done. There is a flashall.bat that I believe is designed to work with windows.
Put your phone in bootloader mode, connect the cable, go to folder the files lies and run the command. In about 5 minutes it is done. :good:

Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?

rodrigorox said:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
Click to expand...
Click to collapse
rodrigorox,
I have called motorola on friday and it seems we will be getting the update in the next week or so...
I'd hold on on flashing it if all you look for is the OTA that US got.

Just a warning

I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.

You tried house of moto to fastboot flash 98.30.1? Sux they found a way to relock them...
Sent from my XT907 using Tapatalk

This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.

RikRong said:
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
Click to expand...
Click to collapse
@AndroidGreg
There's a line in the fastboot xml file with gpt_main0.bin (somithing really similar to that, been a while since I flashed it...) and all that's necessary is removing that line and flashing the fastboot with rsd, or just manually flash the fastboot skipping that partition, either or will work and fix the problem. Even though the bootloader is unlocked, that particular partition IS still controlled by securtiy and is blocked from downgrading -- luckily for us the partition table never changed between rom versions so it's perfectly safe to flash or not to flash it.
I've never flashed with RSD, but IIRC, there's also two more lines in the fastboot's xml that need to be removed for it to properly flash. I've only flashed my phone with moto-fastboot from linux and used MythTools from windows -- MythTools is an interactive script for the Atrix HD to flash stock fastboots, root, unlock the bootloader, flash a custom recovery, boot logos, and soon different radios -- Similar to Mattlgroff's tool.
The Atrix HD has the exact same issue with that partition.

download the sbf file from http://sbf.droid-developers.org/phone.php?device=5
install these drivers https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
connect the phone in fastboot mode.
now extract the "fastboot_rsd.zip " to a folder.
extract the contents of the downloaded sbf/xml file into the fastboot_rsd.zip folder
execute "flash_fastboot_erase_userdata"
worth a shot.
always works for me..
good luck.

RSD does not detect the phone at all, only the quick utilities did and they failed. Verizon overnighted my new phone and its here already, not unlockable im just gona root and keep it for a while till I switch to strait talk with the nexus 5, I cant afford $100 a month anymore anyway.

First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.

LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
Click to expand...
Click to collapse
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.

RikRong said:
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
Click to expand...
Click to collapse
Exactly. The Atrix HD gives us this error if we flashed the stock Mexican firmware (our latest) and try to flash anything below it, or the Bell firmware (2nd newest) and anything below that, and so on and so forth. All that's necessary is to remove the gpt flashing line and go again....just like we have to remove the oem lines from the fastboot xml.
First time I had that error, I went WTF (the first flash after unlocking my bootloader if ya'll's curious), knew that GPT is a partition table from grub experience, figured that the partition table has never changed since stock ICS roms, removed the GPT line, flashed ICS, and I was happy.
I'd love to be able to combine all the data, system, cache, and any other partition that don't need a fixed place (like modem, etc) and be able to use ZFS or BTRFS volumes to maximize the amount of storage we can have -- I've always wondered why they don't do something like that already...

Ok 3 computers 1 xp and 2 windows 7, nothing, mac nothing, even made a factory cable because the battery just got to low, nothing, no computer will detect it, using any of the 3 motorola branded usb cables plugged directly into the laptops. Now the utilities from matgroff and the other guy (cant think of his name but he made the 2.0 utility) will not even try to flash the phone they say please plug a phone in that is in fastboot mode, I

Serious question, but have you tried Linux? My old Bravo wasn't detected by Windows (XP or 7, been 2 years now) after a bad RSD flash, but I was able to manually flash it from Linux (either Manjaro or Debian Testing). After that, to this day it'll flash with RSD, but it isn't detected properly. I still flash it, and almost everything else, from Linux because I don't trust flashing from Windows anymore. I made an exception recently to help with a tool and because my Linux partition was down for a month.

LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
Click to expand...
Click to collapse
I tried doing the exact same thing as the OP - factory reset to "stock" and then flash back up in preparation for KK, after using TiBu to save everything and using SafeStrap to make a Nandroid (very thankful I did). I ended up with the identical screen that the OP had, even stating that my previously unlocked BL had been apparently "relocked." For me, RSD Lite did recognize my phone (I updated RSD to the latest version beforehand), however it would not flash anything for me (the flashing process would start and then immediately say "failed").
See my post for the details and the solution I used: http://forum.xda-developers.com/showthread.php?t=2674431.
I was completely freaked out for a couple of hours until I stumbled upon bweN diorD's GPT partition fix. And then everything was fine for me.
Hope this helps anyone who falls into the same trap.

AndroidGreg said:
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
Click to expand...
Click to collapse
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89

scoobaspeaz said:
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
Click to expand...
Click to collapse
@AndroidGreg, do you still have the phone?
Sent from my DROID RAZR HD using Xparent BlueTapatalk 2

(HELP NEEDED) Onn 8" gen 2, 100011885 no boot

So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!

Two things, I got access to my old account after a password reset
and, I got my tab back up and running, as well as root & xposed + gravitybox
I'm working on a guide as we speak.

Also, I will be dumping my firmware and adding the 10001885 to the list of stock image dumps on the main onn thread.

Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
Ankylo'sburner said:
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Click to expand...
Click to collapse
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do

bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse

Hey, i've had that same issue but have since fixed it by flashing the rom to the 100011886. I used some of the posts here to flash both vbmeta.img and boot.img to gain root, with success https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing . i eventually went too far and currupted my rom and had a hard time finding the stock ROM. I found the stock ROM to the 100011886 and flashed that to fix the problem, now i run that as my system and it boots up just fine. https://www.mediafire.com/file/107jp6gwbiwq87q/MT8168_ONN_Gen2_100011886.zip/file
fastboot erase super
fastboot flash super super.img

Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22

onn. said:
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
Click to expand...
Click to collapse
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT

KMerrimanJr said:
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
Click to expand...
Click to collapse
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.

onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though

KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
I wish I would have waited until I read this today instead of further messing with it yesterday. It looks like everything you have is what I need, but now I am battling trying to get the COM port to stay active when the device is plugged in. I'll tinker with it and see if I can get back to the state I had it in yesterday where it was staying connected.

KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
Would you happen to know/remember all the settings you checked in SP Flash Tool (I assume you used that) when you flashed things to get it working? It seems that my PC is able to communicate with the device again, but I'm unsure of how to proceed next.

Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file

KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
It's hard bricked at the moment unfortunately, so there's no appearance of life to it. Attached picture is the error I get. https://www.gizmoadvices.com/list-sp-flash-tool-error-codes-solution-fix/ appears show info about the error, but it's not something I know how to fix yet.
The only way I can get the tablet to make moves in device manager (which I assume is a sign that the PC can at least partially recognize/see the device) is to click on Download in SPFT, connect tablet to PC via USB cord, and then hold down power button, which led to the error. Errors in SPFT I've received so far are 0xC0060001 and 0xC0060003.
When the tablet is active in the device manager, I assume that the device is in a powered state. However, when the device is grayed out, I assume it's in a powered off state (see other pic). I've yet to find away to actually flash anything to it.

KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
Also, apologies if I'm being a bother, but do you know what version of SPFT you used as well as which DA file?

bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
where did you get this? did you dump it? if so how?