I was using Pixel Experience Rom from the past couple of months. I wanted to check out Paranoid OS. I downloaded pa quartz 4 from the official site. I booted to my OrangeFox recovery and wiped everything. Enables MTP and copied the rom to my phone. I installed the rom zip, the logs showed, 'system image patched unconditionally' and 'vendor image patched unconditionally'.
Then everything was successful.
I rebooted my phone, and the redmi logo showed for 5 seconds and then there is only black screen!
I wiped everything again and tried, but same!!! Can anyone help me?
Nithin Sai said:
I was using Pixel Experience Rom from the past couple of months. I wanted to check out Paranoid OS. I downloaded pa quartz 4 from the official site. I booted to my OrangeFox recovery and wiped everything. Enables MTP and copied the rom to my phone. I installed the rom zip, the logs showed, 'system image patched unconditionally' and 'vendor image patched unconditionally'.
Then everything was successful.
I rebooted my phone, and the redmi logo showed for 5 seconds and then there is only black screen!
I wiped everything again and tried, but same!!! Can anyone help me?
Click to expand...
Click to collapse
You need to format /data partition
Related
My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.
Same problem
cyborgmanu said:
My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.
Click to expand...
Click to collapse
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
I also posted this is the Nexus 4 Community on Google Plus. I am going to try out what they said.
Here is the link:
https://plus.google.com/117172821556811787798/posts/dzVorg3JSUw
SOLVED!
mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
Hey I fixed it! It finally booted up.
You need to use the first Factory Image, that is, the Android 4.2.2 Jelly Bean Factory Image.
Once you have flashed the image, the phone will boot up quickly - Mine booted in around 5 minutes I guess.
Here is the link - https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
So I decided to finally flash OmniROM 9.0 on my XC, and started having some problems.
Basically, I went completely from stock (already unlocked the BL):
1. Installed TWRP 3.3.1-0
2. Rebooted to TWRP and did a factory reset (because it said so on the install guide: https://docs.omnirom.org/Installing_Omni_on_your_device)
3. Flashed OmniROM 9.0 Weekly from the SD card
4. Unsuccesfully installed Open GApps because error 64 (apparently was supposed to use the ARM64 version, even though CPU-Z stated I was on ARM)
5. Installed Magisk 19.3
6. Wiped Dalvik/ART cache and Cache partitions
7. Installed TWRP app to /system and rebooted
Now it gets stuck on the Sony logo every time I power it on.
I tried leaving it for about 15 minutes to see if it was taking so long because of a fresh install, but previously I tried installing Paranoid Android and the boot up took only a few seconds, so obviously that wasn't going to work.
I tried rebooting multiple times, wiping the cache partitions again, uninstalled the TWRP app, did another factory reset, tried fixing contexts, and it still gets stuck on the Sony logo.
At this point I'm not sure if I should just give up, because none of the ROMs I tried flashing actually worked, which includes Resurrection Remix, Paranoid Android and LineageOS, and now OmniROM as well. So far, I haven't found anyone with the same problem as me, except https://www.reddit.com/r/SonyXperia/comments/acot9y/trying_to_install_omnirom_on_my_x_compact_stuck, but that's not quite the same.
EDIT: After flashing the ODM image, the phone booted up, but it's asking me for a password. I tried typing "password", and it said the password was correct, but my data was corrupt. It offered me a factory reset, but it made no difference. This is nothing new to me, the same thing happened when I tried flashing Paranoid Android. Should I do a clean install, like, wipe Internal storage and System?
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
Looks like u skipped Step #3
z0mg.jer1Cho said:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
Looks like u skipped Step #3
Click to expand...
Click to collapse
Right, I'm an idiot. I'll try again and see if that works.
ŽeljkoLončar said:
So I decided to finally flash OmniROM 9.0 on my XC, and started having some problems.
EDIT: After flashing the ODM image, the phone booted up, but it's asking me for a password. I tried typing "password", and it said the password was correct, but my data was corrupt. It offered me a factory reset, but it made no difference. This is nothing new to me, the same thing happened when I tried flashing Paranoid Android. Should I do a clean install, like, wipe Internal storage and System?
Click to expand...
Click to collapse
Did u boot the Phone after u've installed the default firmware?
z0mg.jer1Cho said:
Did u boot the Phone after u've installed the default firmware?
Click to expand...
Click to collapse
Yes, I did. Went through the setup and everything. Ttied it multiple times, didn't make a difference.
ŽeljkoLončar said:
Yes, I did. Went through the setup and everything. Ttied it multiple times, didn't make a difference.
Click to expand...
Click to collapse
Dont boot the Phone after installing the Factory Firmware. After u've installed it, just go on with the flashing procedure as told you in OPs thread
Same issue
I have exactly the same issue. Recovery successfully flashed, did a factory reset, successfully installed Omnirom, and then I reboot into a permanent white screen with the Sony logo in the center...
After several tries I gave up and installed the stock firmware again using Sony's flash tool Emma.
Let me explain what happened step by step
My Redmi 4 Prime was in global stable latest miui 10 build
step 1 : I unlocked the boot loader using the official boot loader unlock tool, i even saw that it was unlocked.
Step 1.5 : i had downloaded Cosmic OS from official site and the beta build of MIUI 11 from an unofficial site but i made sure that they are of Redmi 4
step 2 : I installed TWRP 3.1.1 , wiped Dalvik & Cache, Then tried to install Cosmic OS (Yes i'm a fool to not backup before) It showed an error and Failed to install.
Step 3 : The mistake comes here.. Instead of just Factory reset wipe I did Internal Storage Wipe, Which I guess also that my current Rom is gone?
Then, when i boot it, it comes to the MI Unlocked boot screen, I tried rebooting by using the volume buttons to TWRP, After some time it changed back to Fastboot screen no TWRP, So I flashed TWRP again
I understood that I erased OS but then when i tried to install the beta build i downloaded earlier it failed as well. Now i tried to see what was the error and it says the build was for "santoni" and my device for . (the dot), It said my device just a dot. Then installing of Cosmic began and it said it was for Mido.
and now i am stuck here with that MI unlocked logo screen
Can anyone please help me what to do about this?
Update: My phone is ok now
I just booted into fastboot mode, downloaded mi flash tool, it showed an error of drivers not installed, I created a "log" folder in the place where the tool was there and installed the drivers and then downloaded miui 10 stock ROM of redmi 4 prime, which didn't work, so I tried putting redmi 4x ROM and it worked out without a problem. And later it booted normally
LogaN Kat said:
so I tried putting redmi 4x ROM and it worked out without a problem. And later it booted normally
Click to expand...
Click to collapse
So, apparently, your's is not a markw
Same happens with my redmi 4
Same Happens with me when i was also tried to install ROM. This happened because you didn't flash it with lazy flasher after flashing twrp.
I installed TWRP 3.1.1 using the ODIN patched version and was successful. I had let the system boot into the samsung original stock from where you see "HI" then I rebooted it into TWRP to attempt flashing and I got the /data partition couldn't be wiped. So I ran some of the other repair functions in TWRP and that appear to have fixed it. I then flashed with the latest LineageOS, Gsap, and Magistk20. When it boots up the LineageOS I'm stuck on the Lineage Splash screen. I've let it run over night and it has't changed anything. Any advice?
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
secretwolf98 said:
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
Click to expand...
Click to collapse
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
dizzymon said:
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
Click to expand...
Click to collapse
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Possible corrupted file
secretwolf98 said:
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Click to expand...
Click to collapse
So far you're quite correct I personally have three SM-T580's and they all seem to work just a little bit different. Might I suggest doing an MD5 Sumcheck? The device shouldn't be getting into a bootloop unless there was something wrong with the files, or the device.