Related
ive been running into a strange issue installing roms lately. I can install anything touchwiz no problem and they run great. but for some odd reason if I install any of the numerous aosp roms the just hang on first boot. ive tried almost every aosp there is and they all sit there and hang, ive even let a few sit for hours with no luck. yet touchwiz will boot fine in just a few minutes. anyone have any suggestions or ideas?
Have u done a clean wipe factory reset wipe delvk catche.. Wipe everything clean.. Some stuff from the tw roms could stay behind.. Wen ppl change from aosp rom to a tw rom they use synergy rom cuz it does a clean install .. I could be wrong about this
Just be sure to wipe data/cache. The ROM zip install erases system for u.
Sent from my SCH-I535 using Tapatalk 4
Erasing data problem
I have unrooted Verizon S3.
It was working ok until I decided to put some new ROM. I instaled Synergy S3 r420 rom. It worked OK, but did not have mobile internet. WiFi and mobile hotspot were working fine. I decided to put back my old system, not to mess around any more, and went into CWM mode.
After entering CWM I tried wipe out/factory reset but it stacked at Formatting /data
Previous formating of cache and wiping of Dalvik went OK.
Part of the message was E:unknown volume for path [sd/ext]
What di I done with my phone? Is it soft bricked or what?
I can still boot last ROM, and is functional
How can I return my phone to the state saved in my CWM backup ?
Thanks!
EDIT
I have tryed to instal a different ROM - Hyperdrive, and install went normaly. At the end asked me to reboot and I said OK. Then, upon rebooting, a Warning message appeared warning me that non Verizon softvare is detected and that I should take the phone to them.
Is there anything to do to reverse this state?
You need to use odin to restore stock
Sent from my SCH-I535 using Tapatalk 4
So I am a complete noob to this whole rooting, s-off, custom rom experience. So far I have managed to unlock my boot loader and gain s-off thanks to all the awesome peeps on this forum. I tried installing Liquid smooth and I got stuck in what I assume was a boot loop. It would boot and simply just reshow the boot animation. Managed to get into recovery and flash back to a backup I made. What would cause this to happen to me? My Htc is currently on android version 4.4.2 with a software number of 1.55.605.2. Do I need to somehow get my android version up to 4.4.4 in order to use Liquid smooth (or any rom for that matter). Or is there something else that I may have done wrong? Any suggestions or help is greatly appreciated.
GarnerArms said:
So I am a complete noob to this whole rooting, s-off, custom rom experience. So far I have managed to unlock my boot loader and gain s-off thanks to all the awesome peeps on this forum. I tried installing Liquid smooth and I got stuck in what I assume was a boot loop. It would boot and simply just reshow the boot animation. Managed to get into recovery and flash back to a backup I made. What would cause this to happen to me? My Htc is currently on android version 4.4.2 with a software number of 1.55.605.2. Do I need to somehow get my android version up to 4.4.4 in order to use Liquid smooth (or any rom for that matter). Or is there something else that I may have done wrong? Any suggestions or help is greatly appreciated.
Click to expand...
Click to collapse
This has occasionally happened to me with some ROM's and well the issue could depend on a lot of things, the most simplest solution that works a lot of the time is to clear your cache & dalvik cache and reboot.
Also by "reshow the boot animation" do you mean it just endlessly loads the boot animation or it shows the old one? Did you wipe your /data partition when you installed the ROM or did it automatically do it for you? If not and the cache wiping didn't solve your problem you could always attempt doing that and then freshly installing it again and re-trying. If by any chance neither of these worked for you then could you please provide a bit more detail as to what you do when you're flashing the ROM? If you've managed to solve you problem then you don't need to bother with providing any further information.
Edit: I went to the thread and read a bit more on it just to insure I wasn't instructing you to do the wrong thing and I noticed it has a GAPPS package to flash, did you follow all of the instructions correctly e.g full wipe, flash gapps, reboot and waited at least 5 minutes (max usual = 10 minutes)?
S1L3nTShaDoWz said:
This has occasionally happened to me with some ROM's and well the issue could depend on a lot of things, the most simplest solution that works a lot of the time is to clear your cache & dalvik cache and reboot.
Also by "reshow the boot animation" do you mean it just endlessly loads the boot animation or it shows the old one? Did you wipe your /data partition when you installed the ROM or did it automatically do it for you? If not and the cache wiping didn't solve your problem you could always attempt doing that and then freshly installing it again and re-trying. If by any chance neither of these worked for you then could you please provide a bit more detail as to what you do when you're flashing the ROM? If you've managed to solve you problem then you don't need to bother with providing any further information.
Edit: I went to the thread and read a bit more on it just to insure I wasn't instructing you to do the wrong thing and I noticed it has a GAPPS package to flash, did you follow all of the instructions correctly e.g full wipe, flash gapps, reboot and waited at least 5 minutes (max usual = 10 minutes)?
Click to expand...
Click to collapse
Yeah it would show the Liquid Smooth boot animation then the name Liquid Smooth, then it would just continuously blink the name Liquid Smooth. Sometimes it would go completely black, vibrate, then reboot to the Htc screen and then to the Liquid Smooth animation. Not sure if that is helpful. I would like to try again though. I did do a factory wipe through twrp before I tried installing them. I didn't do the GApps that way, I just simply included it with the Liquid Smooth zip and flashed them both at the same time. I read through the thread and didn't see that is how to properly do it. Thanks. So just to reiterate, do a full wipe, flash GApps, reboot and wait for 5 minutes, then enter back into twrp and then flash Liquid smooth?
GarnerArms said:
Yeah it would show the Liquid Smooth boot animation then the name Liquid Smooth, then it would just continuously blink the name Liquid Smooth. Sometimes it would go completely black, vibrate, then reboot to the Htc screen and then to the Liquid Smooth animation. Not sure if that is helpful. I would like to try again though. I did do a factory wipe through twrp before I tried installing them. I didn't do the GApps that way, I just simply included it with the Liquid Smooth zip and flashed them both at the same time. I read through the thread and didn't see that is how to properly do it. Thanks. So just to reiterate, do a full wipe, flash GApps, reboot and wait for 5 minutes, then enter back into twrp and then flash Liquid smooth?
Click to expand...
Click to collapse
No no sorry if I confused you or said that wrong, wipe, flash Liquid Smooth & flash the GApps (Same way as before will work as long as its after the ROM) then wipe your cache/dalvik cache(best do this before and after flashing) and attempt booting into it.
Tell me the results of this once you've tried it.
Another question is why does a Rom like Liquid Smooth require GApps to be flashed but another Rom like SinLess doesn't. Is it because one is a aosp? Also when they show the Rom version 4.4.X does that mean it will work with 4.4.2 as well as 4.4.4? Sorry for the basic questions, I try searches but a lot of times come up with nothing.
GarnerArms said:
Another question is why does a Rom like Liquid Smooth require GApps to be flashed but another Rom like SinLess doesn't. Is it because one is a aosp? Also when they show the Rom version 4.4.X does that mean it will work with 4.4.2 as well as 4.4.4? Sorry for the basic questions, I try searches but a lot of times come up with nothing.
Click to expand...
Click to collapse
Some ROM's simply require it and others don't. On the ROM versions, whatever version the ROM you are flashing is based off of is the ROM version. So if Liquid Smooth is 4.4.4 then that means it is based off of the 4.4.4 update for either another edition of the device (Sometimes since Verizon doesn't release anything timely) or YOUR version (Verizon in this case) of the device.
Thanks bud. Followed your directions and boom it worked. Time to play with some custom Roms!
Hello all
I am facing a strange issue of phone when I took it I out of pocket it started I use multirom was on secondary rom slimkat latest when this happened. When I took it from the pocket it was on my internal rom PA latest beta2 and lost my baseband to unknown and wifi also not working so I went to twrp to flash the radio zip went fine flashing it but when rebooted there was no baseband so tried again for few times but no luck.
So I decided to start clean by removing all secondary roms and did a factory reset of the internal rom and flashed the PA 4.6 beta2 and gapps to start clean but after that the issue started happening it boots till the welcome screen to select language from there it rebooting again into a endless times tried for times to flash the rom again but still it rebooting from that screen . My phone is unusable now.
Can someone guide me how to start clean from here and to boot a rom properly.
Really hoping someone here can help me out on this. Thanks in advance.
Really need some help to get my device back up and running. Right now my phone is on endless reboot loop from the welcome screen of the rom with multirom twrp recovery.
Fingers crossed and waiting. :/
Why don't you start from scratch aka cm11s
-Tunasty
AhmedFaiz said:
Hello all
I am facing a strange issue of phone when I took it I out of pocket it started I use multirom was on secondary rom slimkat latest when this happened. When I took it from the pocket it was on my internal rom PA latest beta2 and lost my baseband to unknown and wifi also not working so I went to twrp to flash the radio zip went fine flashing it but when rebooted there was no baseband so tried again for few times but no luck.
So I decided to start clean by removing all secondary roms and did a factory reset of the internal rom and flashed the PA 4.6 beta2 and gapps to start clean but after that the issue started happening it boots till the welcome screen to select language from there it rebooting again into a endless times tried for times to flash the rom again but still it rebooting from that screen . My phone is unusable now.
Can someone guide me how to start clean from here and to boot a rom properly.
Really hoping someone here can help me out on this. Thanks in advance.
Really need some help to get my device back up and running. Right now my phone is on endless reboot loop from the welcome screen of the rom with multirom twrp recovery.
Fingers crossed and waiting. :/
Click to expand...
Click to collapse
If you read the OP for the PA 4.6 it says not to use the latest gapps as it doesn't work so try out the one that the OP recommends
Sent from my A0001 using Tapatalk
Tunasty said:
Why don't you start from scratch aka cm11s
-Tunasty
Click to expand...
Click to collapse
I think I need to do that. I am at work now need to download the cm11s from the official link. Can you link me to a good guide to start from scratch. Will try clean later today. So I need to go to fastboot manually by pressing vol up button and power button to enter?
Is it a known issue or are there others with the same issue. Please link me there too.
Thanks for the advice.
jojohnson250 said:
If you read the OP for the PA 4.6 it says not to use the latest gapps as it doesn't work so try out the one that the OP recommends
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Used the old micro gapps I don't think that is the issue here. All this started after losing my radio and wifi not working after that strange reboot from my pocket. When I connect to android file transfer it shows no files in the phone and can't move anything to the device also.
Started from scratch and back on stock cm11s. Gone stay pure stock for a while before I start rooting again.
Flashed official cm11s rom through fastboot mode.?
I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus
Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom
Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk
Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).
Very exited, good job
so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)
coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk
unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.
Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!
HI guys,
Yesterday when i was browsing chromium, my tablet started boot looping ( i'm using ORION rom), I thought the problem came from cash, so i made a wipe cash ( from twrp), but the problem persisted. So i made a full wipe and try to install a new rom but getting error 7 when installing from twrp. So i decided to use odin to flash a stock rom. But after flashing, the tablet boot on orion rom and still bootloops. Any help please and thanks in advance.
walid77dz said:
HI guys,
Yesterday when i was browsing chromium, my tablet started boot looping ( i'm using ORION rom), I thought the problem came from cash, so i made a wipe cash ( from twrp), but the problem persisted. So i made a full wipe and try to install a new rom but getting error 7 when installing from twrp. So i decided to use odin to flash a stock rom. But after flashing, the tablet boot on orion rom and still bootloops. Any help please and thanks in advance.
Click to expand...
Click to collapse
Sounds like the dreaded emmc brick. See andi's GitHub for his take on it.