AFTER CLEAN INSTALLATION OF OMNI ROM 5.1 STUCK AT BOOT LOGO.
Version mni-5.1-20150417-golden
FLASHED VIA TWRP. (ZIP FILE)
I have tried several roms which address to Lollipop custom roms and Its works Perfectly.
Any way Im glad there is a developer ...
Please suggest me at least solution or instruction to root without any issue,..
CYANGANMOD 4.4 , 5.0, 5.1 WORKED PERFECTLY.
Related
Hello
I'm trying to flash PacROM 4.4 and I'm encountering a problem with "set_metadata_recursive: some changes failed".
As I searched its because of old recovery tools, but I'm already uusing CWM 4.4.1 and I cannot find out what to do.
The way I tried to flash ROM :
1. Flash stock .254 ROM
2. Install TowelRoot and CWM
3. Flash with CWM 4.4.1 and this is where error come up (kernel 207 works)
Thank you for help
edit: I managed to install VANIR ROM, and later with the same method I managed to install PAC ROM too. I used CWR not Philz.
Your problem was most likely related to your recovery, which was probably outdated.
CM based ROMs sometimes have issues with older versions of CWM.
The reason why it worked after installing Vanir is probably because of Vanir's kernel which includes a more recent version of CWM.
Anyway, glad you got it working.
Hi. I am supporting my friend. Who has the i9305, via teamviewer so i am using the Universal android toolkit, and it worked ok.
I rooted it, and installed twrp 2.6.3.0 but here i failed. I could not install kitkat or anything else. So i had to revert to cm 10.1.3 and the camera does not work also the android keyboard from gapps 20130812 did fail to work. I had to push him a swiftkey apk, to work.
Now is my question what do i have to do to install cm 11 for i9305 ???
Just a new recovery?
Because every newer file just gets aborted and doesnt install, no liquid smooth or cm11.
Thanks.
My device was on 4.3 and I flashed Philz touch recovery and did a backup and restore. Then it stuck at Samsung logo when booting.
Wiping caches, resettings, fixing permissions, ...... non of them worked.
Finally I could get it booting by flashing 4.4.4 Stock Rom using Odin 3.07
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Its working PERFECT now
also rooted using this guide
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
(In this time I did not used any recovery mentioned in the post. I just rooted it)
:good:
I was updating My samsung galaxy s advance with cm12.1_janice-070715 (CyanogenMod 12.1 [08/07/2015]) lollipop 5.1 but it doesnt work for me can i get help with that :crying: .Currently i have CyanogenMod 11 Kitkat 4.4 with CoCore-E-8.6.4-CWM kernel. i also have backed up my rom. i also have tried cm12.1_janice-070715 (CyanogenMod 12.1 [08/07/2015]) with CoCore-E-6.8-TWRP and CoCore-E-r22-beta kernel but it does work for me please help me i am new with it :crying: .
Hope it's helps
Patil.sid101 said:
I was updating My samsung galaxy s advance with cm12.1_janice-070715 (CyanogenMod 12.1 [08/07/2015]) lollipop 5.1 but it doesnt work for me can i get help with that :crying: .Currently i have CyanogenMod 11 Kitkat 4.4 with CoCore-E-8.6.4-CWM kernel. i also have backed up my rom. i also have tried cm12.1_janice-070715 (CyanogenMod 12.1 [08/07/2015]) with CoCore-E-6.8-TWRP and CoCore-E-r22-beta kernel but it does work for me please help me i am new with it :crying: .
Click to expand...
Click to collapse
First i just want to say.. i'm not good at English.. sorry . I hope you understand what i said
You don't need to flash cocore kernel after flashing cm12.1. because Cocore is only for JB..
there is a new build of cm12.1 18/07 instead 08/07, here is the link http://hastalafiesta.altervista.org/cyanogenmod-12-1-i9070-180715/
Try this method to install cm 12.1:
Make sure the boot.cpio.gz deleted from efs folder
1. flash cm11 by Epirex latest version.. it has TWRP recovery or if you have CWM v6.0.43, you can skip this step
2. reboot to recovery
3 do full wipes (cache, data, dalvik, system)
4. install rom
5. install gapps
6. reboot to system.. and You're done.
Hope it helps..
Patil.sid101 said:
I was updating My samsung galaxy s advance with cm12.1_janice-070715 (CyanogenMod 12.1 [08/07/2015]) lollipop 5.1 but it doesnt work for me can i get help with that :crying: .Currently i have CyanogenMod 11 Kitkat 4.4 with CoCore-E-8.6.4-CWM kernel. i also have backed up my rom. i also have tried cm12.1_janice-070715 (CyanogenMod 12.1 [08/07/2015]) with CoCore-E-6.8-TWRP and CoCore-E-r22-beta kernel but it does work for me please help me i am new with it :crying: .
Click to expand...
Click to collapse
I have a long procedure but it helped me a lot, first flash the stock ROM with the help of Odin and then download latest cm12.1 build and gapps from here http://hastalafiesta.altervista.org/cyanogenmod-12-1-i9070-180715/ download ukf (universal kernel flasher) from here http://forum.xda-developers.com/showthread.php?t=2137598
And download the root browser from play store. After flashing the stock ROM, root your phone, open root browser and extract the ROM somewhere, now open ukf and go where you extracted your ROM and then flash boot.img from the extracted files . after flashing go to recovery mod and you will see twrp. From there flash ROM and gapps,clear data ,cache,dalvik cache. From there restart your phone. First booting takes 15-30 mins , then you would get your 5.1.1, this method is long but effective
Hello XDA Developers!
I'm trying to install a custom rom om my i9305 bought in Denmark.
So far I have gotten the TWRP and Cyanogenmod recoveries to work, and through those I have successfully installed the two last versions of CM11 nightlies for the i9305 and the two last versions of AOSB 4.4.4 for the i9305. Yet I can't get any of them to boot past their respective logos (the phone moves nicely past the Samsung Galaxy S3 logo).
I have tried full system++ wipes, multiple Dalvik cache and cache wipes and Factory resets etc, but whatever I do my phone never gets past the CM / AOSB logo. I have waited for 20 minutes once for CM11 and once for AOSB, and 5+ minutes multiple times on both. Nothing changes.
Is there anyone out there with a 9305 that successfully installs custom ROM's that can help? Any help is greatly appreciated as I'm currently without a working phone
PS: Sorry if this is already an answered question. I googled extensively and looked at all the suggested threads before clicking "Submit" and couldn't find an answer.
Technical info:
Heimdall (latest unofficial from developer to get it working with OS X El Capitan)
Android Studio 1.4 with Platform Tools installed today
TWRP 2.8.7.0
Two latest nightlies from the official Cyanogenmod page attempted (I'm not yet allowed to post links), through TWRP as well as the recovery
Two latest versions from the AOSB website (still not allowed to post links, sorry)
MaHo_66 to the rescue
I was able to bring my phone back using the 9305N ROM posted on /galaxy-s3/development-i9305/rom-samsung-stock-4-4-4-rom-collection-t3124027
Still curious why it didn't work with the others, but at least now I have a phone again.
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
maultasche said:
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply! I also tried with the CyanogenMod Recovery, which ended the same way.
But installing a custom ROM based on stock worked, and is both way faster and pulls way less battery than the original ROM. So it all worked out in the end (until I can't resist the temptation and try to do it all again).
kamikaze702k said:
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
Click to expand...
Click to collapse
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
elysium7 said:
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
Click to expand...
Click to collapse
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
kamikaze702k said:
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
Click to expand...
Click to collapse
Nice, thanks! I'll try cwm next time then
Hi dear developers,
I just got my new Galaxy Tab S2, T813. Updated it to Nougat, firmware T813XXU2BQD1_T813OXA2BQD1_DBT. I rooted it via Chainfire's autoroot and worked perfectly fine. I installed the latest TWRP (twrp-3.1.1-1-gts210vewifi), advance wiped in twrp (like tens of times before with Galaxy S5, Galaxy S7, Redmi 4, ZUK Z2, Xiaomi Mi 5s, LG G2 etc.). I flashed Lineage 14.1 (Lineage-14.1-20170516-nightly-gts210vewifi) but when I rebooted the phone Lineage setup would not start. I went back and advance wiped again and installed an older Lineage version but again the same. I advance wiped again and installed Omni (Omni-7.1.2-20170521-gts210vewifi-weekly), but here again setup would not start. I reformatted the data in twrp and reinstalled Lineage 14.1 but again the same. So I went back and flashed via Odin3_v3.12.3 the stock firmware (for Germany) T813XXU2BQD1_T813OXA2BQD1_DBT. Odin command was pass and i though everything was fine. When the original firmware rebooted i have the same problem, the setup would not start and starting apps would crash. I entered recovery (of course stock recovery because twrp has been wiped by odin), but it says "no command".
Smart Switch would not support my device although it actually should.
I tried to flash via odin also on my second PC but again the same problem. Both PCs are running Windows 10.
I never faced something like this before. And after hours of search I found nothing. Please help me solve my problem so that i can install at least one firmware (no matter which one: Stock, Lineage, Omni etc.).
When you flashed lineageOS or omni rom, did you also flash gapps?
musashiken said:
When you flashed lineageOS or omni rom, did you also flash gapps?
Click to expand...
Click to collapse
First time flash:
+ clean advanced wipe
+ lineage
+ gapps (ARM64, Android 7.1, Pico)
+ addonSU
other times flash:
+ clean advanced wipe
+ lineage
or
+ clean advanced wipe
+ omni
I believe either flashing Chainfire Autoroot file or flashing TWRP might have caused the problem and might have deleted something or maybe i deleted something during first time wipe via twrp.
Is there a patch or aboot or something to flash via Odin prior to flashing the stock firmware to correct the problem with stock rom setup blockade?
Ok, I'm not sure what went wrong with how you did stuff but let's not use Chainfire's autoroot again. The best way to root is to do it manually.
Anyway, firstly you should be able to go back to stock samsung firmware by using Odin and flashing the full tar file. I'm not sure why that is not working for you as that's the only way to reset and fix your tablet.
Please check how to flash the full firmware via Odin again.
- ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Once you are able to load a fresh samsung firmware, then come back again. I'll see if I can guide you through the TWRP and rooting process again.
musashiken said:
ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Click to expand...
Click to collapse
Thanks fo the tip with the new version of firmware. I installed the firmware ...QD3 via Odin...
Closed per OP request