So heres what i got,an lgv410.i kingrooted,then i started deleting bloatware.eventually i deleted the wrong fat from the tablet and process com started looping.each time i clicked it.then if i set it down and screen went dark.on returning to it ,it would be process com then system ui.
I eventually got a bunch of apps into an sd card by transfering them with an rca 7" i bought at walmart.then i got brilliant idea to tether.well i got the otg cable but it seems i cant get it to work right either.i eventually was able to get what i think is a 55kb twrp installed on tablet via cm lite.i also have a lineage 300+ mb nightly.thing is i cant get nothing to install since i got the twrp on there.i got three options with what i assume is twrp.it says at top of black screen,fastboot,select up down,continue,power key then in red,restart,restart bootloader,and power off.
At bottom of black screen it says a bunch of gibberish.including in red,fast boot mode.
So can some one tell me what to do next.im under the understanding that i can somehow use sd card to make this right.like i said,i got this rca 7 ,a wifi hotspot with about 300mb left of data,an sd card. An otg cable,and most important,a frustrated hard head!
thankyou for your time,: )
Ill also add,i may have panicked months back and tried to delete kingroot.then i reinstalled.the label was still up in notification bar.thing is,the fat was gone,lol!
So im assuming i need new firm ware and that nightly lineage sounded sweet.so i got it.i like my tablets light and fast.i love the rush of of 1 ghz plus!
I also went over to hardware info a few days ago and there was none,lol,yep.yes its a real tablet.its just kinda retarded!
Shes my favorite due to having a magnetometer app.and the size is great too for just carrying around.i really like apps and was getting comfortable using rooted apps,especially the cpu clockers.but my absolute hands down most favorite app ever is ultimate emf app.it saved my life.you can even go to goo playstore where i commented to developer.please help me save my lg?
Related
So my wife left her phone on the roof of her car, then drove to work. Our neighbor dozens of houses away found it in his yard, tracked her down, and returned the phone. It worked for a few hours, then the screen died. The phone itself still works, but the screen will not come on. Apparently it got water damaged in this process, so we ended up getting a replacement thru insurance.
She would like to recover her photos from the old phone internal storage, but I can't get the computer to see the internal storage.
I can't remember exactly which recovery is installed, I think it's TWRP 2.2.1, but I'm not sure about that. I tried booting into recovery, then clicking on the screen where the "Mount" button is on my phone (TWRP 2.4.4), but her phone just vibrates when I click that location on her screen, and nothing happens.
Is there any way to force the phone to start into a mode that will allow me to access the internal storage?
I think I have USB debugging enabled, but it was many months since I rooted her phone, so I'm not sure exactly what the exact status of her software is on that phone.
thanks in advance for any help with this!
You can try something like this
http://forum.xda-developers.com/showthread.php?t=1821601
I just tried it and it works great, it looks like you can only do one at a time but its fast!!
Not sure if you know about adb, if not you need this installed.
http://developer.android.com/sdk/index.html
Did it work JustinChase?
That tool is now part of my collection.
Sorry, when I got home from work to get started on the process, the screen came on and I was able to access the internal storage without difficulty. Sadly, I'm still out the $150 for the replacement phone.
Thanks for the help, I hope to not need it again anytime soon.
Sent from my EVO using xda app-developers app
this worked for me. it may work for you but I can't guarantee it. let's start with some history. so I rooted with condi's awesome root tool. everything was great. one day while web browsing, the thing turned off. I was wondering, what the heck? rebooting only got me to the part where the golden ribbon flowed constantly. I guess they call it a bootloop. resetting and wiping data only got me into a worst scenario
so there it was. only had it for 4 months and the thing kaput on me. that's ok, got my receipt. even though it was rooted, I planned on sending it in without a doubt. I had bought as an opened item at frys. I'll just blame it on the 1st owner. anywho, couple of visits to Sony stores revealed that they were remodeling. they couldn't accept the tablet (I guess theres one near san jose, lucky me). Anyways, I even made attempts to contact through the web but nothing. I had just bought a galaxy s3 so I was like, oh well. its just a tablet. I left it sitting there collecting dust. One day my girl nags me to death to get it done. its almost been a year and I need to claim the warranty. Well, LOL. I lose the receipt. Yes, SOL.
What did I have left to resort to? Begging the crap out of condi to do whatever is in his power to help me. It didn't get me far. I gave up. So its been over a year since I bought the thing and I decided to give it another whack because I swear I had gone through the process of making sure I installed the boot loop protection condi had created. well, I can't find the charging cable. Wow, those things are hard to find and very expensive. I give up again.
Today, I was digging through my storage and what do you know, I find the charger. I was confident I could fix the tablet. This is what I did. After sitting there for so long, I charged it up a bit. I knew that I couldn't allow it to charge for too long. I noticed that if I ever ran into a situation that got me stuck at the sony logo and not allowing me to go anywhere, and the only thing I could do was to do a manual power off, the only way to get out of that is to let the tablet die.
So tip. If you get stuck at the sony logo, just let it sit there until it dies. only way I found to fix that.
I also, in the past, ran into the infamous E:verification failed yadda yadda yadda. something about not being able to mount the sd or some crap. I hated that error. I couldn't understand why it did that. well, today, I decided to try something totally outside the box. I figure it couldn't hurt. Prior to even booting up my tablet for the first time in 10 months, I inserted the sd card directly into a slot in my laptop and always noticed the drive letter came up (in my case) as J:. Now I kind of realize that the drive letter may or may not make any bit of a difference since its just a drive letter that the computer assigns, and in some cases, if inserted into another computer and that letter is taken, it then sets a different letter up for that SD. well, again, I'd figure what's the harm in trying so I went into control panel. administrative tools, computer management. on the tabs on the left, I went for the disk management under storage and decided to change the drive letter that my computer sees the sd card to E. Well of course I had a virtual drive set as E but with a little change here and there, I finally get the SD to show up on my laptop as E. I copied the nbx signature file that condi recommends that you copy to try and flash it during these "soft brick" situations, even copied my decrypted and signed update files just in case my first attempt fails.
as soon as I boot it up, I go into recovery mode. I select the file that condi suggested. right away it started saying it was updating. Nice. No e:verification failure messages. so I grin and watched it as it was actually flashing it. wowzers. and of course, towards the end after the 3rd bullet has been highlighted, I get ready to hold the Vol +, so that I can wipe data or else have to face this process again. Boom, wiped data and waited. Of course I was nervous as I watched the dancing golden ribbons, which I have seen dance in front of me endlessly before in the past. Then, the setup screen pops up. YES. I got it fixed!
On what android O.S did your tablet last had?
nbx signature file?
numbaonenewb said:
this worked for me. it may work for you but I can't guarantee it. let's start with some history. so I rooted with condi's awesome root tool. everything was great. one day while web browsing, the thing turned off. I was wondering, what the heck? rebooting only got me to the part where the golden ribbon flowed constantly. I guess they call it a bootloop. resetting and wiping data only got me into a worst scenario
so there it was. only had it for 4 months and the thing kaput on me. that's ok, got my receipt. even though it was rooted, I planned on sending it in without a doubt. I had bought as an opened item at frys. I'll just blame it on the 1st owner. anywho, couple of visits to Sony stores revealed that they were remodeling. they couldn't accept the tablet (I guess theres one near san jose, lucky me). Anyways, I even made attempts to contact through the web but nothing. I had just bought a galaxy s3 so I was like, oh well. its just a tablet. I left it sitting there collecting dust. One day my girl nags me to death to get it done. its almost been a year and I need to claim the warranty. Well, LOL. I lose the receipt. Yes, SOL.
What did I have left to resort to? Begging the crap out of condi to do whatever is in his power to help me. It didn't get me far. I gave up. So its been over a year since I bought the thing and I decided to give it another whack because I swear I had gone through the process of making sure I installed the boot loop protection condi had created. well, I can't find the charging cable. Wow, those things are hard to find and very expensive. I give up again.
Today, I was digging through my storage and what do you know, I find the charger. I was confident I could fix the tablet. This is what I did. After sitting there for so long, I charged it up a bit. I knew that I couldn't allow it to charge for too long. I noticed that if I ever ran into a situation that got me stuck at the sony logo and not allowing me to go anywhere, and the only thing I could do was to do a manual power off, the only way to get out of that is to let the tablet die.
So tip. If you get stuck at the sony logo, just let it sit there until it dies. only way I found to fix that.
I also, in the past, ran into the infamous E:verification failed yadda yadda yadda. something about not being able to mount the sd or some crap. I hated that error. I couldn't understand why it did that. well, today, I decided to try something totally outside the box. I figure it couldn't hurt. Prior to even booting up my tablet for the first time in 10 months, I inserted the sd card directly into a slot in my laptop and always noticed the drive letter came up (in my case) as J:. Now I kind of realize that the drive letter may or may not make any bit of a difference since its just a drive letter that the computer assigns, and in some cases, if inserted into another computer and that letter is taken, it then sets a different letter up for that SD. well, again, I'd figure what's the harm in trying so I went into control panel. administrative tools, computer management. on the tabs on the left, I went for the disk management under storage and decided to change the drive letter that my computer sees the sd card to E. Well of course I had a virtual drive set as E but with a little change here and there, I finally get the SD to show up on my laptop as E. I copied the nbx signature file that condi recommends that you copy to try and flash it during these "soft brick" situations, even copied my decrypted and signed update files just in case my first attempt fails.
as soon as I boot it up, I go into recovery mode. I select the file that condi suggested. right away it started saying it was updating. Nice. No e:verification failure messages. so I grin and watched it as it was actually flashing it. wowzers. and of course, towards the end after the 3rd bullet has been highlighted, I get ready to hold the Vol +, so that I can wipe data or else have to face this process again. Boom, wiped data and waited. Of course I was nervous as I watched the dancing golden ribbons, which I have seen dance in front of me endlessly before in the past. Then, the setup screen pops up. YES. I got it fixed!
Click to expand...
Click to collapse
Where can I find this nbx signature file? Sony Tablet *111GB/s. I've bricked it.
Helo Everyone , its been a while since ive logged on here, but I have an issue, A friend of one of my youngest daughters gave her a netbook WM8850 , her friend had forgotten the password and it came with no paperwork, box, etc. as it boots to password screen it shows android 4.0, and 1.5.1 version, kernel is 3.8.6. i believe. Can anyone tell me an easy way to get around this issue, this particular one does not have vol up/dn buttons, but it does have a reset button in back, I have spent countless hours searching and trying to get this thing to boot to boot menu, I formatted a 4gb sd card and installed script on it , rebooted device and no boot menu, it didn't acknowledge the sd card. I even tried emailing overseas about this issue as it was a gift and they would not help me without a receipt original box and paperwork. Any help will be greatly appreciated. I disassembled the device to get numbers off of inside. I am fairly proficient with hardware and repairing electronics, but when it comes to using software and understanding what everything means I struggle sometimes, especially since the same desired outcome is told so many different ways, lol. Hope everyone had a great Thanksgiving and look forward to your reply
Ok, i've got 5 options and i'm not sure how to un bootloop my tab 4 7.0.... i may not of deleted the OS off the tablet while at the same time losing all my back ups etc..
now,i have a samsung chromebook, it's soul purpose is o collect my kids drool and play cartoons on netflixs over and over. all jokes aside, can't do an adb sideload, considering usb debugging isnt on, another being i have no External SD card, nor a OTG cable of that sort i do have a usb drive yet useless. i'm 6 hours from a walmart mind you (UPS NOR FEDEX deliver anything to my house) and yet charter still supplies service out here, at around 40-50 mbs.. not too shabby lol. so my options i've weighed out over the last two weeks with this problem boil down to this.
1, manually changing permissions threw TWRP terminal on basic functions to get this to boot on and get usb debgging enabled and unknown sources on...(everything even after fixing permissions is read only in which i cant even read)
2. unmount and remount ext4 system, hopfully that'll maybe fix this issue (thinking back after i first rooted I was always on EXT3.. dunno but /system can not be touched or even found if transferring to ext 3 now..(from2 weeks solid research and about 2 thousand forum page later this may just be my problem.. yet i've tried every variation to do this is always fails or gives me another excuse)
3. follow samsungs advice and every advice out there and thats using the factory recovery to enable a hard reset from there which does everything i mentioned above by default, no more dumb luck and pray i stumble upon the problem
4.. all together unroot my phone start from scratch when i go and get my alienware desktop and laptop customized and ordered. I'm willing to spend 3k on a x20" and another 6k their premium dev desk top.. just to learn this skill, trade? gift possibly... unlock this new found love, that has literally made me start menopause at 24 (i can't go into town for another 2-3weeks :/)
5 being "take it apart peice by peice" and let the cpu reset with the battery and hardware no tehered and or connected and everything reset to "holy **** i'm brand new out of the box" <----- i read this only once every where else said ^^^^ this guys a ****ing moron.. Pardon my frenc........ uhh too soon, spanish... yea that one.. lol If you didn't at least smerk at that you're the problem <3 Thanks guys
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
No adb access? That sucks, as it should be pretty easy to fix if you could adb push. Were it mine, I'd go ahead and try to replace the screen on the functioning tablet. Not what you want to hear, but I think that's the only way to get working again. Best of luck.
Valence1981 said:
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
Click to expand...
Click to collapse
You're done if device is running 4.5.2 w/no adb access. There are a few last resort unbrick methods/tools but they are geared toward older versions of FireOS (v3.2.6 and below). Replacing the screen on a 7" HDX is difficult; copious use of glue makes for a tough job. Might check auction sites; prices are pretty low for 16GB models. Also consider the latest 7" tab from Amazon (2015 Fire). Specs are awful vs HDX but it really isn't that bad, especially for video and with apps designed for lower resolution screens (many are). Fully rootable with option for custom roms. FireOS v5 is a nice step up from v4, faster and more 'android like' (although still heavily skinned).