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)!
Related
Well I made a mess out of this situation... I was trying to do the OTA update for MJ7 but it was failing.. I seemed to be one of a very select few that got this issue but from researching, I found that I should be able to update via the USB cable on my PC and let the verizon update utility that installed on my PC find the update and install it. Fair enough, it came up and showed an update ready. After download it started installing, after about 5 minutes, it times out and gave me some error that I needed to connected to kies and do a recovery as the update failed. No matter what I did, restarting my phone and recovery mode, everything, it kept taking me to that message, unless I went into ODIN mode, that showed as it was supposed to...
to try and wrap this long story short, I tried many methods of recovering my phone and/or finish the update WITHOUT losing data. Everything I found led to a dead end and I found the only way was to run the recovery through the verizon utility app on the PC. It stated it would not keep data and basically do a factory reset in a nutshell.. No problem I thought, I was thinking it would put me back on my original OS version like MI7 or even ME7 and I could root and recover a lot of my data through Titanium Backup... i found there was no way to root MJ7 (yet) although after the fact I saw the article of attempting to keep it after update, but we know how that went... nonetheless.. the repair did reset my phone and it put the MJ7 (latest version) on the phone... great, no root method there... now i read and from what I understand if I try to flash back to a previous version it permanently logs it and marks this new KNOX marker that its been changed and "voids" the warranty and thus far there is no found way to keep that from happening nor reverse it after it does..
Question is... IS all my research correct as stated in above paragraph? OR is there a way I can safely flash back to a previous STOCK OS such as ME7 or MI7, be able to root the phone again, then go back on my merry way (with or without updating to MJ7 this time after I get my data back, hopefully?) If possible, I want to MAKE SURE I have the correct files or a link supplied to a existing post with download links with the right downloads I need to get. Hate to brick the phone again and go through all this waiting all over again. Any help appreciated!
Thanks,
David
Sorry, your correct, there is no way back and no way to root.
Ryno77 said:
Sorry, your correct, there is no way back and no way to root.
Click to expand...
Click to collapse
So to confirm, even if I were to ODIN my way back to a older stock image like ME7 or MI7, what exactly would occur then? Would it work but tick that KNOX 0x0 to 0x1 thus "voiding" warranty but still take me back to previous version where I may root once again...?? Or...??
This has been said hundreds of times:
You can not move backwards. Once you're on a release, you can only install the same or later software.
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
dpiffy said:
So to confirm, even if I were to ODIN my way back to a older stock image like ME7 or MI7, what exactly would occur then? Would it work but tick that KNOX 0x0 to 0x1 thus "voiding" warranty but still take me back to previous version where I may root once again...?? Or...??
Click to expand...
Click to collapse
If you try to flash older software, it'll fail and softbrick your device. This will only allow download mode, requiring you to flash what's expected to recover your phone.
You'll only trip the Knox warranty flag if you try to flash an un-signed bootloader (and, I think, an unsigned recovery.)
k1mu said:
This has been said hundreds of times:
You can not move backwards. Once you're on a release, you can only install the same or later software.
Click to expand...
Click to collapse
Well then please excuse me. As I said I researched this for a lengthy amount of time, I found mixed answers on this issue found some saying it is not possible but doesn't say why (much like you just did, not explain what happens as I asked, all due respect). I found places saying it is possible but this new "KNOX" thing on the latest version which I know VERY little about, that it would add a "count" or change the value but would work, of course many people don't want to do that with there not being a way to revert it back, from my understanding. Then some articles are handing out download links to restore/downgrade left and right. So again, excuse my confusion. Even after starting to write this article and the subject line I used produced possible matches to what I was about to post about, NONE and I repeat NONE of those options fit my question, so I don't need this "it has been said 'hundreds of times" when I just spend the greater part of my afternoon getting my phone updated then it failing and trying to do anything to get it back up and running one way or another. Not in the best of moods as I lost some precious data on my internal storage that otherwise would be safe and able to be restored from the titanium backup, which is proving useless right now. Nope, that is not your fault, but show a LITTLE more respect to this open community instead of being Mr. Moderator over there correcting me on things that aren't exactly made clear from all the other posts I have read today!
k1mu said:
This has been said hundreds of times:
You can not move backwards. Once you're on a release, you can only install the same or later software.
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
If you try to flash older software, it'll fail and softbrick your device. This will only allow download mode, requiring you to flash what's expected to recover your phone.
You'll only trip the Knox warranty flag if you try to flash an un-signed bootloader (and, I think, an unsigned recovery.)
Click to expand...
Click to collapse
Now that I see you evidently edited your last response, I saw after the fact your response you ended up making. Thank you for explaining as I only asked for in the first place.
dpiffy said:
Now that I see you evidently edited your last response, I saw after the fact your response you ended up making. Thank you for explaining as I only asked for in the first place.
Click to expand...
Click to collapse
No editing, but there's been two of us replying. JFTR.
Hopefully we've saved you from a trip to softbrick city. :good:
(Edit: I see - the "post edited" - well, what happens is if you post more than once to a thread, the posts get combined where the subsequent posts are marked as edits. That's a bit misleading. THIS is an edit after-the-fact.)
Bummer
Got it. Well thanks...
It's not a question of if but when someone will figure all this out again... especially for a phone as the S4... i'd be more than happy to put forth a donation to further encourage someone to get things rooted AND unlocked again... I have a lot of stuff I'd pay decent money towards getting my data back through my Titanium Backup files... there is still some things I lost and can't even get back through the TB but anything is better than nothing... Where do you give donations through? I've always heard of the "bounty" -- do you have to be in any specific standing on these forums to give to this?
It's finally official for AT&T Htc one m8 read the details of the ota here http://www.droid-life.com/2014/08/2...eed&utm_campaign=Feed:+DroidLife+(Droid+Life)
Sent from my custom M8
Yeah got the update just now. Digging around for changes.
Thanks man just got the update. Waiting for reboot now so I can re-root.
They added a file manager.
Before folks start diving into the OTA pool without thinking, remember a couple things:
1) OTA won't install with custom recovery. You need to return to stock recovery or else the OTA will send you into a bootloop trying find a stock recovery that isn't there.
2) Root is usually okay, as is unlocked bootloader (OTA will install) however, if any system files were frozen or removed, they will need to be returned to their "stock" condition otherwise the OTA will not install. Flashing the stock rooted ROM or RUU might be the fastest way to do this.
3) It won't be known whether sunshine and/or firewater s-off methods will work (firewater was already squashed, so its very unlikely to work) unless somebody actually tries it. If sunshine doesn't work, this means you will be stuck s-on until a new exploit is found. So s-off before you OTA if you want to be sure you can get s-off (until folks report this OTA is sunshine-friendly).
4) Back it up before you OTA. Personal data, pics whatever. If its important to you, and you will be sad to lose it, than back it up. Copy to your computer, cloud, whatever, your choice. OTA is not "supposed" to delete any personal data. But you know . . . Murphy's Law. This goes for any major system change, ROM flash, etc.
redpoint73 said:
Before folks start diving into the OTA pool without thinking, remember a couple things:
1) OTA won't install with custom recovery. You need to return to stock recovery or else the OTA will send you into a bootloop trying find a stock recovery that isn't there.
2) Root is usually okay, as is unlocked bootloader (OTA will install) however, if any system files were frozen or removed, they will need to be returned to their "stock" condition otherwise the OTA will not install. Flashing the stock rooted ROM or RUU might be the fastest way to do this.
3) It won't be known whether sunshine and/or firewater s-off methods will work (firewater was already squashed, so its very unlikely to work) unless somebody actually tries it. If sunshine doesn't work, this means you will be stuck s-on until a new exploit is found. So s-off before you OTA if you want to be sure you can get s-off (until folks report this OTA is sunshine-friendly).
4) Back it up before you OTA. Personal data, pics whatever. If its important to you, and you will be sad to lose it, than back it up. Copy to your computer, cloud, whatever, your choice. OTA is not "supposed" to delete any personal data. But you know . . . Murphy's Law. This goes for any major system change, ROM flash, etc.
Click to expand...
Click to collapse
Good write up and reminder to the folks who aren't experienced [emoji2]
Sent from my custom M8
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Anyone have the ota they can post?
Sent from my custom M8
THizzle7XU said:
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Click to expand...
Click to collapse
Always best to do a FDR after an ota it's actually recommend to do that by the manufacturer I know that's a best bet in possibly fixing the issue. Please give that a try and post an update so everyone else can know and thanks for your post
Sent from my custom M8
Sent from my custom M8
The standard root tools work on the 4.4.3 update. To update-
1. Flashed stock recovery
2. Did the OTA Update
3. Flashed TWRP
4. Rooted
I did S-Off a while ago, so I can't say whether this breaks the tools for that. All in all, easy peasy
THizzle7XU said:
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Click to expand...
Click to collapse
YES! Plummeting like a rock in a swimming pool. Can't even get it to stay level whislt plugged in to a USB port.
Dan
Buddhake said:
YES! It's plummeting like a rock in a swimming pool, I can't even get it to stay level while plugged into a USB port.
Dan
Click to expand...
Click to collapse
Mine is charging fine, as for the drain though I'll have to report back.
My battery is also crap now.
Sent from my HTC One_M8 using XDA Free mobile app
Harshpatil said:
Yeah got the update just now. Digging around for changes.
Click to expand...
Click to collapse
For what it's worth, here's the Changelog-
Android 4.4.3
Security fixes
Wi-Fi fixes
Bluetooth fixes
Mobile network fixes
Camera app update
Gallery (Image Match)
Settings (Power History)
HTC Sync Manager
Boomsound optimization
Extreme Power Saving Mode optimization
Motion Launch optimization
Quick Setting optimization
californiarailroader said:
Mine is charging fine, as for the drain though I'll have to report back.
Click to expand...
Click to collapse
To clarify, I get the charing error when plugged into a PC, which used to charge the phone just fine, even when not in power saver mode. It's still charging with an outlet, albeit probably not as fast as before. I'll try the factory reset even though the message when you are about to update basically says it's an in-place update that won't affect you files.
I'm now having other issues too. Apps won't update. Texts are sending but the apps are saying they are failing to send. The update really hosed this thing.
THizzle7XU said:
To clarify, I get the charing error when plugged into a PC, which used to charge the phone just fine, even when not in power saver mode. It's still charging with an outlet, albeit probably not as fast as before. I'll try the factory reset even though the message when you are about to update basically says it's an in-place update that won't affect you files.
I'm now having other issues too. Apps won't update. Texts are sending but the apps are saying they are failing to send. The update really hosed this thing.
Click to expand...
Click to collapse
Oh, okay, I have mine plugged into a charger. I'm not having any issues with apps not updating or apps saying messages aren't sending, see if the factory reset clears the errors.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
If all else fails, the RUU is up on HTC's web site-
http://www.htc.com/us/support/htc-one-m8-att/news/
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
That will wipe everything though.
Anyone get the ota or ruu downloaded and can upload somewhere?... Would be appreciated...
californiarailroader said:
Oh, okay, I have mine plugged into a charger. I'm not having any issues with apps not updating or apps saying messages aren't sending, see if the factory reset clears the errors.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
If all else fails, the RUU is up on HTC's web site-
http://www.htc.com/us/support/htc-one-m8-att/news/
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
That will wipe everything though.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Anyone get the ota or ruu downloaded and can upload somewhere?... Would be appreciated...
Click to expand...
Click to collapse
Can't you download it from the link in my post?
Itll take 8+ hrs to download from that link...was asking if anyone had it already and could upload it elsewhere so it wouldnt take so long to start working on it.:silly::silly:
californiarailroader said:
Can't you download it from the link in my post?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Itll take 8+ hrs to download from that link...was asking if anyone had it already and could upload it elsewhere so it wouldnt take so long to start working on it.:silly::silly:
Click to expand...
Click to collapse
I have it, do you have a preference for sites to download from? I have Mediafire, Drive, Box, Dropbox and One Drive.
I'm uploading it to Google Drive and Microsoft One Drive. It might take just a bit, I have a 120 Mbps download with Comcast, but only 12 Mpbs on the upload.
Edit-What's your email? I can also share it through WeTransfer.
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:
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
adogg222 said:
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
Click to expand...
Click to collapse
Since you just got your phone, I would say get to know it on 4.3 first. Lollipop is prettier, but you can do more root things on JB, it runs better, has better battery life, and is an all around better experience, IMO.
Lollipop doesn't have xposed either, if you planned on using that. On top of that, it is missing some core functionality like a startup manager(apps that should be running after a reboot are not!) and has a crippling audio bug.
First thing you have to do for root is email Huawei with your IMEI and SN asking for a bootloader unlock code.
[email protected]
Here is the email I sent them:
Hello, I would like a code to unlock the bootloader on my Huawei Ascend Mate 2, please.
Serial - *********
IMEI - *******
Thank you
Click to expand...
Click to collapse
I then got an unlock code within minutes, so it may or may not be somewhat automated.
TWRP for Mate2
Basically that is a zip file with everything that you need to install TWRP on the Mate2. It has:
SHM's Unified TWRP(v2.8.7.3).
Huawei drivers
ADB/Fastboot
SuperSu(v2.46)
stock 5.1 recovery(just incase)
!Readme file with step by step.
TWRP is needed to install SuperSu, which in turn gives you root.
First, make sure you leave all the files in the same folder. Extract them anywhere, like your desktop. Install the Huawei drivers if you don't already have them installed.
***Put the UPDATE-SuperSU-v2.46.zip on your phone's sdcard somewhere easy to find***
1. Turn off your phone
2. Hold Volume DOWN and Power button for a few seconds. When the screen turns on let go of the power button.
3. Now you should be on the bootloader screen, also known as fastboot.
4. Plug your phone into your PC and wait a minute to make sure any additional drivers are installed and setup.
5. Hold shift and right click an empty space in the folder you downloaded with adb.exe and fastboot.exe and select "Open command window here". A command window should open.
6. In command window type 'fastboot devices' and make sure it says there is a fastboot device. If it doesn't, that means your drivers didn't work. Try unplugging your phone and using another USB port.
7. If it showed a device, its working. Type 'fastboot flash recovery twrp.img'
8. If successful, your phone now has twrp installed
9. While still in fastboot, hold VOLUME UP and the POWER BUTTON for about 8 to 10 seconds, as soon as the screen turns off and then back on again, let both buttons go.
10. In TWRP, hit install and find your UPDATE-SuperSU-v2.46.zip and flash it.
11. Should be rooted and good to go.
12. I included the stock recovery if you ever want/need to go back. Just follow the same steps but replace "twrp.img" with "stock_recovery.img"
Click to expand...
Click to collapse
To lower DPI on our phone, a line will need to be added to the build.prop in the "root/system/" directory.
Add:
Code:
ro.sf.lcd_density=264
to the end of the text on a new line. 264 is the lowest you can go without causing multiple apps to crash.
You can go lower, but you will need Xposed and App settings to change the crashing apps to 264 or above.
Wow, thank you SO much for all of this!! So awesome of you!
adogg222 said:
Wow, thank you SO much for all of this!! So awesome of you!
Click to expand...
Click to collapse
Build prop editor on Google play store can very easily change your dpi. And makes a backup if you want to go back. Better than modding it yourself. And I agree with ark. Hold.off on L until things are fixed. Or until Tom get cm12 up and going.
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
My advice to this self proclaimed "noob" is to read the threads and get more educated before just posting a question that has already been answered with it's own thread. All of the info that Ark posted is in these forums. Please don't get in the habit of asking to be spoon fed. That is certainly frowned upon on XDA.
kimtyson said:
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
Click to expand...
Click to collapse
I had most of it done and copy pasted from another post I already made.
I'm glad someone finally gave simple comprehensive instruction. Unlike someone stated above, it was not that easy to find. I have had my phone for about 1 1/2 months since I returned from vacation in Europe. Ordered it online from Frys while I was there. Anyway, I have searched many times for instructions and couldn't find one thing definitive. Always comments alluding to root, and "does this keep root after update" or "how to get root back" or "this root method didn't work" etc... But never could I find instructions on how to achieve root on stock 4.3 until now. So Thank you sooo much. Now are we sure about the email link you provided above? Because I sent them (Basically copy and pasted ) your email above email twice. About a week ago, and a few days ago. And still no response! Any other suggestions? And shouldn't this be stickied since Root is the most basic of function of what we all want?
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
TheIgster said:
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
Click to expand...
Click to collapse
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
---------- Post added at 11:41 PM ---------- Previous post was at 11:36 PM ----------
TTJB said:
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
Click to expand...
Click to collapse
If you have the code, just boot into fastboot and use the command
Code:
fastboot oem unlock *your code, no asterisks*
ArkAngel06 said:
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
Click to expand...
Click to collapse
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
TheIgster said:
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
Click to expand...
Click to collapse
It's on Google Play or XDA. Try looking for it.
kimtyson said:
It's on Google Play or XDA. Try looking for it.
Click to expand...
Click to collapse
Thanks. Maybe try being less snarky next time?
Just a simple question in a forum that doesn't have a helluva lot of posts anyway.
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Callmebaus said:
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Click to expand...
Click to collapse
Just let it update itself.
Moody66 said:
Just let it update itself.
Click to expand...
Click to collapse
how? selecting normal? instead of twrp?
Callmebaus said:
how? selecting normal? instead of twrp?
Click to expand...
Click to collapse
Normal
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Callmebaus said:
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Click to expand...
Click to collapse
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
xordos said:
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
Click to expand...
Click to collapse
that's the exact post that I used yesterday, haha
all fixed and rooted
thank u
Hey guys,
I have bought a Samsung S9+ via Amazon.
Because I am rooting my Samsungs since forever, I intended to do so again immediately. Used Magisk and so on.
Somehow this phone got stuck at the logo (bootloop?) and I couldnt use it anymore. Felt like the whole system was broken cuz nothing was possible.
So I downloaded a legit new firmware (I think it was the right one for my model) and used Odin to upload it on my phone. Then I rooted the phone again without any issues.
Perfect root right now.
However, independent from any used apps the phone reboots everyday by itself, lockscreen or while using. (I assume its not an app issue then..?)
I'd highly appreciate any help.
PS. I forgot where I got the firmware from, but it was definitely a legit website.
Here are some phone stats.
Modelnumber:SM-G965F/DS
ONE UI-Version 1.0
Android Version 9
Kernel Version 4.9.59-15540155
Please let me know if you need more information.
THank you ahead
Nihay
Nihay said:
Hey guys,
I have bought a Samsung S9+ via Amazon.
Because I am rooting my Samsungs since forever, I intended to do so again immediately. Used Magisk and so on.
Somehow this phone got stuck at the logo (bootloop?) and I couldnt use it anymore. Felt like the whole system was broken cuz nothing was possible.
So I downloaded a legit new firmware (I think it was the right one for my model) and used Odin to upload it on my phone. Then I rooted the phone again without any issues.
Perfect root right now.
However, independent from any used apps the phone reboots everyday by itself, lockscreen or while using. (I assume its not an app issue then..?)
I'd highly appreciate any help.
PS. I forgot where I got the firmware from, but it was definitely a legit website.
Here are some phone stats.
Modelnumber:SM-G965F/DS
ONE UI-Version 1.0
Android Version 9
Kernel Version 4.9.59-15540155
Please let me know if you need more information.
THank you ahead
Nihay
Click to expand...
Click to collapse
I have heard that there is a "protective system" against root on the new galaxy phones, did you try flashing this too?
https://download.highonandroid.com/...65_PIE_Root_for_OEM_issue_devices_V5.zip.html
Hope this will help!
Thanks for the reply.
I think I have done that too.
Followed a certain guide on xda actually, which included 3 or 4 files for rooting.
Is it afterwards via magisk possible?
Whats the suggestion anyone can give me, except maybe as last option reflashing everything.
Also, where would I be able to find a proper firmware if that is the issue.
Thanks a lot!
Nihay said:
Thanks for the reply.
I think I have done that too.
Followed a certain guide on xda actually, which included 3 or 4 files for rooting.
Is it afterwards via magisk possible?
Whats the suggestion anyone can give me, except maybe as last option reflashing everything.
Also, where would I be able to find a proper firmware if that is the issue.
Thanks a lot!
Click to expand...
Click to collapse
Try cleaning cache partition, if it doesn't work, try booting into safe mode, and see if the problem persists, if not, it must be a app, disable apps one by one and see which one is causing the problem
Magisk can only flash modules specially designed for it.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
DankMemz said:
Try cleaning cache partition, if it doesn't work, try booting into safe mode, and see if the problem persists, if not, it must be a app, disable apps one by one and see which one is causing the problem
Magisk can only flash modules specially designed for it.
Click to expand...
Click to collapse
If it persists then try disabling apps, sorry, my bad
DankMemz said:
Try cleaning cache partition, if it doesn't work, try booting into safe mode, and see if the problem persists, if not, it must be a app, disable apps one by one and see which one is causing the problem
Magisk can only flash modules specially designed for it.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
If it persists then try disabling apps, sorry, my bad
Click to expand...
Click to collapse
I have actually factory reset my phone completely and while adjusting the first settings (right after the wipe, with no apps yet) it did it again..Reboot.
However, I didnt mention, the reboot might happen, but after the phone is back to its previous state, apps are still opened. Technically its not a real reboot then.
Happens once a day, no fixed time.
Is it a matter of a wrong root? Followed this one
youtube.com/watch?v=-Fx8sD8yqpw
exactly the same way.
Still looking for help :/