Just switched from an older sultan rom, to nightlies. It is still booting. So far it's been about 20 minutes, and its still booting. What should I do?
It takes about 2 mins max to go to optimization screen. Normally under 1 minute
what should I do? Im about to update to twrp 3.0.2.0
My file was corrupted before, should have checked the md5
Yea sure do that. Then reflash the R, maybe the firmware didn't get flashed - an issue with old recoveries. That prevents bootup
Related
When I flash merely anything, my tablet gets stuck on the Samsung boot logo (I have waited, and waited, and waited, until the battery dies). Sometimes even installing ClockWorkMod Recovery (official) will do this. But I managed to get the latest official CWM flashed. But I can't get ANY other rom to work. Even roms I have successfully flashed before.
Note: If it flashes it gets stuck at the Samsung boot logo. But I have also had it not flash sometimes too, giving me error code 7 in CWM which is an authentication/permission/certificate problem.
I am going to try right now using Odin to flash to stock, and work from there, maybe it will completely clean out any crap in the memory.
My tablet is the P3113 model.
Ok! So after flashing stock rom, then cleaning all the cache stuff, then attempting to install CM it fails with CWM Error code 7. And when I just reboot system, it gets stuck at the boot logo. Damn, I get stuck there without even flashing!!
Well, I may have figured it out..... ummm i guess *cough! cough!* I somehow changed kernels *cough! cough!* dang, my allergies! Hahaha, anyways, I flashed a kernel compatible with stock rom and cm10.1 and it has gotten past the flash of cm10.1 and seems to be booting up right now.
Hi all,
I need the pros here. It's NOT the regular wipe/clean/factoryreset bla bla issue.
received OPO from china with colorOS. Having the strangest behavior ever! I just can't install cyanogenmod 44S.
First I'll describe what I did:
unlock bootloader + TWRP with root + installed 44S using that comes prerooted from here: http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551
device stuck on boot (powered by android msg)
wipe dalvik/cache didn't help.
wiped again ((format dalvik cache data system) and installed using fastboot official 44s from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
eventually after almost having a heart attack and trying all the permutation of wiping/installing official/unofficial cyanogem 44S - I thought installing an older version.
I can'ts emphasize how many times and effort I put into installing 44S.
I then wiped everything again (format dalvik cache data system), rebooted to recovery and installed 25s official.
It's working!
now I try to update but OTA doesn't find anything. tried reverting to cyanogenmod recovey also but that didn't help.
so I thought installing the zips one by one (the OTA ones) but that doesn't work because I get error executing updater binary in zip and something with apache.xml
In addition, I hate the fact I don't have native OTA...
Please help me upgrade to 44s and if possible - restore OTA functionality. I have this strange feeling that I destoryed something in the device internally or something. I don't see a reason why 44S won't work on my device after having full wipe....
I love you all please help!!! Thanks!!!!
p.s - One time I did succeed booting to 44S but when I reset the device (after factory reset) It was stuck again in boot screen.
Exactly what happens when you flash the 44S fastboot images? Can you please copy/paste the text from the command prompt here?
Transmitted via Bacon
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
ron.r said:
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Click to expand...
Click to collapse
Yes it does, that's the boot partition.
Transmitted via Bacon
ek69 said:
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
i'm 20 minutes since installing. still boot screen.
I suspect it's something to do with either Color OS that came with my device handles file differently and left some buggy stuff that cyanogemnod can't handle OR cyanogenmod changed the ROM in 44s to raise somekind of a flag for china OPO (however with 25 I still can't use OTA or manual OTA zip)
It really sucks...I don't know what else to do.
Is there a special cleaning methodology I can use? (except format system/data/cache/dalvik from TWRP) to make the device as clean as possible before installing using fastboot?
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
ek69 said:
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
ron.r said:
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
Click to expand...
Click to collapse
Go back to Stock Color Os and try this. Might just work.
https://forums.oneplus.net/threads/oneplus-one-coloros-to-cm11s-the-right-way.77361/
and no I am not a pro
Thanks. Saw that link. Just thought it's usless to go back to Color OS and do the whole process again...
UPDATES:
was able to install 33R using fastboot and everything works amazing including OTA...
BUT - after updating to 38R I have the same issue again. The device doesn't pass the boot screen.
UPDATE 2: After going to sleep frustrated with the device Off I woke up and tried to turn it on - and - it's working. how weird is that?
UPDATE 3: with 38R working (I really don't know how) I got OTA to 44S. I gladly updated. after pressing 'Install Update' the device turned off and didn't show the regular update script running in TWRP. Now the device stuck on boot screen again...so i'm back to square one.
Could it be that cyanogen changed something to block china versions?
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Ok. I know what's happening but I can't explain that.
Unless the device is powered off and after 30 seconds turned on - there's no way to pass the boot screen.
Restarting normally from working state doesn't work, restarting from recovery, power off and power on immediately doesn't work as well.
The ONLY way for me to pass the boot screen is to power the device off completely, go drink a small beer, come back (30 seconds is enough) and turn the device on.
Any advice???
ron.r said:
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Click to expand...
Click to collapse
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
gioninardo said:
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
Click to expand...
Click to collapse
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
ron.r said:
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
Click to expand...
Click to collapse
thank you.
Already done... but without result!
Just flash the 44S ROM using fastboot. You can find them on the forum.
Why flash an old ROM and uwe OTA if the most updated ROM is available...
I am getting a hang on the bootlogo
This happened after installing the OTA for 44S. if I boot reboot the phone 20 or 30 times I can get past it.
TWRP works fine. if you pay close attention when booting into recovery you see the 1+ logo, and just before TWRP loads the screen goes slightly brighter.
When booting into system, you usually see the 1+ logo, and then the screen goes slightly dimmer. Just after this the logo should change into the rotating animation.. This is where my phone hangs. Just after it goes dimmer but before the logo starts to animate.
Now here is the weird part. I've done all the tricks, returning to stock 44s deleting all the partitions and re creating them, deleting cache, dalvik, flashing a persist.img or manually creating that partition, etc etc. after many days of crying and swearing I flashed stock 38R. it boots 100% of the time. I flashed Calkulins 44S rom, back to hanging on boot. I then restored ONLY the boot partition from 38R, and my phone boots 100%
I can't stay on 38R boot/kernel as I have the jumpy touch screen and a few other bugs which 44S fixes.
Does anyone have any ideas?
In a nutshell, 44S boot hangs 95% of the time.
38R boot image works all the time for booting (but I need the bug fixes from 44S)
(working kernel: 3.4.0-cyanogenmod-g33fa374 [email protected] #1 mon Oct 6 11:03:38 PDT 2014)
Try using this return to stock tool by OnePlus, it'll take you back to 38R with a full wipe. Don't do anything else to the phone other than letting it boot up. Then grab the 44S OTA from here and flash it.
Transmitted via Bacon
timmaaa said:
Try using this return to stock tool by OnePlus, it'll take you back to 38R with a full wipe. Don't do anything else to the phone other than letting it boot up. Then grab the 44S OTA from here and flash it.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok I tried that and it didn't work. after installing the 44S update OTA it hung on the first boot, i rebooted and it worked, i rebooted again and it hung for the next 6 tries, #7 it worked... I flashed the 38R boot image, and it boots every time. flash back the 44S boot image and it hangs on boot.
What else is in the Boot.img as well as the kernel. if it possible to have *just* the kernel? or when you flash a kernel does it update other things? I am thinking if I can flash the 38R Boot.img and then put *just* the 44S kernel over the top of that?
artymarty said:
Ok I tried that and it didn't work. after installing the 44S update OTA it hung on the first boot, i rebooted and it worked, i rebooted again and it hung for the next 6 tries, #7 it worked... I flashed the 38R boot image, and it boots every time. flash back the 44S boot image and it hangs on boot.
What else is in the Boot.img as well as the kernel. if it possible to have *just* the kernel? or when you flash a kernel does it update other things? I am thinking if I can flash the 38R Boot.img and then put *just* the 44S kernel over the top of that?
Click to expand...
Click to collapse
I'm pretty sure the boot.img is only the kernel. Not sure why your device doesn't want to boot 44S, it's a really weird one. It fully wiped your device, including user data, right?
Transmitted via Bacon
timmaaa said:
I'm pretty sure the boot.img is only the kernel. Not sure why your device doesn't want to boot 44S, it's a really weird one. It fully wiped your device, including user data, right?
Transmitted via Bacon
Click to expand...
Click to collapse
Oh I wiped and formatted it so well Timmaaaa, the paint started coming off!
I'm not the only one with the problem, I found a thread in the oneplus website forum that a staff member had posted with that 38R recovery zip that basically said they had so many support claims about boot logo hangs they were going to ignore them all and to just run that recovery procedure as it fixes them all. There are a lot of posts saying "hooray! It fixed it!" followed by "the phone said there was an OTA update to 44S which I installed and now it's not working again"
Such a great phone apart from stupid bugs like this and God awful support. Apparently if you run colour OS it doesn't hang, but who wants to run that?
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
You need to be on 5.0 Lollipop. Custom recovery. Rooted. Then flash the ROM after you Wipe in Twrp
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
MuTec said:
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
Click to expand...
Click to collapse
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
U99Dev said:
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
Click to expand...
Click to collapse
As it seems I did not, good thing that its written right at the TWRP download page...
Can't remember doing this when I installed TWRP first but as it seems I did.
Everything is working fine, just flashed Nexus OS and it booted.
Thank you so much dude