Related
Alright...I was not sure to post this in development or what because of the thread that stated it was not a Q&A thread, so I came here.
Reason for is I am totally stuck...i have a rooted evo 4g with omj eclair v1.6 and from there it has given me nothing but trouble. At this point i cannot put my phone in recovery for what ever reason (may I add that i have tried all the necessary ways to do so) and now I can't seem unroot my phone. I followed the youtube vid constantly to every detail but I constantly get get the usb error then I tried doing by powering off my device and turning it on with volume buttons and I constantly get the gives me the 140: bootloader version error. At this point I have no other alternative but to try and return the phone for a new one. If there is any other solution for this problem I would be greatly appreciated because I just want to unroot my phone please.
reference this thread
http://forum.xda-developers.com/showthread.php?t=712844&highlight=ruu
Have you tried looking that this guide and look for the USB part of the thread?
yea the guide is useless because I constantly get errors and for the ruu, again I will try it but I may get the same result. Rest assure if it happens a few more times I will try to gamble and take it back for a replacement phone.
Do you have HTC Sync installed?
lol, guys like i said before when i made the thread, I have tried most of the options that I have found on the net....yes that includes D/L htc sync. If there is no solution for my case then don't worry bout it becasue I have an appointment to go to sprint store tomorrow. Although I do appreciate the help.
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!
heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!
Click to expand...
Click to collapse
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.
Sorry, but where do I enter these commands?
soupmagnet said:
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.
Click to expand...
Click to collapse
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?
heatherrc77 said:
Sorry, but where do I enter these commands?
Click to expand...
Click to collapse
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038
heatherrc77 said:
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?
Click to expand...
Click to collapse
You need to download the Android sdk, then you can run adb from the command line.
Sent from my Amazon Kindle Fire using Tapatalk HD
heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory,
Click to expand...
Click to collapse
I know this isn't helpful now. But the original problem (I am pretty sure) had to do with the drivers with the audio. You probably had the volume all the way down, which causes the error you were receiving. If you mute it, that is fine, just don't have the volume down all the way.
----------------------------------------------
Sorry. I know this probably doesn't do you any good, but I thought I would let you know what I thought.
soupmagnet said:
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".
heatherrc77 said:
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".
Click to expand...
Click to collapse
I put a lot of thought into how I should respond to this post, so bear with what I'm about to tell you.
My previous post was not intended to "belittle" you, rather, wake you up to the reality that you might not be ready to take on such an endeavor. This is not an iPhone and it isn't as simple as plugging it in and pressing a few buttons. For new users, there is a high degree of risk involved in certain aspects of modifying the Kindle Fire, especially when it comes to repartitioning...which is what you'll need to do to get your Kindle working again.
My harshness is NOT out of ego or feeling "holier than thou". It is not to make myself feel better or to make up for some low self esteem. Treating people with kid gloves around here tends to give them a false sense of security that quite often leads to them getting into very stressful situations. Besides, a little "tough love" is better than indifference any day.
I created a thread in the General forum a while back, titled "**WARNING** You will BRICK YOUR KINDLE if you don't READ THIS FIRST!!!". The purpose of that thread is to warn owners of newer 2nd generation Kindle Fires of the DISASTROUS consequences of trying to modify those devices in the same way the 1st generation devices are. One would think, with a title like that, there would be very few people to make that mistake. Of course one would be wrong, as there are at least two individuals a week that were not prepared to deal with the situation at hand and did not give it the appropriate amount of respect, therefore their Kindles are completely worthless. Needless to say, if something I say is construed as rude yet prevents mishaps like that...so be it...and I'll consider it worth the hurt feelings.
And I agree, in order to learn, sometimes you have to get your hands dirty. But there is a big difference between tweaking some system files contained within a single partition and actually modifying partitions. And yes, you do have to start somewhere, but if you don't know that commands go in the command prompt (and I'm saying this respectfully), this is not the place for you to start. Go back, read through the links I gave you, and get a better foundation to work from before trying to fix your Kindle Fire. Not doing so, would do you a great deal of injustice.
No hard feelings,
And I wish you the best of luck.
Hey guys,
First off, I don't have any idea where to post this as the phone I'm working with isn't on the forums, so I thought it would be more appropriate here. Please move it into the correct place if there is one. Thank you.
So I'm a new comer of course and I was browsing the internet for solutions to my friends phone issue and I came across this forum. From what I can tell this is a really intellectual environment and therefore was inclined to make an account to see if anyone can help me out with my issue.
The problem(s):
Currently my friend's HTC Wildfire S (T-Mobile) is locked out.
He had tried too many times to unlock it via the pattern and now has to enter in his google email credentials to unlock his phone.
Right now the wifi or data is not on for the phone
Failed solution 1: I tried to call him and have him answer the phone. I then tried to pull the notification tab down in order to enable data or something but that didn't work. I had read on another website that it could work.
Failed solution 2: I downloaded ADB and tried to access the settings.db file in order to edit it via an add on on mozilla firefox. After going to the path where ADB was located i typed in "dir", where settings.db usually is it wasn't there. I then concluded that he probably didn't have USB debugging enabled as that is a strange setting to turn on for no reason.
And now here I am...
He doesn't want a factory reset because he wants his texts, I can only guess that he has important nudes he wishes to save, haha.
Anyway, I'm not too educated in computer or coding language, so if you have any ideas please provide me with some extra details for my noobie status.
As a result of this tinkering, I'm kind of interested in learning how to code and messing around with my Samsung Galaxy S2, so if you also have any pointers for that I'd really appreciate it.
Thanks for your help in advance,
I look forward to engaging in the community and trying to contribute
There is a forum for the Wildfire S. Search at "Type Your Device..." and you'll find it.
Sent From My GT-I9000 Running Mackay ROM KK4.4
86356522
vhngu930 said:
There is a forum for the Wildfire S. Search at "Type Your Device..." and you'll find it.
Sent From My GT-I9000 Running Mackay ROM KK4.4
Click to expand...
Click to collapse
Thank you very much!
first off, I am sorry for the many posts ans questions about this but i cant get any solid answers or help. I have tried every thing suggested and still no results. when I go into about phone at the bottom (i forget what it says) but the answer says "custom" I have ran every version of odin and have tried, CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5 , also N900TUVUBMI7_VEGA.tar.md5, also N900TTMBBMI7_CSC.tar.md5, and have tried different cords , ports, turned off all security's,. I got into developer mode and checked the usb debugging box but I don't have the option in security to change write privileges.. when I run odin sometimes it will say reset, sometimes it says pass but only once did it reboot the phone, but I have no super user app in the drawer and in odin mode it says write protection: Enable (in grey) it also says current binary :custom, system status :custom, know kernel lock 0*0, and knox warranty void: 0*1
I think I have gotten down all the info I can think of that may help someone figure out what the problem is. I would really appreciate any help or ideas you may have and appreciate your time helping me. I will be sure to hit the thanks button.
also I should when I do reboot my phone it will still go to my launcher but constantly a message ( unfortunately direct pen input has stopped) I have to to hit ok then I can press on something one time then it locks up for a few seconds until the message pops up again and I hit ok then I can press another button, and I have to keep doing this until I get where I'm going. ( a text message would take 20 minutes to write) the phone locks up until that message pops up. I went into settings and turned off everything that has to do with the pen but no help.
also if anyone still has one of the first CF TAR files if youi could get that to me I could give that a try. i got my phone when it first came out and am still on all the older versions of everything so that might work thanks
Use the previous topic you created for this issue:
http://forum.xda-developers.com/showthread.php?t=2736873
You don't need to create a new topic for the same issue.
krelvinaz said:
Use the previous topic you created for this issue:
http://forum.xda-developers.com/showthread.php?t=2736873
You don't need to create a new topic for the same issue.
Click to expand...
Click to collapse
i understand and I apologize but I need this phone for work so it is very important I get it fixed, My thread is getting no real attention so I was hoping to get the topic back on the first page pus I had more information to add. I wont create another on this topic I promise.. I just really need some help on this. sorry for the inconvenience.
So I created this topic because there is hardly anything on the internet regarding this tablet. I just recently purchased it from Best Buy and it took me quite some time to find something that would help me root it. Finally, I tried vroot ( a rooting application) and I succeeded in rooting my tablet. I don't have the exact link I used to get vroot but a simple Google search should suffice. Anyway, I figured I'd start this topic for anyone and everyone who uses this tablet or knows of this tablet to discuss any other developments. For now, if anyone needs help rooting their tablet and getting superuser running, I'm here to help.~
For now, I hope you all can figure out how to use vroot (yes, I know it's in Chinese. I can not read Chinese but it was pretty simple to get through the process of rooting.) Anyway, I don't remember the specifics but if anyone else gets through it, I ask that you please post some details on how you did it for everyone else to get through it as well. Hopefully, with time, we can get some good stuff going with this tablet. Could anyone figure out how to get CWM Recovery running on it? I'm a bit new to this and I don't want to screw anything up.
Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!
arpitp said:
Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work. If you want to try the software, however, I've connected it to my computer numerous times without the need for any special drivers. Only thing I can suggest is the generic google drivers. By the way, I reverse searched the tablet's hardware and kernel and came across a duplicate device from China. It is exactly identical right down to the appearance, hardware and software to our tablet. It is called the Chuwi VX8 and the only difference is that it comes in white rather than black.
After making this discovery I came across a nice little development topic for the clone device (http://www.freaktab.com/showthread.php?16025-Chuwi-VX8-RileyROM-1-1) and it seems they've founded good amount of research into the tablet. They've come up with a rom (I've yet to test), CWM Recovery (Unable to flash. If anyone else can try, that'd be dandy.), root methods (with links), among other things. It seems that anything that would work with the Chuwi tablet SHOULD work with the Digital2 Platinum Pad 8. The same rooting method was required and everything about the two tablets is perfectly identical so I'm led to believe they're going to be able to use identical roms or recoveries. I'll look more into flashing CWM Recovery tonight and get back to you on my results.
Josh8550 said:
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work.
Click to expand...
Click to collapse
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.
arpitp said:
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.
Click to expand...
Click to collapse
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.
Josh8550 said:
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.
Click to expand...
Click to collapse
As you mentioned, the link was for the (Windows) software. It requires ADB connection to a computer (usually requires special drivers).
When you said you used the application instead of the software, I assumed you used an APK. However, there is no apk of (the official) Vroot (it was designed to work through Windows). That makes me think the root app you used was something else. So I have to ask... what did you use to root this device?
vRoot is now iRoot
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
UPDATE: (IMPORTANT, please read): The APK does not work. or at least, I couldn't get it to work on my device. It tells you that you've got root, but doesn't really give it to you. Download the computer based exe from the link that Josh8550 posted earlier.
You will need developer permissions (Settings -> About Tablet -> tap Build Number until it tells you you're a developer).
Install ADB and Drivers on windows PC (http://forum.xda-developers.com/showthread.php?t=2588979)
Connect tablet to PC with USB cable.
Run vRoot (iRoot) on PC. Program will connect to tablet and check for root.
Click the "Get Root" button.
Wait...
Tablet will reboot.
Wait...
Program will connect to tablet and check for root.
Program should verify that you have root.
Download and Install SuperSU from the Play Store.
Open SuperSU and Update SU Binary. You will have to give SuperSU root permissions from the chinese interface (choose the box on the right, don't mark the check box).
Reboot.
Congratulations! You now have root access. Enjoy!
More info to come later...
nahrwoldinternet said:
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
Click to expand...
Click to collapse
Thanks man. I couldn't find the link to the apk again so that's a huge help for everyone here. I'll try to get CWM recovery working soon then I'll see about getting Cyanogenmod 11 ported over.
Rooting Digital 2 tablets
Hey everyone.
I successfully rooted with Kingo ROOT using my PC, however now Im stuck. Cant seem to find ROMs or Mods compatible with this tablet.
Any info out there would be great. Im running a 4.1.1 Jelly Bean.
Rooted now what?
Did you ever try the cwmr or cyanogen ROM you had mentioned above?
[email protected] said:
Did you ever try the cwmr or cyanogen ROM you had mentioned above?
Click to expand...
Click to collapse
I did, and ended up hard bricking it for months until I finally got it back out, fixed it and gave up.
I also have the D2-861G and ended up bricking it but have been unable to fix it, would you mind telling me how you got it back up and running.