Database Info

Easy root for Thunderbolt on Mac OSX

Easy root for Thunderbolt on Mac OSX
I wrote this and seems to work fine the few times I have used it.
If you guys run into any problems or errors please let me know so I can see whats wrong.
Follow the Video set by step.
Sorry if I talked quietly I'm sick.
Enjoy!
Fixed. If you are getting a adb command not found error. Redownload the big file or download the runmefix.zip (Check your tube video) uncompress the file and put runme in the thunderbolt directory of your desktop.
If you download the big file after April 9th 2011 at 7:30am then you do not need this fix

Saw the video. Got the files. Will be doing this as soon as my phone is charged in the AM. Hopefully it works.

hkbladelawhk said:
Saw the video. Got the files. Will be doing this as soon as my phone is charged in the AM. Hopefully it works.
Click to expand...
Click to collapse
Just now saw this. Did it work for you? Any problems after?

djkeller3 said:
Just now saw this. Did it work for you? Any problems after?
Click to expand...
Click to collapse
Yes. Worked awesome. Takes a while, but it worked. Just make sure to follow directions to the T, I accidentally hit enter on a command too soon and had to start over. But all works as far as I can see. Super easy, but takes a while.
Thanks again to OP!

This looks great--no messing around in ADB?

Its uses adb but you don't have to worry about it or anything like that.. The download includes what it needs.

fryetech said:
Its uses adb but you don't have to worry about it or anything like that.. The download includes what it needs.
Click to expand...
Click to collapse
Yeah it worked great for me, the first time around the phone booted earlier than it should have and I had to do the whole thing over, and the second time I tried to remover the Verizon Backup via titanium backup (**DO NOT TRY THIS**) and almost bricked my phone, and so the third time everything worked perfect and now Im running Perfect Storm by Chingy and its awesome thanks!

My phone isn't recognized. Usb debugging is checked but the terminal window just says checking for phone over and over. Any ideas ?

beavis1226 said:
My phone isn't recognized. Usb debugging is checked but the terminal window just says checking for phone over and over. Any ideas ?
Click to expand...
Click to collapse
I had that happen for me as well. It seems that by default the Mac doesn't recognize it. Click ignore on the pop-up and click okay for charge only. Unless this is what you did. In that case try again
Sent from my ADR6400L using XDA Premium App

thanks good work

how do you start over? do you just turn off the phone and restart the app on your computer?

Major problem - tf101 bricked

I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)

need more info
what model number do you have, what can you get into, what cant you get into etc

lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.

You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf

baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.

What is the serial number of your tf?
Hopefully it's one that's nvflash compatible

baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90

i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.

I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.

gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?

The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?

roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?

If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.

gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?

joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.

In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??

gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.

Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.

gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...

Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision

LG-P870 LG Escape: How to root, KDZ and other info

Seeing as there isn't a section for the LG P870/LG Escape I'm going to try and get as much info condensed into one thread for now.
Not even sure how popular this phone is but, hopefully this will be of some use to someone.
KDZ:
I know this isn't posted anywhere so here is the v10f KDZ from LG. It is the latest firmware as of 11/6/2012:
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP870/AATTBK/P87010f_00/P87010f_00.kdz
If you don't know how to flash a KDZ I will make a guide here soon. V10f is rootable using the method below as is v10c
Download Mode:
To get into download mode turn off your phone, press and hold the vol+ and vol- keys, with those held down insert the USB cable while continuing to hold down the keys. After a few seconds phone will enter download mode automatically.
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.

Thanks! My wife just got this. I was able to root and update and retain root with OTA rootkeeper. Was looking for a kdz just in case. If there's enough interest i will see if i can port TWRP so we can cook up some custom roms.

I am definitely interested in custom roms, I have this device. Its not bad considering the price and what you get. 1494 on geekbench too! Pretty decent!
---------- Post added at 07:49 PM ---------- Previous post was at 07:44 PM ----------

Thanks for the effort

Aye guys I'm new into rooting and android in general, but I don't really understand how to root this phone. Kinda been looking around for a while and I was wondering if you can write some sort of guide. As of now I'm pretty lost the other threads aren't giving me any general information on exactly how to root the LG P870 or androids in general.
-Thanks
Btw I understand what exactly what rooting does to your device and the purpose of rooting, its just exactly how to root the device.

Well first things first do you have the android SDK installed on your computer

cyclejim said:
Well first things first do you have the android SDK installed on your computer
Click to expand...
Click to collapse
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Urabewe said:
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Click to expand...
Click to collapse

He
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!

Thanks for the effort

GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
KDZ is the LG format for ROMs which is the built in read only memory that hold the instructions for the phone to run the hardware and features.
But I just rooted my phone with a combination of the above files, and it didnt go exactly as I hoped. First I ran the v1.2 batch file linked above, (the 1.6 batch file archive is invalid and doesnt extract properly. It seemed like it ran properly, i did the restore (no data destructive you shouldnt lost any data) but I didnt have root when completed. Then I tried the v17 of the original thread which can be found here http://forum.xda-developers.com/showthread.php?t=1886460
That one also ran but failed at the end saying something about me not having root on the phone.
I than ran the v1.2 batch file not once, but twice in a row. The second time I found my phone operating in "emulator mode" in other words, it was running laggy as hell and very slow. I then ran the V17 batch file from the link above, and boom it worked. So as you can see it wasnt typical, but I think if you dont have success with the 1.2 the first time, run it again, if it still didnt work, try running v17 like i did. I now have root and my phone is working fine.

Basically, I got the Escape then got the Nexus7 and have been involved in that. Really haven't been doing much with the Escape. I will be looking into more for everyone and hopefully get a custom recovery at the very least. Then at that point we can start thinking about rom. Until then we are stuck with what we have. I will get more info for everyone , till then this is what we have. If you think you can help go for it. If not sorry but this is the best info there is for our phone . I will positively without a doubt post any new info here so if that's what you are looking for this is the right place until then, thank you and you are welcome.
Sent from my Nexus 7 using xda premium

Markyzz said:
He
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Click to expand...
Click to collapse
So when I run the .bat file do I just run it in cmd? I'm kinda knew at this lol.
Also does my phone have to be in download mode?
Sorry for the inconvenience but where exactly do I run the .bat file?
-Thanks
One more thing I never downloaded a .zip or .rar file.. Could you please leave me a link?

Rooted
Thanks people I guess I just needed time to figure it out lol. I ran it in cmd twice(1.2v) but not right after each other and the second time it worked thanks guys.
Well. I tried to install beats audio but now it won't even load up just boot loops when it gets to at&t...

Bricked
Great the first bricked lg p870 lol, anyone know how to fix this. Or is it just a brick?

Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?

GHazard said:
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
Click to expand...
Click to collapse
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium

Markyzz said:
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Is their a guide on how to flash the device using the kdz flash tool? I mean my phone won't turn on though. It goes into the lg logo then just goes black (the back light is still on).

K I have all the tools but
I downloaded every tool from this thread
But in the PDF guides it says to put the phone in Upgrade mode by removing the SIM, battery and SDC(Micro sd card?) so I did that. Then insert the usb while holding the Volume Up button. All that happens on my phone is the home keys on the bottom just flash. And my phone doesn't connect to my computer either.

My Notes on LG P870
Ok I have fixed my device, well twice now. It seems whenever you try to change any file within the root it restarts, then boot loops. I tried too change a font using Rom Toolbox, it restarted then boot looped. I rooted the device using the 1.2v script once, but this time I'll try 1.7v and see if I can change fonts etc.
Are any of you guys having any problem with this?
If you do, and you are soft bricked just:
Download UPK 3.7.1
Then open up LG /mobile Update
Click Install Drivers(Make sure your phone is not connected) Choose your phone and carrier
Let that finish(Gonna take awhile you have to install all of them)
Then click Install updates...Done

Worked
Posting confirmation for an LG Escape (p870). 10f rooted using the tools linked in first post. Used version 1.2 to start and had to use the version 17 of the other rooting kit to finalize like another user encountered as well. Thanks will be given if they haven't been yet.

[Q] I made a stupid mistake. I formated data and now I don't have any OS.

Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?

BombasMirko said:
Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?
Click to expand...
Click to collapse
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.

ttl1982 said:
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.
Click to expand...
Click to collapse
Moutning doesn't work.
I found this: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Will this work for me? I was never in this situation before.

You can either use adb to push a ROM zip to your phone, or just flash the stock images to your phone. http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5

Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?

pyrogoggles said:
Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?
Click to expand...
Click to collapse
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.

BombasMirko said:
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.
Click to expand...
Click to collapse
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!

pyrogoggles said:
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!
Click to expand...
Click to collapse
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.

BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation

BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk

justinisloco said:
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lol I thought I was the only one who does this
Sent from my HAMMERHEAD

Aerowinder said:
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation
Click to expand...
Click to collapse
Yeah and this is actually the best school to learn new things. Now I know that it is not that bad at all

Adb update! Plz help stuck in recovery! [Q&A],[SOFTBRICK/BOOTLOOP], QTAQZ3

Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk

SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49

samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse

samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk

ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse

Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .

ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk

samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse

ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!

samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?

samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk