Stuck @ google logo - Samsung Galaxy Nexus

Hi, I'm stucked at google logo.
I was on 4.2.2 xenon hd, I went back to 4.1.2 to try miui, and now that I wanted to go to paranoid 3.5 i'm stucked.
What I did wrong?
I got folders in 0/ and outside , is that the problem?
tnx in advance
edit: ok flashed only rom and gapps, and booted . I downloaded the latest lean kernel.. why would it be stucked at boot when i flashed it ? :v

AkaGrey said:
Hi, I'm stucked at google logo.
I was on 4.2.2 xenon hd, I went back to 4.1.2 to try miui, and now that I wanted to go to paranoid 3.5 i'm stucked.
What I did wrong?
I got folders in 0/ and outside , is that the problem?
tnx in advance
edit: ok flashed only rom and gapps, and booted . I downloaded the latest lean kernel.. why would it be stucked at boot when i flashed it ? :v
Click to expand...
Click to collapse
Did it boot with the rom and gapps only?
If it did, then the only explanation that comes to my mind is that the Leankernel download was bad.

sarkar1990 said:
Did it boot with the rom and gapps only?
If it did, then the only explanation that comes to my mind is that the Leankernel download was bad.
Click to expand...
Click to collapse
Flashing the rom , gapps and kernel all togheter it didn't boot, then with only the rom and gapps yes.
After it booted, I went into the recovery again, and flashed the kernel and then it booted ...

Strange, I was able to replicate the same issue. I am currently running Carbon / Air Kernel 560. If i flash ANY Lean Kernel, it get's stuck at the Google screen. Pretty sure I'll have to Wipe everything and start clean again.

Because you should should always flash the ROM and GAPPS first, then boot, reboot into recovery, wipe Dalvik cache, THEN flash the kernel .
Sent from my Galaxy Nexus using Tapatalk 2

Factory reset.......

Related

Having issues maybe recovery related

Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
md1008 said:
Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
first more info will get u more accurate advice ie.... build date of aokp.... last nightly is messed up use stable for best results. also the method of which u applyed these roms would be nice htc s-on is a pain so it requires a little diffrent prosses thin on other phones and diffrent strokes for diffrent roms
for wifi u have to reflash boot.img....
for FC and bootloops factory reset, wipe cache partition, wipe dalvik cache....
download latest nightly and follow this------>
1. download rom and gapps,transfer them to root of SD card
2. extract boot.img(the kernel) from ROM zip,or whichever is compatible and place it in fastboot folder
3. go into bootloader, FIRST flash the boot.img in fastboot.
4. go into recovery, then FULL WIPE-factory reset, erase cache and dalvik cache.
5. then flash the ROM.
6. boot into the rom.then again enter into recovery and then flash gapps.
do the above steps in the same order all over again....it should work...:fingers-crossed:
If I am not mistaking I used the latest stable build of aokp, and I flashed both roms through recovery using both CWM and TWRP and also flashed kernel using fastboot. Although I reflashed TWRP and flashed AOKP and all seems to be right in the world. right now in at the set up screen so far no freeze or boot loop and wifi is working. Consider this problem solved
And yeah S-on sucks!

[Q] Custom Rom not installed properly

Hello,
Today i rooted my Galaxy grand with CWM using Odin and intalled SuperSu through recovery mode. Then i entered recovery mode again to install Xperia Z rom for Galaxy Grand , which i had placed in my external sd card. When i installed it using all the steps(Wipe data,cache etc etc) and reeboted my device, it got stuck on the boot screen with Samsung Galaxy grand logo running in loop for several time. Atlast i removed my battery and using the download mode again installed the 4.2.2 update with Odin.
Can u please tell me what went wrong while installing the rom.
nish1991 said:
Hello,
Today i rooted my Galaxy grand with CWM using Odin and intalled SuperSu through recovery mode. Then i entered recovery mode again to install Xperia Z rom for Galaxy Grand , which i had placed in my external sd card. When i installed it using all the steps(Wipe data,cache etc etc) and reeboted my device, it got stuck on the boot screen with Samsung Galaxy grand logo running in loop for several time. Atlast i removed my battery and using the download mode again installed the 4.2.2 update with Odin.
Can u please tell me what went wrong while installing the rom.
Click to expand...
Click to collapse
Maybe your source file is corrupted? In CWM, after installing the ROM, does it appears installation success or update success any similar message?
And suggest you wipe data & cache after installing the ROM, not before. Wipe Dalvik cache too.
soralz said:
Maybe your source file is corrupted? In CWM, after installing the ROM, does it appears installation success or update success any similar message?
And suggest you wipe data & cache after installing the ROM, not before. Wipe Dalvik cache too.
Click to expand...
Click to collapse
Source file? Are you speaking about the rom file I downloaded ?
Yes after installing the rom there is message Updated Successfully in CWM.
But i wiped the data and cache before installing the rom and dalvik cache after installing the rom..
Please help....can you give me detailed steps for installing rom.
If you are coming from stock rom after it shows installation complete again wipe all DATA frm cwm and reboot
Sent from my GT-I9505 using Tapatalk 2
Sulaimanshariff said:
If you are coming from stock rom after it shows installation complete again wipe all DATA frm cwm and reboot
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Hey no worries...
I just installed another Xperia Z rom...and everything is grt nw....
Same Problem it is stucked now on that sceen and I too got the massage that it is install successfully... I cant install any other ROM as I want to use dual sim and most of the ROM are not compatible with dual SIM.... PLEASE HELP
soralz said:
Maybe your source file is corrupted? In CWM, after installing the ROM, does it appears installation success or update success any similar message?
And suggest you wipe data & cache after installing the ROM, not before. Wipe Dalvik cache too.
Click to expand...
Click to collapse
nish1991 said:
Hello,
Today i rooted my Galaxy grand with CWM using Odin and intalled SuperSu through recovery mode. Then i entered recovery mode again to install Xperia Z rom for Galaxy Grand , which i had placed in my external sd card. When i installed it using all the steps(Wipe data,cache etc etc) and reeboted my device, it got stuck on the boot screen with Samsung Galaxy grand logo running in loop for several time. Atlast i removed my battery and using the download mode again installed the 4.2.2 update with Odin.
Can u please tell me what went wrong while installing the rom.
Click to expand...
Click to collapse
"Atlast i removed my battery and using the download mode again installed the 4.2.2 update with Odin."
can you tell me how you did?? i am a newbie
stuck in boot loop
soralz said:
Maybe your source file is corrupted? In CWM, after installing the ROM, does it appears installation success or update success any similar message?
And suggest you wipe data & cache after installing the ROM, not before. Wipe Dalvik cache too.
Click to expand...
Click to collapse
yes everything went right but after i click reboot than i try to start samsung galaxy grand i9082 logo appears there it blink 4 5 times then i remove my battery and try to start again but now it is not even opening not cwm recovery menu and not going to the odin download mod also
ODIN mode is also not opening without usb cavle mean opening when plugged into charging.
please help me ,-_-,
, ,
Xperia Z Rom GT-I9082
Which CWM i recovery i use please tell me
i'm using CWM 6.0.2 recovery but when try to install i stuck in installing screen and then automatically back in recovery mode.
MD5 not found
yogeshp007 said:
Which CWM i recovery i use please tell me
i'm using CWM 6.0.2 recovery but when try to install i stuck in installing screen and then automatically back in recovery mode.
MD5 not found
Click to expand...
Click to collapse
Ik think that the CWM version is to old.
Also if you want to go to lollipop later then you can't do this with CWM 6.0.2.
Download a new CWM with an minimum version 6.4.5 or TWRP 2.8.6.0.
Never tried to install the older version roms with TWRP but with CWM I was able to install all.
Installing Rom
Sir i want to install xperia z rom please help me!!
tell me in details please

[Q] need help!

i got a very strange problem in my htc one x
everything was working fine and suddenly my phone was getting very hot (sometimes battery get hot sometimes cpu)
i was on slimkat rom
i thought re flashing will help as wiping dalvik cache didnt help.
i reflashed the same rom as a new one but the phone was still getting hot and was shutting down
i tried different kernel but same problem
then i tried aicp rom on slimkat's boot.img and without gapps it was working fine but without radio
then i thought it might be the gapps that is causing the problem but as soon as i flashed boot.img of aicp and booted up the same shutting down problem came
so i downgraded my recovery and tried to install viperx rom but in aroma as soon as installation goes ahead after formatting the phone reboots itself without completing installation.
so the conclusion is it is working fine with boot.img of non supported rom(as radio stays off)
so please someone help me what should i do ??????
spark2331995 said:
i got a very strange problem in my htc one x
everything was working fine and suddenly my phone was getting very hot (sometimes battery get hot sometimes cpu)
i was on slimkat rom
i thought re flashing will help as wiping dalvik cache didnt help.
i reflashed the same rom as a new one but the phone was still getting hot and was shutting down
i tried different kernel but same problem
then i tried aicp rom on slimkat's boot.img and without gapps it was working fine but without radio
then i thought it might be the gapps that is causing the problem but as soon as i flashed boot.img of aicp and booted up the same shutting down problem came
so i downgraded my recovery and tried to install viperx rom but in aroma as soon as installation goes ahead after formatting the phone reboots itself without completing installation.
so the conclusion is it is working fine with boot.img of non supported rom(as radio stays off)
so please someone help me what should i do ??????
Click to expand...
Click to collapse
Wipe everything in recovery except sd card and when you install viperx choice without wipe and don't forget to flash the boot.img from viperx rom
Thant said:
Wipe everything in recovery except sd card and when you install viperx choice without wipe and don't forget to flash the boot.img from viperx rom
Click to expand...
Click to collapse
i have philz recovery ...
i do clean to install new rom
wipe data factory reset
wipe cache
wipe dalvik cache
and by wipe everythingdo you to wipe the things under mounts and storage?
rca,rfs,devlog,data,boot???
i installed slimkat latest version with the boot.img provided in it and booted it up without flashing gapps its working fine but as soon as i install gapps and boot it up , after the optimizing app popup it shows shutting down
i have tried 2 gapps slimkat latest gapps and pico modular pa gapps
spark2331995 said:
i have philz recovery ...
i do clean to install new rom
wipe data factory reset
wipe cache
wipe dalvik cache
and by wipe everythingdo you to wipe the things under mounts and storage?
rca,rfs,devlog,data,boot???
i installed slimkat latest version with the boot.img provided in it and booted it up without flashing gapps its working fine but as soon as i install gapps and boot it up , after the optimizing app popup it shows shutting down
i have tried 2 gapps slimkat latest gapps and pico modular pa gapps
Click to expand...
Click to collapse
i downgraded my recovery to philz v5
successfully installed viperx
but it stays on htc boot screen(htc quietly brilliant screen) and before even starts it goes black(switch off).
update-
i did wipe data/factory reset and rebooted the phone it eventually started but for 2-3 seconds at the one time setup screen and again it showed htc screen and got powered off
spark2331995 said:
i downgraded my recovery to philz v5
successfully installed viperx
but it stays on htc boot screen(htc quietly brilliant screen) and before even starts it goes black(switch off).
update-
i did wipe data/factory reset and rebooted the phone it eventually started but for 2-3 seconds at the one time setup screen and again it showed htc screen and got powered off
Click to expand...
Click to collapse
Deleted
spark2331995 said:
i downgraded my recovery to philz v5
successfully installed viperx
but it stays on htc boot screen(htc quietly brilliant screen) and before even starts it goes black(switch off).
update-
i did wipe data/factory reset and rebooted the phone it eventually started but for 2-3 seconds at the one time setup screen and again it showed htc screen and got powered off
Click to expand...
Click to collapse
Try with phone connected to outlet charger and see if boot maybe faulty battery
khairulez said:
Flash boot.img via fastboot.
Click to expand...
Click to collapse
i have done that
Thant said:
Try with phone connected to outlet charger and see if boot maybe faulty battery
Click to expand...
Click to collapse
i had a backup of viperx 4.1.1 from previous month i restored it and rebooted the device first try had same problem
in second reboot with device connected to charger it booted up but wifi was not turning on and battery temp was around 37 c and cpu temp was 65 c which came down in some time to 45-47.
i have also tried that but no use and also phone works fine without gapps installed on aicp or slimkat rom
i have tried 2 gapps both not helping
i think maybe something in boot sector got corrupted?
i guess the problem exist when gapps is installed and wifi is on as i got to get the device on in only 2 conditons when gapps was not installed and wifi on and when wifi off and gapps installed
spark2331995 said:
i have done that
i have also tried that but no use and also phone works fine without gapps installed on aicp or slimkat rom
i have tried 2 gapps both not helping
i think maybe something in boot sector got corrupted?
Click to expand...
Click to collapse
On viperX rom you don't have gapps and you have this problem, or you make something wrong.
1. Flash the boot.img from rom archive
2. Install the rom via recovery TWRP 2.7.1 and after this install the gapps for the rom
3. reboot device
Wich SlimKat you try and with wich gapps post a link here
ARE YOUR bootloader IS UNLOCKED????
Thant said:
On viperX rom you don't have gapps and you have this problem, or you make something wrong.
1. Flash the boot.img from rom archive
2. Install the rom via recovery TWRP 2.7.1 and after this install the gapps for the rom
3. reboot device
Wich SlimKat you try and with wich gapps post a link here
ARE YOUR bootloader IS UNLOCKED????
Click to expand...
Click to collapse
yes bootloader is unlocked and i am using latest slimkat v8.0.4 from teemo and also i have tried v7.6 but same problem
and i have used slimkat latest mini gappsand pa pico modular gapps(24 mb)
spark2331995 said:
yes bootloader is unlocked and i am using latest slimkat v8.0.4 from teemo and also i have tried v7.6 but same problem
and i have used slimkat latest mini gappsand pa pico modular gapps(24 mb)
Click to expand...
Click to collapse
Now download this SLIMKAT 7.9 and this GAPPS and format system and data and dalvik and cache
First you must flash boot.img from rom archive second restart go in recovery install the rom and then gapps restart and report
Thant said:
Now download this SLIMKAT 7.9 and this GAPPS and format system and data and dalvik and cache
First you must flash boot.img from rom archive second restart go in recovery install the rom and then gapps restart and report
Click to expand...
Click to collapse
same problem no luck :'(
spark2331995 said:
same problem no luck :'(
Click to expand...
Click to collapse
And when you flash SlimKat and gapps are your recovery is TWRP.2.7.1 or you use Philz 5
Thant said:
And when you flash SlimKat and gapps are your recovery is TWRP.2.7.1 or you use Philz 5
Click to expand...
Click to collapse
philz 6
spark2331995 said:
philz 6
Click to expand...
Click to collapse
OK now we will try something else
OK now to be clear if you dont install gapps SlimKat work perfect but if you install gapps craches. Now please try install ARHD or Maximus take the boot.img from Maximus,zip paste it in your fastboot folder flash it then go to recovery and flash maximus.zip then restart the phone and report.
And please flash philz 5.15.9 when you flashing the MaximusHD
Don't install anythig else
i got a new data about my problem
i somehow managed to run slimkat with gapps and found out that at the time of boot and for 5 min the battery temperature is above 65c but it comes down to 45-50c and when connected to a charger it goes more down to 27-35c
i take it that is same in all roms for me so it may be that some service is spiking the battery temperature high at boot as without gapps the phone works just fine?
spark2331995 said:
i got a new data about my problem
i somehow managed to run slimkat with gapps and found out that at the time of boot and for 5 min the battery temperature is above 65c but it comes down to 45-50c and when connected to a charger it goes more down to 27-35c
i take it that is same in all roms for me so it may be that some service is spiking the battery temperature high at boot as without gapps the phone works just fine?
Click to expand...
Click to collapse
This is normal when you the phone boot to be hot for CPU and battery

[Q] Canvas A1 never-ending Bootloop.

Hi guys. Recently my Canvas A1 (Android One) got stuck in bootloop. In order to fix it, I flashed it with the stock ROM provided after unlocking bootloader.
However, even after doing that, on reboot bootloop came back. It got stuck on the animation screen after the Micromax logo and restarted again, and this goes on and on.
So, I flashed it with Wormhole ROM after that. But still, it got stuck at splash screen.
I have tried all this along with wiping dalvik cache, system cache etc.
I have CWM installed on the phone.
I tried to flash it once more with stock ROM but it still got stuck as before. Please help! What should I do?
why you flashed it? you should have claim the warranty.
skd1993 said:
Hi guys. Recently my Canvas A1 (Android One) got stuck in bootloop. In order to fix it, I flashed it with the stock ROM provided after unlocking bootloader.
However, even after doing that, on reboot bootloop came back. It got stuck on the animation screen after the Micromax logo and restarted again, and this goes on and on.
So, I flashed it with Wormhole ROM after that. But still, it got stuck at splash screen.
I have tried all this along with wiping dalvik cache, system cache etc.
I have CWM installed on the phone.
I tried to flash it once more with stock ROM but it still got stuck as before. Please help! What should I do?
Click to expand...
Click to collapse
Remove battery, sims and mmc
Wait atleast 1-2 minutes
Put all back
Now go to recovery and wipe all
Install your stable rom zip
Reboot.
It seems that your phone is bricked. I think that you are under warranty and you should go to service centre. You can also flash a custom ROM
skd1993 said:
Hi guys. Recently my Canvas A1 (Android One) got stuck in bootloop. In order to fix it, I flashed it with the stock ROM provided after unlocking bootloader.
However, even after doing that, on reboot bootloop came back. It got stuck on the animation screen after the Micromax logo and restarted again, and this goes on and on.
So, I flashed it with Wormhole ROM after that. But still, it got stuck at splash screen.
I have tried all this along with wiping dalvik cache, system cache etc.
I have CWM installed on the phone.
I tried to flash it once more with stock ROM but it still got stuck as before. Please help! What should I do?
Click to expand...
Click to collapse
Sir, before flashing any ROM wipe all data and dalvik cache
Try this this may help you:thumbup:
how bro
Mohitash said:
Remove battery, sims and mmc
Wait atleast 1-2 minutes
Put all back
Now go to recovery and wipe all
Install your stable rom zip
Reboot.
Click to expand...
Click to collapse
flash your phone with sp flash tool work well
Sushant Rohan said:
Sir, before flashing any ROM wipe all data and dalvik cache
Try this this may help you:thumbup:
Click to expand...
Click to collapse
my android one (micromax) stuck on boot animations .i cant go to boot selections......what to do ..os is marshmallow
android one stuck in boot loop.
hi,
my android one had received OTA update on 1 may. after that once due to low batt it got switched off automatically and since then it is not booting up. i tried charging it full and also tried to flash it using sp tools. but nothing happens once i click the download button. the mobile dosent detect with its battery removed also. i even tried factory reset but it didn't work.
pl help.
I have flashed custom Rom But
skd1993 said:
Hi guys. Recently my Canvas A1 (Android One) got stuck in bootloop. In order to fix it, I flashed it with the stock ROM provided after unlocking bootloader.
However, even after doing that, on reboot bootloop came back. It got stuck on the animation screen after the Micromax logo and restarted again, and this goes on and on.
So, I flashed it with Wormhole ROM after that. But still, it got stuck at splash screen.
I have tried all this along with wiping dalvik cache, system cache etc.
I have CWM installed on the phone.
I tried to flash it once more with stock ROM but it still got stuck as before. Please help! What should I do?
Click to expand...
Click to collapse
I have flashed official 6.0 after bootloop but no service(emergency call) after that.
I have also tried to install CM13 but the problem is still there
my phones warranty is over now.
please help me .
Sushant Rohan said:
Sir, before flashing any ROM wipe all data and dalvik cache
Try this this may help you:thumbup:
Click to expand...
Click to collapse
My Karbonn Android One also got stuck in the bootloop.
Tried:
1) Wipe data/factory reset
2) Wipe cache partition
3) Mount/System
No improvements. Any suggestions please!!!!
Same here.. [Solved]
skd1993 said:
Hi guys. Recently my Canvas A1 (Android One) got stuck in bootloop. In order to fix it, I flashed it with the stock ROM provided after unlocking bootloader.
However, even after doing that, on reboot bootloop came back. It got stuck on the animation screen after the Micromax logo and restarted again, and this goes on and on.
So, I flashed it with Wormhole ROM after that. But still, it got stuck at splash screen.
I have tried all this along with wiping dalvik cache, system cache etc.
I have CWM installed on the phone.
I tried to flash it once more with stock ROM but it still got stuck as before. Please help! What should I do?
Click to expand...
Click to collapse
Hey,
Try this... Worked for my canvas a1...
1. Install Minimal ADB and fastboot (search google)..
2. Download universal sprout 4(or 8) stock rom from xda..
3. Use philz touch recovery and wipe cache in your mobile through recovery....
4. Now install your stock rom from .zip file..
5. That's it.... Reboot and your phone is back..!
Regards,
Aashif
Ashabilash said:
My Karbonn Android One also got stuck in the bootloop.
Tried:
1) Wipe data/factory reset
2) Wipe cache partition
3) Mount/System
No improvements. Any suggestions please!!!!
Click to expand...
Click to collapse
Just flash stock rom with pc or laptop and if you have custom recovery flash stable rom it will be fixed
how!?
Can someone tell me how m I going to install TWRP even my device stuck on bootloop and can't pass on it. I try the recovery method like factory data clear participation but doesn't even work. My device is firefly mobile plss tell me
markphaul13 said:
Can someone tell me how m I going to install TWRP even my device stuck on bootloop and can't pass on it. I try the recovery method like factory data clear participation but doesn't even work. My device is firefly mobile plss tell me
Click to expand...
Click to collapse
Turn off device completely, wait for 100 seconds and connect the turned off phone to the PC. Hold the Power and Volume Up button together. You will see a menu.
1) Select fastboot mode using volume buttons.
2)On your PC download adb and extract it anywhere and navigate there.
3)open command prompt in that directory and type fastboot devices.
4)you will see serial no. Of your phone if not try reconnecting phone and letting the drivers install.
5)Using Android one toolkit Flash TWRP.
6)Flash whatever new system you want and tadaa......

LineageOS-based roms won't boot - Firmware 4.1.0

I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.
do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.
Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot
Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!
AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes
indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now

Categories

Resources