My device's USB is not functioning, it was on CM11 final version till today morning. I tried to install CM 12.1 on it. assuming it would work. The device boots, but i dont have network (I guess baseband problem). I am stuck on the crappy cyanogen recovery that doesnt allow me to flash cm11 zip, or the backup. anything but the cm13 zip is not flashing. I cant install the baseband rils. or any other zips... need help how to fix the device.
srivmanu said:
My device's USB is not functioning, it was on CM11 final version till today morning. I tried to install CM 12.1 on it. assuming it would work. The device boots, but i dont have network (I guess baseband problem). I am stuck on the crappy cyanogen recovery that doesnt allow me to flash cm11 zip, or the backup. anything but the cm13 zip is not flashing. I cant install the baseband rils. or any other zips... need help how to fix the device.
Click to expand...
Click to collapse
Fixed : Flashed FOTA Restore and then flashed CM12.1, followed by dual-sim fix.
Related
So here's the story
I installed CM11 about a month ago but then decided to revert back to stock, but then again due to short battery life decided to go back to cyanogenmod.
However when I try to install cyanogenmod (even the exact same version as before) on various recoveries (including CMW and Philz) I get the status 7 error. I've already tried to change the code in the updater-script and updating the recovery image, but nothing seems to work. Though I have succeeded in installing a SlimKat rom this rom doesn't support my provider or something.
Any idea on what I should do next?
Please help me out people, I'm kinda desperate right now :/
ogradish said:
So here's the story
I installed CM11 about a month ago but then decided to revert back to stock, but then again due to short battery life decided to go back to cyanogenmod.
However when I try to install cyanogenmod (even the exact same version as before) on various recoveries (including CMW and Philz) I get the status 7 error. I've already tried to change the code in the updater-script and updating the recovery image, but nothing seems to work. Though I have succeeded in installing a SlimKat rom this rom doesn't support my provider or something.
Any idea on what I should do next?
Please help me out people, I'm kinda desperate right now :/
Click to expand...
Click to collapse
A sidenote
when I use the latest version of CWM and install cm11 it installs perfectly fine, but when booted up the boot animation just goes on for hours and it won't let me get into the rom
ogradish said:
A sidenote
when I use the latest version of CWM and install cm11 it installs perfectly fine, but when booted up the boot animation just goes on for hours and it won't let me get into the rom
Click to expand...
Click to collapse
First you must know to use the latest CWM from CM11 thread or latest TWRP or Philz, second aere you flash the boot.img form fastboot erase cache from fastboot and delete dalvik to
Hello folks,
Those who are using latest TWRP or 4Ext recovery,Please comment below.Also i want to know which custom rom your on? I do flash roms in every 2-3 days and problem took place i guess somewhere from CM11 nightly 06/12 onwards.
So my question is: Anybody has encountered a problem where flashing latest nightly or any latest build beyond 4.4.3 causes reboot into recovery automatically soon after flashed boot.img and reboot system.
I always prefer Clean wipe, Install rom, Appropriate GApps, Inspiremod Patch, flash boot.img via fastboot.
Also i would like to add,that when i use Musta's CM11 nightly after successfully flashing it and rebooting the device. But nothing comes after typical htc logo and complete blank screen for few seconds and redirects me into TWRP recovery again. Where as If i use any rom made chinese devs like for ex. Mokee Open Source's latest weekly(randomly) it flashes correctly but it stuck at bootanimation.
Yesterday i've tried one more modified version of Musta's 20140622 nightly made by chinese dev, It flashed correctly but hangs up in bootanimation, i couldn't able to see anything beyond that.
Any sort of help will be appreciated.
Thanks.
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
TF666 said:
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
Click to expand...
Click to collapse
Have you tried with another build of CM11? Perhaps the latest milestone? Have you wipe:d all the data and cache and stuff? Can you tell me how you got the TWRP on there? Did it work the first time you flashed the 4.4.2 version? Where you on the latest version of android before rooting?
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
TF666 said:
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
Click to expand...
Click to collapse
Is 50010b also 4.4.2 or is it earlier? Did you just flash TWRP with flashify then after rooting?
I think it was 4.4.2.
My initial root after purchase was done according to http://www.youtube.com/watch?v=05T3mYVnYYE
Everything went smoothly then, but I think you'd achieve the same outcome using Flashify.
So recently i flashed the new cyanogen 14.1 nightly rom but it said their was an update but after i installed it it tried to go into recovery and wouldnt start. I shut it down and it would only go into fastboot mode and show the boot image. after this i downloaded fastboot and adb files and a tool kit and it now boots into the actual rom but still not recovery. so how can i get the recovery to pop up? iv already tried to flash twrp again but it still didnt load. and i even flashed the stock recovery and still wouldnt boot up. if anyone knows a way i can fix my recovery it would help alot. :good:
I have exactly same problem as you k hope it's a problem with the new cyanogenmod 14.1 nightly if not may try to change the kernel? I'm looking around too
Same problem here.... I installed TWRP and Dirty Unicorns on my One Plus 3, but immediately had a host of problems (including home key not working). I then flashed the most recently nightly (cm-14.1-20161119-NIGHTLY-oneplus3.zip). It booted fine, but now I cannot get into recovery. Any attempt to boot into recovery will put me back at the unlock warning screen... The phone is functionally useless at this point, because it doesn't even have gapps on it.
How can I restore this phone to a usable state (i.e., enter recovery to allow flashing of gapps)?
official twrp doesnt work with community builds and cm 14.1. You have to use modified twrp 3.0.2-22. the link can be found easily in official cm 14.1 forum on xda.
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