Related
RIght now I am having a issue with wiping. I do a full wipe and then use a super wipe and I try to install a new rom and I get the screen after I boot up and the old boot animation comes up from the old rom it get the android is upgrading screen it finishes and i get to the home screen without signing into my google account and then my phone reboots after a while and it gets stuck at the main boot animation. I am able to get to the bootloader and recovery. I repeat doing a full factory reset and everything I just described happens again. I can't seem to get a full wipe to work properly. Anyone have any sort of idea what might be going on?
What happens if you completely re-flash the stock images and start over? That's always a good policy if you can't get a ROM to boot.
martonikaj said:
What happens if you completely re-flash the stock images and start over? That's always a good policy if you can't get a ROM to boot.
Click to expand...
Click to collapse
I haven't tried it. I don't know where I can get the stock images. Have any clue?
Also I can't get the phone to stay on long enough to mount my SD card. right now I am using Team Win Recovery Project I was able to flash a new recovery. It was on my sd card. I was using CWM.
1- you don't need super wipe, just wipe data /a cache
2- use the latest cmw http://forum.xda-developers.com/showpost.php?p=31045760&postcount=457
3- make sure the ROM you downloaded is for your device (maguro=gsm / toro=verizon)
DynamicRam said:
1- you don't need super wipe, just wipe data /a cache
2- use the latest cmw http://forum.xda-developers.com/showpost.php?p=31045760&postcount=457
3- make sure the ROM you downloaded is for your device (maguro=gsm / toro=verizon)
Click to expand...
Click to collapse
Yeah, I've done all that. I've even tried to restore a backp and it stops at restoring data and it says error while restoring /data! I'm on clockworkmod now. It seems like I can't do a full wipe. no matter what I do.
xOneSainTx said:
Yeah, I've done all that. I've even tried to restore a backp and it stops at restoring data and it says error while restoring /data! I'm on clockworkmod now. It seems like I can't do a full wipe. no matter what I do.
Click to expand...
Click to collapse
start fresh. read this.
bk201doesntexist said:
start fresh. read this.
Click to expand...
Click to collapse
I'm using a Macbook.
so?
search on how to use same tools, on a mac.
i hear android-sdk is available for mac.
md5: 07dc88ba2c0817ef178a665d002831bf
http://developer.android.com/sdk/index.html
xOneSainTx said:
I'm using a Macbook.
Click to expand...
Click to collapse
There are MacOS specific instructions in that guide...
efrant said:
There are MacOS specific instructions in that guide...
Click to expand...
Click to collapse
// people don't like to read these days. not even while looking at it on a computer screen. i'm not even talking about real books.
// end of rant.
Tried Charmin?
need more high def music...
@rbiter said:
Tried Charmin?
need more high def music...
Click to expand...
Click to collapse
LOL
Guys, i received push notification through system update to B125 and after downloading i tried to update but received error as attached.
i have tried using the dload + 3 buttons method without success so far.
Can anyone please advice how i can update ?
thanks a lot
harryhh said:
Guys, i received push notification through system update to B125 and after downloading i tried to update but received error as attached.
i have tried using the dload + 3 buttons method without success so far.
Can anyone please advice how i can update ?
thanks a lot
Click to expand...
Click to collapse
Try this:
1. Choose factory reset on the recovery.
2. Then retry update.
If that doesn't work:
1. Try to redownload the B125 ROM. It might be just that the file is corrupt.
If that still doesn't work:
1. Tell me; what ROM are you on right now? And did you just revert back from TWRP?
bokchoi2020 said:
Try this:
1. Choose factory reset on the recovery.
2. Then retry update.
If that doesn't work:
1. Try to redownload the B125 ROM. It might be just that the file is corrupt.
If that still doesn't work:
1. Tell me; what ROM are you on right now? And did you just revert back from TWRP?
Click to expand...
Click to collapse
Is that significant and why? I have the same issue and I have jut reverted from TWRP.
Thanks.
iwtfmcl said:
Is that significant and why? I have the same issue and I have jut reverted from TWRP.
Thanks.
Click to expand...
Click to collapse
I still need to know what ROM you installed previously. If you were on a Huawei stock rom, this situation is kinda weird.
If you were on a custom rom, you could try the following:
Warning: You will lose your data in this process. Make sure to backup anything that is valuable to you.
Go back to twrp.
Make sure you wipe the following:
System, Data, Custom storage, Dalvik Cache, cache
Then install stock recovery.
Then install B125.
bokchoi2020 said:
I still need to know what ROM you installed previously. If you were on a Huawei stock rom, this situation is kinda weird.
If you were on a custom rom, you could try the following:
Warning: You will lose your data in this process. Make sure to backup anything that is valuable to you.
Go back to twrp.
Make sure you wipe the following:
System, Data, Custom storage, Dalvik Cache, cache
Then install stock recovery.
Then install B125.
Click to expand...
Click to collapse
I am not OP but I had same issue. What happened in my case is weird. Originally I was on B118 International, then I went to B118CN to try and flash MIUI ROM. That didn't work and I force-flashed B118CN again. That's when I got push notification to update to B120. It was specifically saying that "P6-U06V100R001C17B118 will be updated to P6-U06V100R001C17B120.
After several failed attempts, update was no longer offered, and to my surprise my build number was showing P6-U06V100R001CNCN00B118. I am 100% sure that it was P6-U06V100R001C17B118 when I flashed it.
I have no idea what happened. I wanted to stay on chinese ROM and downloaded P6-U06V100R001C17B120, flashed and all is ok so far. Build number is showing P6-U06V100R001C17B120.
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Vesten said:
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Click to expand...
Click to collapse
what exact version of twrp?
Is the backup a system IMAGE backup?
are you entering TWRP in read-only mode?
When you try to restore now, what does the terminal output say?
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Vesten said:
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Click to expand...
Click to collapse
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
I'll have to check, but don't think it does.
I'll try that new version of TWRP and report back.
Many thanks for the help, greatly appreciated.
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Vesten said:
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Click to expand...
Click to collapse
What happens when you restore your backup and reboot without installing supersu?
jollywhitefoot said:
What happens when you restore your backup and reboot without installing supersu?
Click to expand...
Click to collapse
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Vesten said:
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Click to expand...
Click to collapse
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
jollywhitefoot said:
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
Click to expand...
Click to collapse
Interesting. There's nothing saying it couldn't write anything..
Just tried opening SuperSU from my restored backup, and hits me with "There is no SuperSU binary installed!" This is a problem, blah, blah, etc.
Then tried check-boxing the 'system' box in the Mount section. Then tried flashing UPDATESuperSu.VsXX and just gave me the usual as said above. Crashed and reboots.
https://www.dropbox.com/s/cvkclw8xuzua4u3/2015-07-20 21.56.37.png?dl=0
Losing the will to live! Ha
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Vesten said:
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Click to expand...
Click to collapse
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
jollywhitefoot said:
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
Click to expand...
Click to collapse
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Vesten said:
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Click to expand...
Click to collapse
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
jollywhitefoot said:
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
Click to expand...
Click to collapse
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Vesten said:
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Click to expand...
Click to collapse
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
jollywhitefoot said:
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
Click to expand...
Click to collapse
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Vesten said:
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Click to expand...
Click to collapse
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Wow, thankyou! I've been Googling RUU's all night at work and found nothing like this. Think I'll do that and flash the RUU and start afresh!
Getting a killer 17.4 kbp/s though. 100mb connection wasted. Ha!
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Yay it worked! Using a stock image from that link. Something must of been really screwed up. I'm now re-rooted! Many thanks for your help!
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.
can i dirty flash ob13 over oxygenos 4.1.3 though stock recovery
Dunno try it!
1. Backup system
2. Wipe system and flash OB13
3. Wipe Dalvik and reboot
If it doesn't work you can restore system and you will be back.
Clean flash recommended...
there's no 4.1.4! do you mean 4.1.3 or 4.1.1
to move from stable to beta you'll need to sideload the full rom
theduke7 said:
there's no 4.1.4! do you mean 4.1.3 or 4.1.1
to move from stable to beta you'll need to sideload the full rom
Click to expand...
Click to collapse
I cant flash through recovery
U can but u may not want to though
Bradl79 said:
U can but u may not want to though
Click to expand...
Click to collapse
Please explain
sauravid said:
I cant flash through recovery
Click to expand...
Click to collapse
Probably, you can try but as suggested before , wipe cache after if it worked...Put the full zip on the internal storage , on root not in any folder and try
Also if you sideload also go to recovery after and wipe cache...
theduke7 said:
Probably, you can try but as suggested before , wipe cache after if it worked...Put the full zip on the internal storage , on root not in any folder and try
Also if you sideload also go to recovery after and wipe cache...
Click to expand...
Click to collapse
Actually i dont have my pc with me so i want to be on safe side
sauravid said:
Actually i dont have my pc with me so i want to be on safe side
Click to expand...
Click to collapse
Hmm , o never tried to update a stable version to a beta version with recovery, even on the OnePlus forums beta thread they recommend sideload,. So I would say it's risky...
In theory it could work, what version of OOS you're on!
I think from 4.1.1 have a better chance than 4.1.3 , the later is a newer version to both .
The problem is you don't have a custom recovery so you may take a nap Droid back and return to it of it failed ...It can go ok, or you can end with a bad flash which FCS all the time or even a bootloop.
So I'd recommend against it without​ any access to computer to fix it of something went wrong .
theduke7 said:
Hmm , o never tried to update a stable version to a beta version with recovery, even on the OnePlus forums beta thread they recommend sideload,. So I would say it's risky...
In theory it could work, what version of OOS you're on!
I think from 4.1.1 have a better chance than 4.1.3 , the later is a newer version to both .
The problem is you don't have a custom recovery so you may take a nap Droid back and return to it of it failed ...It can go ok, or you can end with a bad flash which FCS all the time or even a bootloop.
So I'd recommend against it without​ any access to computer to fix it of something went wrong .
Click to expand...
Click to collapse
Yeh you are right and thaks..
If u want to try different things, I suggest u just unlock the bootloader, root and apply custom recovery, it makes things so much easier and if u mess up u can easily go back to normal.