Related
I just got an MK-801 off of DealExtreme (was really trying to get an inexpensive one,...lol)
By some poorly thought out flashing I've somehow managed to brick the device. The power light will turn on but nothing is displayed through either output. Is there some special recovery menu on this device (probably not) or any sort of method available to fix what I have borked?
Many thanks in advance.
shalpp said:
I just got an MK-801 off of DealExtreme (was really trying to get an inexpensive one,...lol)
By some poorly thought out flashing I've somehow managed to brick the device. The power light will turn on but nothing is displayed through either output. Is there some special recovery menu on this device (probably not) or any sort of method available to fix what I have borked?
Many thanks in advance.
Click to expand...
Click to collapse
Hi shalpp, i know the thread is abit old but did you manage to fix it already?
And do you know if theres any rom besides the custom one?
Hi all,
I want to make a logcat but i run into the following issue:
When my phone is in TWRP or booting ADB says device offline.
Wheb booted into Android it works fine. ADB shiws device and also making a logcat works.
But not in Recovery.
Anybody an idea what it can be?
I have this issue on Windows 10 and on Linux.
mmarkvoort said:
Hi all,
I want to make a logcat but i run into the following issue:
When my phone is in TWRP or booting ADB says device offline.
Wheb booted into Android it works fine. ADB shiws device and also making a logcat works.
But not in Recovery.
Anybody an idea what it can be?
I have this issue on Windows 10 and on Linux.
Click to expand...
Click to collapse
hello i have this issue too and drivers are properly installed. I tried both on windows 7 and linux, it shows device offline. I think the prob may be with twrp recovery.
Vivacity said:
hello i have this issue too and drivers are properly installed. I tried both on windows 7 and linux, it shows device offline. I think the prob may be with twrp recovery.
Click to expand...
Click to collapse
Yeah really annoying.
I need a logcat of booting CM13 (which is not booting) but i can't make one and thus i can't see whats going wrong.
Maybe its TWRP but it's the only thing there is for the A7........
mmarkvoort said:
Yeah really annoying.
I need a logcat of booting CM13 (which is not booting) but i can't make one and thus i can't see whats going wrong.
Maybe its TWRP but it's the only thing there is for the A7........
Click to expand...
Click to collapse
Same reason for me lol. Hope someone knows about this issue though.
Vivacity said:
Same reason for me lol. Hope someone knows about this issue though.
Click to expand...
Click to collapse
Yup let's hope so...... but you have TWRP 3.0 right? I have 2.8.7.0 so it's not the version at least.
mmarkvoort said:
Yup let's hope so...... but you have TWRP 3.0 right? I have 2.8.7.0 so it's not the version at least.
Click to expand...
Click to collapse
yes i have twrp 3.0.1-0
For which device is adb not working, do you have MTP disabled?
ashyx said:
For which device is adb not working, do you have MTP disabled?
Click to expand...
Click to collapse
Mine is a Galaxy A7 (A700F).
MTP is disabled in twrp indeed. If I enabke that and do ADB Devices the list is empty.
When MTP is disabled i see the phone id and then offline instead of device in the last column.
Nobody any idea???
ashyx said:
For which device is adb not working, do you have MTP disabled?
Click to expand...
Click to collapse
mmarkvoort said:
Mine is a Galaxy A7 (A700F).
MTP is disabled in twrp indeed. If I enabke that and do ADB Devices the list is empty.
When MTP is disabled i see the phone id and then offline instead of device in the last column.
Click to expand...
Click to collapse
@ashyx Exactly the same for me. If MTP is enabled it shows nothing when i type adb devices. If it is disabled it shows device offline. I have galaxy A8.
@ashyx no idea what this could be??
mmarkvoort said:
@ashyx no idea what this could be??
Click to expand...
Click to collapse
i guess even the devs are clueless bro lol. searched everywhere on the web but nothing mentionned about this.
Vivacity said:
i guess even the devs are clueless bro lol. searched everywhere on the web but nothing mentionned about this.
Click to expand...
Click to collapse
I gues so LOL....
But it would be nice to just give a reply... its annoying that some don't even do that.
Asked for help a lot lately for making a device tree....... finally 1 person wanted to help. All the others don't even reply.
Let us keep eachother in the loop ok? In case we find something
mmarkvoort said:
I gues so LOL....
But it would be nice to just give a reply... its annoying that some don't even do that.
Asked for help a lot lately for making a device tree....... finally 1 person wanted to help. All the others don't even reply.
Let us keep eachother in the loop ok? In case we find something
Click to expand...
Click to collapse
yes you're right. no prob let's keep in touch.
You all assume that we don't have real lives. I have just moved house which has taken up all my time lately, I also have a family and a job.
I do this in my spare time of which I don't have much, I'm sure it's the same for others.
Anyway to answer the question the issue is not TWRP, but certain Samsung kernels. For some reason the kernel itself blocks adb.
I am looking for a solution, but this needs help from others who can test things out.
I don't own any of the devices here so I rely on the assistance of others.
ashyx said:
You all assume that we don't have real lives. I have just moved house which has taken up all my time lately, I also have a family and a job.
I do this in my spare time of which I don't have much, I'm sure it's the same for others.
Anyway to answer the question the issue is not TWRP, but certain Samsung kernels. For some reason the kernel itself blocks adb.
I am looking for a solution, but this needs help from others who can test things out.
I don't own any of the devices here so I rely on the assistance of others.
Click to expand...
Click to collapse
We are not assuming anything. I also work with devs and i know what it involves, we were not talking about you particularly. besides taking 10 seconds to answer a question would not prevent anyone from going to work or having time for his family. neither is it an obligation to reply, we were just asking as it is the purpose of this thread.
Vivacity said:
We are not assuming anything. I also work with devs and i know what it involves, we were not talking about you particularly. besides taking 10 seconds to answer a question would not prevent anyone from going to work or having time for his family. neither is it an obligation to reply, we were just asking as it is the purpose of this thread.
Click to expand...
Click to collapse
+1
-1
Hello!
Now, I know this problem is in other threads. But the only reason why I'm posting a new one is if either that thread had died or the solution wasn't applicable to me (it didn't/doesn't work).
So! What happens is when I try to flash a file to the system or vendor I get this error.
Code:
failed to mount partition '/vendor' (invalid argument)
I've tried in TWRP and the bootloader fixes. And now, I currently have no OS.
What I've tried is as follows:
Flashing just the vendor (bootloader/TWRP) - ends with the vendor error.
Flashing .zip ROMs (bootloader/TWRP) - ends with the vendor error.
Trying the usual return to stock procedure - ends with the vendor error.
Repairing partition in TWRP - Says operation completed but the error is still persistent.
Basically. Nothing works because the Vendor partition is unmountable.
What should I do? I have no idea what a fix could be.
Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
Code:
FAILED (data write failure (Too many links))
or
Code:
FAILED (command write failed (No error))
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.
Nexus Radical said:
Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
or
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try using Nexus root toolkit, I used that today to fix recovery,
jimbomodder said:
Try using Nexus root toolkit, I used that today to fix recovery,
Click to expand...
Click to collapse
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.
Nexus Radical said:
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.
Click to expand...
Click to collapse
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.
jimbomodder said:
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.
Click to expand...
Click to collapse
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.
Nexus Radical said:
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.
Click to expand...
Click to collapse
Have you tried wugfresh Nexus tool kit?
Just thought I'd let you know that I have fully restored stock and locked my bootloader, and if I boot recovery I get " no command" too. Seems latest recovery image does f*@k all.
jimbomodder said:
Have you tried wugfresh Nexus tool kit?
Click to expand...
Click to collapse
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.
Nexus Radical said:
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.
Click to expand...
Click to collapse
O crap, I got 2 "oem" replacement cameras for my 6p from them and both blurry and don't save pictures,. Glad you fixed it yet.
I tried to flash it but it only bootloops for me. Have tried almost everything it seems. Have never had so much trouble flashing a phone.
I have tried Lieage os 15.1 but after i tried to flash N2G48B_4Cores.img from this side https://www.xda-developers.com/nexus-6p-bootloop-fix/ Lineageos bootloops even faster. Even tried the twrp from the side who requires a password I cant find so it it is useless.
I have tried Aquatios but it bootloops.
I have tried to flash stock android but it says something about the zip is wrong.
Someone who knows what I should do or am I stuck? I forgot to make a backup to so I am a bit desperate. Never forget it usually but only because it's not my phone I do forget.
I hope someone knows what I should do.
*EDIT* [SOLVED]
Trie this and got a bit further: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
Only that the screen flashes soon after after the settings come up and turn itself of after a while.
I have not flashed the radio though. Is that necessary?
*EDIT 2* [NOT SOLVED]
The radio were necessary for wifi.
Now is the problem with signing in to google.
Never can anything go smoothly.
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
orrebo said:
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
Click to expand...
Click to collapse
Good to hear. So what did you do wrong and what did you do to fix it?
Aimless Rambler said:
Good to hear. So what did you do wrong and what did you do to fix it?
Click to expand...
Click to collapse
Yeah. What did I do. Tried until I found a solution that worked. Think I mentioned it (did not). This thread I looked at to solve that problem: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
I had to flash a bootloader file and after that it worked better.
But I can't sign in to google how I do. Will try a couple of other gapps. Hopefully someone will work.
I have seen this before but don't remember how I solved it back then.
It even bootloops if it don't like the gapps.
New problems every time. A new one again where it crashes in the initial settings.
It stopped suddenly and is now back to checking info and this time it said it can't connect to google servers.
Have never ever worked with such a ****ty phone.
*EDIT*
I give up. It is as good as it gets.
If someone else of her friends wants to try so be my guest.
Over and out for this time.
If it's toast from the infamous bootloop issue can't blame you for setting the phone aside. But if you venture back to it I'd suggest flashing stock Google firmware then doing the 4cores fix if needed.
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.