Was using an CM13 unofficial build for months... then i decided i needed SPen and Heartbeat sensor
so i was hoping to try Erobots rom ( did full wipe ) , after successfull install... got boot loop... just keeps restarting on the Note 4 Logo
so i tried reflashstock rom(s) with both odin and kies 3 , after every flash , i always get the installing system update... erasing... and then boot loops
i though i got a perma soft brick.. till i tried using Cm13 again.... and it works ??
so what's causing this ? me not being able to use TouchWiz based roms ? both stock at custom
up
Try going to Recovery via the 3-button combo. Then wipe cache and data/factory reset.
If it didn't help, flash the official stock rom via odin. Then do the wipe cache/factory reset again in Recovery after flashing the stock rom.
yup tried those... i always ended up.. installing system update... then erasing... then boot loops
I have the exact same issue, I was stupid enough to not backup my system with TWRP when I had first rooted the device, so I cant just 'restore' my backup. I would like to use another rom but cannot due to this issue.
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
try this: http://forum.xda-developers.com/note-4/help/n910c-stuck-frustrating-bootloop-t3301750
Slaid_ said:
I have the exact same issue, I was stupid enough to not backup my system with TWRP when I had first rooted the device, so I cant just 'restore' my backup. I would like to use another rom but cannot due to this issue.
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
try this: http://forum.xda-developers.com/note-4/help/n910c-stuck-frustrating-bootloop-t3301750
Click to expand...
Click to collapse
have edited my original post ,
I've had something similar when I tried CM. It uses a not so generic recovery.
Try to flash a different recover with Odin - TWRP for example.
Related
Hi,
I am unable to boot anything other than the stock 4.2.2 rom....
I have TWRP 2.7 as recovery, i can flash the bootloader the rom and the radio via the fastboot, but it will sit their for hours bootlooping on the nexus circles...
Now i treid flashin different roms all the same problem...
Any help???
Update your recovery
[email protected] said:
Hi,
I am unable to boot anything other than the stock 4.2.2 rom....
I have TWRP 2.7 as recovery, i can flash the bootloader the rom and the radio via the fastboot, but it will sit their for hours bootlooping on the nexus circles...
Now i treid flashin different roms all the same problem...
Any help???
Click to expand...
Click to collapse
flashing the factory IMG and flashing roms can not give you the same problem. those are two different activities. flashing the factory IMG is done via fastboot, while flashing roms is done via recovery. flashing roms doesn't flash the bootloader, nor radio. you boot into recovery, wipe data, pick what you want to flash, and flash it.
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
CCody said:
Update your recovery
Click to expand...
Click to collapse
na, not his recovery. im using an even older version(2.6.x.x) without issues.
simms22 said:
flashing the factory IMG and flashing roms can not give you the same problem. those are two different activities. flashing the factory IMG is done via fastboot, while flashing roms is done via recovery. flashing roms doesn't flash the bootloader, nor radio. you boot into recovery, wipe data, pick what you want to flash, and flash it.
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
na, not his recovery. im using an even older version(2.6.x.x) without issues.
Click to expand...
Click to collapse
with wipe data u mean dalvik???
I know that flashing the stock roms happens via the fastboot and flashing a custom rom needs to be done in the recovery... After flashing the custom rom (every custom rom i tried) it will bootloop forever...
Also flashing 4.3 of 4.4 will make it bootloop... Even getting the official OTA updates... makes my nexus bootloop
simms22 said:
flashing the factory IMG and flashing roms can not give you the same problem. those are two different activities. flashing the factory IMG is done via fastboot, while flashing roms is done via recovery. flashing roms doesn't flash the bootloader, nor radio. you boot into recovery, wipe data, pick what you want to flash, and flash it.
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
na, not his recovery. im using an even older version(2.6.x.x) without issues.
Click to expand...
Click to collapse
Oh, thought it has something to do with the recovery
[email protected] said:
with wipe data u mean dalvik???
I know that flashing the stock roms happens via the fastboot and flashing a custom rom needs to be done in the recovery... After flashing the custom rom (every custom rom i tried) it will bootloop forever...
Also flashing 4.3 of 4.4 will make it bootloop... Even getting the official OTA updates... makes my nexus bootloop
Click to expand...
Click to collapse
no, not dalvik. flashing a rom automatically wipes dalvik, so you dont ever have to wipe dalvik. wipe data(factory reset), then flash the custom rom. and if you get a bootloop after flashing stock, go back into recovery and wipe data(factory reset) and try booting up again.
simms22 said:
no, not dalvik. flashing a rom automatically wipes dalvik, so you dont ever have to wipe dalvik. wipe data(factory reset), then flash the custom rom. and if you get a bootloop after flashing stock, go back into recovery and wipe data(factory reset) and try booting up again.
Click to expand...
Click to collapse
I do the factory reset every time i flash... does not help either...
I am getting suspicous because the stock 4.3 and 4.4 rom bootloop also
Still not able to flash... Now i have it bootlooping again
Radio updated?
Just flash 4.2.2 stock image back... it is the only one i am able to boot, but even then i have no radio...
I am lost
Does your proximity sensor work properly in 4.2.2 (make a call and cover top of phone, does it turn black? uncover, does it light back up?)
If not that's your problem.
DrFredPhD said:
Does your proximity sensor work properly in 4.2.2 (make a call and cover top of phone, does it turn black? uncover, does it light back up?)
If not that's your problem.
Click to expand...
Click to collapse
Proximity sensor working fine... Just tested it with incoming and outgoing call...
Still unable to flash anything different than 4.2.2
anybody???
I have the same problem like You :/
Wytapatano z Galaxy Nexus PA 4.5 beta2 @DirtyVkernel
Well I flashed SuperS4 this morning. Wont ever make it past the flashing android screen right after the Samsung Galaxy S4 screen. So I go into recovery(TWRP) and it wont go past the dang TWRP logo screen.... Not good... Anyone have any advice? Phone is like a week old... TWRP worked perfectly before. I was using BeanStalk rom and decided to try out SuperS4.
I've always used the latest Philz recovery and never had a problem with it
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
Try flashing the latest Philz recovery with Odin and then reflash super s4
EliteN00b said:
Well I flashed SuperS4 this morning. Wont ever make it past the flashing android screen right after the Samsung Galaxy S4 screen. So I go into recovery(TWRP) and it wont go past the dang TWRP logo screen.... Not good... Anyone have any advice? Phone is like a week old... TWRP worked perfectly before. I was using BeanStalk rom and decided to try out SuperS4.
Click to expand...
Click to collapse
churchey360 said:
I've always used the latest Philz recovery and never had a problem with it
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
Try flashing the latest Philz recovery with Odin and then reflash super s4
Click to expand...
Click to collapse
As @churchey360 says - use the latest philz.
Also, you want to reboot recovery after doing wipes and before flashing the ROM.
Your steps should look like this:
1 - do all your wipes
2 - reboot recovery
2.1 - if asked to install Superuser say yes
3 - Flash ROM
3.1 wipe cache and dalvik if you want.
4 - reboot system and let it sit for 10 minutes before you do setup. If you cannot get past the splash screen after 10 minutes you messed up somewhere. Check the md5 hash of the ROM and verify it matches. You may want to boot to recovery from after a battery pull.
Holler back and let us know.
I have never messed with the s4 but,
EliteN00b said:
Well I flashed SuperS4 this morning. Wont ever make it past the flashing android screen right after the Samsung Galaxy S4 screen. So I go into recovery(TWRP) and it wont go past the dang TWRP logo screen.... Not good... Anyone have any advice? Phone is like a week old... TWRP worked perfectly before. I was using BeanStalk rom and decided to try out SuperS4.
Click to expand...
Click to collapse
On devices with unlockable bootloaders (non odin) such as samsung devices, i think you have to flash the boot image file somehow. (no fan of odin)
but if the device contains fastboot, then flash the boot.img in the rom. if odin, download a stock tar and flash it
I faced the same problem... But i solved it by flashing cwm 6.0.4.4 recovery then wipe system, data, cache and delvik cache... Then reboot recovery then wipe again.... Then flash the rom.
It will work with you.
i'm assuming you can get the phone in download mode (hold power + down arrow) and then use odin to flash a new recovery (preferably cwm 6,0.44) then go into recovery and do another wipe/reset/etc and install the rom again.
Note Stuck in First Boot screen where it says galaxy note 3 sm-n9005
I had aryamod.
Installed xposed(which i shouldnt have).
Rebooted.
It got stuck into samsung logo.
Decided to do a rom install.
After the rom install its stuck in first boot logo. When powered on it gives a vibrate. Remain stuck at that screen. No LED blinking or anything.
Tried to wipe cache factory reset format and even tried to flash again.
::UPDATE::
Flashed SlimKat Custom Rom.
It is working now.
Afraid to Flash Stock Rom over it again, Don't wanna **** up.
Any suggestions?
Via recovery mounts and storage Format system data cache .
Boot to download mode flash stock rom via Odin .
You wanted to flash Xposed on AryaMod.
If you read the thread, many users (including me) have said to flash arter97's version 75 xposed.
Nobody got bootlop with this version
---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------
And now best option is to flash Stock via Odin (as mentioned above) and then try others.
OS is LineageOS 14 (7.1)
With latest TWR
Been using my ZE551KL normally without installing anything new for the past 10 days. Today I rebooted it hoping to fix a weak phone signal but got a bootloop.
Tried wiping dalvic and cache via TWR without luck.
Tried restoring system+boot+data from a 1 month old backup image. No dice...
Tried restoring another TWRP backup image from when I had CM on, also didn't work.
tried wiping everything [dalvic/system/data/internal/cache] and flashed a fresh Lineage ROM then gapps for a brand new system.... no luck... Same bootloop.
Still get bootlooped whenever the OS animation starts, whether it's Lineage's animation or CM's. Sometimes it bootloops before the animation, just before the animation starts.
Do you think I should restore an ASDF image from my brother's phone which is same model and OS?
If anyone got an idea on how to solve this, please let me know. I'm all ears.
Thanks
The last app you used/install might have corrupted something. Make sure you always check the permission an app uses, ESPECIALLY if you're granting it superSU permission. That's some dangerous stuffs. Two ways of unbricking:
1. Reflash your custom rom.
2. Reflash stock firmware.
---------- Post added at 05:05 PM ---------- Previous post was at 05:05 PM ----------
Let me add another way. If you backed up via TWRP, then restore it. That's another fix
Hey guys, I decided to try and install a custom ROM on my phone, but after trying a few things, my phone now won't boot into anything but TWRP. Here's exactly what I did in chronological order:
1. Flashed official TWRP
2. Tried to install Pixel Experience by *only* flashing the .zip - it was extremely buggy, laggy, and just straight-up unusable
3. Used the "format" option from within TWRP > Wipe
4. Tried installing Pixel Experience (had to use it on an external USB) - appeared to install fine but it won't boot into it, just reboots into TWRP
5. Tried Pixel Experience "Plus", crDroid, Lineage OS, and stock ROM, all had the same result as PE in step 4
6. Tried using blu_spark TWRP, same result as step 4
I have absolutely no idea what to do or how to fix this. Can somebody help me? Thanks!
kelvinhall05 said:
Hey guys, I decided to try and install a custom ROM on my phone, but after trying a few things, my phone now won't boot into anything but TWRP. Here's exactly what I did in chronological order:
1. Flashed official TWRP
2. Tried to install Pixel Experience by *only* flashing the .zip - it was extremely buggy, laggy, and just straight-up unusable
3. Used the "format" option from within TWRP > Wipe
4. Tried installing Pixel Experience (had to use it on an external USB) - appeared to install fine but it won't boot into it, just reboots into TWRP
5. Tried Pixel Experience "Plus", crDroid, Lineage OS, and stock ROM, all had the same result as PE in step 4
6. Tried using blu_spark TWRP, same result as step 4
I have absolutely no idea what to do or how to fix this. Can somebody help me? Thanks!
Click to expand...
Click to collapse
2 things.
First flash the latest FW that is needed for the custom ROM as per their thread.
Then format data and flash the ROM you need.
Use CodeowrkX Forced Encryption recovery.
Let me know if it works..
kelvinhall05 said:
Hey guys, I decided to try and install a custom ROM on my phone, but after trying a few things, my phone now won't boot into anything but TWRP. Here's exactly what I did in chronological order:
1. Flashed official TWRP
2. Tried to install Pixel Experience by *only* flashing the .zip - it was extremely buggy, laggy, and just straight-up unusable
3. Used the "format" option from within TWRP > Wipe
4. Tried installing Pixel Experience (had to use it on an external USB) - appeared to install fine but it won't boot into it, just reboots into TWRP
5. Tried Pixel Experience "Plus", crDroid, Lineage OS, and stock ROM, all had the same result as PE in step 4
6. Tried using blu_spark TWRP, same result as step 4
I have absolutely no idea what to do or how to fix this. Can somebody help me? Thanks!
Click to expand...
Click to collapse
i am also facing same issue. keeps going back to twrp recovery..
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
vdbhb59 said:
2 things.
First flash the latest FW that is needed for the custom ROM as per their thread.
Then format data and flash the ROM you need.
Use CodeowrkX Forced Encryption recovery.
Let me know if it works..
Click to expand...
Click to collapse
Hi. i tried that recovery too but it didnt work. i am also facing same issue. no matter what rom i flash , when i reboot into system it starts TWRP recovery. also i had working nandroid backup , but even after restoring it, no luck.. its my first time with oneplus , previously i used to have xiaomi rn5pro an i have never faced any flashing issue. oneplus 5 suppose to be easy while handling flashing and stuff but seems like it is too much complicated..
DeAd_PooL said:
i am also facing same issue. keeps going back to twrp recovery..
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
Hi. i tried that recovery too but it didnt work. i am also facing same issue. no matter what rom i flash , when i reboot into system it starts TWRP recovery. also i had working nandroid backup , but even after restoring it, no luck.. its my first time with oneplus , previously i used to have xiaomi rn5pro an i have never faced any flashing issue. oneplus 5 suppose to be easy while handling flashing and stuff but seems like it is too much complicated..
Click to expand...
Click to collapse
Do something. Just flash any PIE Full Stock ROM, and then work your through over to Custom ROM.
vdbhb59 said:
Do something. Just flash any PIE Full Stock ROM, and then work your through over to Custom ROM.
Click to expand...
Click to collapse
i did flash pie stock rom but no luck. same issue. and when you said full stock rom you mean this https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156143164
Right..?! i downloaded and flash this but same issue... :crying:
DeAd_PooL said:
i did flash pie stock rom but no luck. same issue. and when you said full stock rom you mean this https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156143164
Right..?! i downloaded and flash this but same issue... :crying:
Click to expand...
Click to collapse
Yes. 9.0.11 or 9.0.10
9.0.10: https://otafsg1.h2os.com/patch/amaz...ygen_23_OTA_053_all_1912311131_3aeac3fbd2.zip
9.0.11: https://otafsg1.h2os.com/patch/amaz...xygen_23_OTA_054_all_2002242016_5fa0dcac8.zip
Or else use the MSM Tool to install. After any install wait for 10 minutes before trying. Sometimes stock OOS takes 10 minutes for uptime.
vdbhb59 said:
Do something. Just flash any PIE Full Stock ROM, and then work your through over to Custom ROM.
Click to expand...
Click to collapse
vdbhb59 said:
Yes. 9.0.11 or 9.0.10
9.0.10: https://otafsg1.h2os.com/patch/amaz...ygen_23_OTA_053_all_1912311131_3aeac3fbd2.zip
9.0.11: https://otafsg1.h2os.com/patch/amaz...xygen_23_OTA_054_all_2002242016_5fa0dcac8.zip
Or else use the MSM Tool to install. After any install wait for 10 minutes before trying. Sometimes stock OOS takes 10 minutes for uptime.
Click to expand...
Click to collapse
So flashing above from TWRP worked but Package installer not working, it keeps crashing when i try to install an app.
i did try msmtool to flash stock rom , but it always gets stuck at pram preprocessing... any solution.?!
DeAd_PooL said:
So flashing above from TWRP worked but Package installer not working, it keeps crashing when i try to install an app.
i did try msmtool to flash stock rom , but it always gets stuck at pram preprocessing... any solution.?!
Click to expand...
Click to collapse
You didnt FORMAT data and reboot. Do that and then post reboot, do another format/wipe from stock recovery. You will loose data, I reiterate.
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
DeAd_PooL said:
So flashing above from TWRP worked but Package installer not working, it keeps crashing when i try to install an app.
i did try msmtool to flash stock rom , but it always gets stuck at pram preprocessing... any solution.?!
Click to expand...
Click to collapse
For the param issue, seems your driver is causing issues, or else the unbrick rom file is broken/corrupt.
vdbhb59 said:
You didnt FORMAT data and reboot. Do that and then post reboot, do another format/wipe from stock recovery. You will loose data, I reiterate.
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
For the param issue, seems your driver is causing issues, or else the unbrick rom file is broken/corrupt.
Click to expand...
Click to collapse
i formated data too as well then flashed stock rom zip, same package installer issue..
.
I tested almost all available drivers.. none seems to be working.. i checked the unbrick file integrity, its fine.