Related
I'm curious if anyone else waits a bit before rooting. Just in case the phone breaks early on and needs to be sent back.
I'm thinking maybe wait 1-2 months?
Am I paranoid, or does everyone else do this too?
.jond said:
I'm curious if anyone else waits a bit before rooting. Just in case the phone breaks early on and needs to be sent back.
I'm thinking maybe wait 1-2 months?
Am I paranoid, or does everyone else do this too?
Click to expand...
Click to collapse
Personally I don't worry about that. I DO wait to give myself time to familiarize myself with how the phone functions and such before rooting so that I know when there is a problem, rather than second guessing.
It is also hard to tell if a Rom/kernel is running better when you have no base line to compare it to.
I rooted my phone almost immediately. I don't like using custom ROMs but I do like using apps and tweaks that require root.
Sent from my Nexus 5 using xda app-developers app
1-2 months??? I didn't even make it 1-2 hours. My phone was unlocked and rooted within 30 minutes of delivery.
I unlocked, installed TWRP, and rooted within 20 minutes of UPS delivering it.
I used to root and start flashing almost immediately. But as the years have passed and I've become more reliant on my phone for work and such, I've started pulling back a bit. I've reached a point where I just get too frustrated with even the slightest bugs so now I immediately unlock the bootloader (to prevent having to do a full factory restore later) and just use the phone as is until a fully stable ROM comes around that I feel comfortable flashing without losing any functionality at all.
This time around I'll probably stay stock with Nova Launcher (once the new 4.4 version is finalized) for another couple months. Time will tell though, I suppose.
.jond said:
I'm curious if anyone else waits a bit before rooting. Just in case the phone breaks early on and needs to be sent back.
I'm thinking maybe wait 1-2 months?
Am I paranoid, or does everyone else do this too?
Click to expand...
Click to collapse
Seeing as I have a Nexus device, with factory images provided directly from Google that will return my phone completely back to stock (except lock the bootloader), I usually don't hesitate to root or flash custom ROMs. The only reasons I haven't unlocked my bootloader yet is because CWM isn't completely stable yet (I don't like TWRP for some reason), and because my brother is debating on a Nexus 5 for his new phone, and I wanted to show him complete stock because he won't be a tinkerer. He'll be using the unmodded, unrooted bare stock image.
I rooted it out of the box yesterday.
Waiting myself. Want to get a feel for this device as is. Maybe later I will root/flash. But for now I am happy as is. No rush.
The important thing is you learn about the phone and how to root it and potential issues before you do it. I'm still waiting for my phone but the first thing I'm going to do is put a custom recovery on and make a nandroid. Then I'll root it as I have apps I like to use that require root. I'm not worried about warranty issues as it's pretty straight forward to put the factory image back on it and relock it.
Also, remember that when you unlock it you'll lose all your data and apps. And you'll need to unlock it to root it.
I booted, took the ota, unlocked the bootloader, installed TWRP and Super SU as soon as the phone was in my grimy hands.
Rooted immediately after taking out of the box .. no point waiting...
I unlocked and rooted before activating. Not really planning on flashing any ROMs, but just wanted it done in case I needed to tweak cpu to increase battery life.
Just until you familiarize with your new device.
Just successfully rooting won't affect the end results when using the stock Rom. Everything should still work the same way but with more options for the user.
I jut waited until next day, but took time to play some games, make calls/texts, web browsing and tested all features. There I learned the battery life, Net speed and stock performance. Everything was the way should be Firmware/Hardware wise:good:. Then, unlocked/rooted/ & flashed its first Rom
and here we are!
I didn't even boot it. I powered it on in download mode, fastboot oem unlocked, flashed twrp and rooted. Then booted for the first time. I only rooted for tibu and adaway. Now just waiting on aokp.
I waited 4 days only and mainly because we have no stable recoveries yet. Twrp is a joke while cwm is not official yet.
caribouxda said:
I waited 4 days only and mainly because we have no stable recoveries yet. Twrp is a joke while cwm is not official yet.
Click to expand...
Click to collapse
I'd say just the opposite, but then I like twrp
You can unroot, so....
I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed
Ok, I've been here on XDA for almost a year and until now I haven't had a problem I couldn't handle.
My Galaxy S6 (5.0.2) has been rooted since October 2015, it was May when I decided to Unroot and restore as a normal phone (I use Snapchat quite often and can't be used on a rooted phone). So July 9th, I decided that it was time for me to Root my phone again, and I did. I booted into TWRP and I'm sure everyone knows how long it takes to boot it into Recovery and back into normal mode, so I went deeper and tried switching where the USB is routed (or whatever). I switched it from (Guessing the name) NXT24 to USB-OTG (Which I've used to copy files to and from my laptop to the TWRP Boot which were mainly backups and ZIP Files.
Anyway, I've tried flashing 5.0.2, 5.1.1, and 6.0.2. I've pretty much exhausted all possible fixes and I need help. I've switched to the Moto G4 and Motorola is just... not good.. anyway, I would really appreciate any and all help you provide, thank you!
SiPhone1997 said:
Ok, I've been here on XDA for almost a year and until now I haven't had a problem I couldn't handle.
My Galaxy S6 (5.0.2) has been rooted since October 2015, it was May when I decided to Unroot and restore as a normal phone (I use Snapchat quite often and can't be used on a rooted phone). So July 9th, I decided that it was time for me to Root my phone again, and I did. I booted into TWRP and I'm sure everyone knows how long it takes to boot it into Recovery and back into normal mode, so I went deeper and tried switching where the USB is routed (or whatever). I switched it from (Guessing the name) NXT24 to USB-OTG (Which I've used to copy files to and from my laptop to the TWRP Boot which were mainly backups and ZIP Files.
Anyway, I've tried flashing 5.0.2, 5.1.1, and 6.0.2. I've pretty much exhausted all possible fixes and I need help. I've switched to the Moto G4 and Motorola is just... not good.. anyway, I would really appreciate any and all help you provide, thank you!
Click to expand...
Click to collapse
Stumbled upon this searching another thingy. How are You flashing the ROMs? Used Odin in fastboot with Stock ROM to start over?
Hello people of XDA!
I know that this thread may be repetitive, but I unfortunately didn't find any help in all threads regarding GSII's NAND r/w problem.
So in short, I will explain what happened to this device
I bought this GSII brand new as my 1st flagship device, and I am kind of sentimentally connected to it, if not I would've thrown it in trash a long time ago.
So here is the thing
I had stock firmware on this device (4.1.2 JB) , and after some time decided to flash CM 11 on it when it came out, and had it on my phone for 4-5 weeks but I instantly noticed that my device was overheating with that ROM so I decided to get back on stock firmware, unfortunately thing is that i flashed android 4.0.3 ICS (Movistar Mexico) then my device got bricked (I had a really bad knowledge back then about roms and things that I SHOULD and SHOULDN'Tdo), anyway I tried fixing the mess I made by flashing my original android 4.1.2 JB rom (Telenor Serbia) hoping that will solve my bricked device, but unsuccessfully. Then I tried flashing again standardly for maybe 4-5 times with no success and decided to explore more functions that odin provides, so I checked NAND erase all last time I flashed and I guess made a huge mistake, but still I couldn't boot my device, I tried hard resetting it (I lost my power button while replacing the screen of my phone, so I couldn't boot into recovery to check if device is soft bricked or really hard bricked, but download mode works just fine). Still I tried, I flashed custom kernels hoping they would fix this brick but nothing happened, I would really like to get this thing working again, I had no success at finding a good mainboard to replace the old one, and doing it in official repair shops and non-official ones costs more than the phone itself. Sorry for asking the same old question I guess but I would be really thankful if I could get this working again!
I've only had this phone for a few weeks, bought new from Target. It is a US BLN-L24. It originally was running Marshmallow but I updated it to Nougat via the official updater (BLN-L24C567B360).
The first time I got this issue was when I rooted the stock ROM with Magisk. I later installed Apps2SD Pro (for linking apps to 2nd partition on SD card). It mounted this partition, I rebooted, the device then asks for a PIN# which I didnt have and never set. Afterwards I rebooted to @OldDroid's TWRP, it couldnt mount data partition, some error about not being able to find the crypto footer. I then used the dload method to rollback to MM, then updated to Nougat again, and rerooted, this time with systemless SuperSU instead..
Then eventually everything went fine for awhile, but it happened again. So I decided to try a custom Nougat ROM. I went with Resurrection Remix 7.1.2. And then.....it happened again. This time I had rooted with Magisk. I tried yet again, but with SuperSU. And yet again with Phh's Superuser.
I've also tried AOKP, AOSPA, LineageOS, OctN, all Nougat, the issue returns with all of them.
So, no matter what root solution I use, the encryption issue eventually returns. Magisk, SuperSU, and Phh are all supposed to disable data partition encryption. But it seems they aren't.
What I've tried so far:
1. 3 different root solutions, same results
2. Formatting data and wiping all partitions in TWRP immediately before installing a ROM zip, which is supposed to remove the encryption
3. A custom kernel (CycloX)
4. Formatting my MicroSD, as exFAT, every time I check it for errors in Windows 10 corruption is found and repaired, but it always returns. I had initially thought that the encryption might be related to the SD
It has happened numerous times, on different ROMs including stock, and MM/Nougat, and with different root solutions. I know when it happens, I get stuck on the boot logo forever. TWRP reports that data can't be mounted. At one point my phone randomly rebooted into eRecovery and I was shown a message stating that data partition was corrupted. Sometimes it happens as little as 15 mins after booting into a freshly installed ROM, sometimes it takes a few days, but it always comes back no matter what. So far several dozen times.
I'm at a loss as to what is the cause. It could be a hardware defect, a firmware defect/bug, or something I'm doing wrong/missing. So I really have to ask if others are experiencing this too, and what you did to resolve it, I'm sure I'm not the only one. Please provided detailed steps. This is driving me crazy. I bought the 6X to replace my Samsung Note 4 which recently died after 3 years of loyal service. I'm liking this phone alot, it's very powerful, but this is killing me.
If anyone can help then I would greatly appreciate it. If I can't get this resolved then I'll just sell the phone on Craigslist after returning it to stock.
Thanks!
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
AnonVendetta said:
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
Click to expand...
Click to collapse
Actually I think you are the only one with this issue. Flashing Magisk alone will remove auto-encryption. But then you already flashed custom roms.
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
AnonVendetta said:
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
Click to expand...
Click to collapse
Hello, can you help me? I have the same model BLN-L24C567B360. I got this phone today and updated today as well right out of the box. My problem is that I installed TWRP 3.1.1.0 Berlin version for this phone and it doesn't work at all. Now I have my phone working ROM but with no recovery option. Can you give me a link with the files I need? I was thinking on putting back the original recovery.img file back but unfortunately I never thought on doing a backup of it. I read on the top that you have all original stock files. Thanks
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
AnonVendetta said:
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
Click to expand...
Click to collapse
You can stop crying now, I won't be using your "topic" anymore. I just replied to you asking for files that you already have.
And BTW, I don't need them anymore but thanks anyways.
Yoooooo did Huawei do anything yet?
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
AnonVendetta said:
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
Click to expand...
Click to collapse
Sorry to hear you had such a bad experience with them. Pretty crappy that they used a lame excuse like water damage to deny responsibility in fixing the issue.
I agree with you, I will never buy Huawei again. The phone itself is great but the audio is so so bad Im trying to sell mine at a loss as well but no ones calling so Im tinkering with it again. I would be absolutely livid if I spent the money on one of the flagship Huawei phones. Oh well live and learn I guess, at least the 5T comes out sometime next month.