This is as little long, but I wanted to be as thorough as possible. I have loaded custom ROMs successfully in the past and I beileve I followed all the directions in the FAQs. Nevertheless, I could have missed something.. so here you go.
I installed the cyanogen7 RC2 release today. I installed it on a freshly wiped phone. I updated the incredible to the latest official update from verizon, rooted it with Unrevoked3 and then did a nandroid backup.
I rebooted, opened recovery and wiped the cache and then the phone. I installed the rom update-cm-7.0.0-RC2-Inc-signed via SD card. It said it was successful. After I restarted, the phone worked.
Next, I went into the rom manager and downloaded gapps. it asked me to reboot I said yet but declined to backup prior (as I already had the fresh verizon backup). It said it installed successfully.
Upon rebooting I hit the cyanogen load screen which cycles ~4 times.. After that the "welcome to adr6300" screen pops up where it tells you to click the droid in the middle of the screen. The screen is almost unresponsive. If I can get it to click, i advance to the next screen where it becomes completely unresponsive. Regardless of where I get on the setup page, after ~3 seconds it takes me back to the cyanogen load screen and this continues in an endless loop.
I tried clearing the cache and wiping the drive in recovery and reinstalling the rom but I still get that screen (which leads me to believe its an issue with gapps??). So I went ahead and cleared the cache, dalvik cache, wipe, and then restored my original official vwz rom.
I downloaded gapps-hdpi-20101114-signed from the CM6 stick this time and put in on my sd card (root). I got the phone back into recovery mode, and cleared both cache's (realized I missed this the first time) as well as wiped the phone. The CM7RC2 rom installed successfully and once again I was able to get into the rom.
I restarted after that success, booted into recovery, and flashed the gapps-hdpi-20101114-signed.zip file. It said it was successful and I rebooted. However... the phone still will not get past the CM7RC2 screen...
Do you know what I'm missing? I've tried to be as thorough as possible. When I first boot up the CM7RC2 rom, do I need to do something else prior to installing GAPPS? Do i need to install GAPPS immediately after CM7RC2 prior to booting the phone up at all?
edit: With the fresh vwz rom install, I did install a few apps (about 10) prior to backup as well as remove about 15 bloatware apps so I wouldn't have to re download or delete them if I flash back to the regular rom (re installed beautiful widgets, astro, titanium backup, etc. Removed vm, vzwnav, etc). I didn't open or input preferences in any of them.. but could this be causing the conflict? Should I hard reset the phone, get the OTAs all over again, root etc w zero apps?
Just realized I had the wrong version of gapps and not to get the ones from the sticky under the Dinc rom section.
I got the latest (and correct one) here:
at goo-inside.me/google-apps/
Not sure how I missed this before but I now have the correct one and its working.
Thanks anyway!
Hellow,
I'll start at the start.
So i have a OP3 with 3.2.2 and installed a EX kernel (latest) through twrp recovery. All fine here...
Today i wanted to install Resurrection remix (latest release as from 10/09/2016) (tried both kernel versions cm and rr)
both gave me error 7. I did a factory reset through the base OS and tried again wich was not the solution it seemed.
So i tried reinstalling the nandroid backup (cache, system, and...) i took before getting into installing the new rom.
when i rebooted after putting the backup back it hangs on de 1+ logo and powered by android sign.
wichever rom i tried installing afterwards (even sideload) didnt work 'error 7'
I dont get why he keeps giving me an error 7.
hope some of you guys can gimme a hand with this cause its my daily driver :s
greets Verdi
P.S. i am a regular follower of xda just dont post alot so forgive me if this is the wrong section. I tried to find the most apropriate one to the best of my abilities.
Hello,
I'm really new to all this android thing, but I decided to root my Samsung Galaxy A7 2017 using magisk, for which I used this guide.
After some time of enjoying some root features I decided to try a custom ROM, the first one I tried was this one, since I heard that resurrection remix is one of the most feature rich ROMs. After flashing the zip file with TWRP I booted into system, I read that the first boot after flashing a ROM usually takes up to 10 minutes, but after just 1 to 2 minutes of showing the boot animation the device restarted and sent me back to TWRP. After this I did some searching here on XDA and watched some youtube videos that claimed to solve the problem, but none of them worked for me, as they mostly just said to reinstall the ROM and wipe dalvik cache and normal cache.
Since my phone came with stock android 8.0 I thought of installing LineageOS which was only official ROM based on android 8.0 that I could find for my device, but the same thing happened, boot animation for 1-2 minutes and then it sends me to TWRP.
In both of these attempts I downloaded everything to my pc and then moved it to my phone's internal storage.
I noticed that people were donwloading the files direcly from the phone itself, so I did that with LineageOS and after tring to boot it gave me the error "Encryption unsuccesful" with the option to reset my phone, I search in google about this problem but I'm doubtful of what to do now.
I would apreciate if someone told me what this error is, what could be the cause of it and how to fix it, and most important of all why won't my phone boot into a custom ROM and how can I get it to do so.
Thanks in advance!
I'm trying to get my phone set up as a backup cause i dont have much faith in my replacement one anymore(very unstable Redmi 9s running jailbroken stock rom). I recently updated it and got a weird boot issue the next day... Everything worked as i was updating and i even hard the UI set up to how i like... but the next day it wouldnt boot past the Zuk powered by android screen. I figured i'd just reflash it again, only to get a vendor error. I then flashed a factory2vendor_z2_plus file, which allowed me to install all my stuff without errors... And it looked like it worked perfectly(lineage-17.1-20200924-nightly-z2_plus-signed, Magisk, and open_gapps-arm64-10.0-micro-20200926 all went in without any errors). I also took the opportunity to update TWRP to 3.4.0(before it was 3.1.1-0) I wiped the dalvik and cache and rebooted.
Upon reboot tho, i dont go into android.... But i dont get stuck on the Zuk powered by android screen either... Instead it sends me to this fastboot page(none of the options, btw, will boot into android).
I'm guessing there's some really minor thing i need to change to fix this, since its just not being pointed to the right file to load up. Can anyone help me out with some pointers? Its all the more frustrating, cause again, yesterday everything was working perfectly fine without having done anything beyond installing the newest nightly lineage build.
Brand new device. Flashed custom OS (Arrow OS and google pixel)- no sound at all. No Youtube sounds, no call sounds, no media sounds, even Bluetooth, even with headphones. Phone are silent absolutely.
Please help.
Thanks in advance, guys!
Dude ask that in the arrow OS Apollo Pro discussion group. They are developers for the Roms and can solve the problem better. However they will require you to clean flash the rom and also the logcat file for your device bug. Hope you know how to get that.
If u still got that issue try things in my topic. maby some of it will help u it is similar case to mine dont think it is arrow os problem because it happened on many xiaomi devices and different updates eaven stock ones - everything is related to update and restarting after it. dunno what cause it yet but there is problem with audio driver.
No sound issue can u help?
Hello Im xda forum user sience many years but on this account im new (lost my old one). I remember flashing pda's, nokias and other ancient hardware :), not an expert but quite experienced user. I had some break with flashing, tempering with...
forum.xda-developers.com
Delete Dalvik/Art Cache with booting (no flash) a no oficial twrp by geoanto555, and the issue will be fixed https://xiaomi.eu/community/threads...redmi-k30s-ultra-thorough-step-by-step.61742/ (here is the link and the steps for boot a custom recovery)
I deleted all except Cust and OTG, but maybe only with Dalvik Cache will be fine. (I had the same problem but not now)
Sorry for my english
Hi All,
Did we find any solution on that matter?
Thanks in advance
The problem has to do with not doing a clean installation, completely clean, surely, when I finally unlocked the phone and installed Lineage, the sound on the phone didn't work, I tried other roms like Pixel Experience and it didn't work either, until I decided to go back to Miui and looking for Xiaomi.EU I came across the geoanto twrp, which will no longer be available now, but any twrp up to the task will do and I deleted absolutely everything except the cust and the problem was solved when I installed Lineage again .
Puruixa said:
The problem has to do with not doing a clean installation, completely clean, surely, when I finally unlocked the phone and installed Lineage, the sound on the phone didn't work, I tried other roms like Pixel Experience and it didn't work either, until I decided to go back to Miui and looking for Xiaomi.EU I came across the geoanto twrp, which will no longer be available now, but any twrp up to the task will do and I deleted absolutely everything except the cust and the problem was solved when I installed Lineage again .
Click to expand...
Click to collapse
Thanks for that, I will try it soon, by the way I've sent you a PM asking you if you can provide more details with links if its possible?
Anyway, thanks for your support on that, I will try it and let you know.
Thanks again
same problem here. this sucks..
Putting the device in a frezzer then reboot makes at least audio work, but mic still broken.
Puruixa said:
The problem has to do with not doing a clean installation, completely clean, surely, when I finally unlocked the phone and installed Lineage, the sound on the phone didn't work, I tried other roms like Pixel Experience and it didn't work either, until I decided to go back to Miui and looking for Xiaomi.EU I came across the geoanto twrp, which will no longer be available now, but any twrp up to the task will do and I deleted absolutely everything except the cust and the problem was solved when I installed Lineage again .
Click to expand...
Click to collapse
Hi! I read your post in xda that you solved your Mi10t pro no sound problem.
If you don't mind can please tell steps to do it?
I used oficial twrp by geoanto555, format data, then wiped everything except cust and otg, then reboot into bootloader.
At bootloader, boot into twrp again, installed rom, then wiped cache and dalvik, reboot into recovery.
At recovery, wipe data, then reboot.
Still no sound at all. When checking our ringtones and choosing any sounds to play them, it shows "error"...
Phone completely no sound, can't listen music, can't hear calls etc...
Thanks