whenever i flash a custom android 11 rom after upgrading toa custom android 12 rom , my phone gets stuck in bootloop. The only time it works is if I flash havoc os however white horizontal line appear if I leave my phone unattended when using havoc. any solution?
junestic said:
whenever i flash a custom android 11 rom after upgrading toa custom android 12 rom , my phone gets stuck in bootloop. The only time it works is if I flash havoc os however white horizontal line appear if I leave my phone unattended when using havoc. any solution?
Click to expand...
Click to collapse
I think it is may not help but have you tried flashing your region's stock rom?
downgrade is only possible on same bootloader level
Related
Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it
Probably your internal storage if full or something. Which ROM were you installing anyway?
rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Thnx for ideas
my problem solved
Now Installed​ lineage 7.1
Bdw how to close this Thread ?
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...
Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.
Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.
Hi,
For some reason my phone is booting to TWRP every time I try to Power On the phone or charge my phone while its turned off. I am facing this for these couple of weeks. I don't think I did any sort of change to device. It started to happen all of the sudden. The problem started on Stock TouchWiz 5.0. So I thought maybe flashing custom rom may fix it. So I tried to flash AospExtended ROM and the problem is still not gone. On top of it the phone also reboots randomly and boots to recovery. The frequency of the reboots on Stock TW was low but in Custom ROM it is frequent. I didn't tried flashing stock firmware yet for now because I don't have access to my PC yet.
Please can anyone help me with the problem. My phone is SM-G530H running on XCU1BPB1 Firmware.
Thanks
Just flash the stock rom using odin everything will be fine
tasnim_tamim said:
Hi,
For some reason my phone is booting to TWRP every time I try to Power On the phone or charge my phone while its turned off. I am facing this for these couple of weeks. I don't think I did any sort of change to device. It started to happen all of the sudden. The problem started on Stock TouchWiz 5.0. So I thought maybe flashing custom rom may fix it. So I tried to flash AospExtended ROM and the problem is still not gone. On top of it the phone also reboots randomly and boots to recovery. The frequency of the reboots on Stock TW was low but in Custom ROM it is frequent. I didn't tried flashing stock firmware yet for now because I don't have access to my PC yet.
Please can anyone help me with the problem. My phone is SM-G530H running on XCU1BPB1 Firmware.
Thanks
Click to expand...
Click to collapse
I'm facing the same problem :crying:
Sent from my fortunave3g using XDA Labs
hi
I can not upgrade to Android 5.0.2. Because After flashing screen is black.
My phone only boots with Android 4.4.4
Android 5.0.2 I've also tested 4 files. Do not boot again
I also have the same problem with installing the Custom ROM. Custom ROM is installed. But my phone will not boot. And the black screen stays there after flashing
How can I fix this problem?
please help!!!
maziar__rahmannezhad said:
hi
I can not upgrade to Android 5.0.2. Because After flashing screen is black.
My phone only boots with Android 4.4.4
Android 5.0.2 I've also tested 4 files. Do not boot again
I also have the same problem with installing the Custom ROM. Custom ROM is installed. But my phone will not boot. And the black screen stays there after flashing
How can I fix this problem?
please help!!!
Click to expand...
Click to collapse
same problem i am facing now - Did you get a solution for this ? I only have to use the stock rom
After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(
Download Mi flashtool and fastboot rom.
Here a good how to
https://in.c.mi.com/thread-714161-1-0.html
alejandr769 said:
After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(
Click to expand...
Click to collapse
As said by the other member (joke19), the best solution is to use the mi tool so as to bring the phone back to its original condition, certainly one of the partitions (probably The vendor partition or persist) (it's just a guess) but ... did you install the latest firmware available in the version of the rom that you then installed?(you said you did a clean install, which means formatting sistem data cache vendor ... And then before installing the new rom reinstalled the Appropriate firmware ...) Personally only once did I return from custom to MIUI (not MIUI stock, however, and at the time I lost the IMEI despite all the correct steps) but it was a long time ago However, these are things that can happen even when you switch from one custom to another, even if one does all the steps. Correct "formatting" from twrp is never a formatting Really clean ... only from fastboot or using the xiaomi tool you usually have a Complete formatting And I would like to underline COMPLETE because in twrp only some partitions are cleaned and this can sometimes lead to small problems
After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.