Hi,
I have quite a serious problem with my phone.
I used stable CM11 as my ROM lately, worked nice, seemed to be ok. Now, if I want to boot my phone, it suddenly crashes as soon as I want to enter unlock code. "Funny" thing is, performing a full backup via TWRP didn't help.
So I decided to wipe everything (even sdcard) and do everything from scratch, including flashing boot.img. After flashing the ROM zip, it's still the same.
After that, I flashed boot.img from AOSP 5.1 Unstable, installed this new, different ROM (which I had successfully tested on my device before) and STILL THE SAME?!
What's going on here? It sounds a bit like defective hardware, but I never experienced a crash when I was in Recovery mode, so that's quite unplausible.
My last idea is to flash stock ftf. Perhaps this will help...
Related
Hi,
I recently bought an HTC Amaze. I have it rooted, bootloader unlocked. Unfortunately, its a SEA (unbranded) version. I tried S-Off so many times but failed. So, I decided to give CM10 and AOKP a try, as I had heard that they don't require S-Off to work on any set.
Firstly, I tried CM10 with TWRP. It didn't work. It was because TWRP doesn't have Smart Flash. So, I switched to 4EXT. It worked. CM10 started, showed me its beauty. Then, suddenly, restarted. And kept restarting. I restored to stock GB ROM. Then, I tried its older builds. Same thing happened. Some people said, kernel could be the issue. So, I decided to try AOKP. Same thing happened. It showed me some screens; select language, lock screen etc. And then restarted. I also tried Dark Glass 0.4, with Mk4 kernel. Same issue happened.
The steps I followed flashing the ROMs are as follows:
For CM10 and AOKP:
1. Wipe data/factory reset
2. Wipe cache/dalvik
3. Format system
For Dark Glass 0.4:
1. Format all partitions except SD
I have been facing this issue. Please help...
Found my answer...
magnum_2007 said:
Hi,
I recently bought an HTC Amaze. I have it rooted, bootloader unlocked. Unfortunately, its a SEA (unbranded) version. I tried S-Off so many times but failed. So, I decided to give CM10 and AOKP a try, as I had heard that they don't require S-Off to work on any set.
Firstly, I tried CM10 with TWRP. It didn't work. It was because TWRP doesn't have Smart Flash. So, I switched to 4EXT. It worked. CM10 started, showed me its beauty. Then, suddenly, restarted. And kept restarting. I restored to stock GB ROM. Then, I tried its older builds. Same thing happened. Some people said, kernel could be the issue. So, I decided to try AOKP. Same thing happened. It showed me some screens; select language, lock screen etc. And then restarted. I also tried Dark Glass 0.4, with Mk4 kernel. Same issue happened.
The steps I followed flashing the ROMs are as follows:
For CM10 and AOKP:
1. Wipe data/factory reset
2. Wipe cache/dalvik
3. Format system
For Dark Glass 0.4:
1. Format all partitions except SD
I have been facing this issue. Please help...
Click to expand...
Click to collapse
Sorry to disturb, I found my answer. To have a ROM based on firmware higher than GB, I need to have that firmware. And to upgrade firmware, I need S-Off. Thanks.
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
iJaviXR said:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
Click to expand...
Click to collapse
Check my POCO F1 Ultimate Collection & Guides. Try to Clean Install Pixel Experience for example, according my guide (u need to format data also). Let me know how it goes.
Tried Android 10 and 11 Pixel Experience, tried with stock and NG Kernels. Still stays forever in the first load of the SO.
Just got the properties file from XiaomiADBFastbootTools. Maybe someone can see something wrong on it.