Related
I recently rooted my phone to try and recover some deleted pictures after the phone completely crashed and wouldn't load up , I have tried to install an original firmware using Odin but I keep getting the same message about not being authorized . Am I installing the wrong files or am I not doing something thathat causes it to fail?
Where did you download the firmware? Are you sure you're using the correct version?
Are you on a G930T or a G935T?
I had the same problem on mine before, what solved it was downloading a later version of the firmware, as you can't downgrade just like that.
You can download the latest firmware from Sammbile. (I would link but I have less than 10 posts.
The T stands for T-Mobile, and the 930 is the regular, 935 is the edge. If you're not T-Mobile, you're in the wrong section, but I'm still glad to help once I obtain more information.
http://forum.xda-developers.com/showthread.php?t=2798396
apowers98 said:
Where did you download the firmware? Are you sure you're using the correct version?
Are you on a G930T or a G935T?
I had the same problem on mine before, what solved it was downloading a later version of the firmware, as you can't downgrade just like that.
You can download the latest firmware from Sammbile. (I would link but I have less than 10 posts.
The T stands for T-Mobile, and the 930 is the regular, 935 is the edge. If you're not T-Mobile, you're in the wrong section, but I'm still glad to help once I obtain more information.
Click to expand...
Click to collapse
It worked ... thanks man , I thought the sammobile website was fake because of the processence to download but it worked perfectly
xxmessxx said:
It worked ... thanks man , I thought the sammobile website was fake because of the processence to download but it worked perfectly
Click to expand...
Click to collapse
hey man i have the same problem ,
i rooted my phone like week go and was crappy but expected and lived with it ,
today punch of apps were crashing and stopped working , reboted the phone got stuck in the T-mobile welcome screen ,
decided to go back tried to get the stock rom but no luck
exact same problem now the phone goes straight to recovery mode , i can do to download mode ,
my question here which software of sammobile used ?
the last recent one ??
any help will be appreciated
my phone is Galaxy S7 With T-mobile , 930T
makemesway2007 said:
hey man i have the same problem ,
i rooted my phone like week go and was crappy but expected and lived with it ,
today punch of apps were crashing and stopped working , reboted the phone got stuck in the T-mobile welcome screen ,
decided to go back tried to get the stock rom but no luck
exact same problem now the phone goes straight to recovery mode , i can do to download mode ,
my question here which software of sammobile used ?
the last recent one ??
any help will be appreciated
my phone is Galaxy S7 With T-mobile , 930T
Click to expand...
Click to collapse
Always flash the most recent firmware becasue if you don't remember chances are you can flash an old version and run into issues, so to be safe flash the latest available firmware. Also when you first rooted did you change the CPU governor or run/install anything that could have caused the bootloop in the first place?
KillerClaw321 said:
Always flash the most recent firmware becasue if you don't remember chances are you can flash an old version and run into issues, so to be safe flash the latest available firmware. Also when you first rooted did you change the CPU governor or run/install anything that could have caused the bootloop in the first place?
Click to expand...
Click to collapse
thanks all for the help i got my phone back from the dead.
it has now the most recent stock rom. gave me so much hard time but i got it back from the dead .
and i didn't do any thing to the governor or any thing the root was running for 10 days fine and yesterday was freezing and a lot of apps stopped working restarted the phone. was stuck in the boot loop
all good stable again under the stock rom.
waiting for a stable root method to get rid of all the crap we got of T-Mobile
makemesway2007 said:
thanks all for the help i got my phone back from the dead.
it has now the most recent stock rom. gave me so much hard time but i got it back from the dead .
and i didn't do any thing to the governor or any thing the root was running for 10 days fine and yesterday was freezing and a lot of apps stopped working restarted the phone. was stuck in the boot loop
all good stable again under the stock rom.
waiting for a stable root method to get rid of all the crap we got of T-Mobile
Click to expand...
Click to collapse
You can install this awesome rom to speed things up don't worry it's a stock rom so no Knox trip. The link I will provide also has instructions. So to get started I recommend making a backup of applications with titanium backup which might require the pro so unfortunately you may have to buy a full version( if you don't want to spend money you can patch the app with lucky patcher). And I recommend checking out this rom: http://forum.xda-developers.com/tmo...stockdeodexeddebloatedrom-7-10-t3415952/page1
It is somewhat debloated and has the best speed I've seen yet... Ive been using it for a month now and I love it!
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Moley1985 said:
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Click to expand...
Click to collapse
Greetings and welcome to assist. Xiaomi phones are encrypted by default so you need to wipe your phone in fastboot to access your storage again and you also need to flash latest su zip to disable dm verity. That should clear you internal memory issues and allow you to flash a zip through twrp
Good Luck
Sawdoctor
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.
Gentlemens, I ask for your help because it's 30 hours that i'm fighting for this
Last morning I woke up and I looked at my Nord, and I saw it sluggishly slow, a bit like it has been in recent times and I was really tired of it, so I decided to clean the Nord by restoring everything in the most pristine way possible to try to make it more like it's Out-Of-The-Box, so i chose to downgrade with msm and luckily i had the wit to back up the persist.img
Making a summary, after I reset everything I reviewed how many bloatware there were in the Nord Indian version (I have that) and I wondered if you could put the global or eu rom on top of the ac2001
Reading on xda, reddit and oneplus I saw that many have done it and everything is semi all right, at most the 5g, the footprint or similar gave them a bit of problems, then I said to myself FINALLY I can get out of this Indian hell as an european (I have not a damn way to use amazon on the nord, because it does not accept that I am in Italy, so it refuses to connect, I breathed fire to make it work by removing the bloatware version, fighting with the router, adb, and the list goes on) and then I immediately threw myself into it
The global / eu version worked, but they crashdumped as soon as I updated them
I thought "Oh well" and I go back to edl and try to put the Indian back
Everything is fine with oos10, but as soon as I ******* go back to updating to oos11 it crashdumps, and i and go back to msm with edl to flash
I feel idiotic, oh well
fact that says something with sensor_process rc
device_restart_work_hdlr
and various other little things
Anyone have any idea how I could upgrade to oos11, global/eu (maybe god) or india?
Thank you in advance and forgive me for the papyrus: /
PS: relatively relevant detail, at more or less the second hour and a half at 12 o'clock in hell the pc while flashing went to bsod for unreleated issues (how lucky am i) and there it gave the first crashdump, but as soon as I reflashed in edl it it booted and then the continuous is over
I've flashed various combinations various versions and several times with edm today, so I don't really know what I can do anymore
crashdump is
err_qdi.c:1045:EF:sensor process:0x1:SNS_REG_INIT:0x9e:sns_registry
_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - ad
sp crashed.
device_restart_work_hdlr
GiuseppeT03 said:
crashdump is
err_qdi.c:1045:EF:sensor process:0x1:SNS_REG_INIT:0x9e:sns_registry
_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - ad
sp crashed.
device_restart_work_hdlr
Click to expand...
Click to collapse
The same issue for me bro. Did you solve it?
GiuseppeT03 said:
Gentlemens, I ask for your help because it's 30 hours that i'm fighting for this
Last morning I woke up and I looked at my Nord, and I saw it sluggishly slow, a bit like it has been in recent times and I was really tired of it, so I decided to clean the Nord by restoring everything in the most pristine way possible to try to make it more like it's Out-Of-The-Box, so i chose to downgrade with msm and luckily i had the wit to back up the persist.img
Making a summary, after I reset everything I reviewed how many bloatware there were in the Nord Indian version (I have that) and I wondered if you could put the global or eu rom on top of the ac2001
Reading on xda, reddit and oneplus I saw that many have done it and everything is semi all right, at most the 5g, the footprint or similar gave them a bit of problems, then I said to myself FINALLY I can get out of this Indian hell as an european (I have not a damn way to use amazon on the nord, because it does not accept that I am in Italy, so it refuses to connect, I breathed fire to make it work by removing the bloatware version, fighting with the router, adb, and the list goes on) and then I immediately threw myself into it
The global / eu version worked, but they crashdumped as soon as I updated them
I thought "Oh well" and I go back to edl and try to put the Indian back
Everything is fine with oos10, but as soon as I ******* go back to updating to oos11 it crashdumps, and i and go back to msm with edl to flash
I feel idiotic, oh well
fact that says something with sensor_process rc
device_restart_work_hdlr
and various other little things
Anyone have any idea how I could upgrade to oos11, global/eu (maybe god) or india?
Thank you in advance and forgive me for the papyrus: /
PS: relatively relevant detail, at more or less the second hour and a half at 12 o'clock in hell the pc while flashing went to bsod for unreleated issues (how lucky am i) and there it gave the first crashdump, but as soon as I reflashed in edl it it booted and then the continuous is over
I've flashed various combinations various versions and several times with edm today, so I don't really know what I can do anymore
Click to expand...
Click to collapse
Bro, please help me. How did you solve the issue?
ajaygrylls said:
Bro, please help me. How did you solve the issue?
Click to expand...
Click to collapse
Hello, I was wondering, do you have the solution to the problem ?