Related
Hi all,
Was working on stock xoom that was running the latest 4.1.2 OTA. Ran through the process of unlocking, then rooting using the needed files, adb and fastboot commands from OSX via USB connection (usb debugging, etc. enabled) and seemed to work. However now when i boot all i get is the moto logo. I can power+volup to get into fastboot mode or into Android system recovery and do reboot, apply update from ADB or USB Drive, Wipedata/Factory Reset or wipe cache partition. Was trying to unlock and drop the latest CM 10.1 nightly or M2 on here. Any suggestions appreciated. Not sure if I can push the CM .zip file via adb, etc onto the device. Appreciate anything to try to get it back functioning
d1c1ple said:
Hi all,
Was working on stock xoom that was running the latest 4.1.2 OTA. Ran through the process of unlocking, then rooting using the needed files, adb and fastboot commands from OSX via USB connection (usb debugging, etc. enabled) and seemed to work. However now when i boot all i get is the moto logo. I can power+volup to get into fastboot mode or into Android system recovery and do reboot, apply update from ADB or USB Drive, Wipedata/Factory Reset or wipe cache partition. Was trying to unlock and drop the latest CM 10.1 nightly or M2 on here. Any suggestions appreciated. Not sure if I can push the CM .zip file via adb, etc onto the device. Appreciate anything to try to get it back functioning
Click to expand...
Click to collapse
Also found a thread and tried to do adb sideload CM...zip and stock 4.1.2 rooted update_US-Xoom-WiFi-4.1.2-JZO54K_stachre_v01.zip but it does finding update package, opening update package, verifying, installation aborted
you need to install CWM http://forum.xda-developers.com/showthread.php?t=1074979
download the second file and flash it through fastboot
boot into recovery again, this time it will put you into CWM and flash CM
zvonkorp said:
you need to install CWM http://forum.xda-developers.com/showthread.php?t=1074979
download the second file and flash it through fastboot
boot into recovery again, this time it will put you into CWM and flash CM
Click to expand...
Click to collapse
Awesome thanks will give it a go!
d1c1ple said:
Awesome thanks will give it a go!
Click to expand...
Click to collapse
Thanks for the assist! Now enjoying CM10.1 on my XOOM
d1c1ple said:
Thanks for the assist! Now enjoying CM10.1 on my XOOM
Click to expand...
Click to collapse
? - I updated to the latest nightly 1/31/2013 and afterwards the Google play store did not work; should I have to re apply the googleJB apps .zip after each nightly?
d1c1ple said:
? - I updated to the latest nightly 1/31/2013 and afterwards the Google play store did not work; should I have to re apply the googleJB apps .zip after each nightly?
Click to expand...
Click to collapse
Most likely, it depends on if you do a full wipe between installs and what is done in the nightly.
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...
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
So I've been messing around with this phone and I've gotten it stuck in TWRP before, but that version had a download mode option and I was able to fix it using odin + the default firmware. This version doesnt seem to have it. My phone is unrecognized by my PC (previously it was), I can't seem to use universal drivers, and ADB reports no devices connected. I have an SD card so I was wondering if there is any way to fix it using that? TrapKernel is also installed. I don't have access to an OTG cable but I'm assuming its my only option? Thank you in advance.
tried this said it was not found. (tried multiple times)
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Phone: Galaxy core prime sm-g360t1
TWRP: 3.0.2-0
Hello,
Welcome to XDA.
It seems you have wiped out your OS by mistake. Try flashing the ROM and Gapps from the link below. Post questions in that thread if you need to.
http://forum.xda-developers.com/gal...rom-slimpickins-stock-rooted-bloated-t3250883
Research this option before you do it. Good luck.
Droidriven said:
Hello,
Welcome to XDA.
It seems you have wiped out your OS by mistake. Try flashing the ROM and Gapps from the link below. Post questions in that thread if you need to.
http://forum.xda-developers.com/gal...rom-slimpickins-stock-rooted-bloated-t3250883
Research this option before you do it. Good luck.
Click to expand...
Click to collapse
Got this: updater process ended with signal: 6
error installing zip file '/external_sd_/ASP.zip
Think I am just screwed. Gapps worked tho. Would I be able to put my factory .tar.md5 file on my SD card and flash that somehow?
Hi, I gave a problem with 2 SM-G900I kltedv phones after updating to lineageOS 18.1. After boot the screen goes dark, phone boots in background. trying to wake phone by pressing on power button is random, often as many as 20 attempts to wake. then when display times out same issue to wake, to overcome installed app to keep screen awake. any thoughts here, is in coding. updated from Lineageos 17 via heimdall process. All went well for sometime. I seem to think that original 18.1 Rom did not display this issue. I tried to reinstall 18.1 original via recovery to see if issue disappeared. Unfortunately did not resolve. Trying to avaoid reinstalling via Heimdall or SDK if possible. not sure if some change in coding that would likely result in same outcome
ZAC2170 said:
Hi, I gave a problem with 2 SM-G900I kltedv phones after updating to lineageOS 18.1. After boot the screen goes dark, phone boots in background. trying to wake phone by pressing on power button is random, often as many as 20 attempts to wake. then when display times out same issue to wake, to overcome installed app to keep screen awake. any thoughts here, is in coding. updated from Lineageos 17 via heimdall process. All went well for sometime. I seem to think that original 18.1 Rom did not display this issue. I tried to reinstall 18.1 original via recovery to see if issue disappeared. Unfortunately did not resolve. Trying to avaoid reinstalling via Heimdall or SDK if possible. not sure if some change in coding that would likely result in same outcome
Click to expand...
Click to collapse
gave = have
Reflash the 2 phones with their Stock ROM.
jwoegerbauer said:
Reflash the 2 phones with their Stock ROM.
Click to expand...
Click to collapse
I do like what lineageos offers in general, are you suggesting reflash to stock because you have some reservation with the lineageos.
I have nothing against LOS.
IMO best to get rid off of the issues you have is to reflash Stock ROM. Afterwards you can try again to flash LOS.
Hi, I do like what lineageos provides in general, have used it on my S5 from cm 12 to lineageos 16, 17 and now 18. would like to take advantage of what it offers. Is there something you feel is an issue with 18.1
Never used LOS.
Sorry for repeating didn't see your response.
With your ADB do you have a text file or other format that provides instructions on how to use it and details on how to flash recovery and OS. Do you prefer TRWP or Lineage recovery for updating
To flash a phone's ROM ( Stock or Custom as LOS ) a Custom Recovery like TWRP isn't needed at all, but ADB is required.
The ADB command sequence is like this
Code:
adb devices
adb reboot sideload
adb sideload <ROM-ZIP>
adb reboot
BTW: I don't make use of Custom Recovery like TWRP because all can be done via ADB and/or Fastboot methods, too. Both Stock Recovery and Custom Recovery internally run ADB and/or Fastboot commands. Both simply are a menu from where you can select what should get applied.
Thank you