So far, fit and finish is outstanding. Better than a number of units that have gone through our hands in testing. (I'm keeping this one) Very, very little bloatware. But, not having root and the ability to write to SD etc is a PITA
Root was achieved using the method developed by social-design-concepts You will want to use the T4 trigger option. His thread is here. You will want to be sure that you use the download he mentions that are what he calls the public trial release, it's here
Glad to answer any questions about the device and follow up questions as well. I'm conversant with adp, etc.
Thanks!
Sent from my Venue 10 7040 using Tapatalk
Does this work on the latest Lollipop 5.1 firmware update?
Yes, it does.
How did you get the adb fastboot to work? I've installed the universal adb driver from http://androidxda.com/download-dell-usb-drivers but I still haven't gotten it to work.
I checked the Device Manager and the only unknown device is MTP.
Thanks!
I generally switch connection types to mass storage VS MTP and that makes it happen. Do remember that on occasion you have to specify the exact driver in device manager, Windows necessarily get it right. (Not being condescending mind you, just not sure where your skill level is at.)
I could use some help... After the T4 selection Fastboot Mode starts doing it's thing and attempting to copy over files but in the end it says Result: Fail (command now allowed in this device state) and I noticed the device state is Locked...
That's pretty straight forward. In short, your bootloader is still locked. Social design concept covers this well in his post. It's the first link in my original post. My apologies for the late reply. Been bringing up my Nexus devices to Marshmallow and dealing with all that.
Fearcher said:
That's pretty straight forward. In short, your bootloader is still locked. Social design concept covers this well in his post. It's the first link in my original post. My apologies for the late reply. Been bringing up my Nexus devices to Marshmallow and dealing with all that.
Click to expand...
Click to collapse
Hello Fearcher Congrats on rooting your 7040! Im in desperate need of your expertise. Trying to root my 7040 on L5.1
-installed drivers
-bootloader unlocked but text is in red?
-adb devices attached successfully
-fastboot devices found successfully
-have tried t4 on both tools with remote flashing to this partion error?
-tablets encryption is "encrypted"
Please help me root this tablet what am I missing?!
Is there anything about rooting 5.1 on a venue 10 that would prohibit future updates? I have read of rooted venue 8 users being unable to update to 5.1 after root but there was speculation that it was due to it being a 5.1 based root to begin with. I don't know enough about the details to know if this is plausible. This is the post I am reffering to: http://forum.xda-developers.com/showpost.php?p=64196214&postcount=15
I'd like to root but if it means no future updates that would be a deal breaker. Fearcher, you say this root method works on 5.1. Does this mean you had updated your tablet from 5.01 (rooted) to 5.1? If so did it require any special procedure or was it an OTA update? Thanks for you help
what driver do i need
Hello.
I've tried the ADB fastboot driver found in this thread and the stickied one. I've gone into device manager and selected several different drivers including the one named "dell adb fastboot" something which required me to turn off driver signature enforcement. Driver installed fine every time. When I launch the program I get the correct status message. Everything is right according to the instructions. I'm still getting the fail when it tries to install its files (command not allowed in this state).
What am i missing exactly? I've followed everything i can find in both this thread and the linked thread.
I have the latest 5.1 update from dell/google. I just bought the device from dell. My PC is Windows 10 64 bit if that matters. Driver signing is off.
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
r_nation said:
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
Click to expand...
Click to collapse
That's what I was thinking. is this because the 10 has a different chip than the smaller versions or something? It seems like they're having fun with their root and stuff. I thought moving to a device without a carrier would be easier. I have no idea why these are locked. it's nuts.
both models have same processor. It has to do with android 5.1 , they were able to root because there was kitkat firmware they could flash. Actually I don't even think my above method will work. We have to wait for an Intel based custom recovery for lollipop 5.1 but don't unlock your bootloader til there is one available.
whosloosin92 said:
I...
I'd like to root but if it means no future updates that would be a deal breaker. ...
Click to expand...
Click to collapse
Don't worry about future updates because they aren't coming. Dell killed off the Android dev team last year, so these are amazing but orphaned devices.
Are you sure?
bcjackson said:
Don't worry about future updates because they aren't coming. Dell killed off the Android dev team last year, so these are amazing but orphaned devices.
Click to expand...
Click to collapse
bc are you sure, who told you this? I am also a corporate customer of Dell, I am going to go to my SE and see what he saids. I am not doubting you, really hate to hear this actually. But I just find it hard to believe. But you and I know, it's all about the money. If they are not moving the 7040, then...bye, bye.
r_nation said:
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
Click to expand...
Click to collapse
Do tell if u are able to root it in 5.1
They have enabled encryption by default so it would be tough
I don't want to go back to 4.4 :c
That opensource firmware is lollipop. There is literally no development for venue 10 7000 root is still impossible.
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
rcbarr said:
bc are you sure, who told you this? I am also a corporate customer of Dell, I am going to go to my SE and see what he saids. I am not doubting you, really hate to hear this actually. But I just find it hard to believe. But you and I know, it's all about the money. If they are not moving the 7040, then...bye, bye.
Click to expand...
Click to collapse
Dell now confirming that they are discontinuing Android lines and will not provide further updates.
http://www.pcworld.com/article/3090466/android/dell-stops-selling-android-devices.html
bcjackson said:
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
Click to expand...
Click to collapse
So the baseline is that u cannot root once you upgrade to 5.1?
---------- Post added at 02:15 PM ---------- Previous post was at 02:09 PM ----------
bcjackson said:
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
Click to expand...
Click to collapse
So the baseline is that u cannot root once you upgrade to 5.1?
well now that they have abandoned android maybe they will release the open source?:crying:
Related
So I have the ZTE Midnight (Z768G) and I am getting the classic "low on space" message and I know what rooting is as I rooted my Nook Tablet 4GB but I can't seem to find a root that will work for my phone so that I can set my default storage to the SD card and I was wondering if someone could help me. Or if there's alternatives to rooting it that would also be nice. I installed an app that can erase cache but it's not doing much for me right now. I can't even update my apps. Any help would be nice!!
-Luciano
Root ZTE Midnight using kingo root - works!
lucianodiaz5 said:
So I have the ZTE Midnight (Z768G) and I am getting the classic "low on space" message and I know what rooting is as I rooted my Nook Tablet 4GB but I can't seem to find a root that will work for my phone so that I can set my default storage to the SD card and I was wondering if someone could help me. Or if there's alternatives to rooting it that would also be nice. I installed an app that can erase cache but it's not doing much for me right now. I can't even update my apps. Any help would be nice!!
-Luciano
Click to expand...
Click to collapse
went to kingoapp.com and downloaded and ran the app against my ZTE Midnight from Net10 - I now have root access. I did not buy the phone to make calls - the $20 price tag for an Android test platform was too goo to pass up.
covergeek said:
went to kingoapp.com and downloaded and ran the app against my ZTE Midnight from Net10 - I now have root access. I did not buy the phone to make calls - the $20 price tag for an Android test platform was too goo to pass up.
Click to expand...
Click to collapse
It worked but now I can't move the apps over to the SD card like I wanted to. I tried doing the /System app mover method of turning system apps to normal apps and uninstalling but it's still giving me that message.
Find the posts dealing with zte and link2sd. I am able to now install anything without space worries
Sent from my Z768G using xda app-developers app
Question:
After Rooting, can anyone install CWM & Install Custom ROM?
I'm looking to Root, Install CWM, then Install Custom ROM for Android v4.0 or higher.
Anyone successfully Rooted & Updated to Android v4.0 or higher.
Please advise. Thank you!
*** UPDATE: Kingo Android ROOT = ROOTED my (NET10) ZTE Z768G ***
*** LOOKING: Custom Recovery & Custom ROM (Android v4.0 or higher) **** Anyone ???
dtkool said:
Question:
After Rooting, can anyone install CWM & Install Custom ROM?
I'm looking to Root, Install CWM, then Install Custom ROM for Android v4.0 or higher.
Anyone successfully Rooted & Updated to Android v4.0 or higher.
Please advise. Thank you!
*** UPDATE: Kingo Android ROOT = ROOTED my (NET10) ZTE Z768G ***
*** LOOKING: Custom Recovery & Custom ROM (Android v4.0 or higher) **** Anyone ???
Click to expand...
Click to collapse
What drivers did you use to get Kingo Android Root to work? Nothing seems to be working for me...
ZTE Midnight!!!! No luck
I am having no luck with root.... tried all
How?
covergeek said:
went to kingoapp.com and downloaded and ran the app against my ZTE Midnight from Net10 - I now have root access. I did not buy the phone to make calls - the $20 price tag for an Android test platform was too goo to pass up.
Click to expand...
Click to collapse
How did you get kingoroot to run? I get stuck at "Installing Drivers" forever. I've tried installing my own drivers, both the included ones from the phone's internal memory as well as the latest ones from ZTE, and the ZTE ones that kingoroot points me to in the troubleshooting section. I'm running Win8 and I've also tried disabling Signed Driver Verification. What is the magic spell to get this thing to run? I agree $20 is *****in if I can just get the thing rooted so I can install more than 1 app and *cough* turn on tethering
jawa6988 said:
How did you get kingoroot to run? I get stuck at "Installing Drivers" forever. I've tried installing my own drivers, both the included ones from the phone's internal memory as well as the latest ones from ZTE, and the ZTE ones that kingoroot points me to in the troubleshooting section. I'm running Win8 and I've also tried disabling Signed Driver Verification. What is the magic spell to get this thing to run? I agree $20 is *****in if I can just get the thing rooted so I can install more than 1 app and *cough* turn on tethering
Click to expand...
Click to collapse
Haha that's the point right xD $20 hot spot! But I agree. Nothing seems to be working ATM... Too much bloatware and need to get started on a CM nightly...
Right
wireproof said:
Haha that's the point right xD $20 hot spot! But I agree. Nothing seems to be working ATM... Too much bloatware and need to get started on a CM nightly...
Click to expand...
Click to collapse
Seriously, I left it sitting all night to see if it would ever start to download. The help section says that it's stalling on Driver Verification and to disablle it, but it makes no difference. I have trouble believing that's the problem since it won't even download the driver, how can it even try to "verify" it. Besides that fact that I have the latest driver from the manufacturer and have tried the one from the link in their help pages to the ZTE driver. Is there no command line option to skip the driver installation and just see if it will run? I know i can access it by adb. OR does anyone know of a method to root this thing manually? I'm not skeered to use terminal and dox boxes, but I'd rather not do it blind. THis phone is nearly useless to me without root especialy since i just figured out why I get no signal... It's a damn T-Mobile based device. It's doesn't say this ANYWHERE on the box or documentation. I should have researched it first as I usually do, but I got too excited by the idea of a droid for $20. I thought, at least if it doesn't work, it will be a toy for my 5 year old... But even he will want to install more than 1 teeny app LOL
With a custom 4.2 or later rom and good signal this thing would be.... OK... not great, but not too bad either. It isn't all that slow as I was afraid. Kit Kat might be great on it
Will a root method from any other ZTE devices work for the Midnight? I read that it might possible be the same as the ZTE Concord from t-mobile, but I tried a root method for it using a jcase update.zip, but it did not work. I'm at a loss. I've never had this much trouble getting one rooted. Apparently this device just wasn't popular enough
jawa6988 said:
Seriously, I left it sitting all night to see if it would ever start to download. The help section says that it's stalling on Driver Verification and to disablle it, but it makes no difference. I have trouble believing that's the problem since it won't even download the driver, how can it even try to "verify" it. Besides that fact that I have the latest driver from the manufacturer and have tried the one from the link in their help pages to the ZTE driver. Is there no command line option to skip the driver installation and just see if it will run? I know i can access it by adb. OR does anyone know of a method to root this thing manually? I'm not skeered to use terminal and dox boxes, but I'd rather not do it blind. THis phone is nearly useless to me without root especialy since i just figured out why I get no signal... It's a damn T-Mobile based device. It's doesn't say this ANYWHERE on the box or documentation. I should have researched it first as I usually do, but I got too excited by the idea of a droid for $20. I thought, at least if it doesn't work, it will be a toy for my 5 year old... But even he will want to install more than 1 teeny app LOL
With a custom 4.2 or later rom and good signal this thing would be.... OK... not great, but not too bad either. It isn't all that slow as I was afraid. Kit Kat might be great on it
Will a root method from any other ZTE devices work for the Midnight? I read that it might possible be the same as the ZTE Concord from t-mobile, but I tried a root method for it using a jcase update.zip, but it did not work. I'm at a loss. I've never had this much trouble getting one rooted. Apparently this device just wasn't popular enough
Click to expand...
Click to collapse
I tried the root method for the T-Mobile branded version of the phone... I have the NET10 GSM version.. Nothing seems to be working either. Not even Gingerbreak... This is a freaking NET10 phone... And Kit Kat would be nice on this phone! 800 mhz processor and 512MB RAM so it should work well.
I just bought this phone too. It comes with CM 2.3.7 installed on it. I"m wanting a KitKat ROM. I'm hoping my by Wambo_Bomb will compile a version of his BlakAndroid for the ZTE Midnight. I've asked him to do so. He said he needs the modules an Kernel info to do it. If he does come through for me, I will share with everyone.
ROOTED!!!
I just wanted to come back and let you guys know: After A few days and much frustration, I tried Kingoapp.com again and it worked flawlessly on the first try, so now I'm rooted and able to run root apps on my rooted stock rom. Now does anyone know of a way to get a custom recovery on this phone? And if there are any cutom roms available yet? If your friend does compile a rom, I'd be happy to help with testing.
---------- Post added at 10:34 AM ---------- Previous post was at 10:29 AM ----------
Sleepycloud said:
I just bought this phone too. It comes with CM 2.3.7 installed on it. I"m wanting a KitKat ROM. I'm hoping my by Wambo_Bomb will compile a version of his BlakAndroid for the ZTE Midnight. I've asked him to do so. He said he needs the modules an Kernel info to do it. If he does come through for me, I will share with everyone.
Click to expand...
Click to collapse
Mine is now rooted, so let me know if you need me to dig out any files and send them to you. I can't make a full nandroid yet, but I can get in there with FTP or adb and hopefully get anything you need
---------- Post added at 10:51 AM ---------- Previous post was at 10:34 AM ----------
wireproof said:
What drivers did you use to get Kingo Android Root to work? Nothing seems to be working for me...
Click to expand...
Click to collapse
Try Kingoapp again. The server issue appears to be fixed. I did try from a fresh clean install of Win8, but I had tried that before and it stalled at installing drivers, so maybe had nothing to do with it. I simply connected the phone, installed drivers from internal memory (appeared as "CD-ROM in Win8), enabled development mode, then ran Kingoapp and it worked flawlessly. Good luck. The more people we get rooted, the better the custom ROMS will become I hope
GOT ROOT!!! cool thanks. now what... no roms yet?
sorry to steal the thread but does anyone know how to unlock sim for tmobile.
I was able to root the zte midnight using kingo root. So now Im looking for cwm and a custom rom for this phone. Does anyone know if any are out for this phone?
ultravioletnanokitty started a developers thread but i cant post on there to motivate them...
http://forum.xda-developers.com/showthread.php?t=2715570
I need a custom recovery for this phone, i will donate 50 USD if somebody help me to convert z768g to v768. So i could be able to Unlock it. Please help.
zte miniget10 phones root
ok I was having same problems do this plug device to pc go to thispc or my computer click on your phone and it will install right drivers and use kingo and your done figured th out 20mins into trying to root I bought this device just todo this to fiue out for have a nice day
---------- Post added at 10:01 PM ---------- Previous post was at 09:44 PM ----------
datboirobbie said:
ok I was having same problems do this plug device to pc go to thispc or my computer click on your phone and it will install right drivers and use kingo and your done figured th out 20mins into trying to root I bought this device just todo this to fiue out for have a nice day
Click to expand...
Click to collapse
sorry misspelled it zte midnight
ZTE midnight root???
has anyone ever found a root for zte z828tl??
What version of kingo?
please delete
Tips & Suggestions, Common Fixes & Questions
please delete
Cant get PC to read watch in step 10 of flashing
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Tom19146 said:
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Click to expand...
Click to collapse
Are you trying to flash the ROM or trying to run the patch? They are two different things. This thread is for the Patch.
No root
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
urmcgwy said:
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
Click to expand...
Click to collapse
What OS?
EDIT;
What model?
Lokifish Marz said:
What OS?
Click to expand...
Click to collapse
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
urmcgwy said:
Sorry Win7 x64
Click to expand...
Click to collapse
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
---------- Post added at 09:25 PM ---------- Previous post was at 09:18 PM ----------
urmcgwy said:
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
Click to expand...
Click to collapse
Omate "Developer Edition" 1/8
urmcgwy said:
Sorry Win7 x64
And I have no idea why I wrote Win7.... its Win8.1 x64
Omate "Developer Edition" 1/8
Click to expand...
Click to collapse
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Lokifish Marz said:
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Click to expand...
Click to collapse
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
urmcgwy said:
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
Click to expand...
Click to collapse
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Lokifish Marz said:
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Click to expand...
Click to collapse
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
urmcgwy said:
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
Click to expand...
Click to collapse
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Lokifish Marz said:
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Click to expand...
Click to collapse
Thanks for all the help! I'll just wait until tomorrow to see if the watch dies on me and see what Omate has to say. Really appreciate the quick responses!
I just flashed back to stock, what next is needed?
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Tom19146 said:
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Click to expand...
Click to collapse
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Lokifish Marz said:
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Click to expand...
Click to collapse
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Tom19146 said:
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Click to expand...
Click to collapse
Fixes have not made it to official firmware yet.
Rom = Patch + extras
Use an adblocker and only the actual download button will be seen.
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Tom19146 said:
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Click to expand...
Click to collapse
Iv'e had that happen to me a couple of times even when on stock w no patch. Short of pulling the battery you have to wait for the battery to die.
Omate TS slow and built-in memory full
Hi all, hopefully this time I am posting in the right place. After flashing the patch my TS seems to be slower and seems to ignore storing things on the sd card. The TS memory now has only 228mb free and the SD card is all free (this is set up as the default storage). Has anybody come across a similar situation (TS slow and memory full) and how could I overcome that? Many thanks in advance (please be patient, I am not an expert)!
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
doctor-cool said:
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
Click to expand...
Click to collapse
AdamOutler's Root is obsolete, Thanks for the good times
Click to expand...
Click to collapse
Adam has done A LOT for this community especially for Samsung phone in general.. His work is NOT obsolete and he still very involved on this forum. I am not friends with him or do I know him but he was the master mind behind unlocking/exploiting Verizons bootloader.. which currently on 4.3 and 4.4.3 is still not possible. This is most likely do to him not having the phone and the phones age..
SOo I hope I got the wrong impression from your statement.. Bc that man you mentioned.. Is a LEGEND.. Hands down
Just to confirm, Ghettoroot does not work on 4.4.2 baseband ND7. Is that correct?
Sent from my Galaxy Note 2 using Tapatalk
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
jtsmall said:
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
Click to expand...
Click to collapse
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Yes, that's it. Samsung's drivers work for me.
Sent from my Galaxy Note 2 using Tapatalk
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
crossing fingers
shissler said:
crossing fingers
Click to expand...
Click to collapse
woot woot im rooted..lol now what way to go
shissler said:
woot woot im rooted..lol now what way to go
Click to expand...
Click to collapse
I used it to replace the APN config file in my wife's phone for use on other carriers (T-Mobile & international use):
http://forum.xda-developers.com/showpost.php?p=57070787&postcount=7
It worked great for up to HSDPA+ speeds, but no LTE.. ..then she left the phone on top of her car; it fell off in traffic and got run over.. maybe this will help someone else!
Before it got smashed, I had planned on trying the following thread out next (for the VZW Note 3) to see if I could get LTE working on T-Mobile:
http://forum.xda-developers.com/showthread.php?t=2530523
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
samloves said:
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
Click to expand...
Click to collapse
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
zbomb5610 said:
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
Click to expand...
Click to collapse
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Thanks for the reply. I figured that was the case. I had 4.1.2 a few days ago also and figured "hey, i haven't updated in over a year" and didn't read into it enough and then upgraded to stock ota 4.4.2 so that sucks. I guess I can live with it like this for now till a fix comes out if one does.
also having trouble
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
UPDATE: Just got it to work. Will post soon what I was doing wrong and what I did to correct it.
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
IceCo1d said:
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
Click to expand...
Click to collapse
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
The part you are talking about does not come up until after the command prompt finds your device. Then you get the message to accept. That message came up the very first time but now it will not find the device for me to get to that part.
zbomb5610 said:
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
Click to expand...
Click to collapse
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
I had similar issues with some of my trials.. ...try turning developer mode off and on, plug in and then give the phone 30-90 seconds or so for installer mode to time out and verify the device is in MTP or PTP mode.
Just rooted my Note 2 running 4.4.2
Ok gang, so after about a week of trying every method to root my phone I finally got it to work. I'm going to tell you what I was doing wrong and what you can check to see where you are messing up. Hope this helps someone.
The issue I kept running into was that my device could not be found. I would run Ghettoroot and it would just tell me error device not found. This made no sense because I could get Kies to work and the bubble in the lower right corner that says installing device drivers would always succeed. However if I went into Device Manager (on the computer) there was a little yellow exclamation point next to my device. After looking in to the properties it said there were no drivers installed.
Also if you open a command prompt and type "adb devices" (with your phone plugged in) it should show you your device, if nothing comes up then the drivers are not properly installed.
So... First check that drivers are properly installed in your Device Manager (again this is on your computer), and then open a cmd window and type adb devices to see if your phone shows up. If it does then you are ready to use Ghettoroot.
I used this Ghettoroot:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
and the drivers I used were called:
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0 (I can't remember where I DLed it from, sorry)
Also, if you are interested. My method for figuring out what was wrong started by right clicking on the GhettoRoot .bat file to see the sequence cmd commands. They began with adb commands and I then googled to see how to check that the command would work. That is when I stumbled on the comman "adb devices" to make sure my phone was properly connected.
I hope this helps someone and if I can help in any other way just ask!
Heimdahl? Odin?
mattnmag said:
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Click to expand...
Click to collapse
I've only had this phone a week. My vs980 fractured :crying: now I'm stuck with this "thing" which I've done nothing with as I'm still trying to figure out WHAT never mind how. There's so much bloat I'm thinking AOSP. But how?
So far, ghetto-root hasn't worked for me but have removed Kaspersky etc to see if that was the problem. Then worry abt boot loader. Am on Pageplus Carrier so there wont be any OTA updates
Is there any merrit in the "Heimdahl" (??) method shown here CYANOGENMOD
I've read some of people using Odin to load pre-rooted stock image (and have found the images... but... )
I bricked the vs980 playing too fast and not waiting for answers. (learned a thing or 2 unbricking it)
So am I correct in understanding that you can no longer "Drop" an Un****** version of the factory image into the phone? By any means?
THANKS
VW
I have the Huawei Ascend Mate 2 MT2L03
Build number is currently MT2-L03C00B322
Android 5.1
EMUI 3.1
I don't have it rooted, and have never flashed anything to it.
Everything running on it is stock, which I don't mind. But I was thinking it'd be nice to step up to android 7.0 or so.
I have read around some and see that a dev SHM is working on it?
Also my bootloader is still locked, but I found out how to get the unlock code.
Just wondering... should I bother with upgrading to something newer, rooting it and all that? Or is 5.1 still fine?
the closest youll get is a cm 13.1 nightly or snapshot. i think its worth the switch.
I'm using SHMs CandySix 6.0.1 and it was definitely worth it for me to unlock and root to use custom ROMs.
Since you have never flashed before, allow lots of time to read the instructions and don't be in a hurry when you do it.
Check out the HAM2 index (link in my signature). Should be very helpful. The only problem is I don't know what the latest method is for getting the bootloader unlock code. Can you tell me what it is now so I can update the index and the starter pack?
As for SHM's 7.0, he's not working on it anymore. However our phone is officially supported by CyanogenMod, so I think we'll be getting CM14? Not sure though.
CandySix is a good choice. I've been running it for several months now and it's been great.
Latest bootloader unlock method from Huawei Website
ScoobSTi said:
Check out the HAM2 index (link in my signature). Should be very helpful. The only problem is I don't know what the latest method is for getting the bootloader unlock code. Can you tell me what it is now so I can update the index and the starter pack?
As for SHM's 7.0, he's not working on it anymore. However our phone is officially supported by CyanogenMod, so I think we'll be getting CM14? Not sure though.
Click to expand...
Click to collapse
I made a post in another topic, maybe this will help you!? http://forum.xda-developers.com/showpost.php?p=69309478&postcount=463
Forgive me, but what android version is cm 13.1 nightly or snapshot or CandySix running? I currently use android 5.1, and everything is stock.
I don't mind the EMUI interface. I also don't have any application that I'm wishing to uninstall.
I want to upgrade to a newer version because I feel maybe it'd be faster? But I have just also considered getting the LG G5, or maybe the pixel?
So would using a newer android version make my phone faster? I know the HAM2 only has 2gb of ram, and for internal storage it says I have total: 11.69gb but 2.94gb free. But that's not bad considering the amount of apps I have. I also have a 32gb microsd card.
If I flashed a different android version would I still have the radio and the EMUI? Sorry if my terminology is off, still new
Security is the key?
that1guyyep101 said:
I have the Huawei Ascend Mate 2 MT2L03
Build number is currently MT2-L03C00B322
Android 5.1
EMUI 3.1
I don't have it rooted, and have never flashed anything to it.
Everything running on it is stock, which I don't mind. But I was thinking it'd be nice to step up to android 7.0 or so.
I have read around some and see that a dev SHM is working on it?
Also my bootloader is still locked, but I found out how to get the unlock code.
Just wondering... should I bother with upgrading to something newer, rooting it and all that? Or is 5.1 still fine?
Click to expand...
Click to collapse
I use the HAM2 as a mini tablet/media player now to save battery life on my Nexus 6p. Currently on Android 5.1 with EMUI 3.1 and have just unlocked the bootlock and now seeking to figure out how to proceed with rooting and flashing to CM 14 or later. My concern is with all the security holes on 5.1 Official version from Huawei since it has known security holes and is not getting moved forward or patched. While I like the features on the 6P and the improved security the battery life sucks compared to the HAM2 (true for most phones).
I will watch this thread and will keep searching for tips to make this first round of rooting and flashing to CM on my own a learning experience. I would strongly recommend anyone on older versions of Android seek to get more current due to the massive security issues. Hate leaving behind old equipment that I can keep in some use with rooting and upgrading on the software.
To the OP, you can try out CM14.1 now thanks to mdmower.
As for learning how to root and flash, check out the HAM2 index thread for some useful goodies and the starter pack I made. They should be helpful. If not, you can ask us of course.
Unlocked bootlocker, HiSuite and ADB present, can't load twrp
ScoobSTi said:
To the OP, you can try out CM14.1 now thanks to mdmower.
As for learning how to root and flash, check out the HAM2 index thread for some useful goodies and the starter pack I made. They should be helpful. If not, you can ask us of course.
Click to expand...
Click to collapse
Thanks for the great information package ScoobSTi.
Have HAM2 MT2L03 with Android 5.1 stock, EMUI 3.1, attempting to root then flash from a Windows 10 PC. Bootlocker unlocked, HiSuite 5.0.1.300_OVE and ADB loaded and appear to be working as both phone and SD card files are accessible from PC. Have placed TWRP version in the ADB folder and renamed to TWRP.img, placed SuperSu_v2.79....... in root of SD card.
Getting no devices listed when run adb devices from ADB on pc although drivers show good in device manager and files on device are accessible.. When run c:\adb>fastboot flash recovery c:/adb/twrp.img get response error: cannot load 'c:/adb/twrp.img' after I reboot HAM2 into recovery.
What am I missing?
Have reviewed many threads and posts and am too dim to get what I am doing wrong.
Need to turn off phone and go to bootloader the cmds won't reboot the phone,it needs to manually put in too bootloader and then run the cmds
Sent from my Ascend Mate 2 using Tapatalk
Fastboot looking for HiSuite only
hopkins31 said:
Need to turn off phone and go to bootloader the cmds won't reboot the phone,it needs to manually put in too bootloader and then run the cmds
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
When I manually reboot into recovery the HAM2 goes into Fastboot & Rescue Mode but does not root with TWRP as noted. The HAM2 Fastboot screen does show the device as "PHONE: Unlocked". New here so cannot post a pic of the boot screen or screenshots of the adb responses in the command prompt. Issue seems to be with the HAM2 not showing up on the adb devices listing.
So I am really new at this and have problems even getting through reading a sentence without having to google terms and read for pages... I am not getting far reading old posts on this specific phone because its from 2013 or there abouts. I keep reading about someone having luck with x rooting tool but with some older andriod version or whatever. I have watched a few videos on youtube as well but don't know which to trust or still even apply.
I am getting sick of the phone being a battery hog, lagging more that another older phone a nexus 5 with lower specs, and all the annoying sprint bloatware that may or may not be causing other issues. I am using hangouts and freedompop for my phone service anyhow. I just want a simple phone webbrowser, camera... I dont need to cloud print,keep track of my heartrate, have two screens open, tv remote, fm radio.... or to have sprint constantly be unclosable in the background. Just some of my motivations for attempting this.
I have tried kingroot (pc on a pos netbook, as the soon to be exwife took the good pc). I have also tried towel root. Kingroot tried for a while and gave up I was #95 with the same problem. Towel root just said something about a rare phone and that it didn't work. I will try whatever again to get a more proper error message but thats the best I remember at the moment :silly:
What current method should I be looking at to root this LG G3 phone? Is it a difficult phone to root or am I just making it difficult? Should all of the rooting methods that did work 2-3 years ago still work or no?
Let me know if I need any more info from this thing.
andriod version 5.0.1
kernal ver 3.4.0
build # LRXZ1Y
software version LS9902VG
model # LGLS990
OK so honestly with or without root the G3 was a major battery hog(that display is very power hungry and when I had my Verizon G3 I always had to carry a portable battery with me just so I could get through my work day... That being said-with root and a decent AOSP ROM and kernel you can kinda make it more tolerable- being that you're on Lollipop(5.0.1) means towelroot won't ever work, kingroot should work but without unlocking the bootloader with either "Loki" or "Bump" you'd just have root and no custom recovery to flash ROMs and the things you need. I know for a fact there is a few different threads in the LG G3 general and in the Sprint G3 threads to get you rooted and get TWRP flashed on there with no problems-- I'll post some links here shortly for you that will hopefully get you rooted and booted
---------- Post added at 11:26 PM ---------- Previous post was at 10:54 PM ----------
@jere-m check these out https://forum.xda-developers.com/sprint-lg-g3/help/rooting-ls990zvg-problems-t3528679
Last Post says it all with a link- run the batch file and manually reboot into download mode, let the .bat file run and do it's thing and use Flashify to flash a Bumped TWRP recovery image... Hope this helps you out and if you have any issues or questions PM me or post here and I'll answer ASAP... (oh and please if you get any error messages please post exactly what they said and what was done to make the error come up) And make sure you have a copy of the ToT or KDZ file for the same model/version you are currently using so you can restore to 100% stock and try again.