Related
Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
Hi, I will have my hands on this tablet very soon and want to use the Cleanrom that is listed in a thread here. This will be my first time doing this and have been searching around for a guide. I have read a few bits and pieces but would like someone to explain in a few steps so i can get this right the first time.
I found a guide to Root it at rootgalaxynote.com but would like to understand how to install the CleanROM.
Hello,
You have to install TWRP Recovery first, then you need to copy Rom.zip to storage and then flash it using Recovery, dont forget about Wipe.
52224489
WeedyEyes said:
Hello,
You have to install TWRP Recovery first, then you need to copy Rom.zip to storage and then flash it using Recovery, dont forget about Wipe.
Click to expand...
Click to collapse
I havent installed anything yet as i will be receiving it for christmas. Not 100% sure on process so was posting here hoping someone could explain the process a bit more in laymans terms as this will be the first time i will be doing this. i understand you have to root the device so you can change the ROM, wasnt sure on what to do after that.
reetzy said:
I havent installed anything yet as i will be receiving it for christmas. Not 100% sure on process so was posting here hoping someone could explain the process a bit more in laymans terms as this will be the first time i will be doing this. i understand you have to root the device so you can change the ROM, wasnt sure on what to do after that.
Click to expand...
Click to collapse
All you need is to Install Custom Recovery to change ROM, that will allow you to do anything you want with your device (such as System Backup/Restore, installing .zip packages, and etc.) read thread about TWRP so you can find everything you need to know.
But notice the fact you'll lose your warranty installing custom roms, as I know there is no way to change warranty bit back to 0 yet.
All information you need to know about Custom Roms is already there.
WeedyEyes said:
All you need is to Install Custom Recovery to change ROM, that will allow you to do anything you want with your device (such as System Backup/Restore, installing .zip packages, and etc.) read thread about TWRP so you can find everything you need to know.
But notice the fact you'll lose your warranty installing custom roms, as I know there is no way to change warranty bit back to 0 yet.
All information you need to know about Custom Roms is already there.
Click to expand...
Click to collapse
Thanks Weedy :good: Once i get this tablet i will give it a go.
Can you give me a link to the TWRP thread you refereed to thanks.
http://forum.xda-developers.com/showthread.php?t=2515656
Here you can find TWRP. I would recommend flashing the ".0"version because some people are having problems with the newer one
Worked fine for me , just did the same process as you
Sent by my Note 10.1 2014
benni2903 said:
http://forum.xda-developers.com/showthread.php?t=2515656
Here you can find TWRP. I would recommend flashing the ".0"version because some people are having problems with the newer one
Worked fine for me , just did the same process as you
Sent by my Note 10.1 2014
Click to expand...
Click to collapse
Thanks, all i need is Santa to hurry up now lol.
Are you sure you wanna get P600 not P605?
Make sure you get the right version, whether Quality or Exnyos. I had a freeze until I got the right version.
Sent from my SM-P600 using Tapatalk
In this guide what is this file for ?
Step 3. Download and unzip P600_Autoroot.zip:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-2014-edition/
Edit: Should i do this first before the TWPR?
Build says CleanRom 1.0 but all apps are still present
My build says CleanRom 1.0 but I still have all of the apps that others say are removed such as Sketchbook. My note was rooted using the AutoRoot file with Odin and then the stock recovery was flashed. I then used the twrp 3.0 file and booted into recovery. I then installed CleanRom (without reset per instructions) and the device rebooted and everything worked except all of the apps were still there. I then tried to re-flash CleanRom and perform the wipe but I then got stuck on the Samsung splash screen to no avail. I booted into recovery and tried re-flashing the CleanRom zip to no avail. All I could do to get this thing booted was to flash the auto-root file again in Odin, re-flash twrp, and install cleanrom again from the recovery but all of the apps are still there. Before I did any of this I had a bunch of the bloatware either frozen or uninstalled in Titanium but now some of those apps show lines through them in TBP. Either way, my device is showing CleanRom 1.0 under the build but I really don't think it is... any ideas on how to fix this?
Hi i'm a newbie on android
i've tried to install this rom a lot of time but unsuccessfully at any time
i've tried all the solutions i found here but none were successfull
i am under TWRP 2.6.3.0
my tablet is rooted but after the rom flash ,when i reboot ,just after the "galaxy note edition 2014" logo there's a black screen
the only way to repair is to flash with the mk1 stock rom after or to restore my old version saved with TWRP
can someone help ?
thanks
shoresteve626 said:
My build says CleanRom 1.0 but I still have all of the apps that others say are removed such as Sketchbook. My note was rooted using the AutoRoot file with Odin and then the stock recovery was flashed. I then used the twrp 3.0 file and booted into recovery. I then installed CleanRom (without reset per instructions) and the device rebooted and everything worked except all of the apps were still there. I then tried to re-flash CleanRom and perform the wipe but I then got stuck on the Samsung splash screen to no avail. I booted into recovery and tried re-flashing the CleanRom zip to no avail. All I could do to get this thing booted was to flash the auto-root file again in Odin, re-flash twrp, and install cleanrom again from the recovery but all of the apps are still there. Before I did any of this I had a bunch of the bloatware either frozen or uninstalled in Titanium but now some of those apps show lines through them in TBP. Either way, my device is showing CleanRom 1.0 under the build but I really don't think it is... any ideas on how to fix this?
Click to expand...
Click to collapse
Before flashing your rom perform a factory reset in twrp and format /data. All your apps will be deleted and you should be fine if you are stuck on the samsung boot logo it might help to boot into recovery and format /cache and dalvik cache
Sent by my Note 10.1 2014
Messed it up even more
benni2903 said:
Before flashing your rom perform a factory reset in twrp and format /data. All your apps will be deleted and you should be fine if you are stuck on the samsung boot logo it might help to boot into recovery and format /cache and dalvik cache
Sent by my Note 10.1 2014
Click to expand...
Click to collapse
So, I did the factory reset in twrp and then formatted the data. Naturally, everything was lost but when I went to install CleanRom it was no longer on the internal memory due to the format... but I did copy it to the Ext SD Card. MY problem is that twrp won't install the zip from the sd card. Each time it says its unable to mount "/data" even though I'm going into "advanced settings" and placing the check mark. I re-flashed twrp and tried using file manager to move the file to the internal storage but came up with the same problem. Also, I can't place the check on mount data for some reason. Now, my tablet starts to boot up but hangs on the samsung screen before the boot animation. Basically, its like there isn't any firmware on it and I tried re-doing the auto-root and stock recovery but thats a no go as well. Is this thing toasted?
shoresteve626 said:
So, I did the factory reset in twrp and then formatted the data. Naturally, everything was lost but when I went to install CleanRom it was no longer on the internal memory due to the format... but I did copy it to the Ext SD Card. MY problem is that twrp won't install the zip from the sd card. Each time it says its unable to mount "/data" even though I'm going into "advanced settings" and placing the check mark. I re-flashed twrp and tried using file manager to move the file to the internal storage but came up with the same problem. Also, I can't place the check on mount data for some reason. Now, my tablet starts to boot up but hangs on the samsung screen before the boot animation. Basically, its like there isn't any firmware on it and I tried re-doing the auto-root and stock recovery but thats a no go as well. Is this thing toasted?
Click to expand...
Click to collapse
Boot into TWRP and click "Restore Back Up" (Cannot remember exact verbiage) . Find where it says internal storage and press it and it will switch to a drop down and you can choose "External SD" Then go back and and it should be going to External SD instead of internal SD when you select install
Make sure you factory re-set. For safety, I advance wipe but I don't think that is necessary.
You may need to re-flash recovery if you're unable to access it.
shoresteve626 said:
So, I did the factory reset in twrp and then formatted the data. Naturally, everything was lost but when I went to install CleanRom it was no longer on the internal memory due to the format... but I did copy it to the Ext SD Card. MY problem is that twrp won't install the zip from the sd card. Each time it says its unable to mount "/data" even though I'm going into "advanced settings" and placing the check mark. I re-flashed twrp and tried using file manager to move the file to the internal storage but came up with the same problem. Also, I can't place the check on mount data for some reason. Now, my tablet starts to boot up but hangs on the samsung screen before the boot animation. Basically, its like there isn't any firmware on it and I tried re-doing the auto-root and stock recovery but thats a no go as well. Is this thing toasted?
Click to expand...
Click to collapse
Your device is not toasted I always have the Rom zip on the root directory of the device so formatting /data will not affect the rom zip. If you cant get it working then you might need to flash a firmware via odin and after that copy the rom on the internal root directory. Resetting your device should not format the whole internal storage so you can install the rom afterwards. Good luck mate
Sent by my Note 10.1 2014
Thanks for all the help!
benni2903 said:
Your device is not toasted I always have the Rom zip on the root directory of the device so formatting /data will not affect the rom zip. If you cant get it working then you might need to flash a firmware via odin and after that copy the rom on the internal root directory. Resetting your device should not format the whole internal storage so you can install the rom afterwards. Good luck mate
Sent by my Note 10.1 2014
Click to expand...
Click to collapse
After the holiday (and many stressful attempts) I was finally able to re-boot the device and get past the splash screen. Opening Kies seemed to "kick" past the splash screen even though it said my device wasn't compatible with Kies. Anyway, I flashed the stock recovery, wiped, reset, flashed original firmware via Odin, flashed TWRP again, and then installed the CleanRom zip. Phew... it's FINALLY over with no issues and running smooth. I think the problem came in with TWRP not wiping correctly even though it said it did. I do appreciate all of the help and advice as you guys are life-savers!
Exnyos?
sdelliott31 said:
Make sure you get the right version, whether Quality or Exnyos. I had a freeze until I got the right version.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
How do you know with version you have?
jkitsmiller said:
How do you know with version you have?
Click to expand...
Click to collapse
Wifi Only Version = P600 = Exynos processor
Lte = P605 = Snapdragon800
Gesendet von meinem SM-P600 mit Tapatalk
When I installed with TWRP 2.6.3.3 & 2.6.3.1 I got the write permission denied and then I tried with 2.6.3.0 it got hung while installing CleanRom 1.5R2. Does anyone know how to resolve this issue? Thanks
I was attempting to flash a clean copy of SkyNote Air with the 3.5 update and came across a problem when wiping the internal storage using TWRP. I've noticed this error previously when wiping the cache to install an update, but everything worked fine. When attempting to wipe the internal storage, I received a failed message. I went ahead and flashed the ROM and update, but I am now encountering a Play Store error (-24) when trying to download apps that were previously on my phone. I've researched this error and have been able to delete the previous data files using a root browser. However, I am unable to erase the folder that was causing the error (turns out that it was Battery Doctor) by using the root browser. The app attempts to erase the folder, but never does. So now I am stuck with no way to wipe the internal storage to get a clean flash of this ROM. I'm pretty sure this problem is not associated with the SkyNote ROM, so I wanted to see if I could get help here first. Thanks in advance! I have attached a picture of the error messages I was getting in TWRP.
mjt010 said:
I was attempting to flash a clean copy of SkyNote Air with the 3.5 update and came across a problem when wiping the internal storage using TWRP. I've noticed this error previously when wiping the cache to install an update, but everything worked fine. When attempting to wipe the internal storage, I received a failed message. I went ahead and flashed the ROM and update, but I am now encountering a Play Store error (-24) when trying to download apps that were previously on my phone. I've researched this error and have been able to delete the previous data files using a root browser. However, I am unable to erase the folder that was causing the error (turns out that it was Battery Doctor) by using the root browser. The app attempts to erase the folder, but never does. So now I am stuck with no way to wipe the internal storage to get a clean flash of this ROM. I'm pretty sure this problem is not associated with the SkyNote ROM, so I wanted to see if I could get help here first. Thanks in advance! I have attached a picture of the error messages I was getting in TWRP.
Click to expand...
Click to collapse
What version of TWRP ?
dicksteele said:
What version of TWRP ?
Click to expand...
Click to collapse
v2.6.3.1
mjt010 said:
v2.6.3.1
Click to expand...
Click to collapse
Is battery doctor still running? Just a guess, maybe go to application manager and do a force stop on it.
Then try and delete it.
dicksteele said:
Is battery doctor still running? Just a guess, maybe go to application manager and do a force stop on it.
Then try and delete it.
Click to expand...
Click to collapse
Thanks for the suggestion. I am unable to install it on this new flash. The folder that I was trying to delete is left over from the previous ROM. There is nothing in the folder, but I still cannot delete it and it continues to give me that same error message.
mjt010 said:
Thanks for the suggestion. I am unable to install it on this new flash. The folder that I was trying to delete is left over from the previous ROM. There is nothing in the folder, but I still cannot delete it and it continues to give me that same error message.
Click to expand...
Click to collapse
So the folder is under /data/app or /system/app ? Or ????
dicksteele said:
So the folder is under /data/app or /system/app ? Or ????
Click to expand...
Click to collapse
When going through root browser, it is data/data/com.ijinshan,kbatterydoctor_en. I have cleared out all of the folders I could, but there is one folder that remains titled shared_prefs with an unnamed folder inside with no contents. That is the only thing still associated with that app but something is causing that error in recovery and preventing the full wipe.
mjt010 said:
When going through root browser, it is data/data/com.ijinshan,kbatterydoctor_en. I have cleared out all of the folders I could, but there is one folder that remains titled shared_prefs with an unnamed folder inside with no contents. That is the only thing still associated with that app but something is causing that error in recovery and preventing the full wipe.
Click to expand...
Click to collapse
Maybe try Philz recovery. You can copy to external card. Flash, reboot to recovery from TWRP.
Worth a shot....
Been a long day, can only think of easy sh*t to try.
Bump
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I had something like that happen on my T889. I was running 2.7.0.0 and something got corrupted between a 4.1 rom and 4.3 with a backup and restore thrown in.
I ended up wiping my phone a couple times and odin flashing the last 4.1.2 rom (I still have the non-Knox bootloader).
Nothing worked. I ended up flashing the very first release firmware via Odin 2x times. I believe that it reset the partitions. I was then able to flash twrp 2.7.0.0 and then Jedi Master X to an intact file system.
Ir was kinda hairy for about 2 hrs though. Started a minor modified freak out for a minute...
Hastily spouted for your befuddlement
Hello to everybody and Merry Xmas,
Indeed using the dirty flash method using TWRP did the trick so far on my rooted Oneplus 3.
Until yesterday when everything changed. I was using OxygenOS 3.2.6 before my attempt to update my OS.
So i went to the download section of the Oneplus 3 as i always did and downloaded the OS i wanted to upgrade to which was 3.2.8 ( http://downloads.oneplus.net/devices/oneplus-3/ ). After the downloaded .zip file was finished, i copied the file in the internal storage of my phone. I rebooted to recovery mode, run TWRP, selected install, selected the .zip file of the 3.2.8 and the SuperSu file. The update went smoothly but when it tried to install the supersu file, it showed me an error message that the supersu file was corrupted and it didn't proceed. SO what happened...?? i lost everything i had on my phone and ofcourse since the supersu didn't install i had no root. I installed all my apps from scratch, installed twrp again, installed supersu to regain root and after some hours of painful work i finally had my phone updated to 3.2.8
Do you know the reason of the error? Does anybody know why that happened?
P.S
There was nothing wrong with the supersu file, because i used the same file to regain root and it installed like charm but only after i lost everthing. I also tried different versions of supersu and they all came up with the same error when i was trying to dirty flash the 3.2.8 version.
Thank you for your time
File was corrupted don't tell me how. Sometimes it just happenda.
Puddi_Puddin said:
File was corrupted don't tell me how. Sometimes it just happenda.
Click to expand...
Click to collapse
That's what i thought myself in the first place so i did the whole process all over again using the latest supersu .zip file downloaded directly from the official site and i got the same error.
So something else is going on. I used the TWRP 3.2.0 version and the 3.2.0.1 and i used the latest supersu .zip file, but in vain
I tried even using the supersu 2.64 version but it ended up with the same error
Seems that for some reason unknown i cannot perform a dirty flash anymore:crying:
dinothenino said:
That's what i thought myself in the first place so i did the whole process all over again using the latest supersu .zip file downloaded directly from the official site and i got the same error.
So something else is going on. I used the TWRP 3.2.0 version and the 3.2.0.1 and i used the latest supersu .zip file, but in vain
I tried even using the supersu 2.64 version but it ended up with the same error
Seems that for some reason unknown i cannot perform a dirty flash anymore:crying:
Click to expand...
Click to collapse
You are sure system is not read only?
I had the exact same problem. First I couldn't figure out why. But after a while I found that the reason was the downloaded zip for full 3.2.8. For some reason, unclear to me, OnePlus decided to put a line at the end of the update script that formats the whole userdata partition. Including all your photos, TWRP backups, downloaded files and more... Big warning to you all!
I solved the problem by removing the last line in the update script.
ptblad said:
I had the exact same problem. First I couldn't figure out why. But after a while I found that the reason was the downloaded zip for full 3.2.8. For some reason, unclear to me, OnePlus decided to put a line at the end of the update script that formats the whole userdata partition. Including all your photos, TWRP backups, downloaded files and more... Big warning to you all!
I solved the problem by removing the last line in the update script.
Click to expand...
Click to collapse
Not for me ,
I was on 3.2.4 with official twrp,
I flashed modified twrp-3.0.2-1.28-oneplus3.img first then,
flashed full 3.2.8 ROM , wiped cache then flashed
SR4-SuperSU-v2.78-SR4-20161115184928.zip, wiped cache again,
then flashed xposed-v87-sdk23-arm64-test1.zip wiped cache and let reboot,
Everything works fine with no data loss
Petesky said:
Not for me ,
I was on 3.2.4 with official twrp,
I flashed modified twrp-3.0.2-1.28-oneplus3.img first then,
flashed full 3.2.8 ROM , wiped cache then flashed
SR4-SuperSU-v2.78-SR4-20161115184928.zip, wiped cache again,
then flashed xposed-v87-sdk23-arm64-test1.zip wiped cache and let reboot,
Everything works fine with no data loss
Click to expand...
Click to collapse
When did you download the file from http://downloads.oneplus.net? The one that I got two days ago contains the bad part in the end that erases everything in userdata, including your downloaded SuperSU zip. See last line in updater-script in META-INF/com/google/android:
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "0", "/data");
My guess is that this file is intended for those who are reverting from the Nougat Beta (which uses F2FS on userdata partition) to 3.2.8. Since 3.2.8 uses EXT4 you need to reformat to EXT4. But for all others that just want to reflash 3.2.8 this is just bad. Without warning, everything is wiped. I did make a fresh TWRP backup before running the script, but didn't copy it to my PC. The backup was effectively wiped (many thanks OnePlus) so I had to start over again...
P.S. At the moment http://downloads.oneplus.net responds with a 403 Forbidden. Maybe new files are being published? Just wait and see :laugh:
ptblad said:
When did you download the file from http://downloads.oneplus.net? The one that I got two days ago contains the bad part in the end that erases everything in userdata, including your downloaded SuperSU zip. See last line in updater-script in META-INF/com/google/android:
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "0", "/data");
My guess is that this file is intended for those who are reverting from the Nougat Beta (which uses F2FS on userdata partition) to 3.2.8. Since 3.2.8 uses EXT4 you need to reformat to EXT4. But for all others that just want to reflash 3.2.8 this is just bad. Without warning, everything is wiped. I did make a fresh TWRP backup before running the script, but didn't copy it to my PC. The backup was effectively wiped (many thanks OnePlus) so I had to start over again...
P.S. At the moment http://downloads.oneplus.net responds with a 403 Forbidden. Maybe new files are being published? Just wait and see :laugh:
Click to expand...
Click to collapse
Thank you very much!!!! You are a problem solver, i knew something was wrong but i didn't know what or why.
Thanx to your knowledge you knew what and where to look. I wish i knew that before i did the whole update process which caused me a heap of time spent and a nervous breakdown and my precious data wiped out:crying:Shame on Oneplus 3 which added that line without warning any of us out there.
Thank you much for your time and your precious answer:good:
ptblad said:
When did you download the file from http://downloads.oneplus.net? The one that I got two days ago contains the bad part in the end that erases everything in userdata, including your downloaded SuperSU zip. See last line in updater-script in META-INF/com/google/android:
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "0", "/data");
My guess is that this file is intended for those who are reverting from the Nougat Beta (which uses F2FS on userdata partition) to 3.2.8. Since 3.2.8 uses EXT4 you need to reformat to EXT4. But for all others that just want to reflash 3.2.8 this is just bad. Without warning, everything is wiped. I did make a fresh TWRP backup before running the script, but didn't copy it to my PC. The backup was effectively wiped (many thanks OnePlus) so I had to start over again...
P.S. At the moment http://downloads.oneplus.net responds with a 403 Forbidden. Maybe new files are being published? Just wait and see :laugh:
Click to expand...
Click to collapse
I only updated a couple of days ago but I downloaded the rom from the oneplus3 forums here https://forums.oneplus.net/threads/...root-non-root-users-without-data-loss.451853/
I just assumed it was the official 3.2.8 since it was from their forum but after reading the replies on this thread I think I may have just got lucky
https://download.lineageos.org/crackling
The First One!
Do we need su for arm or su for arm64?
Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64
What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs
kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite
M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs
AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.
Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"
Can this be installed over the top of cm13.0 nightly?
Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.
M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.
Wifi
Installed tonite smoothly however no wifi - anyone else with this?
Same here, just reported a bug to the bugtracker.
Make a clean install three days ago, all works fine
pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-
Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.
M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.
I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.
ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English