I was using cm 12.1 and wanted to update it to newer version, but after flashing it stuck in bootloop.
Now i can only flash cm 12.1 and don't know why ?
I've tried many types of different rom's but all end up in bootloop, only version 12.1 works.#
Thanks for help.
Fastboot doesn't work for me, when im trying start it, screen flashes and goes back to bootloader.
I dont care about any files so i've tried wiping everything mounting unmounting, factory resets etc. but still it boots only cm 12.1
Will someone be able to help me please ?
It's really important.
eskejpmi said:
Will someone be able to help me please ?
It's really important.
Click to expand...
Click to collapse
well you can only flash lollipop roms until you update your bootloader as far as I know. I haven't messed with any custom rom though, but I at least read the threads.
lafester said:
well you can only flash lollipop roms until you update your bootloader as far as I know. I haven't messed with any custom rom though, but I at least read the threads.
Click to expand...
Click to collapse
When I search for " bootloader update nvidia shield " there is no such thing on the internet.
I read a lot of threads and still haven't found a solution to my problem.
Still thanks for the reply.
So basically i can only boot CyanogenMod 12.1 on mine device. No other ROM boots.
You can find the Marshmallow bootloader (4.2.0) under Firmware Update of the OP of the CM13 thread. First, make sure you're using the latest official TWRP 3.0.2-2 before flashing the bootloader.
*PROBLEM RESOLVED*
Firstly i had to unlock bootloader through fastboot - I haven't checked it at first.
After that I flashed updated firmware from upper post.
Had a lot of problems making fastboot working on my pc, but after few hours spent on searching I finally got it running.
Then I flashed CM13 and it worked !
Thanks for help !
Related
I'm currently on a custom 5.1 ROM with the new bootloader and radio. I read about issues when flashing the CM12 ROM with this setup. Is this still a problem? Do I have to go back to the 5.0 stock android (with full wipe) before flashing CM12?
Would like to know something similar of the sort, also have the 5.1 boot loader and radio and am on resurrection remix 5.1. Would like to go to CM12 if possible.
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
daniel.1983 said:
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
Click to expand...
Click to collapse
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
KentuckyGuy447 said:
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
Click to expand...
Click to collapse
I flashed the zip file from post one with the 5.0 bootloader (https://www.androidfilehost.com/?fid=95916177934545628). Afterwards I flashed the latest CM12 nightly and the Gapps on top. I'm not sure about which action/configuration could brick the device. I have seen much positive feedback in the other thread, so I tried this too.
KentuckyGuy447 said:
I thought downgrading the bootloader would result in a hard brick?
Click to expand...
Click to collapse
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
beekay201 said:
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
Click to expand...
Click to collapse
It is more of a concern you know. My knowledge is very limited as all this is new to me. I don't have money to throw around for a new device but thanks! I'm taking this as its safe to. Just hard bricking would permenatly destroy a device so don't wanna do that you know...
EDIT: Tested and Confirmed Woking! Big thanks to Daniel!
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
matanp said:
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
Click to expand...
Click to collapse
A few questions:
What method are you using to switch between KK and LP? Fastboot (flashing stock images) or recovery?
If it's recovery, are you flashing the correct firmware/modem?
Are you still able to see your baseband and IMEI in About Phone?
IF you haven't flashed the stock images with fastboot that's the first thing you should try. I have detailed instructions in my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
matanp said:
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
Click to expand...
Click to collapse
Have you flashed the latest Lollipop build with fastboot as outlined in my guide?
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
matanp said:
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
Click to expand...
Click to collapse
That's because the LP images don't usually contain it, but the ones I link to do.
i'll try and report
thanks
i just got a message from oneplus support:
Hi Matan,
Thank you for reaching out. Sorry for the inconvenience that has caused to you. Rest assured that we will be providing you solutions in solving the issue.
You can also try to flash the device to the latest Oxygen OS, it is designed to fix common bugs that causes the issue.
To install OxygenOS on your OnePlus One, you need to flash the device. You may follow the guidance here:
https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
Please also note that since OxygenOS is a product from OnePlus therefore it is currently only available for OnePlus One.
Please don't hesitate to contact us for any update and feedback.
Thank you and have a good day.
Regards,
Jefflee
Click to expand...
Click to collapse
can i flash oxyOS (to check if it solve the problem) and after that flash your COS12 img with the fastboot commands or is there anything else i should know about?
flashed the latest COS12 version with your guide and i still have bootloops
Having this exact problem.... No wifi in CM11 and when updating tot CM12 getting boot looped.
Found a solution to your problem?
It's because of the modem files.. When u downgrade or upgrade from/to lollipop/kitkat u must flash the appropriate files!! Pm me if u want more info
Sent from my A0001 using Tapatalk
yes, i've open a ticket with oneplus one and their tech guy installed oxygenOS and it works well
hi all, i am new here. so, please pardon me if i do any mistake.
here is problem,
as i am interested in technical things, my friend asked me to update his HTC one m8 into lollipop. at that time the mobile had custom rom with twrp version 7.0.2
android version: 4.4.2, sense version: 6.0, software number: Android Revolution HD 5.0 by mikel 1986, API level: 6.17
so i looked for resources and found a link. i could not add the link.
so i followed the steps and flashed the boot via fastboot with boot.img of new custom rom. the upon restart the mobile got stuck into bootloop. I could not go into recovery according to hardware button combination described there. Later once i found right combination i managed to go to recovery mode of twrp. then, i tried the remaining steps that is installing custom rom and gapps from zip file being in the recovery. Every command i gave got executed but still i could not get into system. even thought i had flashed the boot.img as an early step while starting the hboot it shows there are no images to load. So, i tried to restore from twrp recovery and i failed again. I tried to update the twrp image to run the image file of the custom rom from the twrp. but the update failed. so, i gave it to a repair shop and the repair man managed to get it working. he installed stock 5.0.1 version and in bootloader option it says software as official and relocked which showed tampered and unlocked before. BUt the problem is there are few settings that are grayed out. cant be changed. like brightness, developers option, wifi. I thought of updating os from within the set but wifi did not work.
SO, now how i can install a proper stock rom in that mobile? please help
ya you can install stock rom on your mobile..you can find your stock rom from XDA developers only......
kiranchaitanya said:
ya you can install stock rom on your mobile..you can find your stock rom from XDA developers only......
Click to expand...
Click to collapse
thank you.. i will find the rom from here. but how should i install it as i tried a process as i mention and failed. will this present rom conflict in any way? u can direct me to the point where i can find how to install the stock from the present state i m ..
naziullah said:
thank you.. i will find the rom from here. but how should i install it as i tried a process as i mention and failed. will this present rom conflict in any way? u can direct me to the point where i can find how to install the stock from the present state i m ..
Click to expand...
Click to collapse
try this once
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
kiranchaitanya said:
try this once
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Click to expand...
Click to collapse
Thank you again..and sorry i had been busy and away. Could not response early. The phone was given to repair shop by my friend.
Okay so here's the info to the best of my knowledge,
Phone Model : Moto G 3rd Gen (XT1550, dual sim, 2gb RAM, 16gb ROM, India)
Bootloader Status : Unlocked
Root Status : Rooted
Recovery : Stock
ROM : Stock ROM 5.1.1
I've been running the stock Recovery & ROM with high hopes of getting an official OTA Marshamallow update.
To truly customize the device to my liking I flashed the xposed framework (the arm version) , it worked fine and all the modules I installed worked perfectly.
I also had Device Control, Xposed Gels, and some other apps to bring my Stock ROM experience close to that of Cyanogen MOD.
When the OTA Marshmallow update started rolling in , I was unable to install the update even after successfully downloading the file numerous times. But i was so comfortable with my device and all the customization I had on my device that I decided to keep using my customized Stock ROM.
4 months later (now) the lack of a gyro in this device and my eagerness to get into VR headsets has left me with no choice but to sell it and get another phone. So i needed it in a sale worthy condition, without the customization and with the Marshmallow update installed.
I uninstalled the xposed framework and all the modules but was still unable to install the OTA update.
So i figured i'd install CyanogenMOD with TWRP custom recovery.
I have done this for quiet a lot of my friends and am fairly used to the steps involved. I use the " minimalADB fastboot " kit and my device on fastboot to flash recovery. For some reason i was not able to flash the lastest TWRP image (twrp-osprey-3.0.0-r2.img ) for the device nor was i able to boot from it :crying:. The fastboot command prompt on my PC would show success but the devices would not restart into the custom recovery like it is supposed to, but the device would stay at the fastboot mode and kept restarting everytime i selected the recovery mode option.
I had an older image (twrp-osprey-2.8.7-r3.img ) which i couldn't flash either but i was able to boot into TWRP with this image. From here i tried installing the latest CM12.1 nightly available (cm-12.1-20160227-NIGHTLY-osprey.zip) as soon as i swiped the device would just reboot, i tried this numerous times and with other nightly builds as well.
In haste and frustration i wiped the cache/dalvik , internal storage and system through TWRP , thinking that changes made in the quest of customizing my device were causing this hindrance. I had no OS now. I went over trying to flash TWRP and CM12.1 many times again with the same issues.
I came about a thread on How to " Fastboot Flash Moto G (3rd Gen) Factory Firmware Images " (http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750) & used this firmware image " Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7 ". Still no progress.
The bootloader unlocked warning has come back (i flashed a stock MOTO logo there earlier) which keeps flashing on my screen again and again , no booting into OS or anything else. Not even an error. As if there is no OS installed.
I have gone about the procedure in the above thread a couple of times, with no success and the same problem.
Is there any reason why i'm unable to flash a custom recovery or ROM ??? What am i missing???
Please help i'm stuck, pulling my hair out with no phone and completely frustrated.
Thanks in advance.
Did you check your build no for stock ROM?
samirza692 said:
Did you check your build no for stock ROM?
Click to expand...
Click to collapse
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
ashrith.s said:
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
Click to expand...
Click to collapse
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
samirza692 said:
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
Click to expand...
Click to collapse
the link provided is the exact same link from where I flashed a stock rom before.
build number for stock rom??? am i missing something???
all i see is the model variant (xt1550 is my phone)
RAM specification (mine is 2gb)
and the region (mine is retails asia | india )
so i went with the following firmware
Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7
where does the build number come into the equation???
Please lemme know if im doing something wrong. Thanks for the replies.
So I've successfully flashed twrp-osprey-2.8.7-r3.img to my device and I've been able to boot into twrp. The touchscreen doesn't seem to respond though. It asks to swipe to begin and I'm stuck again.
I had the screen replaced a couple of days ago.
Could it be a faulty screen or a software issue?
P.S. I have not been able to flash any version of twrp after the above mentioned version (v 3.0.0 is the latest stable version) but the ones prior are flashable.
Hey, contact me via PM and il do my best to help you in this.
therealduff1 said:
Hey, contact me via PM and il do my best to help you in this.
Click to expand...
Click to collapse
Is not big issue
Is it still possible to boot back into the OS? If it is, check if you have OEM unlocking enabled, since you're on stock ROM, it might be gotten unchecked after unlocking your bootloader because that's what happened with me. If you do t wether or not that was checked, you're at a dead end and there's nothing you can do. You can try paying someone to fix it, i.e., Motorola.
Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?
OEM unlock toggle in Developer's Options
Hi ยก...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers