Develop Bugs

[Q] Can't flash a ROM from TWRP

Hello there,
I was trying to install CM10 on my A100 but I messed it up.
I got everything right till TWRP installation, then I accidentally delete everything on my device, CM10 rom included. Now the only thing accessible is TWRP.
I understand from other posts of the forum that it should be still possible to flash a ROM choosing Mount from the menu, but I can't work out how.
I click on the mount tab, and I connect it to my computer via USB. My linux system recognises the tablet as a multimedia player, but it does not allow me to copy files on it. Changing the status of mounting System, Data and Cache does not change the behaviour. The option mount SD card is not selectable.
I have got TWRP 2.2.0, and my A100 does not have external SD.
Any help will be greatly appreciated

Do you have a microsd? Or twrp just won't see it. That would probably be the easiest option, load a ROM on the micro SD.
Did you make a backup first thing?
If your tab is in recovery, you should be able to use adb and push a ROM to the internal memory, but it is not recommended to flash from it. That's why I mentioned the microsd first.

Romman0 said:
Do you have a microsd? Or twrp just won't see it. That would probably be the easiest option, load a ROM on the micro SD.
Did you make a backup first thing?
If your tab is in recovery, you should be able to use adb and push a ROM to the internal memory, but it is not recommended to flash from it. That's why I mentioned the microsd first.
Click to expand...
Click to collapse
Unfortunately not, no microSD slot. I do not even have a backup; in my clumsiness while I was following the procedure I skipped an entire paragraph and I jumped to the wiping section.
I will try to use ADB, I saw that there are few threads covering the procedure. Thanks for the tip, I'll be back with the results

Ok, all went well.
I followed the instructions in this post: http://forum.xda-developers.com/showthread.php?t=1667929
with two minor corrections:
1 - as I did not have the /sdcard directory, I used the /data directory
2 - there was no need to add the ROM file name again after /data
thanks for help

Cannot flash with TWRP
Hi,
I am trying to flash ROM from http://forum.xda-developers.com/showthread.php?t=2016575 which is N7105XXDMC3 ULTIMATE v1.1C....
i did wiped cache/dalvik and system wipe and then went in install and pointed the zip file and says cannot open zip file…
please help!

msiddiqu said:
Hi,
I am trying to flash ROM from http://forum.xda-developers.com/showthread.php?t=2016575 which is N7105XXDMC3 ULTIMATE v1.1C....
i did wiped cache/dalvik and system wipe and then went in install and pointed the zip file and says cannot open zip file…
please help!
Click to expand...
Click to collapse
Consider yourself lucky, that ROM has nothing to do with this device and would likely have killed it. Only use ROMs from the device forum of the device you're flashing. I mean go to the development section of the a100 and get a ROM there, not some random device ROM with a great name.
Tapatalked from my HTC DNA - ReVolt

pio_masaki said:
Consider yourself lucky, that ROM has nothing to do with this device and would likely have killed it. Only use ROMs from the device forum of the device you're flashing. I mean go to the development section of the a100 and get a ROM there, not some random device ROM with a great name.
Tapatalked from my HTC DNA - ReVolt
Click to expand...
Click to collapse
but it says that its for canadian I317M devices, and confirmed working? i don't understand?
help

msiddiqu said:
but it says that its for canadian I317M devices, and confirmed working? i don't understand?
help
Click to expand...
Click to collapse
OK I think you ended up in the wrong forum then, this is for the Acer iconia A100, it has nothing to do or in common with those devices, you may wish to post in their forums for help.
Tapatalked from my HTC DNA - ReVolt

[Q] Samsung Galaxy Nexus system Damage

Good Evening everyone, I have a very big problem with my samsung galaxy nexus. It started 2 weeks ago when I tried to turn ON my phone, and it randomly can't Load the system (Jelly Bean 4.2.2). When I try to Turn it ON, the Nexus Picture stock up (the green red blue yellow moving image suddenly stop) and then a MATRIX like will appear on the screen (sometimes around the nexus image there will be green lines and dots. And sometimes the whole screen will have green pixels/Dots). I thought that the system is damaged, after many trials of recovering the system, I Decided to do a factory reformat/ return to factory settings.
Since I can't access the system, I unlocked the phone , installed teamwin recovery system, and did a wipe of all the things inside the internal memory (that was the most stupid decision ever) since I lost the backup system image inside the internal sd card.
I decided all of that all because that the Galaxy Nexus don't have a external SD CARD. And since I can't do a recovery of my files (because I need to be inside Android to have a DB connection to the phone). I had no option than to wipe all System, Dalvik, Cache, and Data. Now I can't flash any android system since the Clockwork and teamwin need the android image to be inside the SD CARD. And I can't send/receive any file from/to the SD card. I already tried "Nexus Root Toolkit" and "Galaxy Nexus Toolkit". But there is no hope.
One good thing is I did install an "ICE CREAM SANDWICH image" using "Odin" (Since that was the only image I found in the internet that can be installed using Odin, but there is no luck also, when the animation is loading, the animation suddenly stop and the phone restarts.
Anyone please kindly help meif you encountered this problem before. Life without Android is so lonely. :crying::crying::crying:

abo0badr said:
Good Evening everyone, I have a very big problem with my samsung galaxy nexus. It started 2 weeks ago when I tried to turn ON my phone, and it randomly can't Load the system (Jelly Bean 4.2.2). When I try to Turn it ON, the Nexus Picture stock up (the green red blue yellow moving image suddenly stop) and then a MATRIX like will appear on the screen (sometimes around the nexus image there will be green lines and dots. And sometimes the whole screen will have green pixels/Dots). I thought that the system is damaged, after many trials of recovering the system, I Decided to do a factory reformat/ return to factory settings.
Since I can't access the system, I unlocked the phone , installed teamwin recovery system, and did a wipe of all the things inside the internal memory (that was the most stupid decision ever) since I lost the backup system image inside the internal sd card.
I decided all of that all because that the Galaxy Nexus don't have a external SD CARD. And since I can't do a recovery of my files (because I need to be inside Android to have a DB connection to the phone). I had no option than to wipe all System, Dalvik, Cache, and Data. Now I can't flash any android system since the Clockwork and teamwin need the android image to be inside the SD CARD. And I can't send/receive any file from/to the SD card. I already tried "Nexus Root Toolkit" and "Galaxy Nexus Toolkit". But there is no hope.
One good thing is I did install an "ICE CREAM SANDWICH image" using "Odin" (Since that was the only image I found in the internet that can be installed using Odin, but there is no luck also, when the animation is loading, the animation suddenly stop and the phone restarts.
Anyone please kindly help meif you encountered this problem before. Life without Android is so lonely. :crying::crying::crying:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
Learn before using a toolkit.
Sent from my Nexus

bk201doesntexist said:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
Learn before using a toolkit.
Sent from my Nexus
Click to expand...
Click to collapse
I know I had to learn. but I didn't. Because almost all of the people is saying the same thing, that's why I followed what almost all said.
And now I am stocked. Please someone help me. I tried following Sir Efrants procedure but I was stocked with the image flashing. Since I cannot transfer the images to my internal SD Card. Now I have no solution. Someone pls help.

Read the DRIVERS part first.
Sent from my Nexus

bk201doesntexist said:
Read the DRIVERS part first.
Sent from my Nexus
Click to expand...
Click to collapse
My drivers are good and good to go. but the method requires the image to be inside the internal sd card. And I don't have the image inside it. it is just stored in my laptop. I can't drop it to the sd card since the adb mode requires the phone to be inside the android system. Any help guys?

adb doesn't require the phone to be in Android, custom recoveries allow adb.
Also, as long as you can get into the bootloader, with it unlocked you can try flashing stock images via fastboot.

abo0badr said:
My drivers are good and good to go. but the method requires the image to be inside the internal sd card. And I don't have the image inside it. it is just stored in my laptop. I can't drop it to the sd card since the adb mode requires the phone to be inside the android system. Any help guys?
Click to expand...
Click to collapse
Indeed, if you had read the thread like you're told to, you would know that ADB works in a custom recovery.

Just flash a stock image and lock the bootloader...
https://developers.google.com/android/nexus/images
And oh, don't ever unlock the bootloader.

Mach3.2 said:
Just flash a stock image and lock the bootloader...
https://developers.google.com/android/nexus/images
And oh, don't ever unlock the bootloader.
Click to expand...
Click to collapse
Lol. most people learn from their mistakes...
faxed from my nexus

[Fixed] Soft Bricked SPH-L710

Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.

signalsoldier said:
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
Click to expand...
Click to collapse
Good morning (not really, I assume, sorry). So where are you at? Not sure what you mean that you cannot install files on the phone... Can you get into download mode and your computer recognizes the phone? If yes, can you do what you started to say - odin stock rooted? Or... if you can get into a custom recovery but your internal sd card has been wiped, can you put a stock rooted ROM in zip format on an external sd card, put that sd card into your phone, and flash in custom recovery?

erikalin said:
Good morning (not really, I assume, sorry). So where are you at? Not sure what you mean that you cannot install files on the phone... Can you get into download mode and your computer recognizes the phone? If yes, can you do what you started to say - odin stock rooted? Or... if you can get into a custom recovery but your internal sd card has been wiped, can you put a stock rooted ROM in zip format on an external sd card, put that sd card into your phone, and flash in custom recovery?
Click to expand...
Click to collapse
Here is the problem...the ROM I have is in zip format and based on what I have been reading I cannot install via Odin. Due to the fact that the phone refuses to mount as an external storage device I have no way of placing data on the the internal or external card. The only recourse I have now it to attempt to find an adapter to be able to mount this microsd card to my PC. I am out of town and have no idea where I could find one.....uggggh. Ill keep you posted.

signalsoldier said:
Here is the problem...the ROM I have is in zip format and based on what I have been reading I cannot install via Odin. Due to the fact that the phone refuses to mount as an external storage device I have no way of placing data on the the internal or external card. The only recourse I have now it to attempt to find an adapter to be able to mount this microsd card to my PC. I am out of town and have no idea where I could find one.....uggggh. Ill keep you posted.
Click to expand...
Click to collapse
Walmart. .. target. ... and most any office store you should be able to find one. http://forum.xda-developers.com/showthread.php?t=2538543 ... This thread gives you the stock unrooted rom in a flashable zip. To my knowledge no one has put out a stock rooted zip, but I will check around.
http://i.imgur.com/qrByUGN.jpg

signalsoldier said:
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
Click to expand...
Click to collapse
You always have the Factory Reset/Wipe Data option inside your Recovery. But if that doesnt work use your downoad mode and Reset in KIES. but whatever you do, now that you have upgraded to 4.3 DO NOT try and dowgrade. it will cause a hard brick.

You did the ota update which put KNOX on your phone which is bad especially if you have a warranty. There is currently no way to get rid of it. I read a while ago the peoples phones has been getting bricked because they were trying stuff.
Anyway the only option I guess you have is to use your computer and reset your phone using kies. It will flash your phone back to stock in download mode.
Sent from my GT-N5110 using xda app-developers app

Ok team here is the latest
I was able to grab an adapter for my micro and I attempted to install the stock rom posted above located here
http://forum.xda-developers.com/showthread.php?t=2538543
That was a no-go and gave me the following error during installation.
assert failed: apply_rename_check("/system/app/ALLSHAREPLAY.apk","/system/app/ALLSHARECASTPLYER.apk","f90c86cf5423131dcd04f9a5b169df5f83ab9170" "81dbc5115c7c1121f70ada147f7297e192af4d38")
E: Error in /external_sd/cffb350e111c431bcd19eea86e0d0e6816950053.USER_L710_SPR_MD4_to_MK3_Update_FWD.zip
Click to expand...
Click to collapse
I attempted to connect to Kies 2.6.1 via download mode. Kies will timeout attempting to connect after about 8 to 10 mins.
"Device does not respond. Reboot to Resolved the Issue."
Click to expand...
Click to collapse
at this point I am still able to get into Recovery and Download. I really hosed this **** up

Here is the stock tar thread....You can use this to Odin back to stock. http://forum.xda-developers.com/showthread.php?t=2565972
Good luck!
http://i.imgur.com/qrByUGN.jpg

Thanks bro.....Ill download it and give it a try. I have nothing to lose at this point. Ill be back with praise or tears.

Problem resolved I was able to go back to stock using the link posted above by Bigpappa!!!
Thank you all so much for you help!

Congratulations
I am glad you were able to get use of your phone back. I wish I had seen this thread sooner. I was in exactly the same boat a couple of weeks ago, only mine lasted 3 days. I even bought a new GS4 when I thought my phone was dead. Took it back when someone finally helped me do what you did. It's a helpless feeling when you have been rooting and Romming for years safely. Sure seems like a sticky thread is in order for this specific issue. As you can see, I haven't got enough history for credibility on this forum since I rarely post. Oh well.

Phone no longer has anything in 'Internal Storage', can't download files

A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
Click to expand...
Click to collapse
Did you update the binaries?

xunholyx said:
Did you update the binaries?
Click to expand...
Click to collapse
I was never given an option, it said they couldn't be installed by the app. I was going to try the fix where you install them directly by saving a zip to your phone's internal storage and then installing it but then I noticed the problem with my internal storage.

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone
Click to expand...
Click to collapse
When you chose to make the SD a part of internal storage (known as the new "adoptable storage" option in Marshmallow), you merged it (with the phone's internal storage) as part of the data partition. Then you yanked out a part of that partition, by removing the SD (and why you did that in order to root, I don't know).
I'm not too familiar with what happens (or is supposed to happen, anyway) when you choose adoptable storage, then remove the SD. But I think its safe to say, that resulting storage issues is not a surprise.
dezzybird said:
I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
Click to expand...
Click to collapse
The toolkit hasn't been updated in over a year, and causes many issues for that reason. It hasn't been updated for Marshmallow (Android 6) and therefore can't root MM. Toolkit also contains an obsolete version of TWRP which will also cause some issues.
Good rule of thumb: whenever rooting an Android device, you should be sure to use updated methods; and verify the method works with your Android version.
Since you have TWRP installed, try going to the Wipe section in TWRP. Then select the button that says "Format Data" and see if that helps your issue with writing to internal storage. Do not select to wipe any other things in the Advanced section of Wipe (another rule of thumb - if you don't know what it is don't wipe it. For instance wiping "System" will delete the OS entirely).
Of course, formatting data will cause any data to be lost. So backup accordingly (if there is anything left) before you format data.
Once you have the storage issue sorted out (hopefully the above helps), ditch the toolkit, and do the following steps manually:
1) Unlock bootloader (should already be done)
2) Flash TWRP 3.0 with fastboot
3) Flash SuperSU 2.65 in TWRP, to properly root

Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
I've managed to sort the issue now so I'll post what I did here for any people who may happen upon the thread in future. I'm still not sure what caused the issue in the first place; maybe it was the memory card, maybe I selected the wrong thing to wipe in TWRP, maybe it was the toolkit or maybe a bit of everything because I'm stupid.
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason) and install a custom ROM, so I decided to just go ahead with it. After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod. According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Thanks for your help!

dezzybird said:
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
Click to expand...
Click to collapse
The best way to achieve bootloader unlock and root is to just do the steps manually.
You don't need a toolkit to do these things. Anyone that can follow instructions and type a few fastboot commands can do it.
All that folks need to do it manually is here. Everything in Section 1 is valid, with the exception that the TWRP version number in the command needs to (obviously) match the number you are trying to install (the example given in the guide is an older version). Some things in Section 2 and 3 are obsolete (s-off method, firmware version) but that's irrelevant in this case (and for most folks) since those things aren't necessary to unlock the bootloader, root, or flash custom ROMs.
dezzybird said:
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason)
Click to expand...
Click to collapse
What do you mean "for some reason"? I told you the reason. The toolkit uses an old, long obsolete version of SuperSU that existed before MM. It therefore can't root MM, and there is no reason to believe it would. New Android builds often (almost always) require new root methods, and old versions of SuperSU are usually going to cause you trouble. That is why you should always research the current root methods, when trying to root.
dezzybird said:
After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod.
Click to expand...
Click to collapse
You don't need to root after flashing a custom ROM, they are already rooted.
You also don't need to root in order to flash a custom ROM. Unlocked bootloader and custom recovery is all you need to flash custom ROMs.
dezzybird said:
According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
Click to expand...
Click to collapse
These are not correct assertions. Doing the default wipe in TWRP (it says most of the time, this is all that is needed, and it means it!) doesn't touch internal storage.
On a similar note, flashing a ROM doesn't touch internal storage, either. It just flashes system partition and boot.img partition.
dezzybird said:
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Click to expand...
Click to collapse
I'd strongly advise against using the toolkit at this point, or suggesting to others to use it. As I've already tried to explain (but you seem to be ignoring) the components of the toolkit are woefully obsolete. By the time you flash recovery manually (with fastboot) and manually flash the proper version SuperSU, there isn't much of value that the toolkit does. The bootloader unlock procedure via HTCDev.com is pretty self-explanatory (and the guide I've posted explains whatever isn't already obvious). And is justifiable to say that if you can't handle doing these things manually, you probably shouldn't have root.

I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started. I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not. Like I mentioned, this was my first time rooting a device and I was kinda winging it as a learning experience, hence not doing things optimally (or particularly right)
Thanks for the info, that'll definitely make things easier next time!

dezzybird said:
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started.
Click to expand...
Click to collapse
And what I am saying is: what you stated you "would have done instead" (or do "next time") is in fact not the correct thing to do.
Also, when you say "this is what I would have done" it read strongly like a suggestion to others what "they should do".
Just trying to prevent obvious pitfalls for both you and others in the future.
dezzybird said:
I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
Click to expand...
Click to collapse
My advice would be to stick to XDA, and just use the search function here; or simply browse the forums. Reason being, randomly Googling for root methods will often yield random "root" websites with poorly organized, outdated information; which is often just stolen from XDA in the first place.
The question (and answer) of rooting this device pops up pretty frequently; as well as common pitfalls, solutions, etc. While the forums may be a bit intimidating to work through, the answers are all here; and not hard to find, once you become accustomed to how the forum is organized.
dezzybird said:
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not.
Click to expand...
Click to collapse
The knowledge in the following 2 paragraphs are fairly esoteric, but proboably could have been found in the CM thread or other threads:
CM has a slight oddity to it (and I'm sure its devs have there reasons) versus many other ROMs (but you may find a similar thing in other AOSP based ROMS) in that the ROM is pre-rooted, but root access is toggled "off" by default. To turn it on, do to phone's Settings>Developers Options, and there you find the option to toggle root on or off (default is off).
If you don't see Developer Options in Settings, its a bit of a quirky Android trick to make it appear. Go to Settings>About>Software information>More, then tap the "Build number" 7 times, and you will see a toast message that "You are now a developer" (yeah, that is what it really says!) and the option is now available in Settings.

Unending trouble with system partition for hydrogen

hi guys, I am having trouble with my MI Max having 32GB internal memory.
From it's behaviour for last few days I have inferred it's system partition is the culprit.
On stock miui rom, it gives msg that encryption unsuccessful and I need to factory reset it. But even after doing factory reset it shows the same msg.
Its with locked boot loader but referring one thread I could install twrp latest version on it by replacing recovery image in stock rom and flashing with mi flash tool in edl mode.
So with two I tried installing few vision rooms like miui eu ROM, RR and crdroid based on Oreo. All the rooms while flashing fine error E1001, saying system image not updated and flashing failed.
I even tried repairing file system, fixing file system, Channing file system to fat, exfat, ext2, ext3, ext4 and f2fs several times (from advanced wipe menu) but things are not improving. Even tried formatting data partition as it's suggested at few places.
I am out of ideas after spending few days trying to fix it by flashing several times.
So please if some one can assist in resolving the issue, I would really appreciate.
Thank you in advance.

You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.

Zasnizas said:
You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.
Click to expand...
Click to collapse
Have already done it several times by now. Didn't make any difference.

harpy.eagle said:
Have already done it several times by now. Didn't make any difference.
Click to expand...
Click to collapse
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/

Zola III said:
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/
Click to expand...
Click to collapse
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.

harpy.eagle said:
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.
Click to expand...
Click to collapse
It's still ain't bricked so you can do this relatively easy. When it's bricked EDL programmer for used NAND chip used is needed.
So take a deep breath, see the exact size & type of the partition, delate it, create a new one exactly the same (type, size & name).
https://s10629.pcdn.co/wp-content/pictures/2010/01/captured_Image1.png51.png
https://helpdeskgeek.com/wp-content/pictures/2010/01/captured_Image1.png111.png
The tool I gave you URL is very good documented and with plenty examples & user guides available all which can be found on the site, it uses graphics GUI so it's as easy as it can be. So if you are inexperienced read/watch first how it's done. After you are done flash what you want in TWRP.
Best regards.

What I meant to ask is, how to access partitions of mobile on PC? I have used partitioning app on windows but never for android device. Anyway, as u have clued, I shall try accessing partitions with mobile connected in edl mode.