Unable to flash new rom - Xiaomi Redmi 1S

hi friends.. basically i am unable to install any new rom on my Redmi 1s, I searched almost everything but couldn't find the solution.. so i am posting it here... i will try to describe my problem below..
Back a few months i was using CM 12.1-20150603-UNOFFICIAL-armani.. then a OTA update came i installed it joyfully.. but my joys didn't last longer as a noticed that after booting my Wifi always shows "Turning WiFi On" but never got really opened. So i flashed back to old version... Then i installed Xtreme Music Mod and and the Earpeice Speaker went off... So i thought of flashing again, This time I flashed Flex OS.. was sucessful and then days later i installed xposed and got struck in bootloop due to an improper mod... due to my noobness i staraight away tried to flash flex OS again and then the install was successful but after the initial boot phone worked for like 30 seconds then freezes and reboot.. this happened again and again untill i flashed the CM 12.1-20150603-UNOFFICIAL-armani again... in middle of all this i tried using Multirom but was unsucessful....
And NOW MY PHONE WON"T ACCEPT ANY ROM OTHER THAN CM 12.1-20150603-UNOFFICIAL-armani
I tried changing recovery, gone through the Fastboot flashing and doing things a fresh
but every time i install a rom My phone either freezes on "ANDROID IS UPGRADING" or it boots completely and then freezes and reboot...
I hope someone has a solution for this.. coz m dying to use MM ..
Thanks

niimtz said:
hi friends.. basically i am unable to install any new rom on my Redmi 1s, I searched almost everything but couldn't find the solution.. so i am posting it here... i will try to describe my problem below..
Back a few months i was using CM 12.1-20150603-UNOFFICIAL-armani.. then a OTA update came i installed it joyfully.. but my joys didn't last longer as a noticed that after booting my Wifi always shows "Turning WiFi On" but never got really opened. So i flashed back to old version... Then i installed Xtreme Music Mod and and the Earpeice Speaker went off... So i thought of flashing again, This time I flashed Flex OS.. was sucessful and then days later i installed xposed and got struck in bootloop due to an improper mod... due to my noobness i staraight away tried to flash flex OS again and then the install was successful but after the initial boot phone worked for like 30 seconds then freezes and reboot.. this happened again and again untill i flashed the CM 12.1-20150603-UNOFFICIAL-armani again... in middle of all this i tried using Multirom but was unsucessful....
And NOW MY PHONE WON"T ACCEPT ANY ROM OTHER THAN CM 12.1-20150603-UNOFFICIAL-armani
I tried changing recovery, gone through the Fastboot flashing and doing things a fresh
but every time i install a rom My phone either freezes on "ANDROID IS UPGRADING" or it boots completely and then freezes and reboot...
I hope someone has a solution for this.. coz m dying to use MM ..
Thanks
Click to expand...
Click to collapse
*go to cm12.1 thread
*download and flash firmware.zip from post #3 and flash it
*wipe all in twrp(leave internal,external,usb otg)incase you want to wipe internal too,don't forget to make a backup before on pc.
*flash R31+5.1.1 gapps(i will prefer open gapps)
*wipe cache and dalvik
*reboot

Related

Miui rom - Phone keep booting itself

Hi.
Im looong time om my favorite Miui rom. I was all the time on version 4.11.13. Last few days i had updates ( like 5 times ) until 5.5.20 which i had yesterday.
Today i had few boots with no reason but after few hrs. phone keep booting all the time. After boot everything is loaded normally, i get service and then shows " settings has stopped" or something like that, few sec norma using and boot. Its not even boot just logo lg with no sound and coming back. I still can access twrp. I found one backup which was CM and problem gone. Phone works fine. Then i try download every version from here http://goo.gl/lHnRMA and still booting. Even after install the same 4.11.13
Do i have to install something else, did i forgot about something ?
What is wrong how to fix it ? I fighting all day with this and now i don't have idea whats wrong.

[Q] I need all the help i can get !! Soft-Bricked Note 2 stuck Bootloop

Ok so i will try and explain step by step what is the matter here.... Since i have been trying to fix my Note 2 since 2 weeks now and i got nowhere.
I was running 4.4.2 and i had TWRP on it but it wasnt Rooted. (Bought it like that) Had some custom Rom on it etc...
Used it for 2 months with no problems whatsoever,decided to root and went on installing AGNI Kernel for better audio (Eargasm ON). Everything worked as a dream for 4-5 days...was enjoying the crazy sound. Till one morning i woke up,received a call and i had to swap my sim cards,after i did this i had Emergency calls only on screen. BAFFLED !! Went on factory restoring the phone,still Emergency calls only on screen. JUST LIKE THAT !! All of a sudden,with no reason at all !! o.0
Anyway,after that i tried again factory restore and wipe cache and something else from TWRP i think it was a FULL DELETE or something like that,including System and all... so i can install a new fresh ROM on it (As i thought it`s the ROM). Well that didnt went well for me,as the phone got stuck into Samsung bootloop. AGAIN AND AGAIN AND AGAIN !!!
I gave up on TWRP and connected it to the laptop so i can use ODIN and flash stock ROM. Worked !! It went pass the Samsung boot,i set it up,still had the same `Emergency calls only` error,BUT THEN as soon as i unplugged my usb cable from it,BOOM !! Phone restarts itself,and gets stuck on Samsung boot. I connected the charger,works fine. Stays in menu,apps work,etc. As soon as i unplug the charger or the usb cable,it kept on restarting itself and going into Samsung Bootloop.
Went on different threads,tried a lot of ROMS and Kernels,nothing worked,so i gave up and BOUGHT A NEW BATTERY.
With the new battery,phone worked ok,no more bootloops,but still the same `Emergency calls only` issue.
Tried installing the modem fix with twrp,phone got stuck on samsung boot,tried installing nb4_N7100_Patched Modem_CWM with philz_touch_6.46.3-n7100 phone got stuck on samsung boot.
Then tried installing back the Android that Worked as a dream before (TWRP-Android Revolution HD) but this time i had the philz CWM and guess what,whatever Rom i install with philz,the same Samsung boot comes on.
Right now i tried installing Phoenix ROM,got stuck on bootloop,then cleaned the WHOLE DEVICE by a MEGA WIPE with Zoot's-Wipe-Scripts_SGS_N-II then tried installing again Phoenix Rom with philz,phone still NOPE,stuck on Samsung bootloop.
I am dead !! Please somebody give me some hope here,as i am dying.
I will put back TWRP now,and install again the only ROM that worked for me that is Android Revolution HD and stay with the bloody Emergency Calls Only on screen till somebody will be able to help me out here.... Please guys... i dont know what to do anymore,i am actually loosing my hope,it`s been 2 weeks since i am REALLY REALLY trying to get it back working....i feel i am growing white hair !!
use odin and go back to stock
HERE
there is factory firmware with pit file.
do everything as said in instruction

Strange problem

Firstly 1 month ago my phone started rebooting itself randomly and I was using s-team desire eye and I tried to upgrade to S5.2 X10.0.8u and it didn't worked phone goes into endless bootlop after that I tried to flash every rom and no one worked. And finally I tried stock rom in this thread firstly I think it worked firstly "android is upgrading" screen comes and after that first install language screen comes and it freezes for 1-2 second and bootloop again. Any help?
EYE_UL
UNLOCKED
S-ON
TWRP 3.0.0-0
I'm not sure, but your phone is s-on, and switching from MM back to LP is not good idea... maybe you should try to install stock MM rom?
Download the Lollipop RUU from the HTC's website and try it. Maybe that works...

LG G3 bricked???

Hello everyone
I am writing this post to ask for help. I think I may have bricked my LG G3, and I can't fix it :/
I was trying to wipe everything, to later install a Fulmic ROM (6.6). I wiped everything by mistake after a factory reset, and since, I can't flash any new ROM :/
I am using TWRP 3.1.0, and I can mount the device and the sd card to the computer, and move ROM files onto the SD card. However, when I go to install, and after selecting the ROM (FulmicsROM-6.6Zip), the phone crashes... It runs something and when it reaches the part where it is starting "aroma installer version ...." the loading progress bar freezes and after a few seconds it crashes, rebooting into the LG Logo and stays stuck in there (if I didn't remove the battery I would assume it would stay there for ever, but without removing the battery, it stays in that LG Logo screen without much happening until I run out of patience after several minutes).
I tried install the previous ROM (Fullmics ROM 5.0, which was my previous ROM), but the same thing happens.
Has this happened to anyone? Does anyone has any idea how to fix this? It would be very appreciated if anyone could spare some moments to try and help me sort out this...
Ok, so another update on the situation (but not a good one )
I downloaded another ROM to test (CloudyG3), but unfortunately, the same situation occurs. The phone starts running the ROM after install and soon after that, once it is getting ready to start the AROMA installer, it crashes, and reboots onto the LG Life's Good logo and stays stuck in there
Has this happened ever to anyone? Any idea on how to sort this?

UNABLE TO BOOT ANY ROM AFTER LATEST GApps INSTALLATION

Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.
what ZUI version you flashed with QFIL ?
AndroidUser5 said:
Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.
Click to expand...
Click to collapse
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????
arielcasari said:
what ZUI version you flashed with QFIL ?
Click to expand...
Click to collapse
zui 2.5 st which is meant for indian users.
Naresh Rawat said:
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????
Click to expand...
Click to collapse
android 9.0.
what could be the problem... what do you think?
AndroidUser5 said:
android 9.0.
what could be the problem... what do you think?
Click to expand...
Click to collapse
I m at job so i reply late. No offense please ???
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY???
Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
i have already tried using twrp 3.2, but no luck. I will try flame gapps and will let you know. i will try this coming saturday.
Dhanyavad.
Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
I again flashed the Stock ZUI 2.5. ST ROM using QFIL. But before doing this I had moved the SIM Card to another fone, so this fone was without any connection. This time the fone booted up successfully. Then I reflashed the Carbon ROM mentioned before and flashed Flame GApps Basic edition as suggested by you. This time the fone booted up successfully. But as soon as I connected the fone to internet, it downloaded something from Google Play Services in the background and again it started the same problem.
SO BASICALLY WHEN IT DOWNLOADS SOMETHING FROM GOOGLE IN BACKGROUND, IT STARTS THE REBOOTING NONSENSE.
I searched the internet for this and some articles on the internet suggested that "Google Dialer" component is causing reboot. Those articles suggested that if the "Google Dialer" is not set as the default dialer, it reboots. BUT HOW TO SET IT AS DEFAULT, WHEN IT STARTS REBOOTING IMMEDIATELY AND IT DOES NOT GIVE ENOUGH TIME?
EVEN THE EARLIER GApps 9.0 stock package that I flashed had warned to set the "Google Dialer" as default, but upon boot up it kept rebooting.
Even initially I started this UNLOCKING AND CUSTOM ROM FLASHING exercise after the factory ROM started rebooting after updating "Google play services".
So this seems to me an issue from Google.
Has Google done this on purpose to make people switch older phones to new ones?(Because I own a total of 3 android devices and only this device is rebooting not the other ones).
Looking forward to your reply.
Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out
Naresh Rawat said:
Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out
Click to expand...
Click to collapse
I am now not able to boot any ROM. Just keeps rebooting after the ZUK splashscreen. Hence, I again reflashed the Recovery properly, using the procedure as before. Now I am not able to boot into the recivery, too.

Categories

Resources