Related
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
ricm68 said:
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
Click to expand...
Click to collapse
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
garyd9 said:
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
Click to expand...
Click to collapse
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
garyd9 said:
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
Click to expand...
Click to collapse
I flashed the one found at the post: [RUU] att ruu 1.58.502.1 posted
Hmm.. Not sure what to suggest in that case. I'm not very familiar with the whole RUU thing myself...
Sent from my Nexus 7 using Tapatalk
Download the ota update. Extract the firmware.zip from it but don't extract firmware.zip. boot to fastboot.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Do it again
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
Fastboot flash recovery twrp.img
Fastboot erase cache
Load recovery
Wipe, advanced wipe
Select dalvik, cache, data, system, internal. Wipe.
Put Rom on ext sd card or
Adb push Rom.zip /sdcard/
Install zip this will obviously erase everything on your phone.
Click thanks.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
You don't need to repair. You just need to troubleshoot. You are throwing the baby out with the bath water, if you go for a hardware repair for what is likely a software issue that is easy to resolve.
You also need to provide more details, and be specific as possible. Namely:
What recovery and version number?
S-on or off?
What exactly have you tried to flash?
Did you factory reset in bootloader?
Do you have working adb?
What happened when you ran the RUU?
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You wont need the whole thing but some of it might pertain to you
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back.
Click to expand...
Click to collapse
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
ricm68 said:
They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Click to expand...
Click to collapse
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
redpoint73 said:
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
Click to expand...
Click to collapse
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
ricm68 said:
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
Click to expand...
Click to collapse
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
I did the factory reset from within cyanogenmod and it didn't wipe it. It restarted back to cyanogenmod. I copied andoid revolution to my internal memory and try to install from there.
ricm68 said:
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
Click to expand...
Click to collapse
You need to try the things I've suggested. I've made some definitive recommendations, and you seem to have ignored them. Honestly, I don't see a point in trying to help anymore, if you don't read what I'm taking the time to post; or you don't try what I've suggested.
Worst case is RUU and start over (install custom recovery again, etc.). But again, I have no idea what happened when you tried to RUU since you still haven't answered that.
You aren't going to make any progress, if you keep ignoring the advice that is given to you.
I'm doing what you told me!!!
I reinstalled twrp and tried but it failed again. Believe me, I've been doing what you suggested.
Can you please give me the steps to RUU and what ruu file to download and use. I really appreciate all you're doing for me and the time you are taking to help.
Sent from my One M8 using XDA Premium 4 mobile app
I was able to install cyanogen mod again and I am using the phone but I want to install sense again.
Sent from my One M8 using XDA Premium 4 mobile app
What do I do to avoid permanently bricking this?
Story: Had Cyanogen mod installed on my HDX 8.9"; everything was rosy. Cyanogen kept pestering me with new nightly updates; thought "why not? can't cause any harm now everything's sorted!" Lo and behold, it soft bricked the device. Managed to recover to TWRP. What are my steps from here to get back to the Cyanogen ROM I had before, where everything was perfect (yes, I'm an idiot)?
Just reflash the ZIP you downloaded from XDA.
EncryptedCurse said:
Just reflash the ZIP you downloaded from XDA.
Click to expand...
Click to collapse
I tried; it says failed. Any thoughts?
Edit: Also, if I reinstall the ROM I had, will I have to reconfigure blocking the autoupdates from Amazon? Or will that still all be configured?
BRPW said:
I tried; it says failed. Any thoughts?
Edit: Also, if I reinstall the ROM I had, will I have to reconfigure blocking the autoupdates from Amazon? Or will that still all be configured?
Click to expand...
Click to collapse
Looking through previous posts it appears you have native twrp recovery (not safestrap) with a locked bootloader. If accurate try a factory reset from within twrp (slider under wipe option). This will wipe cache, dalvik and data partitions. You will loose personal data; might want to backup first. Do not wipe system unless instructed.
OTA will remained blocked if you reinstall a previous version of FireOS that was backed up via twrp. If you opt for a fresh install you must use a custom variant that has components removed that could brick your device.
Nexus v4 is a better choice IMO if you can't get CM to work. Avoids the hassles/risks associated with FireOS.
Davey126 said:
Looking through previous posts it appears you have native twrp recovery (not safestrap) with a locked bootloader. If accurate try a factory reset from within twrp (slider under wipe option). This will wipe cache, dalvik and data partitions. You will loose personal data; might want to backup first. Do not wipe system unless instructed.
OTA will remained blocked if you reinstall a previous version of FireOS that was backed up via twrp. If you opt for a fresh install you must use a custom variant that has components removed that could brick your device.
Nexus v4 is a better choice IMO if you can't get CM to work. Avoids the hassles/risks associated with FireOS.
Click to expand...
Click to collapse
Davey, you helped me install this originally; thank you for that!
So just so I'm clear; perform a factory wipe (no personal data that I care about on here), avoiding the wipe of the system partition. I can from that point, install the file on there labelled something akin to 'cm-apollo-nightly05032015.zip" right? And that will bring me back to where I was before this happened.
Edit: If I wipe the data partition, won't that wipe the cm-nightly.zip and other .img's etc?
BRPW said:
Davey, you helped me install this originally; thank you for that!
So just so I'm clear; perform a factory wipe (no personal data that I care about on here), avoiding the wipe of the system partition. I can from that point, install the file on there labelled something akin to 'cm-apollo-nightly05032015.zip" right? And that will bring me back to where I was before this happened.
Click to expand...
Click to collapse
I can not speak to the nightly referenced above. The most recent variant that was prepared/tested for your device is located here. If you browse through the full tread some individuals had luck with more recent nighties while others encountered difficulties.
BRPW said:
Edit: If I wipe the data partition, won't that wipe the cm-nightly.zip and other .img's etc?
Click to expand...
Click to collapse
Likely not as those images should be located in 'Internal Storage' (sdcard) which is a separate partition. You can verify this by locating the images in twrp file manager (under advanced). Use caution while in File Manager and you can mess your system if you accidentally delete/move critical file and folders. Like you mum use to say ... look but don't touch
Comment: Keep in mind you have opted not to unlock your bootloader which leaves your device vulnerable should something go wrong. Also, the build of CM11 you are using is not regularly updated for HDX devices as other cm variants and roms have become available. However, those either require an unlocked bootloader or Safestrap v4. If your are considering the latter be aware there are mandatory steps required to prepare your device for Safestrap v4. In your shoes I would seriously consider unlocking once the current problem is resolved. Risks are negligible (a failed unlock attempt has no adverse consequences) but does involve a bit of work.
Davey126 said:
I can not speak to the nightly referenced above. The most recent variant that was prepared/tested for your device is located here. If you browse through the full tread some individuals had luck with more recent nighties while others encountered difficulties.
Likely not as those images should be located in 'Internal Storage' (sdcard) which is a separate partition. You can verify this by locating the images in twrp file manager (under advanced). Use caution while in File Manager and you can mess your system if you accidentally delete/move critical file and folders. Like you mum use to say ... look but don't touch
Comment: Keep in mind you have opted not to unlock your bootloader which leaves your device vulnerable should something go wrong. Also, the build of CM11 you are using is not regularly updated for HDX devices as other cm variants and roms have become available. However, those either require an unlocked bootloader or Safestrap v4. If your are considering the latter be aware there are mandatory steps required to prepare your device for Safestrap v4. In your shoes I would seriously consider unlocking once the current problem is resolved. Risks are negligible (a failed unlock attempt has no adverse consequences) but does involve a bit of work.
Click to expand...
Click to collapse
Davey,
thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
BRPW said:
Davey,
thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
Click to expand...
Click to collapse
You can access TWRP with the HDX powered off this way: press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen.
BRPW said:
Thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
Click to expand...
Click to collapse
Just for clarification, you are not able to access TWRP recovery after powering down your device (full shutdown...not sleep), holding [power]+[vol-up] buttons together and then releasing after the grey logo appears? What happens?
Cl4ncy said:
You can access TWRP with the HDX powered off this way: press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen.
Click to expand...
Click to collapse
Davey126 said:
Just for clarification, you are not able to access TWRP recovery after powering down your device (full shutdown...not sleep), holding [power]+[vol-up] buttons together and then releasing after the grey logo appears? What happens?
Click to expand...
Click to collapse
I was just pressing buttons in the wrong way. I was getting frustrated because I knew I was doing it wrong, heh. Thanks guys! So regarding unlocking the bootloader, do you have some resources I can follow to fully unlock and perhaps find a Lollipop ROM, keep up with the times!
BRPW said:
I was just pressing buttons in the wrong way. I was getting frustrated because I knew I was doing it wrong, heh. Thanks guys! So regarding unlocking the bootloader, do you have some resources I can follow to fully unlock and perhaps find a Lollipop ROM, keep up with the times!
Click to expand...
Click to collapse
I assume you have Minimal ADB and Fastboot installed, so you should grab these drivers, download the software and follow the procedure mentioned here. Requires a little knowledge about the usage of command prompts. Any questions just ask.
Regarding Lollipop check this, or this ROM, note that both are in beta stage. Regarding the first one the 20150814 ROM seems to have issues regarding WLAN only (reboot required to re-enable it), the 20150815 ROM has some issues regarding sound and auto-rotation on some devices (rotation works perfect on my Thor).
Since there seems to be no way of installing current (and future) patches from stock recovery when the device is rooted, it'd be good to know if someone has information about whether it's possible or not to develop a custom recovery. The old method using 5.02 droidboot won't work because the updates mess up the whole system if you use them. So since we have unlockable bootloaders in 5.1, could there be the possibility of compiling a permanent CWM?
since there seems no one to be working on it at the moment, i'll start a few tries myself and document the progress in this thread. Feel free to help or comment.
For now, i', stuck at unlocking the bootloader and still don't know why. "OEM unlock" was set in the developer options, rebooted to fastboot and tried "fastboot oem unlock". Results as attached. :\
I'll google a bit around and see if i can get it working....
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
He's asking about a recovery that can be installed to the recovery partition, not just tethered.
It's possible, but we'd need somebody to build one. I tried one a while back from the Zenfone 2, but it didn't want to boot.
jumpup said:
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
Click to expand...
Click to collapse
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
toxic_garden said:
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
Click to expand...
Click to collapse
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
@xBIGREDDx made some instructions on this. Let me find it.
http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
This is not straightforward, but you *can* get to tethered CWM and root your 5.1 system. I did exactly this.
jumpup said:
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
Click to expand...
Click to collapse
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
toxic_garden said:
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
Click to expand...
Click to collapse
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
jumpup said:
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
However, I have always used a multi-tiered backup system:
* Titanium Backup (FULL on Sunday, INCREMENTAL every other day)
* Online NAndroid Backup (One per week using CWM format)
Each app's backup data syncs to the home NAS and Dropbox once a week.
I thought I had the Stagefright fix already in place. That's why I wanted to compare build/version details with a device that has the fix installed.
jumpup said:
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
Click to expand...
Click to collapse
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
toxic_garden said:
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
Click to expand...
Click to collapse
D'oh. I should have remembered about the data encryption. Need more caffeine
If you need anything tested or confirmed in the field, I'd be glad to help.
Sent from my Venue 8 7840 using Tapatalk
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
jumpup said:
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
Click to expand...
Click to collapse
oops you're right. Didn't even notice.
First steps forward: it seems like it's not possible to unlock the bootloader with installed sf-patch. No matter which version of fastboot i tried, i always got "FAILED: (some text i can't remember)". After downgrading to 5.1 stock firmware, unlock was possible. So as i now at least have the possibility to boot another recovery, i'll try setting up the build env. The Recovery Builder from CWM seems to be out of order at the moment.
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
I now have the Stagefright patch installed. Used the 5.02 droidboot temporarily to engage tethered CWM and install SuperSU. Reflashed 5.10 droidboot and firmware before proceeding. All is well. As you mentioned, it makes for a mixed 5.1 boot system, but I simply cannot live without root.
Here are the new build/version details:
After taking your advice and flashing the sg droidboot, my IWFI version is in line. I'll see if any system issues occur.
Is anyone still working on the 7840? Would be nice to have TWRP or CWM
I've been poking around on my 7840 on and off for a few weeks now. I seem to have verified that, after unlocking the bootloader, you can modify the boot and recovery partitions to your heart's content. However, any time I rebuild the kernel myself, I end up back at the "Dell" screen, frozen. Any other files are free game.
Assuming that the kernel needs to be signed using some tool I haven't figured out yet, I'm going to see if I can get a version of CWM working w/ the stock kernel. I tried dumping the version from the tethered recovery onto the recovery.img, but running it results in a black screen. I'll keep poking around though.
Hello,
Wondering what would happen if device get stolen? I've just started, especially since recovery is so easily accessible. Basically, anyone can enter, wipe data and everything left and put a new system... All that he needs is an microSD. Or in my case, I left all .zip files on mine, so that he can even chose whether he'd like more stock 5.1.1 or existenz.
Sometimes I don't know why I bother with a screen lock at all...
Anyone has any idea about preventing boot into recovery? Locking the recovery? Would disabled debugging and unknown sources fix the problem? Encryption?
Sorry if such subject already exists, couldn't find one.
Cheers!
Preventing recovery boot isnt something not known to be able to do however there is a "Theme" for Twrp that allows a password to be loaded up before accessing it
For your phone being turned on you can use Google device manager and enable required settings on your phones
Envious_Data said:
Preventing recovery boot isnt something known to be able to do however there is a "Theme" for Twrp that allows a password to be loaded up before accessing it
For your phone being turned on you can use Google device manager and enable required settings on your phones
Click to expand...
Click to collapse
OH. Didn't know about that. I'll have to try that one.
Sent from Xperia Z2
Luckily not from an iPhone = Yesterdays technology at tomorrows prices
I'll try that too. Found something for locking for 2.8.6.0, hopefully it will work for 2.8.7.0 too.
If all recoveries are locked and the android as well, would it be possible for someone to flash another recovery on top of existent ones?
dennnic93 said:
I'll try that too. Found something for locking for 2.8.6.0, hopefully it will work for 2.8.7.0 too.
If all recoveries are locked and the android as well, would it be possible for someone to flash another recovery on top of existent ones?
Click to expand...
Click to collapse
Depends on how you install
Flashable zips typically erase the partition where as images being flashed via command need to be wiped before installing
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.