Related
Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?
turtleletortue said:
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?
Click to expand...
Click to collapse
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.
hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
I've been experimenting with my own since I bricked mine as well, and I was able to bring mine to full functionality. Here are a few things I learned. The scatter file in the firmware on the internet is messed up. They made the scatter file incorrectly, so as a result, whenever you flash the device with it you have to completely flash it. Their firmware has also been tampered with and probably doesn't have a serial number in it. So, I bet you wiped all of your partitions, including ones that potentially had the serial number. I dunno how to fix it, maybe see if you can get a new one from B&N for no extra cost. Unless you have a full sp flash tool backup of the device before you bricked it, I'm unsure of what to do for you. I was able to help myself because I only messed up system.img, which I took a backup of before modifying it, and I used the wwr_mtk + sp flash tool guide to make a proper scatter file so I could flash my system.img using download in sp flash tool. (Also sorry that it's been a few months since I've responded, I just thought up how I could fix my own device last night and successfully did it). Also, here is my scatter file.
hassanhassan said:
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.
Click to expand...
Click to collapse
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this. NOTE: This rom is only for the Oreo version of this device, BNTV460, so for anybody with the BNTV450/Marshmallow device, your device likely will get messed up by this.
turtleletortue said:
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this.
Click to expand...
Click to collapse
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.
xKroniK13x said:
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.
Click to expand...
Click to collapse
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.
turtleletortue said:
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.
Click to expand...
Click to collapse
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...
xKroniK13x said:
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...
Click to expand...
Click to collapse
Yeah, your device may be completely bricked. The Nook Tablet 7's are confusing due to the two of them being only slightly different, but different enough for disaster to happen.
Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Slightly better picture without anything cut off.
reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing
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.
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?