Related
I searched the internet and threads on XDA for this problem but couldn't really find one!
The problem is- My Galaxy S3 (GT-I9300) doesn't boot any AOSP/AOKP/CM ROMs! It's just the bootanimation and DONE! For hours and hours the bootanimation only! But I can flash any Sammy 4.3 / 4.4 ROMs! They boot! They work properly!
I used to change to AOSP to Sammy and vice versa so many times with no issues. One day I downloaded the UltimaAOSP Valhalla ROM and flashed it. This was the first time my S3 didn't boot. I flashed custom Kernels like boeffla on it but all in vain. It was stuck on the bootanimation. I flashed NeatROM AOSP on top of it, which worked properly. Then it was with the fusion sp ROM that it didn't boot again. Again I flashed NeatROM AOSP on top of it (it's my favorite ROM), which I used just to copy some other ROM from my PC to my phone.
Now, I'm on my Stock ROM which came with my phone since so long! I'm shocked to see now NO AOSP ROMs are booting! I've used C-ROM, NeatROM, Resurrection Remix and SOKP Milestone. I have the ROMs' ZIP files and also a Nandroid Backup which I made when I changed to other ROMs. Not the ZIP files neither the Nandroid Backups are helping! ZIP files get flashed succesfully (I wipe the data & cache & dalvik-cache every time) and the Nandroid Backups get restored successfully! But always the phone gets stuck on the bootanimation!
I always moved to AOSP from Sammy (never Sammy to Sammy) but this time I gave it a shot.
Result : All the Samsung ROMs are flashing, working properly, even the Nandroid restores boot. I flashed my newly downloaded FlashingDroid Sammy 4.4 ROM which also works.
BUT I CAN'T GET THE AOSP ROMs onto my phone!
My thought (it could be wrong) : Is it to do something with the data in a partition other than system, data, and cache? Some partition which has stored files needed to boot Sammy ROMs and is preventing AOSP ROMs to start?
HELP!
:crying:
MORE UPDATED INFO ON POST #6
::ROBLEM SOLVED:::
Wipe system, data, cache and preload partitions manually in mounts and storage in CWM Recovery.
DONE! AOSP Working!
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
boomboomer said:
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
Click to expand...
Click to collapse
Have lots of data on my internal memory! Still I deleted lots of unwanted files. Any other way to wipe the hidden preload partition other than using Philz Recovery? I remember I flashed Philz after which I couldn't restore any of my Nandroid Backups backed up with CWM Recovery..
Sent from my GT-I9300 using XDA Premium 4 mobile app
In cwm mounts and storage wipe preload
Press thanx if i helped you in anyway...
Update - Got More Info
Update : Just noticed that when it's the bootanimation on the screen after flashing an AOSP ROM, pressing any of the buttons on the phone vibrates the phone vigorously 2 times.. why??
Also, I want to ask about the connection between a kernel and a bootanimation without starting a new thread 'cause I think it's the solution to my problem here.. The data which I probably suspect that prevents AOSP ROMs from booting is some different bootanimation file? I mean when I'm on a Sammy ROM, I started to flash different bootanimations after flashing some CWM Custom Bootanimation ZIP file. The bootanimation changes on all Kernels on Sammy ROMs -except 1 that is the boeffla kernel. The strange thing is that the first custom bootanimation I had flashed (after flashing Boeffla's Sammy Kernel) when I switched to Sammy from my last AOSP was the hTC One Bootanimation which worked fine (the bootanimation successfully changed). After that, it never changed. My phone always booted up showing the hTC One Bootanimation no matter how many times I flashed another bootanimation ZIP or the CWM ZIPs which enable/disable Custom bootanimations. But! When I changed to any other kernel (the stock that came with the ROM/GoogyMax 2/AGNi), the bootanimation was the last one flashed by me before changing the kernel. I could change the bootanimations successfuly every time after that. Now, I flashed Android Revolution HD ROM and was on Stock Kernel. As soon as I changed to boeffla kernel (without flashing any other ZIP), the bootanimation changed! (automatically!) And it was again the same old hTC One Bootanimation.
Can someone please tell me WHERE is this bootanimation data and the data that prevents AOSP ROMs to boot is stored? Certainly not in the data or system or cache partition...
Update 2 : Just figured out where the automatic htc bootanimation magic happened. The hTC bootanimation.zip file was found in data/local . However, I always knew the bootanimation directory as system/media.. So now, is it safe for me to delete all files in data/local 'cause it seems it is the problem for AOSP ROMs?
Sent from my GT-I9300 using XDA Premium 4 mobile app
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
jimbobpro87 said:
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
Click to expand...
Click to collapse
I'm not trying to go back to Jelly Bean! I'm flashing AOSP based ROMs of KitKat 4.4.2 which don't boot!
SOLVED!
Yayy!
I guess I got a solution!
Wiped system, data, cache and preload partitions manually in mounts and storage in my CWM Recovery.
DONE! AOSP Working!
:victory:
THANKS TO ALL WHO HELPED! :angel:
Thank you for your post.
I am having the same problem, phone not booting past boot animations using aosp ROMs. Haven't tried Sammy ROM to test the theory yet but will try soon.
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
alaska_ryder said:
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
Click to expand...
Click to collapse
Strange- it happened that day but not now. Even I get an error formatting preload. But! I guess the problem is the system partition! There IS an option to format /system in mounts and storage option on the first screen.
Sent from my GT-I9300 using XDA Premium 4 mobile app
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Eden532 said:
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Click to expand...
Click to collapse
Have you flashed the rom then factory reset?
Beamed in by telepathy.
shivadow said:
Have you flashed the rom then factory reset?
Beamed in by telepathy.
Click to expand...
Click to collapse
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Eden532 said:
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Click to expand...
Click to collapse
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
MigoMujahid said:
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
Click to expand...
Click to collapse
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Eden532 said:
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Click to expand...
Click to collapse
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
MigoMujahid said:
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
Click to expand...
Click to collapse
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
shivadow said:
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did flash the custom rom twice but still no good.
(And also i checked the IMEI via a custom Sammy rom)
Eden532 said:
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
Click to expand...
Click to collapse
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
MigoMujahid said:
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
Click to expand...
Click to collapse
Thank you so much for sending the link, Its really difficult to download from sammobile.com . Ill check it right away and report. Thanks.
I try to install Lineage 14.1 but I can't because It says wrong bootloader, and that my bootloader is unknown. I installed lollipop by flashing the system.img image and the boot.img image because I had no ROM installed because my internal storage and SD card got corrupt or something. Can anyone help me by supplying a Lineage 14.1 backup or a LineageOS system.img and boot.img file? Thanks in advance...
Wrong bootloader . . .?????
I think the issue you are having is what I was having, and that is that you are not COMPLETELY wiping the previous operating system. Use TWRP's advanced features to make sure you do a complete wipe.
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Billc47 said:
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Click to expand...
Click to collapse
I was getting the same error the user above was until I used TWRP's advanced wipe and got rid of everything. Of course make sure you do a backup of whatever you currently have working just in case, but once I did an advance wipe I was able to installed Cyanogen. I however still cannot get Lineage 14.1 to work, it simply gets into an install loop. But since your question was about the boot loader, once I did the complete wipe the error message you are referring to went away for me.
thank you for your reply
hi i am from india and huge fan of huawei i got this phone from usa(mt2-l03) i rooted the phone using some one click root tool and tried to flash twrp which ended in saying recovery image failed,please update to the authorized images.however as there was was root i changed the dpi(think 420) now the phone screen is blank(only in the system ui not the boot image or vendor image(huawei)) i am having the imei and s/n at the battery but i dont have the product id so is there any way i can get the product id and unlock the bootloader of my phone or is there any way to repair my phone
In the general area, in the stickies there are many options you might try. This one https://forum.xda-developers.com/as...to-fix-soft-bricked-phone-using-twrp-t2886630. Seems like it might be the way out for you but I'm not a dev or an expert, just someone who's screwed up his phone alot and found fixes in that section
Sent from my MT2L03 using XDA-Developers Legacy app
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Same here...i flash all nougat rom and got bootloop..now i stay in mm only...:C
Reflash newest stock image, than hack the emmc bootloader of it and try again
reemar said:
Reflash newest stock image, than hack the emmc bootloader of it and try again
Click to expand...
Click to collapse
So you mean to flash the latest stock ROM, won't it remove TWRP and lock the bootloader? And how to "hack" the emmc bootloader? Sorry, I'm a newbie
Just wait for at least 15 minutes after flashing
DdroidTHEGAMER said:
Just wait for at least 15 minutes after flashing
Click to expand...
Click to collapse
What do you mean, wait in TWRP for 15 minutes or when booting up the OS? As I said, I waited for 30+ minutes while it booted up.
Try installing ROM without flashing the firmware
Minions007 said:
Try installing ROM without flashing the firmware
Click to expand...
Click to collapse
That was the first thing I did (I didn't know a firmware was needed so I only flashed the RR ROM). Same bootloop
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
SpeRator said:
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
Click to expand...
Click to collapse
Did it, same result. Wiped everything, copied zips to internal storage, flashed from there and boom, bootloop
Hmm strange. You could test a good modified rom of rr.
Try this Rom:
https://www.androidfilehost.com/?fid=673791459329049490
And these Gapps:
https://www.androidfilehost.com/?fid=673791459329049438
If it all not Work, you have to flash actually official Rom to restore all with edl.
I have the exact same problem. Cant flash any ROM without getting bootloop. The bootloop though isnt a standard one, i think. I get the logo of the ROM and the phone starts to give Tiny vibrations in regular periods of time. I also left the phone for a long time hoping it'll eventualy boot. No luck. Tried flashing stock ROM with miflashtool and edl. Didnt help as well. I wonder if it could be the fault of any previous roms i had installed.
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
SpeRator said:
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
Click to expand...
Click to collapse
Changed to writemode.. default options selected in the mounts screen.
unable to flash any Nougat roms- stuck in boot animation.
is it because the bootloader was unlocked unofficially via lollipop fastboot ROM 7.1.8??
All right, got it working.
I flashed the latest official MIUI ROM with the official flashing tool with the option "clear all". Then I had to open the bootloader again, then flash TWRP, then flash RR, and it works! Looks like something was wrong with the previous installation, the clearing everything did the job.
Were your bootloader unlocked officially?
aldhi said:
Were your bootloader unlocked officially?
Click to expand...
Click to collapse
Unlocked Unofficially via this method https://www.youtube.com/watch?v=2FmaCdnLi58
tonyrulez said:
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Click to expand...
Click to collapse
Backup all of your data from internal storage and flash latest fastboot developer ROM and setup it. This will fix all issues regarding ROMs, zips, bootloops and firmware and any other. After that flash latest ZCX recovery as RedWolf recovery causes problems for flashing ROMs and zips as per my experiance. Then simply flash RR and gapps and boot and wait for 15 minutes and till then don't restart device.
Hello, guys,
i unlocked my Bootloader properly, i flashed a ROM, i flashed all ROMs but the phone function is gone, no Audio Sound, no FP working!!! I dont know what to do, could someone teach me how to get my phone working again?
Did you flash xiaomi.eu pie rom before flashing an android pie rom?
Did you follow the installation instructions in the rom post that you tried to install?
you can always go back to miui stock downloading a fastboot rom image and using miflash
Flash stock miui 10 with mi flash and after this install miui 10 based on android p.
alexlowas said:
Hello, guys,
i unlocked my Bootloader properly, i flashed a ROM, i flashed all ROMs but the phone function is gone, no Audio Sound, no FP working!!! I dont know what to do, could someone teach me how to get my phone working again?
Click to expand...
Click to collapse
I have the same problem only the custom miui roms work properly
Did you fix it?
venezolano69 said:
I have the same problem only the custom miui roms work properly
Did you fix it?
Click to expand...
Click to collapse
Try flashing the firmware over your rom https://sourceforge.net/projects/revolutionos-miui/files/9.3.7/Mi 8 Lite/ then do wipes (cache and dalvik)
SubwayChamp said:
Try flashing the firmware over your rom https://sourceforge.net/projects/revolutionos-miui/files/9.3.7/Mi 8 Lite/ then do wipes (cache and dalvik)
Click to expand...
Click to collapse
Flash it before the rom and then reboot?
venezolano69 said:
Flash it before the rom and then reboot?
Click to expand...
Click to collapse
Yes, it could be before or after. This issue would be solved by restoring vendor partition but most of user don't made a backup before flash custom roms
SubwayChamp said:
Yes, it could be before or after. This issue would be solved by restoring vendor partition but most of user don't made a backup before flash custom roms
Click to expand...
Click to collapse
I can try with the backup of vesnor partition
venezolano69 said:
I can try with the backup of vesnor partition
Click to expand...
Click to collapse
Try it before if you have it
SubwayChamp said:
Try it before if you have it
Click to expand...
Click to collapse
I have the vendor partition of miu.eu pie
venezolano69 said:
I have the vendor partition of miu.eu pie
Click to expand...
Click to collapse
Try the next if one of this doesn´t result:
- Restore the vendor partition, do wipes, reboot
- Flash the firmware linked over your rom, do wipes, reboot
- Do a clean flash again, wipe cache, dalvik, system and data (if it´s important backup it before), flash the custom rom you are using, GApps, Magisk, reboot.
Report results to help others.
SubwayChamp said:
Try the next if one of this doesn´t result:
- Restore the vendor partition, do wipes, reboot
- Flash the firmware linked over your rom, do wipes, reboot
- Do a clean flash again, wipe cache, dalvik, system and data (if it´s important backup it before), flash the custom rom you are using, GApps, Magisk, reboot.
Report results to help others.
Click to expand...
Click to collapse
All of those step?
This guy is a savior.
Thank you, @SubwayChamp
Flashing fw_platina_miui_MI8LiteGlobal_9.2.15_35fd209ab5_9.0.zip solved my problems with sound and mic!
venezolano69 said:
All of those step?
Click to expand...
Click to collapse
No, just one and it doesn´t work then try the next. An user are reporting that by flashing firmware was solved so try first this step. @Snowdine Glad it solved.
SubwayChamp said:
No, just one and it doesn´t work then try the next. An user are reporting that by flashing firmware was solved so try first this step. @Snowdine Glad it solved.
Click to expand...
Click to collapse
It works with flashing the firmware
Thanx you save me
Hi, I am facing wired situation in my mido. I reset my phone once and it said encryption interrupted. Now, the phone is in very bad condition. All rom I boot into has issues in app opening.. Apps says keep stopping.. Also I lost my imei numbers from about phone.. Sim not working.. Can you please give me solution what to do? Is it software issue or hardware? Or what can be o remedy...
Thank you.
khalakuzzaman.apon said:
Hi, I am facing wired situation in my mido. I reset my phone once and it said encryption interrupted. Now, the phone is in very bad condition. All rom I boot into has issues in app opening.. Apps says keep stopping.. Also I lost my imei numbers from about phone.. Sim not working.. Can you please give me solution what to do? Is it software issue or hardware? Or what can be o remedy...
Thank you.
Click to expand...
Click to collapse
Copy the ROM you want to use to your external SD card, also download the matching GApps.
Do a full reset of the phone. Go into Recover (most recent OrangeFox) and format DATA partition (type YES) and do a full wipe (DATA, System, Cache and Dalvik).
All your is now completely clean. Install your ROM, install GApps, restart your phone and be happy
Did, but it did not help brother..
Did, I wiped all partition. Then flashed rom. No help.. I formated all partition. Then flash. No help.. I flashed with edl mode clean all. No help.. Flashed mint miracle thunder app. No help... Now I also lost imei.. And force closing app also their...
khalakuzzaman.apon said:
Did, I wiped all partition. Then flashed rom. No help.. I formated all partition. Then flash. No help.. I flashed with edl mode clean all. No help.. Flashed mint miracle thunder app. No help... Now I also lost imei.. And force closing app also their...
Click to expand...
Click to collapse
The last option is to flash original Xiaomi ROM with EDL mode. Do that and see what's working and what not. Then we can continue
Did brother.
I already did that brother.. Problem exists.. I can share a log file..
https://del.dog/giniphorre.txt
https://del.dog/deemokasit.txt
Noter2017 said:
The last option is to flash original Xiaomi ROM with EDL mode. Do that and see what's working and what not. Then we can continue
Click to expand...
Click to collapse
This is what is says when I click summary.
Your issues were mostly caused by error in EFS partition. EFS stand for Encrypted File System, and it responsible for the modem, wifi, mobile data connection, and your IMEI. Once EFS error, your device won't be able to read IMEI nor give wifi and mobile data connections.
My advice is try to clean flashed Mido's latest official MIUI ROM (MIUI 11), which contain the right EFS for your device. Do not attempt to flash other ROM first, since that wouldn't succeed if your EFS still broken.
It is because the significance of EFS why official TWRP also offer to backup it in it's feature.