Hello,
I'm trying since over 2 days to get my OnePlus One working again. It always crash 5-10 Seconds after android booted up.
The screen bightness goes to 100% and then does it crash. I've tried everything to get it working again but now I'm out of ideas.
I've tried
* Factory Reset (at first befor doing anything)
* Flashing stock rom via fastboot mode (http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541)
* Flashing paranoid android via TWRP recovery
* Installing stock rom / paranoid android via adb sideload
The offical vanilla rom works (https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/) in compare with the offical CM11S Stock Kernel (XNPH25R) from here http://forum.xda-developers.com/oneplus-one/general/official-stock-color-os-cm11s-flashable-t2844348 but I want to stock rom for my OnePlus and not this one.
I don't know what else I can do, does someone have a idea?
Joooosh said:
Hello,
I'm trying since over 2 days to get my OnePlus One working again. It always crash 5-10 Seconds after android booted up.
The screen bightness goes to 100% and then does it crash. I've tried everything to get it working again but now I'm out of ideas.
I've tried
* Factory Reset (at first befor doing anything)
* Flashing stock rom via fastboot mode (http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541)
* Flashing paranoid android via TWRP recovery
* Installing stock rom / paranoid android via adb sideload
The offical vanilla rom works (https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/) in compare with the offical CM11S Stock Kernel (XNPH25R) from here http://forum.xda-developers.com/oneplus-one/general/official-stock-color-os-cm11s-flashable-t2844348 but I want to stock rom for my OnePlus and not this one.
I don't know what else I can do, does someone have a idea?
Click to expand...
Click to collapse
I'm interested in your question, as well.
Did your phone work well before you began experimenting with it? With your "Flashing stock rom via fastboot mode", is there a command that clears cache, et al, before and or after the flash?
Is there a method to re-format before you do a new OEM flash?
Related
Hi, I'm new to flashing roms and after installing CWM 6.0.4.7 on my xt1032 and rooting whenever i try to flash a rom it gets stuck in the boot animation. I have tried CM 11 Carbon rom and paranoid android. I don't know if I'm using the wrong GAPPS or what. Please help.
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
Ok thanks, I will try that when i have some free time. And how do you revert back to 4.3
never mind i found a post on how to testing now
Brick?
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Go back to Stock and start from Scratch.
As long as you can enter fastboot you should be fine.
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Worked
quizmaniac said:
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Click to expand...
Click to collapse
Yes thank you so much I'm back on 4.4.2 You guys are great
hello everyone
I have a question about PaulOBrien superboot root method (look in modaco forum the moto g root method 1).
I have a 16GB Moto G and updated to Kitkat via OTA.
yesterday I used the method 1 (superboot) on windows 7, to root my phone, and run it for the first time and ended on a black screen with green bars (supposedly normal). I power off the phone and turned on and load kitkat normally and noted that the phone was not rooted.
y tried the method for a second time and have the same results (ended on a black screen with green bars), but when kirkat launched, on the initial screen i saw a message "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and the system didn't respond.
I performed a factory reset via stock recobey and kitkat showed the same message but let me in the "i´m feeling lucky button" worked this time. there I noticed that my device was now rooted but non app was able to access the internal memory due to some r/w permissions as I think, because when I try to copy files to the phone via USB cable, I get have the same denial, even whit ADB push i get the same message of permissions denial.
I need a way to solve this because in this actual stage the phone works but the apps have like no access to the memory making them unusable,
for example i cannot take a picture, or download a file, for some reason all google apps not work or force close every time.
I need a way to upload a .img file to the phone in order to perform a recobery or to make a fresh install via fastboot, donn't know how to make the phone let me wrhite files on it. :crying:
(note: sorry for my bad English)
A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
As long as you can enter the bootloader you haven't bricked anything!!! so don't you worry!
I have two questions: when did you download the stock rom, did you check the MD5 ??? Are you sure that it wasn't a bad download ?
Additionally: are you sure that you have downloaded the appropriate ROM? Did you try to flash any other ROM?
will8578 said:
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
Click to expand...
Click to collapse
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
dreezz said:
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
Click to expand...
Click to collapse
I am having the same issue. I got this xt1032 after it was OTA upgraded to Lollipop 5.0.2 and I downgraded it to KitKat 4.4.4 Stock. Now I'm also getting stuck on the boot animations on every Custom ROM I try to flash on it.
Does anyone know if having the bootloader upgraded due to the Lollipop update has anything to do with this? mine is at Ver. 41.18.
EDIT: I was finally able to flash after Formatting Data from Recovery. Keep in mind this will basically delete everything from the internal storage and you need to put everything back there manually. Always make sure you backup your info/apps/music/fotos before Formatting Data.
Okay, so I'm pretty conflicted/concerned. So I guess I should explain how I ****ed this up. Well, I was pretty tempted to flash PA Beta 4.6, it really looked good to me. But having not flashed on my Nexus 5, I didn't have a custom recovery, so I installed flashify and TWRP and set it up. Went well. Then I downloaded PA Beta 4.6 and also flashed it, took a bit, but I got it to work. All is good right? Well, I was confused at the lack of Google Apps (Play Store, Youtube, G+, you know). So I went into the recovery and wiped my data and tried to flash again. Only problem is, I accidently also erased the download for PA Beta 4.6. So, I get home (I was doing this all at school) and try to flash the factory images for 4.4.4 Hammerhead. But I cant seem to get it to work. When ever I use fastboot and flash the images, I end up with either 1. Non stop Google screen when I boot up, or 2. A picture of an Android with his front hatch opened and a red triangle with an exclaimation mark. What do I need to do? Please help!!
The android on his back is the stock recovery. Just hit vol up and do a factory reset. That'll fix your problem of booting
Sent from my Nexus 5 using XDA Free mobile app
You have to flash google apps aka gapps separately after flashing the ROM
ldubs said:
You have to flash google apps aka gapps separately after flashing the ROM
Click to expand...
Click to collapse
This. And don't flash custom firmware without PC access.
if TWRP is still working I would use ADB or FASTBOOT to push the PA Beta 4.6 ROM or another rom to your phone and then use TWRP to install it... sounds like you just wiped your SD card so move the ROM you want back to the phone and try try again.... GOOD luck hope everything turns out!
Hello guys,
I installed CM11 a while ago on my Nexus 5. I had no trouble installing it through Cyanogenmods own installer, but now i want to install
the official rom again, so android 4.4.4 Kitkat. But when I want to flash it through TWRP i get the error that there is no MD5 file found.
I got the rom from the official site from Google.
I want to install the clean version of android again because i have some trouble with my battery and want to try if its still a problem with original software
installed.
So can you help me with this?
Thanks in advance.
Eelke91
When you after trouble shooting a battery issue you should wipe your phone and flash the stock image. Do not trouble shoot a battery issue with a custom ROM. Period. There are too many factors involved. And bugs can arise that won't be in a stock image.
I do want to flash to my stock image, but sadly i didnt backup so i want to manually install stock android kitkat.
Eelke91 said:
I do want to flash to my stock image, but sadly i didnt backup so i want to manually install stock android kitkat.
Click to expand...
Click to collapse
You don't have to wipe internal. Just Data and Cache. Go fastboot a stock image. If you aren't backing up Your Apps and you aren't clean flashing ROMs, that's why you are having so many issues. Never dirty flash a ROM unless your ROM Dev says otherwise.
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Eelke91 said:
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Click to expand...
Click to collapse
Google nexus factory image. Use that with fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Eelke91 said:
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Click to expand...
Click to collapse
The instructions to flash a factory image are on the same page you download the image from. You need to flash it with fastboot, not recovery.
Okay i flashed it back to the stock os but still problems with my battery so i think its broken..
Eelke91 said:
Okay i flashed it back to the stock os but still problems with my battery so i think its broken..
Click to expand...
Click to collapse
Not likely. Probably just wakelocks. Go visit the battery help thread in my signature
Hello all. I found my Moto G ( XT1033) and decided to use it as a backup phone. Anyway, I flashed a CM12.1 ROM. Worked well for a while before switching off and getting stuck on a bootloop. Strange, I've already used it for some time. I thought maybe there were some problems with the ROM file. But now, I've tried it with Tesla, Blisspop, CM11, CM13. All have worked well for me in the past. Every ROM is facing the same problem.
Any help would be appreciated.
i face the same problem. its like everyday i have to do stock rom on my phone because it stuck on boatloader.
if all new clean flashed ROMs result in boot loops, you will have to reinstall stock ROM (with fastboot) to fix it. flashing stock ROM with custom recovery will not fix it though
koshikas said:
if all new clean flashed ROMs result in boot loops, you will have to reinstall stock ROM (with fastboot) to fix it. flashing stock ROM with custom recovery will not fix it though
Click to expand...
Click to collapse
Any idea what's causing it, though? I'm not able to flash a ROM into the device using the fastboot method. I've tried various builds, they all show the error after a few commands 'PARTITION SIZE IS SMALL' .
i'm not exactly sure whether you did it right. refer;
https://forum.xda-developers.com/showthread.php?t=2542219
https://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
As the title says it I've got a massive issue.
My Nexus 5 didn't work, I remember getting angry at lineage and leaving it in a boot loop. I wiped everything and using TWRP and installed the latest Resurrection Remix V6.21 Final rom available for hammerhead. I got it to work and was able to boot. I then realized It didn't have GAPPS, so i downloaded The Open GApps Project pico version for Android 8.1 and moved it to the phone. Tried installing it and came up with error 70. My /system was eaten up and only had 182mb free. So i said screw it and tried to go back to stock android. I downloaded the latest version from googles site and tried flashing it using adb. It flashed it and now the phone is boot looping at the google splash screen that happens when you initially boot the phone.
I would prefer help with getting RR cause i love what it brings to that table.
Cheers and thankyou!
Some Nexus 5 phones had an issue with any stock ROM above 4.4.2 (I used to have a phone that had this problem). Try flashing a stock 4.4.2 Google ROM.
You flashed the stock ROM using fastboot or adb commands?
audit13 said:
Some Nexus 5 phones had an issue with any stock ROM above 4.4.2 (I used to have a phone that had this problem). Try flashing a stock 4.4.2 Google ROM.
You flashed the stock ROM using fastboot or adb commands?
Click to expand...
Click to collapse
yea i flashed it using adb
Flash it using fastboot commands as recommended by Google.