Related
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Please give more details on how you flash it.
Enviado do meu GT-I9305 utilizando o Tapatalk now Free
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!!
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
If you did all required wipes and followed the instructions did you try a different recovery? I read in the SB thread for example of people having issues with TWRP
Sent from my Nexus 7 (2013)
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Try cwm 6.0.3.6 and after you install the rom and after its set up go to recovery and factory reset
nikolav75 said:
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Click to expand...
Click to collapse
That's strange, I run Philz recovery and every 4.3 flash till now went through without issue.
Sent from my GT-I9300 using xda app-developers app
I tried all the recoveries I could find. Including Philz. Still the same.
And something else strange. I installed CWM, CWM, touch and Philz and with them I made backups. After restoration of the backup the phone freezes. I also tried to install Omega 49 and the installation goes OK, but freezes before the first start-up.
The only solution was to install manually TWRP (Odin) to restore some of my old backups. I'm beginning to think that there is something wrong with my phone. It's black if it is important.
Suggest total wipe of phone install your stock rom and test
Hi,
I just want to say I'm also having the same problem.
Started using TWRP with full wipe, same issue on 4.3 and no issues on 4.2.
On latest CWM same problem and 4.2 wont even pass the first boot on Samsung logo.
Also had to use Odin to get back on TWRP and flash a 4.2 rom again.
Anyway there is one more thing I would like to try but haven't had the chance to do so, is installing the latest modem and ril. But I'm kind skeptic about that currently because there is also some risks and my S3 is my daily driver.
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
andrewwright said:
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
Click to expand...
Click to collapse
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
bla166 said:
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
Click to expand...
Click to collapse
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
andrewwright said:
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
Click to expand...
Click to collapse
yes tried that, also used the mega wipe zip thing
Start fresh and flash stock with Odin then try again after you root and install cwm.
andrewwright said:
Start fresh and flash stock with Odin then try again after you root and install cwm.
Click to expand...
Click to collapse
Tried to go stock and flashed a 4.3 rom again that fixed my problem. =)
Thanks! :good:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
nikolav75 said:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
Click to expand...
Click to collapse
http://www.sammobile.com/
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
nikolav75 said:
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
Click to expand...
Click to collapse
Hi, I think I did the following steps to get it working on my device.
1. Flash stock with odin
2. Hard reset
3. Boot up and finish first run menus
4. Flash twrp with odin
5. Format data with twrp
6. Flash 4.3 rom
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.
Flash this recovery on the community build: http://forum.xda-developers.com/devdb/project/dl/?id=20236
And then flash the super SU file via recovery:
https://www.androidfilehost.com/?fid=24591000424944601
Let me know if this works or you need any help ?
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
From other posts in other topics it seams that it's the only twrp version that installs OOS 3.1.1
Sent from my ONE E1001
trendchanger said:
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
yes this is working
Jab_ said:
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
Click to expand...
Click to collapse
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Exodusche said:
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Click to expand...
Click to collapse
Maybe the problem is not xposed itself, maybe the issue is related to an specific module. I'll try one by one tomorrow and see what happens, thank you!
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Exodusche said:
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Click to expand...
Click to collapse
I know what the problem was. My xposed zip was correct. As I thought, it was because of a module. "Android N-fy", in recents, I just had to uncheck quick switch and change no recent image and that was it. I don't know if that module is optimized for this oos especific build, because in settings of the phone, the module does not change as much as in lollipop oos. Thank you tho
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Worked fine. Thanks OP.
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
TarushS said:
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
Click to expand...
Click to collapse
Oh lol, glad this helped
StraightEdgeKid said:
Worked fine. Thanks OP.
Click to expand...
Click to collapse
Np?
Sachin7843 said:
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Click to expand...
Click to collapse
What exactly are you looking to do?
marwan2704 said:
What exactly are you looking to do?
Click to expand...
Click to collapse
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Sachin7843 said:
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Click to expand...
Click to collapse
Make sure you have both .zip files on your phone, clean flash 3.1.1 then boot it up. If you don't like it, you can go back to 2.2.2 via stock recovery anytime. You don't even need twrp unless you want to root, install Xposed or backup.
might be a bit off-topic but...
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
error23 said:
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
Click to expand...
Click to collapse
Sounds like you forgot to wipe data. Wipe system, data, cache and just flash 3.1.1. As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Exodusche said:
As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Click to expand...
Click to collapse
It's not the place, but I can confirm that it didn't work for me. I still have the drain from time to time.
And if I don't have the Wifi drain I have a service Google Play service drain (33% for today's charge for example...).
And sometimes, I even had the wifi drain with Wifi completly switched off...
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Dileter said:
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Click to expand...
Click to collapse
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
Yes I am rooted and I tried flashing this ROM http://forum.xda-developers.com/lg-g5/development/unofficial-cyanogenmod-14-1-lg-g5-h850-t3494001
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
I also dont really care if I lose photos or anything I already got all of them saved on my pc before I even started rooting the damn thing. I do need to ask tho how do you dirty flash and Do i just flash twrp normally since im already in it or ??? As I said im rlly new to this
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
DidierMoulin said:
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
Click to expand...
Click to collapse
Okay thanks a lot I will see if Any of it helps.
Please report.
DidierMoulin said:
Please report.
Click to expand...
Click to collapse
UPDATE I fixed it I just downgraded to the 2nd to lates version of twrp and it booted normally. Now I regret flashing the pixel one XDD If you have any idea for a good custom rom tell me Thanks for the help it actually helped a lot gave me the idea to downgrade the twrp recovery.
What you mean by pixel one xxd?
DidierMoulin said:
What you mean by pixel one xxd?
Click to expand...
Click to collapse
Its a 7.1.1 android rom from the google pixel
Dileter said:
Its a 7.1.1 android rom from the google pixel
Click to expand...
Click to collapse
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Pphish20 said:
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Click to expand...
Click to collapse
What he asked [emoji32]
It's happened to me too! Like three times lol. Just use UpperCut / LG UP to flash the latest nougat rom. That will fix the issue. You will need to re-root after that. There are instructions in this forum that tell how to do all of that. Good luck
Well and don't flash a ROM which is not for your device...
Hey guys, in the last month I've noticed my device randomly bootloops after a reboot. For example, just the other day I flashed Nitrogen OS 8.1 and everything ran smoothly when suddenly after about a week I rebooted my phone and got stuck in bootloop. I formatted and reflashed the ROM again through twrp and it got fixxed but I had to format my device. Today I decided to install Havoc-OS pie and again everything installed correctly but after 2-3 restarts the phone got stuck in a bootloop again. It's the first time I've encountered this problem in 2 years of flashing ROMs. I tried flashing different firmware(8.7.3, 8.11.22) but that didn't fix the problem. Cany anyone suggest a solution?
Thanks in advance.
jimakos98 said:
Hey guys, in the last month I've noticed my device randomly bootloops after a reboot. For example, just the other day I flashed Nitrogen OS 8.1 and everything ran smoothly when suddenly after about a week I rebooted my phone and got stuck in bootloop. I formatted and reflashed the ROM again through twrp and it got fixxed but I had to format my device. Today I decided to install Havoc-OS pie and again everything installed correctly but after 2-3 restarts the phone got stuck in a bootloop again. It's the first time I've encountered this problem in 2 years of flashing ROMs. I tried flashing different firmware(8.7.3, 8.11.22) but that didn't fix the problem. Cany anyone suggest a solution?
Thanks in advance.
Click to expand...
Click to collapse
Did u do format data or wipe data reset ?
naik2902 said:
Did u do format data or wipe data reset ?
Click to expand...
Click to collapse
Did both. First formatted data(where you have to type "yes") and then did a advanced data wipe(cache, data, dalvik etc...). Also, I forgot to mention that I have officially unlocked my bootloader.
jimakos98 said:
Did both. First formatted data(where you have to type "yes") and then did a advanced data wipe(cache, data, dalvik etc...). Also, I forgot to mention that I have officially unlocked my bootloader.
Click to expand...
Click to collapse
Dont use havoc. It gets stuck on bootanimation. Bug.
But u say u getting bootloop. Dont copy data while initial setup wizard. Clean flash means redownloading all apps from playstore not restoring.
R using magisk?what modules ?
Custom kernel?
naik2902 said:
Dont use havoc. It gets stuck on bootanimation. Bug.
But u say u getting bootloop. Dont copy data while initial setup wizard. Clean flash means redownloading all apps from playstore not restoring.
R using magisk?what modules ?
Custom kernel?
Click to expand...
Click to collapse
During initial setup wizard I chose "Set up as new device", yes I'm using latest stable magisk, no modules, no custom kernel. As I said it's the first time this has happened to me.
Update: I just did an advanced wipe data again(without format data) and the phone booted successfully again at the initial setup wizard. But I can't guarantee it won't happen again(since it happened in 2 different ROMs)
jimakos98 said:
During initial setup wizard I chose "Set up as new device", yes I'm using latest stable magisk, no modules, no custom kernel. As I said it's the first time this has happened to me.
Update: I just did an advanced wipe data again(without format data) and the phone booted successfully again at the initial setup wizard. But I can't guarantee it won't happen again(since it happened in 2 different ROMs)
Click to expand...
Click to collapse
What twrp u using?
naik2902 said:
What twrp u using?
Click to expand...
Click to collapse
Official twrp-3.2.3-0. I decided to do a reboot just to test, and I got stuck in the boot animation once again. Rebooted again and for some reason it booted normally this time. It seems really random and that's driving me insane...
jimakos98 said:
Official twrp-3.2.3-0. I decided to do a reboot just to test, and I got stuck in the boot animation once again. Rebooted again and for some reason it booted normally this time. It seems really random and that's driving me insane...
Click to expand...
Click to collapse
U officially unlocked? When is the last time u flashed miui global rom ?
naik2902 said:
U officially unlocked? When is the last time u flashed miui global rom ?
Click to expand...
Click to collapse
Yes I have officially unlocked my bootloader. Last time I flashed miui ROM was about 1 week ago(flashed latest global stable for RN3).
jimakos98 said:
Yes I have officially unlocked my bootloader. Last time I flashed miui ROM was about 1 week ago(flashed latest global stable for RN3).
Click to expand...
Click to collapse
What gapps u use? Dont use stock or heavy gapps. Use nano gapps.
naik2902 said:
What gapps u use? Dont use stock or heavy gapps. Use nano gapps.
Click to expand...
Click to collapse
I've always used micro gapps and never had such problem. Just yesterday I flashed latest firmware, then ArrowOS pie and so far haven't faced the problem yet. Hopefully it got fixed.