[Q] Nabi2 no longer allows me to do anything

[Q] Nabi2 no longer allows me to do anything - Fuhu Nabi 2

So I admittedly goofed up up somewhere on my Nabi2.
I followed the instructions found within this forum to install TRWP,etc and for the most part it worked.
I however could not get one app that I really needed to run.
That is the Google Device Policy app that is required by the domain policy by for Google Apps and Mail.
Without that app I cannot authenticate to the G-Mail servers.
Whenever I attempt to load that app it says "Device not compatible"
So then I tried the app "Market Helper" to see if I could trick it.
The Market Helper app reported it was functioning as another device but the "Device Policy" app still said incompatible.
This is where the trouble begins.
I get the great idea that I am going to restore the Nabi to factory settings and then maybe side-load the Device Policy app.
This is all new to me and ultimately I now have a Nabi that does not have a control panel, no access to adult mode, no nothing except maybe a few games.
TWRP is no longer there when I boot into recovery mode.
I do remember the droid bot laying on its back looking pretty pissed off.
I tried to run the NabiLab batch files and it reports that no device is found.
I know the drivers are loaded because I can see the Nabi under device manager with no exclamation point.
I cannot get into settings to put the Nabi into USB debug mode as I did when I first started.
I don't know what to do.
I would like to get back to a fresh start.
How do I go about getting this device to Out Of The Box operation.
If I can get there then I can continue my quest to learn a little more about the entire rooting thing.
Also is the Google device app going to ulimately work on this device? Or am I just spinning my wheels?
Thanks a million!

generatorlabs said:
So I admittedly goofed up up somewhere on my Nabi2.
I followed the instructions found within this forum to install TRWP,etc and for the most part it worked.
I however could not get one app that I really needed to run.
That is the Google Device Policy app that is required by the domain policy by for Google Apps and Mail.
Without that app I cannot authenticate to the G-Mail servers.
Whenever I attempt to load that app it says "Device not compatible"
So then I tried the app "Market Helper" to see if I could trick it.
The Market Helper app reported it was functioning as another device but the "Device Policy" app still said incompatible.
This is where the trouble begins.
I get the great idea that I am going to restore the Nabi to factory settings and then maybe side-load the Device Policy app.
This is all new to me and ultimately I now have a Nabi that does not have a control panel, no access to adult mode, no nothing except maybe a few games.
TWRP is no longer there when I boot into recovery mode.
I do remember the droid bot laying on its back looking pretty pissed off.
I tried to run the NabiLab batch files and it reports that no device is found.
I know the drivers are loaded because I can see the Nabi under device manager with no exclamation point.
I cannot get into settings to put the Nabi into USB debug mode as I did when I first started.
I don't know what to do.
I would like to get back to a fresh start.
How do I go about getting this device to Out Of The Box operation.
If I can get there then I can continue my quest to learn a little more about the entire rooting thing.
Also is the Google device app going to ulimately work on this device? Or am I just spinning my wheels?
Thanks a million!
Click to expand...
Click to collapse
Use fastboot to put TWRP back on, use it to restore your backup, or if you dont have one a clean image.
If you say you have NabiLab use the option to install TWRP. First though manually get the tablet to the fastboot protocol(at power on press and hold power and vol+ button, then enter fastboot protocol). Now start Nabilab and select Install Recoveries. Ignore the error screens in Nabilab, and keep pressing enter when prompted. This should restore TWRP.
Boot TWRP manually(at power on press and hold power and vol + button, enter recovery kernel). Then you could use Nabilab to restore the backup you made(?) or download the fully Nabilab and install a fresh 1.9.37

Related

Soft bricked my device HELP!!!

I did my search before posting this, so I'm sorry if this has been already resolved but I couldn't find solution to this.
I've a Kindle HDX 8.9 64GB wifi model, it was rooted installed SU, installed safestrap on it and had google play store and gapps working on it., I was too busy so left it device as it is and never used it. Recently got free and noticed it was downloading update. I remembered reading that update breaks Root so switched off device as I panicked and then turned it on in airplane mode. I came here and saw what could be done to prevent update. Tried firewall with IP tables that didn't help as download of update resumed after I turned airplane mode off. Then I did more search did below changes
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
along with above changes I made changes suggested in this thread http://forum.xda-developers.com/showthread.php?t=2678600
"edit build.prop
ro.build.version.number=999999999"
After doing all these changes, update stopped and started giving me error of unable to check update. I was all happy. Started using device normally and everything was fine till I rebooted device and that's when it messed up.
Tablet starts normally with Kindle fire logo and then comes Safestrap menu with options to continue or go into recovery. I clicked continue as usual and it just sits there with grey screen. Doesn't do anything at all from there on. I rebooted again and was able to go into recovery mode but I never took backup (I know dumb of me) so there was nothing I could do there. I tried to turn on adb sideload in recovery but it kept attempting to turn on but never did. When kindle is in grey screen its been detected on Laptop. In device manager device is detected 2 places as shown in picture attached, One under other devices with shows android device with yellow triangle on it and also under portable devices as MTP usb device. Though I'm unable to see it detected in file system. I've kindle drivers already installed.
I'm not sure renaming those files messed my system up or changing build prop messed it up. But I'm unable to find solution to fix this mess.
I would really appreciate help as I'm in pretty tight position here. Device can't be returned to amazon as I'm in India now. So only option I got is to repair it somehow or its $500 down the drain
UPDATE : ADB detects Kindle as emulator-5554 device. May be its a good sign? :\ again any help would be appreciated.

arvinchugh said:
I did my search before posting this, so I'm sorry if this has been already resolved but I couldn't find solution to this.
I've a Kindle HDX 8.9 64GB wifi model, it was rooted installed SU, installed safestrap on it and had google play store and gapps working on it., I was too busy so left it device as it is and never used it. Recently got free and noticed it was downloading update. I remembered reading that update breaks Root so switched off device as I panicked and then turned it on in airplane mode. I came here and saw what could be done to prevent update. Tried firewall with IP tables that didn't help as download of update resumed after I turned airplane mode off. Then I did more search did below changes
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
along with above changes I made changes suggested in this thread http://forum.xda-developers.com/showthread.php?t=2678600
"edit build.prop
ro.build.version.number=999999999"
After doing all these changes, update stopped and started giving me error of unable to check update. I was all happy. Started using device normally and everything was fine till I rebooted device and that's when it messed up.
Tablet starts normally with Kindle fire logo and then comes Safestrap menu with options to continue or go into recovery. I clicked continue as usual and it just sits there with grey screen. Doesn't do anything at all from there on. I rebooted again and was able to go into recovery mode but I never took backup (I know dumb of me) so there was nothing I could do there. I tried to turn on adb sideload in recovery but it kept attempting to turn on but never did. When kindle is in grey screen its been detected on Laptop. In device manager device is detected 2 places as shown in picture attached, One under other devices with shows android device with yellow triangle on it and also under portable devices as MTP usb device. Though I'm unable to see it detected in file system. I've kindle drivers already installed.
I'm not sure renaming those files messed my system up or changing build prop messed it up. But I'm unable to find solution to fix this mess.
I would really appreciate help as I'm in pretty tight position here. Device can't be returned to amazon as I'm in India now. So only option I got is to repair it somehow or its $500 down the drain
UPDATE : ADB detects Kindle as emulator-5554 device. May be its a good sign? :\ again any help would be appreciated.
Click to expand...
Click to collapse
try rebooting the device and go into safestrap recovery and when you hear the driver try to load in windows go to device manager,it should be listed as mtp under portable devices,uninstall that driver do not reboot,,unplug device and then plug it right back in it should try to load the driver as kind fire hdx but fails,when it is done check device manager for the kindle fire with the triangle on it and click update driver,then click browse my computer for driver software,then click let me pick from a list of device drivers on my computer,then scroll down until you see kindle fire click it and then click ADB ANDROID user interface and the click next,if a box pops up saying something about drivers might not be compatible just click yes to install,when its done you will have kindle fire in device manager and in adb it should say what ever you device is and then RECOVERY after in adb then you can push the files needed
which i would use this one
https://mega.co.nz/#!WlQliIgZ!-SxzW77e4m0S5e520uxvwf6EYrbDNb-yL7O5ElnrO5c
from this thread
http://forum.xda-developers.com/showthread.php?t=2665683
when the bin file is done downloading make a copy of it and put it in your
platform-tools folder with adb and change the .bin to .zip,,then push it to your sdcard (adb push update-kindle-14.3.1.0_user_310079820.zip /sdcard)
THIS WILL TAKE A WHILE! so let it do it's thing and when adb says it is done and the file is pushed press on the screen,(which has blacked out by now),, swipe to unlock and press install, you should see the
update-kindle-14.3.1.0_user_310079820.zip file on the sdcard now,,if so great lets move to the next step...
now hit the back button and go to the home screen,,,press wipe and swipe to wipe it (just do the regular wipe and thats it) DO NOT REBOOT YET
hit the back button or home button to go back to the home screen,,,now press install press the update-kindle-14.3.1.0_user_310079820.zip file and swipe it
it will say checking md5 no md5 found skipping modem update, installing and when it says finished successfully reboot system and it will be back to stock needing rooted and the whole works again except safestrap will still be there when it boots back on,,just let it continue or press continue it may take a few minutes to load the color kindle fire screen like any new rom would take to boot the first time,, KEEP WIFI OFF AFTER REBOOT,,,safestrap will stay installed but you will not see the app in the app draw and you dont need it because it is still installed ,so just root it using this http://forum.xda-developers.com/showthread.php?t=2542456
dont worry about the errors just do what it says and then install busy box and supersu then do this http://forum.xda-developers.com/showthread.php?t=2618158 and reboot the device one or twice,,after that download this http://android.mydedibox.fr/thor-gapps-installer-1.zip put it on your sdcard and then reboot to safestrap and press install and press thor-gapps-installer-1.zip and swipe when its done just reboot
then you will need to change the build.prop to keep it from updating
hope this helps you, it is what i had to do when the same thing happened to me so i know it will work!! good luck if you need any help let me know

jjrizzelcincy said:
try rebooting the device and go into safestrap recovery and when you hear the driver try to load in windows go to device manager,it should be listed as mtp under portable devices,uninstall that driver do not reboot,,unplug device and then plug it right back in it should try to load the driver as kind fire hdx but fails,when it is done check device manager for the kindle fire with the triangle on it and click update driver,then click browse my computer for driver software,then click let me pick from a list of device drivers on my computer,then scroll down until you see kindle fire click it and then click ADB ANDROID user interface and the click next,if a box pops up saying something about drivers might not be compatible just click yes to install,when its done you will have kindle fire in device manager and in adb it should say what ever you device is and then RECOVERY after in adb then you can push the files needed
which i would use this one
https://mega.co.nz/#!WlQliIgZ!-SxzW77e4m0S5e520uxvwf6EYrbDNb-yL7O5ElnrO5c
from this thread
http://forum.xda-developers.com/showthread.php?t=2665683
when the bin file is done downloading make a copy of it and put it in your
platform-tools folder with adb and change the .bin to .zip,,then push it to your sdcard (adb push update-kindle-14.3.1.0_user_310079820.zip /sdcard)
THIS WILL TAKE A WHILE! so let it do it's thing and when adb says it is done and the file is pushed press on the screen,(which has blacked out by now),, swipe to unlock and press install, you should see the
update-kindle-14.3.1.0_user_310079820.zip file on the sdcard now,,if so great lets move to the next step...
now hit the back button and go to the home screen,,,press wipe and swipe to wipe it (just do the regular wipe and thats it) DO NOT REBOOT YET
hit the back button or home button to go back to the home screen,,,now press install press the update-kindle-14.3.1.0_user_310079820.zip file and swipe it
in will say checking md5 no md5 found skipping modem update, installing and when it say finished successfully reboot system and it will be back to stock needing rooted and the whole works again except safestrap will still be there when it boots back on,,just let it continue or press continue it may take a few minutes to load the color kindle fire screen like any new rom would take to boot the first time,, KEEP WIFI OFF AFTER REBOOT,,,safestrap will stay installed but you will not see the app in the app draw and you dont need it because it is still installed ,so just root it using this http://forum.xda-developers.com/showthread.php?t=2542456
dont worry about the errors just do what it says and then install busy box and supersu then do this http://forum.xda-developers.com/showthread.php?t=2618158 and reboot the device one or twice,,after that download this http://android.mydedibox.fr/thor-gapps-installer-1.zip put it on your sdcard and the reboot to safestrap and press install and press thor-gapps-installer-1.zip and swipe when its done just reboot
then you will need to change the build.prop to keep from updating
hope this helps you it is what i had to do when the same thing happened to me so i know it will work good luck if you need any help let me know
Click to expand...
Click to collapse
Thanks so much for reply, I've been busy so Haven't had time to try this out. however I've downloaded file just incase it goes offline. I'll reply here again if I've any trouble setting it up. Again thanks for taking time out to reply and posting such a detailed procedure for me to follow. Really appreciate it. :good::good:

arvinchugh said:
Thanks so much for reply, I've been busy so Haven't had time to try this out. however I've downloaded file just incase it goes offline. I'll reply here again if I've any trouble setting it up. Again thanks for taking time out to reply and posting such a detailed procedure for me to follow. Really appreciate it. :good::good:
Click to expand...
Click to collapse
No problem ,,,hope it all works out ,,,let me know how it goes

it does not help, because adb does not work after editing build.prop

amazonhdx said:
it does not help, because adb does not work after editing build.prop
Click to expand...
Click to collapse
what type of problem are you having and what did you do to get that problem

jjrizzelcincy said:
what type of problem are you having and what did you do to get that problem
Click to expand...
Click to collapse
just edit build.prop and save without normal permission. and kindle fire hdx: soft bricked! :victory:
tablet start step: 1. grey logo 2. black screen
adb not working.
after connect factory cable device view on "qhsusb bulk"
Safestrap not installed

amazonhdx said:
just edit build.prop and save without normal permission. and kindle fire hdx: soft bricked! :victory:
tablet start step: 1. grey logo 2. black screen
adb not working.
after connect factory cable device view on "qhsusb bulk"
Safestrap not installed
Click to expand...
Click to collapse
try a factory reset through stock recovery
even though im reading a lot on here not to do that with certain issues but if yours is just build.prop that may help you but read around before wiping though

jjrizzelcincy said:
try a factory reset through stock recovery
even though im reading a lot on here not to do that with certain issues but if yours is just build.prop that may help you but read around before wiping though
Click to expand...
Click to collapse
reset from default recovery not help

amazonhdx said:
reset from default recovery not help
Click to expand...
Click to collapse
Sorry wish I could be more help for you buddy

amazonhdx said:
just edit build.prop and save without normal permission. and kindle fire hdx: soft bricked! :victory:
tablet start step: 1. grey logo 2. black screen
adb not working.
after connect factory cable device view on "qhsusb bulk"
Safestrap not installed
Click to expand...
Click to collapse
i would only use ROOT EXPLORER to edit any files like build.prop
try to reboot oem from there
can you see it in fastboot with the factory cable ???
if so try fasboot reboot oem
then press enter

jjrizzelcincy said:
try rebooting the device and go into safestrap recovery and when you hear the driver try to load in windows go to device manager,it should be listed as mtp under portable devices,uninstall that driver do not reboot,,unplug device and then plug it right back in it should try to load the driver as kind fire hdx but fails,when it is done check device manager for the kindle fire with the triangle on it and click update driver,then click browse my computer for driver software,then click let me pick from a list of device drivers on my computer,then scroll down until you see kindle fire click it and then click ADB ANDROID user interface and the click next,if a box pops up saying something about drivers might not be compatible just click yes to install,when its done you will have kindle fire in device manager and in adb it should say what ever you device is and then RECOVERY after in adb then you can push the files needed
which i would use this one
https://mega.co.nz/#!WlQliIgZ!-SxzW77e4m0S5e520uxvwf6EYrbDNb-yL7O5ElnrO5c
from this thread
http://forum.xda-developers.com/showthread.php?t=2665683
when the bin file is done downloading make a copy of it and put it in your
platform-tools folder with adb and change the .bin to .zip,,then push it to your sdcard (adb push update-kindle-14.3.1.0_user_310079820.zip /sdcard)
THIS WILL TAKE A WHILE! so let it do it's thing and when adb says it is done and the file is pushed press on the screen,(which has blacked out by now),, swipe to unlock and press install, you should see the
update-kindle-14.3.1.0_user_310079820.zip file on the sdcard now,,if so great lets move to the next step...
now hit the back button and go to the home screen,,,press wipe and swipe to wipe it (just do the regular wipe and thats it) DO NOT REBOOT YET
hit the back button or home button to go back to the home screen,,,now press install press the update-kindle-14.3.1.0_user_310079820.zip file and swipe it
it will say checking md5 no md5 found skipping modem update, installing and when it says finished successfully reboot system and it will be back to stock needing rooted and the whole works again except safestrap will still be there when it boots back on,,just let it continue or press continue it may take a few minutes to load the color kindle fire screen like any new rom would take to boot the first time,, KEEP WIFI OFF AFTER REBOOT,,,safestrap will stay installed but you will not see the app in the app draw and you dont need it because it is still installed ,so just root it using this http://forum.xda-developers.com/showthread.php?t=2542456
dont worry about the errors just do what it says and then install busy box and supersu then do this http://forum.xda-developers.com/showthread.php?t=2618158 and reboot the device one or twice,,after that download this http://android.mydedibox.fr/thor-gapps-installer-1.zip put it on your sdcard and then reboot to safestrap and press install and press thor-gapps-installer-1.zip and swipe when its done just reboot
then you will need to change the build.prop to keep it from updating
hope this helps you, it is what i had to do when the same thing happened to me so i know it will work!! good luck if you need any help let me know
Click to expand...
Click to collapse
Can confirm this worked just as stated, thanks again for taking your time out and making and excellent easy to follow guide to unbrick my device. Really really appreciate it.
Thanks again

arvinchugh said:
Can confirm this worked just as stated, thanks again for taking your time out and making and excellent easy to follow guide to unbrick my device. Really really appreciate it.
Thanks again
Click to expand...
Click to collapse
no problem man

Nabi 2 root brick issue - experts needed please!

Ok, so I attempted to root a Nabi 2 so I could use the SD card to hold apps since the onboard memory is terrible and I bricked the dang thing. I unlocked root supposedly using a one click app method, then I was able to attempt to update using the updater already on the Nabi. During the reboot, thats when it bricked. It is stuck in a constant boot loop mode that eventually ends up on a dead android screen.
My main problem is I know there has got to be a way to restore a stock rom/os on it, but every how to guide out there assumes that I already know what the hell they are talking about. SDK, ADB, HIV, STD, its irritating. Also, I tried TWRP, ADB, etc. but since the Nabi is in a constant boot loop and dead android screen, I can't get my PC to recognize it for more than 5 seconds. Is there a step by step guide to what I need to do for a novice? Like step 1. "since your PC can't recognize the device in the first place this is where you start". Step 2, use "this program, then this, and this is why".
Can anyone out there help me get pointed in the right direction? I am tech savvy but the existing guides assume too much, have broken links, and don't say anything about what to do when you can't even get your device to be recognized.
Thanks
Aaron

I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.

Higher-Primate said:
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Click to expand...
Click to collapse
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.

aicjofs said:
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
Click to expand...
Click to collapse
I want to say it was running 4.1 or 4.2 but I'm not positive. Stupid me should have written it down. Is it possible to load any of the versions now that I have wiped it? I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen. From there I did a - and + and got an option to side load recovery or boot to ADB I think it was. So since I can at least get there, is there anything I can do? Other than that, TWRP won't recognize it and says no drivers are loaded. I'm assuming because I can't get the Nabi to stay stable long enough to actually load anything on to it? The device recognizes for a few seconds then disappears.

Higher-Primate said:
I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen.
Click to expand...
Click to collapse
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550

aicjofs said:
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
Click to expand...
Click to collapse
Ok, I tried fastboot, but it doesn't really do anything. Once I go into fastboot, I have more options. Bootloader, continue, reboot bootloader, reboot, and power off. None of the options allows the Nabi to show up as a device in device manager. Everything just takes me to the dead android unfortunately.

So I guess my next question would be, how do I get drivers loaded for a device that can't show up?

Higher-Primate said:
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Click to expand...
Click to collapse
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.

aicjofs said:
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
Click to expand...
Click to collapse
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?

Higher-Primate said:
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Click to expand...
Click to collapse
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.

aicjofs said:
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
Click to expand...
Click to collapse
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.

Higher-Primate said:
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Click to expand...
Click to collapse
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly

aicjofs said:
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
Click to expand...
Click to collapse
No problem at all. Ok, that seemed to have done something. I put in the exact one you just changed above, and I rebooted normally, now I have a TWRP screen on the Nabi display. Now, what instructions do I need to follow? Do I still use NabiLab2015, if so the Disney/Nick or NV7A - US? Both now say "TWRP +mount:mounting /system on ext4 failed: no such file or directory.

Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]

Higher-Primate said:
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Click to expand...
Click to collapse
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.

aicjofs said:
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
Click to expand...
Click to collapse
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.

Higher-Primate said:
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Click to expand...
Click to collapse
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.

aicjofs said:
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
Click to expand...
Click to collapse
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.

Higher-Primate said:
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Click to expand...
Click to collapse
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot

aicjofs said:
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
What happens if it won't let me create the backup folder? It errors out and says it can't create one.

"Fully" factory reset firmware on ASUS MEMOPAD FHD 10 (me302c) tablet

I decided to root my ME302C tablet to remove some bloatware using an app that required a rooted device. I had the latest firmware so I couldn't use any of the rooting guides online, but I tried Kingo Root, an automatic rooting PC program (all I had to do was enabled USB Debugging), and it worked, at least for one session (after a reboot, it appears to stop working).
After I removed the bloatware, I reset the tablet to its factory state without using the remove root option in Kingo SuperUser (not SuperSU) (I did not know that the option existed). I'm not sure if it would have made a difference if I had used that option, but after resetting, Android booted properly, but I had no lock screen, broken default browser, unresponsive on-screen home button, no notification area, and I lost some options that appeared when powering off (airplane mode and mute). I occasionally get "unfortunately *app* has stopped" errors, but it doesn't appear to affect anything. The tablet works fine otherwise.
I would really appreciate it if someone could direct me on how to restore the default firmware entirely. If I factory-reset, it just removes the apps and resets the settings without affecting the system (clears cache and user partitions), and this website confirms that: search for Isn't Factory Reset exactly the same as wiping /data and /cache? stackexchange. I can't link to it directly. Sorry.
I found a post about an unrelated problem while typing the title where somebody attempted to root using an unofficial firmware update and totally bricked their FHD 10. They ran these commands:
fastboot erase cache
fastboot erase system
fastboot flash update "updatename".zip
Suppose that instead of using the unofficial, rooted update.zip he used, I used an official one from this page (it contains links to updates for my tablet's firmware): search for me302c asus. I can't link to it directly. Sorry.
Would that work? I am assuming that a firmware update is a copy of the entire firmware.
If I could use an update, could you please let me know how to flash it exactly? I can boot into recovery mode, Droidboot Provision OS. It has an option to update the firmware, I believe, called "SD DOWNLOAD". If I place an update.zip file named ASUS_BUNDLE.zip on an external SD card and use the option, it'll look like it's updating (there are a few screens, I think they say "clearing cache" and something else, but nothing mentioned of the system partition) - however, it just acts as if it is a factory reset, taking me back to that state where things are borken.
SD Download doesn't look like it is doing something for every random ZIP you put on the SD card, because if I use a ZIP file that has, say, a picture of my cat enclosed, it will not do anything. I think that it does do something with the ASUS_BUNDLE.ZIP, but just not anything that solves my problem.
In Droidboot, if I plug a USB cable into the tablet and the other end into my PC, an icon will appear saying "USB connected". If I enable USB debugging in Android and connect the tablet to my PC in the Droidboot Provision OS recovery mode, should I run the commands then?
I realize that this is a mouthful and thank you for taking the time to read my post.

Did you solve this in the end?

Yes.

_MsG_ said:
Did you solve this in the end?
Click to expand...
Click to collapse
I used the method that I posted to fix the tablet.

Nabi 2 hangs on bootloader

I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...

najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.

One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...

najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119

bricked lg k8 (lg-k350n) - is there a way to get to fastboot to flash anything?

I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!

Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?

xor512 said:
I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!
Click to expand...
Click to collapse
same here, we are two now.

Don Pedro! said:
Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?
Click to expand...
Click to collapse
your phone cannot be trusted loooooop, cannot goto download and fastboot mode...

If you don't manage to enter download mode you have probably indeed bricked the phone. If what I've written above doesn't work for you I know of no other way to resurrect it, sorry.
This is because you cannot burn TWRP to the Flash plus there's no tool available to bootstrap an LG phone with a completely naked or corrupted Flash. There must be something like that, because a freshly manufactured phone has by definition a naked Flash.
With Samsung phones you have Odin and with it it is possible to burn a software to a completely dead phone. So it is almost impossible to hard brick it. With LG unfortunately it is different. Plus this phone is somehow crippled, it has only a very, very limited amount of Flash. So I would recommend to not care for this phone anymore, it's not worth it, and instead get a current one with a decent amount of memory.

Better Mobile App

welcome