Okay, I've rooted my n5110 8.0 and manually flashed 4.2.2 XXCMH3. I have reset the flash counter with triangle away. It shows software update is available. Is it possible to use OTA Root keeper to update the OTA update? IM me or answer here please no guesses. Thanks in advance.
capitoldach said:
Okay, I've rooted my n5110 8.0 and manually flashed 4.2.2 XXCMH3. I have reset the flash counter with triangle away. It shows software update is available. Is it possible to use OTA Root keeper to update the OTA update? IM me or answer here please no guesses. Thanks in advance.
Click to expand...
Click to collapse
Yes it should work fine, there have been issues with 4.3 but in a video I watched about the app the update from 4.2.1 to 4.2.2 went smoothly for him. Granted nothing is guaranteed. If you are using superSU you can buy the pro version and it has an OTA survival mode. Alternatively you could also flash the update via odin or recovery but since you're asking about OTA Root Keeper I'm sure that isn't something you are interested in. Make sure you follow the steps and make any other backups you can because you never know.
http://www.youtube.com/watch?v=ky5miA8ilr0&noredirect=1
That's the video I watched also I looked at other posts regarding known issues and it doesn't look like there are problems specifically with certain UI types (Touchwiz Sense etc). GOOD LUCK let me know how it goes
Thanks.
dwibbles33 said:
Yes it should work fine, there have been issues with 4.3 but in a video I watched about the app the update from 4.2.1 to 4.2.2 went smoothly for him. Granted nothing is guaranteed. If you are using superSU you can buy the pro version and it has an OTA survival mode. Alternatively you could also flash the update via odin or recovery but since you're asking about OTA Root Keeper I'm sure that isn't something you are interested in. Make sure you follow the steps and make any other backups you can because you never know.
http://www.youtube.com/watch?v=ky5miA8ilr0&noredirect=1
That's the video I watched also I looked at other posts regarding known issues and it doesn't look like there are problems specifically with certain UI types (Touchwiz Sense etc). GOOD LUCK let me know how it goes
Click to expand...
Click to collapse
Thanks for the response and link, I really appreciate it. I actually do have the pro version of superSU. I was unaware that superSU has that option.
capitoldach said:
Thanks for the response and link, I really appreciate it. I actually do have the pro version of superSU. I was unaware that superSU has that option.
Click to expand...
Click to collapse
Did it all work out?
dwibbles33 said:
Did it all work out?
Click to expand...
Click to collapse
Yeah I'd really like to hear back from the OP about this.
No it didn't
dwibbles33 said:
Did it all work out?
Click to expand...
Click to collapse
Although I do appreciate the time. I was unable to make it work. I was informed by Mr hyde, that this is one of the models that always have +1 if you have a custom recovery or any other changes to the device. Not sure though, because when I when I was on xxchm3 I tried the update and instead of saying device has been altered it said successfully registered. So I'm not sure what that means. Currently I'm having another issue I'm trying to figure out. I have a large amount of misc. Files taking up a few gbs of space. I have factory reset and wiped partition each time, but when I install superSU pro version it says needs to update binary. So I do, it restarts into cwm 6.x and says either erase disable stock recovery, I haven't accepted so I select go back on the bottom of the list, it restarts and everything appears to be working, but now I'm wondering if I am supposed to delete/disable stock recovery or if there's no way to get stock recovery back if I do erase/ disable. And also if that is where my misc. Memory is allocated or it is something else entirely, as when I backup I backup to external sd card. Thanks for the consideration and I will hit the button as well. It is really cool of you to follow up.
capitoldach said:
Although I do appreciate the time. I was unable to make it work. I was informed by Mr hyde, that this is one of the models that always have +1 if you have a custom recovery or any other changes to the device. Not sure though, because when I when I was on xxchm3 I tried the update and instead of saying device has been altered it said successfully registered. So I'm not sure what that means. Currently I'm having another issue I'm trying to figure out. I have a large amount of misc. Files taking up a few gbs of space. I have factory reset and wiped partition each time, but when I install superSU pro version it says needs to update binary. So I do, it restarts into cwm 6.x and says either erase disable stock recovery, I haven't accepted so I select go back on the bottom of the list, it restarts and everything appears to be working, but now I'm wondering if I am supposed to delete/disable stock recovery or if there's no way to get stock recovery back if I do erase/ disable. And also if that is where my misc. Memory is allocated or it is something else entirely, as when I backup I backup to external sd card. Thanks for the consideration and I will hit the button as well. It is really cool of you to follow up.
Click to expand...
Click to collapse
By +1 do you mean the flash counter? If you boot into download mode it'll show you a flash counter. For the binary update select the Normal install not the TWRP/CWM option. You shouldn't have to flash the binaries they SuperSU should be able to update within the app. As for the misc files it could be the partitions are messed up, if you use a root file explorer goto /data/media check those folders, your 0 folder should be your normal files but see if another 0 shows up or it might have a clockworkmod folder that has backups in it (I've seen the backups that are supposed to end up on the extSd end up there so its worth checking). Let me know if you want/need any more help I have worked my way through a lot of crap between my tablet and phone and I wish there was more help out there than there is so please let me know if I can help.
0 file in 0 file like 4 times each dated days I flashed different builds
dwibbles33 said:
By +1 do you mean the flash counter? If you boot into download mode it'll show you a flash counter. For the binary update select the Normal install not the TWRP/CWM option. You shouldn't have to flash the binaries they SuperSU should be able to update within the app. As for the misc files it could be the partitions are messed up, if you use a root file explorer goto /data/media check those folders, your 0 folder should be your normal files but see if another 0 shows up or it might have a clockworkmod folder that has backups in it (I've seen the backups that are supposed to end up on the extSd end up there so its worth checking). Let me know if you want/need any more help I have worked my way through a lot of crap between my tablet and phone and I wish there was more help out there than there is so please let me know if I can help.
Click to expand...
Click to collapse
Ok, so I started over with OUEMFI1 factory rest and wiped partition. I still have misc. files. So, I went to data/media I found the 0 file, inside that file is another 0 file, inside of that file another 0 file, and on and on all with different dates. Should I remove the 0 files within the 0 files, are they necessary, or they left over each time I flash? I did mean flash counter, but I haven't checked it via download mode, I will do that.
capitoldach said:
Ok, so I started over with OUEMFI1 factory rest and wiped partition. I still have misc. files. So, I went to data/media I found the 0 file, inside that file is another 0 file, inside of that file another 0 file, and on and on all with different dates. Should I remove the 0 files within the 0 files, are they necessary, or they left over each time I flash? I did mean flash counter, but I haven't checked it via download mode, I will do that.
Click to expand...
Click to collapse
Okay so what happened with all those 0 files is basically with the ability to change users that number changes if you add more users. For whatever reason when you flash a ROM it creates a new 0 file and pushes your old 0 file further in. If you go through those files you may see folders you used to have on other ROMs containing old stuff you had. So if you have stuff to keep then copy it to the /0 folder then delete the extras. I have been trying to modify a script from the GSIII that basically wipes everything except your external card but it didn't work last time. My advice would be to back your files up to your external, go into recovery and instead of a factory reset go into mounts and format /data (again be sure to back your stuff up because this will take it all out). That should wipe out everything (0 files and such) I would go as far as formatting system too. MAKE SURE you have a ROM on your external card because formatting /system will wipe out your existing ROM, but you will get a fresh start and at that point you know that nothing is hanging around from before.
Related
I have a new T-Mobile Note 2. I installed TWRP and SuperSU using the toolkit. I then used Root Browser and deleted a bunch of apps ("bloatware", I thought), and apparently removed too much, as the phone no longer boots android.
I downloaded the two Tweaked 2.4.1 Rom files, checked Md5sums, OK, and coped same to external SD card. I did the recommended wipes using TWRP. Thereafter, also using TWRP, BasicInstall finishes with success, but the Tweaked.2.4.1.UVBMD1.073113.zip install fails with "E: Unable to open zip file". Then I try to reboot, and get a message "your phone does not appear to be rooted", and take the option "Install SuperSU? That also fails.
I think maybe I can't install Tweaked.2.4.1.UVBMD1.073113.zip because the phone isn''t rooted? Is that right? But I can't figure out how to root the phone either. I'm stuck in a loop. Recommendations to fix appreciated.
Thx, Gus
gus_zernial said:
I have a new T-Mobile Note 2. I installed TWRP and SuperSU using the toolkit. I then used Root Browser and deleted a bunch of apps ("bloatware", I thought), and apparently removed too much, as the phone no longer boots android.
I downloaded the two Tweaked 2.4.1 Rom files, checked Md5sums, OK, and coped same to external SD card. I did the recommended wipes using TWRP. Thereafter, also using TWRP, BasicInstall finishes with success, but the Tweaked.2.4.1.UVBMD1.073113.zip install fails with "E: Unable to open zip file". Then I try to reboot, and get a message "your phone does not appear to be rooted", and take the option "Install SuperSU? That also fails.
I think maybe I can't install Tweaked.2.4.1.UVBMD1.073113.zip because the phone isn''t rooted? Is that right? But I can't figure out how to root the phone either. I'm stuck in a loop. Recommendations to fix appreciated.
Thx, Gus
Click to expand...
Click to collapse
If you got an unable to open zip file error - even though the md5s check out the only thing I can think of is the zip has become corrupted somehow. Did you check the md5 on a computer and move the file over? Might be worth checking it on the phone (you can use the terminal interface in twrp fwiw - just use the md5sum command).
Bottom line recommendation - try to copy the full zip over to the sdcard again. Also, just to sate my curiosity - did you wipe /system before flashing?
RE: Stuck
dwitherell said:
If you got an unable to open zip file error - even though the md5s check out the only thing I can think of is the zip has become corrupted somehow. Did you check the md5 on a computer and move the file over? Might be worth checking it on the phone (you can use the terminal interface in twrp fwiw - just use the md5sum command).
Bottom line recommendation - try to copy the full zip over to the sdcard again. Also, just to sate my curiosity - did you wipe /system before flashing?
Click to expand...
Click to collapse
I did recopy the two Tweaked .zip files to the sdcart - repeated attempt to install on phone, same problems.
I also unzipped the two Tweaked files on linux, and although I don't know exactly what I'm supposed to see, there's no errors and a bunch of directories and files that generally look reasonable
I think I did wipe /system on the phone before flashing - could that be my problem? Also, when I go into terminal mode in TWRP on the phone, I get a hang at "Updating partition details"
Is it possible I've accidentally deleted the unzip program on the phone?
Is there stuff I could/should do from an adb shell on my PC through a USB hookup to the phone?
thx, Gus
You could flash stock rom with odin and start over.
Tweaked Out
gus_zernial said:
I did recopy the two Tweaked .zip files to the sdcart - repeated attempt to install on phone, same problems.
I also unzipped the two Tweaked files on linux, and although I don't know exactly what I'm supposed to see, there's no errors and a bunch of directories and files that generally look reasonable
I think I did wipe /system on the phone before flashing - could that be my problem? Also, when I go into terminal mode in TWRP on the phone, I get a hang at "Updating partition details"
Is it possible I've accidentally deleted the unzip program on the phone?
Is there stuff I could/should do from an adb shell on my PC through a USB hookup to the phone?
thx, Gus
Click to expand...
Click to collapse
Hmm... maybe reflash recovery? That's very strange - especially if the first zip worked fine and the second had the issues...
rail205 said:
You could flash stock rom with odin and start over.
Tweaked Out
Click to expand...
Click to collapse
I wish I could! But when I try that it hangs at "Waiting for USB debugging to be enabled". And that's even if the phone is booted into download mode.
Gus
Odin back to stock. Twrp started failing everything I tried to flash also. That's why I stopped using it. But you need to Odin to stock
Sent from my SGH-T889 using xda premium
[SOLVED] Stuck ...
dwitherell said:
Hmm... maybe reflash recovery? That's very strange - especially if the first zip worked fine and the second had the issues...
Click to expand...
Click to collapse
Finally got it working. dwitherell was more or less right about the problem. Here's my steps: 1) did a low-level format on the external sda card 2) recopied the two Tweaked zip files onto the external sda card 3) Cheked md5sums for both files on the external sda card 4) ainstalled from TWRP, as before. BUT - this time it worked.
I'm guessing either the external sda card or one of the zip files was corrupted - as dwitherell had suggested. Thanks to him and other forum members for helping out.
Gus
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.
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.
Guys, I'm having a tough time deleting a file or two that were recently installed in the root's /product folder and I guess I don't understand what I am doing wrong, or what security is in place to prevent me from doing this. I would greatly appreciate any help or suggestions here. I cannot change permissions to make the folder recursively rw. I first started with Root Explorer and Solid Explorer. Both are capable of changing permissions but failed saying it was a "system folder". I used terminal to setenforce to 0, and tried with su from terminal and could not manually change folder permissions using chmod either. I thought maybe TWRP would be the answer, so I booted recovery and tried mounting the data partition (I think it's on data) and used file manager to browse to the folder, but I cannot see the contents of the folder nor can I delete it. What am I missing here? Is the TWRP mount function busted atm? Last night I reflashed November's update with the -w thinking it might "overwrite" the folder, but there was no joy there either. I do have a couple of TWRP backups of the data folder and that is my next step. Before I apply the December image tonight, I'm going to restore the most recent /data partition backup. There has to be a way to get control of that folder and it's contents but so far it has eluded me.
Cheers and TIA.
As far as I'm aware, the only way currently to write to the product partition is to fastboot flash it. I've went as far as to modify TWRP fstab to mount it in recovery and use the file manager to replace the bootanimation only to have it either never write properly or for it to "correct" itself. Not sure which happened.
Sent from my Pixel 3 XL using Tapatalk
I appreciate the response... anything helps. Product is a folder in root also and that is what I am trying to access. Unless there is some kind of symlink linking that product folder to the product partition. I don't know. When I flashed the full image yesterday I would have thought that partition.img (nested in the zipfile) would have been flashed, too. Maybe I can try fastboot formating the product partition. Can't hurt. Thanks again!
Edit: Just found this thread where you also contributed. I'll try to flash that partition with the partition.img and see what happens. I just want to reset it to stock.
superchilpil said:
As far as I'm aware, the only way currently to write to the product partition is to fastboot flash it. I've went as far as to modify TWRP fstab to mount it in recovery and use the file manager to replace the bootanimation only to have it either never write properly or for it to "correct" itself. Not sure which happened.
Click to expand...
Click to collapse
I flashed product.img first and it rendered the phone unbootable... corrupt. I then went back into TWRP and wiped system and ran the flash-all script in fastboot and re-rooted. The net result is the product folder is unchanged. Everything is up and running just fine. That folder is just untouchable for me so far. Next I will format data and re-flash. I didn't fully understand what you meant about the custom kernel being the solution but so far EX is not working. May reach out to flar2 and see if he can make some kind of change to his kernel to support mounting this partition? Thanks again.
v12xke said:
I flashed product.img first and it rendered the phone unbootable... corrupt. I then went back into TWRP and wiped system and ran the flash-all script in fastboot and re-rooted. The net result is the product folder is unchanged. Everything is up and running just fine. That folder is just untouchable for me so far. Next I will format data and re-flash. I didn't fully understand what you meant about the custom kernel being the solution but so far EX is not working. May reach out to flar2 and see if he can make some kind of change to his kernel to support mounting this partition? Thanks again.
Click to expand...
Click to collapse
Yeah I have yet to be able to mount the product image to modify it, but I haven't tried all that much lately. I'm pretty sure it's fixable with a kernel edit but that's beyond my ability, and even if I could I have a 8 year old laptop that wouldn't be able to build it.
What are you trying to accomplish? The bootanimation?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Yeah I have yet to be able to mount the product image to modify it, but I haven't tried all that much lately. I'm pretty sure it's fixable with a kernel edit but that's beyond my ability, and even if I could I have a 8 year old laptop that wouldn't be able to build it. What are you trying to accomplish? The bootanimation?
Click to expand...
Click to collapse
No, I see boot animation in that folder, and yes we all used to use it, but this time it's just an apk from apkmirror that wrote to that system partition (don't ask me how) and now I can't uninstall or update it. com. breel.wallpapers18. I tried to uninstall it using pm uninstall, but it uninstalled it for user 0 so it remains as a system app, and not available to me. I can't uninstall it completely or upgrade... or even use it! It's just a fk'in set of Google live wallpapers I like, but now want to re-set. Waay too much time spent on this so I'm (just about) ready to flush and start over. Every year Google makes it harder for us (fans) to customize our own phones. wtf? Pissed.
Hey there,
I have the Galaxy a50 SM-A505Fn and I just broke my internal storage by flashing TWRP and Multidisabler.
First, I should note that I am completely blind, so I use TWRP with ADB in CMD.
First I tried to root my phone with a patched boot image, using Magisc, but that didn't work, so I switched to TWRP.
After flashing it with Odin and booting into the recovery, my pc saw it as Galaxy A50 and the folders inside it were literal giberish and I couldn't paste anything in it, so I switched to a micro SD to flash Disabler and that worked surprisingly well.
Note, I did the wiping before that.
After the disabler worked, I rebooted into TWRP and used the command to reboot into recovery, as I was instructed, then the phone booted up just fine.
I set it up, and gained root with Magisc manager, but after connecting it to the PC to get the sound files I wanted to change it was still giberish and didn't let me make folders or paste anything into it.
The card also looked like it had the internal storage files like you would see on any phone, it had like 256 KB used on it from 2 gb it is formated at since I used it for a pi before and didn't have time to fix the capacity on it back to 64, but again you can't put anything onto it while in the phone.
Any help on how to make it work like normal?
Also apps don't see the storage properly either, so I can't use it for the reasons I rooted it for.
Thanks a lot.
After reading about it, it seems that the storage is encripted.
I managed to flash Infinity os on it, but the thing doesn't talk since it is missing text to speech, so I wanted to flash a zip to make it talking.
After rebooting into twrp, again, still encripted.
Got the zip onto my card, but doesn't flash, which is fine since that can be fixed, but I can't really do anything to fix it.
Does anyone know the command to format data?
twrp format data doesn't work like in the TWRP guide.
Any ideas?
you need to install multidisabler
yamen_tn said:
you need to install multidisabler
Click to expand...
Click to collapse
Did that already, that is how I flashed a rom on it, but was still encripted.
The rom said that there is a problem with my device, but it set up just fine.
I am back on ful stock right now and it decripted, I might try it again in some time.
The only things I want from root is to be able to change system sounds, to add haptic feedback which I already did and tweak it so it works faster.
If I could change the sounds without root and without event sound that would be awesome and would let me stay on stock.
Dragos597 said:
Did that already, that is how I flashed a rom on it, but was still encripted.
The rom said that there is a problem with my device, but it set up just fine.
I am back on ful stock right now and it decripted, I might try it again in some time.
The only things I want from root is to be able to change system sounds, to add haptic feedback which I already did and tweak it so it works faster.
If I could change the sounds without root and without event sound that would be awesome and would let me stay on stock.
Click to expand...
Click to collapse
Good thing you got it decrypted back again, i have had kind of the same issue with internal storage decreasing drastically multiple times, as far as i understood it happens when i install patched AP with magisk then install multidisabler and reboot it without formatting the whole device, maybe try that when your root next time to get past the internal storage issue. Note that mine was in android 9 and device storage was not encrypted unlike yours.
And as a suggestion, if there's someone near you who can help you with actually rooting your device with magisk rather than TWRP it will be much easier.
Regards
SuizShaw said:
Good thing you got it decrypted back again, i have had kind of the same issue with internal storage decreasing drastically multiple times, as far as i understood it happens when i install patched AP with magisk then install multidisabler and reboot it without formatting the whole device, maybe try that when your root next time to get past the internal storage issue. Note that mine was in android 9 and device storage was not encrypted unlike yours.
And as a suggestion, if there's someone near you who can help you with actually rooting your device with magisk rather than TWRP it will be much easier.
Regards
Click to expand...
Click to collapse
I've got the patched image for AP from a friend, also patched TWRP, but it did that after flashing auto disabler and wiping everything, so I still don't get it.
Anyway, it is back for now and I will have to see if it breaks next time I install twrp on it.