Related
GUIDE: HOW TO INSTALL/UPDATE ROM WITHOUT STATUS 7 ERRORS
p.s this guide is totally noob friendly and to the best of what I could explain. But then again, I don't mind replying to kindergarten-noob level queries either.
Okay, this is for those who face these Status 7 Errors, don't panic, I found a partial-but-working fix. Your phone is not corrupted. Just follow these steps to get out:
Method 1:
1) You can simply quit Recovery Mode and go back to using your ROM as it is (that is only if you haven't Wiped Data).
2) Once you're phone's booted, download ROM Manager from the Play Store
3) Using USB Mass Storage, copy the ROM (zip) file to your internal drive.
4) Then (obviously) unplug/turn-off the USB Mass Storage mode and go to the ROM Manager app.
5) Click on Install ROM from SD Card (which means internal over here, idk why) and select the ROM. Ignore step 6 if you don't want to backup.
6) This is optional, but if you wish to come back to this ROM later click on Backup
7) Click on wipe-data if you're upgrading to another ROM (from CM10.1>CM10.2 or CM10.2>CM11) or ignore this step if you're flashing a new build (nightly/alpha)
8) The ROM will be flashed and you're good to go. If you're upgrading to a new nightly/alpha build, ignore step 8.
ONLY IF YOU'RE UPDATING TO ANOTHER ROM:
Just before the bootanimation, be ready to take out your battery and go to recovery mod with the combo keys (Volume Up+Power) and flash Gapps. (Preferably from this)
Method 2only works if you are updating to another nightly/build of the same ROM)
1) You can simply quit Recovery Mode and go back to using your ROM as it is (that is only if you haven't Wiped Data).
2) Once you're phone's booted, download ROM Manager from the Play Store
3) Using USB Mass Storage, copy the ROM (zip) file to your internal drive.
4) Reboot to Recovery
5) Flash the zip and reboot to recovery, again, and flash Gapps. (Preferably from this)
Oh and make sure to go to this thread and thank them for the gapps
credits:
ZordanKV (for ZGapps)
For my fellow Stingray users (and possibly Everest users as well, if they're having similar issues), I was one of the group of people who couldn't get data on any 4.4 roms after going through the BigPart process. After a bunch of trial and error (and some excellent suggestions from fellow community members, I was able to get data working again and I'm happily enjoying KitKat on my three-year-old Xoom. If you've got a bit of patience and an hour or so, I believe I've got the solution to help you restore your data as well.
IMPORTANT: This entire process should be completely harmless to your Xoom, and the goal here is to help the group of Stingray users who lost all data functionality to repair that issue so that they can enjoy the full benefits of Android 4.4 (and potential future updates). That said, you do this at your own risk, and in doing so, you agree not to hold me accountable if you brick your Xoom, or if it dies, loses data (you’re going to lose everything but what’s on your SD Card, so think about that before you start the process), or any other unforeseen circumstances.
STAGE 1: Reverting to Stock Partitions
1.) DISCLAIMER: Any and all data on anything but your external SD Card will be completely wiped. If there are any back-ups you value, move them to your SD Card, your computer, or a cloud storage account. There’s no getting them back once you start this process.
2.) First off, you need to make sure you have everything you need downloaded and ready. You will need the following on your SD Card:
-TWRP 2.6.3.0 touch recovery from @runandhide05
-TWRP 2.6.3.0 BigPart touch recovery from @runandhide05
-a standard partition Stingray rom (I used CM 10.1 from @Steady Hawkin, 10/28 build, which you can find here)
-(optional) GApps package for standard partition rom (I used the 02.20.2013 Unified GApps found here, but you seriously don’t need them for anything.
-your BigPart rom of choice (I went with CM 11, which you can find in this thread, but there’s also OmniRom, which you can find in this thread, both of which were kindly ported by @Schischu. If you opt for Omni, you’ll also need a flashable zip file of the Superuser app of your choice.)
-your 4.4 GApps of choice (I use the PA Modular Full GApps, but any 4.4 GApps will be fine once you’ve repartitioned)
-Universal Xoom root .zip file, created by @solarnz (which you can find here)
As well as the following on your computer:
-The Android SDK, specifically ADB and Fastboot (if you don’t have this set up yet, start at the very beginning: http://developer.android.com/sdk/index.html)
-a stock android rom for the Stingray (I used HRI66, which you can find here)
-TWRP 2.6.3.0 touch recovery from @runandhide05
And one last thing:
-A good wifi connection (either through a wireless router or using your phone or other device with a data plan)
3.) Reboot your tablet into recovery and flash the non-BigPart TWRP 2.6.3.0 touch recovery. DO NOT REBOOT YET!
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
5.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
6.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
7.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time. (I’ve done this process multiple times and each time, the amount of time that it needed on various reboots was different, so be patient if you don’t want to brick your Xoom.)
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’re back to the standard partitions.
9.) Tap the Install tab. Your external sdcard should be showing by default. Flash your standard partition rom (in my case, CM 10.1) and your GApps, if you so choose (though again, they serve no purpose).
10.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen standard partition rom. Ensure that everything loads (again: this may take some time) and go through the setup process.
11.) Go into Settings and enable developer options (Settings --->About Tablet--->tap Build Number several times until Developer options are enabled.
12.) Go into Developer options and make sure that Android debugging is checked. Now you’re ready for Stage 2.
STAGE 2: Returning to stock Honeycomb
1.) Find your stock Honeycomb rom (as mentioned earlier, I used HRI66) and unzip it into a folder of its own.
2.) Inside the folder you unzipped, you may find another folder designated MZ600_HRI66. Inside that folder, there will be four files, boot.img, recovery.img, system.img, and userdata.img
3.) Copy those files into the folder that has adb.exe and fastboot.exe (if you simply installed the Android SDK as instructed, it’ll be inside the platform-tools folder, which is itself inside the sdk folder).
4.) Connect your Xoom to your computer using a USB data cable (preferably a Motorola one if you have one available) and ensure that there is a notification that says “Android debugging enabled” (if you don’t see this notification, go back into Settings --> Developer options, and make sure that “USB debugging notify” has a check in the box next to it).
5.) Open a command prompt in the directory that contains adb.exe and fastboot.exe (Windows 7 and up, click the File tab and choose “Open Command Prompt”; if you’re on Vista or older, I can’t help you, but I’m sure Google can).
6.) Enter the following command:
Code:
adb reboot bootloader
7.) Your tablet will reboot to the red “M” logo and it should say “Fastboot protocol initiated” at the top in white letters. If so, proceed to step 8; if not, and assuming your tablet has rebooted normally, try step 6 again.
8.) Enter the following commands into your command prompt, one at a time, and let each one compete. You’ll get a series of status updates in both your command window and on your tablet as each process completes. Wait for it to say “Done!” before entering the next command.
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
9.) Once all those steps have completed, enter one last Fastboot command:
Code:
fastboot reboot
10.) Your tablet should now reboot into factory Honeycomb and you can disconnect from the USB cable. As mentioned before, this is one of those reboots that could take a few seconds up to several minutes, so just be patient!
NOTE: These next several steps are much easier to complete if you have a high-speed wifi connection. At this point, if you don’t have a data connection, don’t panic, at least not yet. I tried multiple times to activate my device on the Verizon network, and while it said it was successful each time, I never managed to get a 3G connection back. Your best bet is to connect to Wifi and continue the process.
11.) On your tablet, go to Settings --> About tablet --> System Updates. More than likely, your tablet has already started downloading the next update, so you can just sit back and wait for it to download. You’ll get a notification when the download is complete. While you’re waiting, on your computer, move boot.img, system.img, recovery.img, and userdata.img from your ADB folder back into a folder where you’ll have them on-hand if you need them again.
12.) Once you get the notification that the update is downloaded, you’ll have the option to reboot and install or install later. Choose to reboot and install. Your tablet will reboot into the stock Android recovery and install the update, then go to the “M” logo screen and more white text will appear. Wait for this to complete and your tablet to reboot again.
13.) Repeats steps 11 and 12 until you receive and install the IMM76L build (I believe that’s the one) – it’ll be Ice Cream Sandwich and your data should be working. If it’s not, then I’m not sure what to suggest. Your tablet will attempt to download the stock 4.1.2 build (JZO45M) and if it completes, it’s not a big deal, but MAKE SURE YOU DON’T INSTALL IT!
14.) Go to Settings --> Developer options and turn on USB debugging again. (If everything is grayed out, tap the On/Off slider in the upper righthand corner to make the checkbox clickable). At this point, you’re ready for Stage 3.
STAGE 3: Re-rooting
1.) On your computer, find the copy of TWRP 2.6.3.0 touch recovery from @runandhide05 (the standard one, not the BigPart one, yet), and unzip it into its own folder. Copy the recovery.img file from the unzipped folder into the same directory that contains adb.exe and fastboot.exe. IT IS CRUCIAL THAT YOU REMOVED THE RECOVERY.IMG FILE THAT YOU USED TO GET BACK TO STOCK EARLIER!
2.) Connect your Xoom to your computer via USB data cable and ensure that the USB debugging notification appears and that your computer recognizes your Xoom.
3.) Open a command prompt in the directory with adb.exe and fastboot.exe and enter the following command:
Code:
adb reboot bootloader
4.) Your tablet will reboot to the “M” logo screen and it will again say “Fastboot protocol initiated”. When it’s ready, enter the following command into your command prompt:
Code:
fastboot flash recovery recovery.img
5.) Once you get the “Done” notification in the command prompt and on your tablet, enter the following command:
Code:
fastboot reboot
6.) Your tablet will reboot, and when you see the “M” logo screen, wait three seconds and press the Volume Down key. “Android recovery” will appear, press the Volume Up key.
7.) Your tablet will now boot into TWRP 2.6.3.0 and it may “hang” at the TWRP splash screen for some time – that’s normal, wait it out, and when TWRP loads, tap the Install tab. Navigate to the root of your external sdcard (if it’s not showing by default), choose the Xoom Universal root.zip file, and install it.
8.) Tap the Home icon, tap the Reboot tab, and tap System from the reboot menu. Your tablet should boot back into ICS, but you should now have a superuser app installed (ChainsDD’s, I believe). If that’s the case, and you’ve still got data functionality, then it’s time to move to Stage 4.
STAGE 4: BigPart and KitKat
1.) Reboot your tablet into recovery (you have two options – either shut down your tablet, power it back on, wait three seconds at the “M” logo screen and then press Volume Down, followed by Volume Up when it says “Android Recovery”, or reconnect your tablet to your computer with a USB data cable, open a command prompt in your adb directory, and enter the following command: adb reboot bootloader)
2.) Reboot your tablet into recovery and flash the TWRP 2.6.3.0 BigPart touch recovery. DO NOT REBOOT YET!
3.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
4.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
5.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
6.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time.
7.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’ve successfully repartitioned your tablet back to BigPart.
8.) Tap the Install tab. Your external sdcard should be showing by default. Flash your BigPart rom (and, if you’re installing Omni, your superuser zip file, or, if you’re not flashing one of Schischu’s KitKat roms, the corresponding BigPart boot img or the ElementalX kernel). NOTE: BECAUSE THIS WASN'T SUCCESSFUL FOR EVERYONE, FOR THIS STEP, PLEASE FLASH SCHISCHU'S JANUARY 4TH VERSION OF CM 11 FOR THE STINGRAY, WHICH YOU CAN FIND HERE.
NOTE: You probably can flash your GApps at this point as well; however, I’m detailing the process as I had success with it.
9.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen BigPart rom. Go through the setup process, ensure you have data, and if you do (and you didn’t do so already), reboot and install your GApps.
NOTE: You may get com.android.phone force close errors when going through setup – if this happens, it’s a good thing – pull your SIM card and reboot, complete setup, re-insert SIM card and reboot again.
If this post helped you, then give thanks to the following people (because they did all the hard work):
@bigrushdog (for the hard work on BigPart) @realjumy (for the hard work on BigPart)
@Schischu (for the excellent KitKat roms)
@xyrcncp (for clarifications that led to a minor breakthrough) @rapson2000 (for thinking outside the box and leading to my breakthrough)
There are probably a bunch of other people who contributed that I missed, but I wanted to get this up there in case other people were still having issues.
Reserved to answer any questions that may arise.
LTE data still not working
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
variatbg said:
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
Click to expand...
Click to collapse
I've repartitioned multiple times now - once from stock, rooted Jelly Bean, and got no data, then back to standard partition and CM 10.1 with only 3G, back to BigPart with no data, then I followed the steps that I wrote up here and now I'm BigParted on CM 11 with data. So it's not the repartitioning process. I'm a testament to that. What were you on when you did the BigPart process for the first time?
Edit: if you're willing to do the whole process again, would you try installing the very first CM 11 that Schischu released? I should've specified that that's the rom I installed first after repartitioning this time. One I had working data, I updated to the latest version.
Sent from my HTC6435LVW using xda app-developers app
Help with MZ605 (Everest) stock (step 10 of stage 2)
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
LTE data still not working
webeougher said:
What were you on when you did the BigPart process for the first time?
Click to expand...
Click to collapse
I was first using OmniROM of January 12, though I can't quite recall. Then I also tried CM 11 and no dice there. Following your process, when I first reverted to CM 10.1 on original partitions, data was immediately present again.
It was there through all the reversions to stock 3.2.2, and through every OTA update Motorola sent to the device. In fact, some of the updates wouldn't even show up except over Mobile Data.
One thing that might make a difference is that this Xoom is on a business account through Verizon. It's not part of a shared data plan, but there might be a different categorization perhaps?
Anyways, I'm not going through all that partitioning and flashing again just now. I will though, eventually do a Nandroid backup and try again, once I see here or elsewhere that something might have changed for me. I have spent just too much time on this, and data is more important in this case than KitKat.
Thiago Delatorre said:
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
Click to expand...
Click to collapse
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
webeougher said:
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Not stupid at all, it could make all the difference!
I flashed the MZ605 Brazilian, MZ601 International and the one you linked. The formers booted and asked for the SIM card and the last just didn't boot. I put two different SIM cards and it didn't work, I was wondering it there were a way to circumvent the first check. I also read somewhere that the MZ601/MZ605 US Retail version didn't check for a SIM card on the first boot, but I didn't find an official stock rom for such a device (I don't even know if these devices exist).
The next trial would be with the MZ600 Verizon 3G, but I'm not that confident that it is gonna work...
Another problem is that I stopped using the 3G data on Xoom for more than one year, so I can't even tell if the SIM card would be recognized nowadays...
Beside that, what choices do we have? Is it possible to avoid the first boot SIM card verification? Is it possible to extract the baseband files from another MZ605 and put them in mine?
Do you know what kind of file/library is the baseband?
Another thing, how the modem stays working if we completely clean the internal storage of Xoom going from the official to the CM11 (on your procedure)? What I'm missing...?
Thank you very much for your guide, I didn't know how to revert the bigPart
Regards,
Thiago
So @webeougher ...I FINALLY had some time to sit down with my Xoom and try this. In the interest of verifying that this process works, I went through your guide step by step without deviation and... SUCCESS! I'm back to BigPart CM11 w/ full 4G LTE!!! Thanks for taking the time to write out such a detailed guide! It was just about perfect.
I have just two things to mention... First, the link to the stock image HRI66 didn't work. I had to look elsewhere (http://rootzwiki.com/topic/1586-stock-images/). Also, in step one of stage 4, the adb command should be "adb reboot recovery", not "adb reboot bootloader"... correct?
One last thing, at this point should we start recommending people not attempt BigPart / CM11 if they start from stock Jelly Bean?
Again, I can't tell you how stoked I am to be back up and running. This... all of it... BigPart, CM11 for Xoom, and the fix for the no data situation... it's all awesome.
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
rmkenney12 said:
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
Click to expand...
Click to collapse
It's not necessary to relock to get OTAs, so long as you're running a pure stock rom.
Sent from my Galaxy Nexus using xda app-developers app
webeougher said:
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
...
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked;
Click to expand...
Click to collapse
There was aleady a problem with Step 4... unable to mont /cache - therefore Failed to wipe /data and /cache.
Step 8 also showed NO /data-partition.
I downloaded the original Xoom stock boot,system,recovery (MZ601) MZ601_H.6.1-38-5_TMO_Germany...
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
Click to expand...
Click to collapse
boot status - done!
system status - done!
recovery status - done!
userdata status | | | | | | | | | | | | | | | | | | | | | | - done! (there have been such weird lines)
formatting cache: CAC status: -done!
Rebooting - after 60 min of M-logo I quit.
Is there a way to TOTALLY MANUALLY repartition the xoom and recover everything from scratch?
EDIT: New development: not even in fastboot mode I'm able to flash anything anymore... CWM recovery (recovery-clockwork-touch-6.0.3.2-everest.img and recovery-Tiamat-R4c-100611-1150-cwm.img) for example: status done! Still TWRP
Thank you and Question
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
semp3rfi said:
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
Click to expand...
Click to collapse
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Thank you
webeougher said:
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Awesome thanks for the reply!
What does this whole sequence actually accomplish? Is the problem that we have the wrong radios installed, and this is a way to get the right ones installed? If so is there a way to extract the new radios so that they can be installed directly?
I am just trying to understand the process, and see if it can be simplified.
Thanks much for coming up with a solution. I will try it soon.
I'm no developer, but my best theory is that these BigPart roms and kernels use proprietary files from ICS. By taking the OTA to JB, something changed. I tried flashing other radio files and nothing worked, so when it was suggested that only people who had taken the OTA were losing data, I went through this process just on a whim to see if it worked. When it did, I didn't really think much else about it.
Sent from my HTC6435LVW using xda app-developers app
thx
The for this topic really informative
Wow
Talk about a long process but it worked for me! Thank you so very much!
I did have an issue with the google keyboard fc on me after going through the whole process but I ended up downloading the go keyboard (not selecting it) and for some reason that took care of the Google keyboard fcing.
I also used the omnirom instead of cm.
Again, thanks for your hard work!
Wanted to thank you. I pulled out the ole Xoom and flashed Omni and the data wasn't working... But you're instructions got me back on track. Thanks again bro! :good:
This thread is for Japanese s7 edge scv33 that’s being booted up with SC-02H firmware after carrier unlocking.
This guide covers/ will help you
• Install Latest available Twrp recovery (Caution: will Trip Knox!)
• Magisk Root
• Remove Japanese carrier bloatwares.
• Make the default device language to English.
• Install latest available updates via default or, will add additional useful Samsung apps (will update the device stock apps like SMS, Touch wiz launcher, AOD, Contacts, etc to latest available.
• Various tweaks like sms delivery options turned on by default, always on display turned on by default etc-etc.
Overall, this guide is to help your Japanese S7 Edge scv33/SC-02H to look more like a standard international model.
So let’s begin.
Step 1:
All required files can be downloaded from here
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Caution. Backup all of your personal data. This process will need you to factory reset or will erase all of your data including your personal photographs, apps, videos etc.
You will also require to have a fresh piece of sd card (16 gb or more recommended) to store the twrp nandroid backup if anything goes wrong.
So, First, you will need to remove the modifications that were made to your device stock boot image. If you have flashed the modified kernel or have rooted using super-su, then, you will need to undo all the changes. You can flash the stock boot image file only but I would recommend you to flash the whole latest firmware that you can find easily over UPDATO Firmware website to start better all over again.
Here is the link to the latest SC-02H android 7.0 firmware:
http://updato.com/firmware-archive-select-model?record=AD3D69507E2D11E7963AFA163EE8F90B
Download and extract it. You will find 5 files. You can ignore the HOME……. file. Flash the 4 firmware file using latest Odin.
After flashing, let it boot up. Finish the setup wizard and turn off the device.
Step 2:
Flash the TWRP that you downloaded from here. Download Link is same as above.
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Twrp Bug: Device will reboot to twrp recovery if you choose to power down the phone from recovery option. You will have to choose “Reboot System” from twrp menu to solve this.
After installing, boot into twrp recovery. Go to Wipe and at the bottom right, you will have option to format data. Perform a Format data process. Then, make a TWRP backup to your sd card.
I repeat. Make a backup. This will help u a lot if anything goes wrong
Step 3:
Time to install magisk.
Extract root.zip file and there you’ll see magisk.zip
Flash this magisk installer file from twrp and reboot the device.
Install the latest magisk manager app apk.
Now your device is rooted with the latest magisk available.
Step 4:
Time to remove the bloatwares.
You will need ES file manager and System app remover from playstore.
Grant super-user access to both apps. Navigate to device/system/preloadFactoryResetOnly using es file manager and delete all the contents inside that folder.
Download the apps.zip file from here
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Extract it to your pc. Copy all the extracted apps including their folder to your device and paste it inside the same path i.e, device/system/preloadFactoryResetOnly folder.
Important: You will need to change the copied each app file permission to RW-R-R.
You do-not need to change the folder’s permission. But you will need to change the each apk’s permission one by one. Long press on the apk and then go to properties. Tick mark on (read-write, read, read).
But there will still remain some Japanese DoCoMo bloatwares. You will not be able to remove it by simply using system app remover.
So, use the system app remover app to track down the bloatware’s location by long pressing and delete it by using es file manager. Remember, only delete the bloatwares that are found in device/system/priv-app and device/system/app folders.
Caution:
You do-not need to super trim down your system in hopes for getting more internal space or whatsoever by deleting the bloatwares that you don’t know. Just delete the DoCoMo apps that you can see in the app drawers.
So be aware.
Factory reset after the above step.
Step 5:
Now comes the last part:
CSC Tweaks:
Download the 3 modified csc files from above link. Copy and replace them to path device/system/csc
Change the copied file permission to (rw-r-r).
To change the default device language and set the sms delivery option on by default, copy the Customer.xml file to your pc and edit it by using Notepad++.
Find the line as shown as in the picture below and modify as in it. Save it and replace it back to where it was from which will be device/system/csc and change its file permission again to rw-r-r.
Now turn off your device and boot into TWRP recovery. Perform a factory reset and reboot.
You will have latest apps with all the custom changes including your default language changed to English.
No need to install magisk manager apk as it is already there in the apps.zip folder.
Done!
Credit goes to all the rightful owners.
Special thanks to Mr. Buddha Tuladhar again for the phone.
Android 8.0 rom..and root/ twrp for scv33/sc-02h
Stock rom is in the link given
then flash
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
Boot to twrp and install:
1: no-verity-opt-encrypt-6.0.zip
2: Magisk-vXX.X.zip
Download link for all files
https://www.mediafire.com/folder/kn5cg1rolfjas/
Well done sir! thank you very much.
It would be wonderful if you can upload an odin flashable all in one file.
Appreciate your time and effort very much!
01. Flash 2017.03.07_SC02HOMU1BQC4 with Odin (upload by tienquynh93)
02. Flash 2017.04.07_1BQC4_Gobal_ManhIT.zip with Odin (upload & rebuild by ManhIT)
03. Flash 2017.03.17_TWRP_3.1.0 with Odin (AP) (Rebuild by ManhIT)
3.1 Reboot to TWRP Flash:
3.2 MaGisk to root (topjohnwu)
3.3 xPosed SDK 24 (Android 7.0) (rovo89)
This rom support multilanguage with defaulft vietnamese.
Lasest firmware: 2017.12.12_SC02HOMU1BQL3
Confused.
DariasLuc said:
01. Flash 2017.03.07_SC02HOMU1BQC4 with Odin (upload by tienquynh93)
02. Flash 2017.04.07_1BQC4_Gobal_ManhIT.zip with Odin (upload & rebuild by ManhIT)
03. Flash 2017.03.17_TWRP_3.1.0 with Odin (AP) (Rebuild by ManhIT)
3.1 Reboot to TWRP Flash:
3.2 MaGisk to root (topjohnwu)
3.3 xPosed SDK 24 (Android 7.0) (rovo89)
This rom support multilanguage with defaulft vietnamese.
Lasest firmware: 2017.12.12_SC02HOMU1BQL3
Click to expand...
Click to collapse
Is it necessary to flash 2017.03.07_SC02HOMU1BQC4 and 2017.04.07_1BQC4_Gobal_ManhIT.zip ? Or can i just simply flash the latest firmware 2017.12.12_SC02HOMU1BQL3 and root my phone?
Thank you, great job on compiling all this! It took quite a bit of study, but I understand now. Thanks again.
This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)
Hi
audioqueso said:
This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)
Click to expand...
Click to collapse
Hi, what Twrp Work in Android 8.0 you can Shared whith me?
3.1.1, 3.2.1 and 3.2.3
They all worked. I had originally started working with 3.1.1 and 3.2.1. However, I tried the latest 3.2.3 because I couldn't get NFC to work. I did it just to give it a try.
But all three versions that I listed had no problem installing.
Are you having trouble installing TWRP?
Yes, recovery is not remplace
Will you have a link and instructions for Android 8?
How to install TWRP on Galaxy S7 Edge (SC-02H)
TWRP Installation:
1) Download and installed Odin 3.12.5 (or the latest)
2) Turn off phone. Pressed and hold Volume Down+Home+Power at the same time to get to Download Mode. Once you see the Download Mode page, let go of the buttons. Press Volume Up to accept. (To cancel, press Volume Down )
3) Open Odin and click on AP. Load the TWRP file from your computer.
4) On the second tab of Odin, uncheck "Auto-reboot" (you need to have auto reboot disabled in order to successfully install TWRP). Press 'Start'.
5) Once the Odin status changes to a green "Pass", the installation is complete.
At this point, your phone will still be in Download Mode screen. For this step only, you will need to do two steps back to back. First, press and hold Vol.Down+Home+Power in order to get the phone out of the Download Mode screen.
As soon as the screen changes, press Volume UP+Home+Power.
You will see TWRP load.
That's it. You have successfully loaded TWRP.
From here on out, you will need to press Vol. Up+Home+Power in order to boot into TWRP. If you reflash your phone back to stock firmware using Odin, you will lose TWRP and will need to repeat these steps in order to install TWRP again.
audioqueso said:
TWRP Installation:
1) Download and installed Odin 3.12.5 (or the latest)
2) Turn off phone. Pressed and hold Volume Down+Home+Power at the same time to get to Download Mode. Once you see the Download Mode page, let go of the buttons. Press Volume Up to accept. (To cancel, press Volume Down )
3) Open Odin and click on AP. Load the TWRP file from your computer.
4) On the second tab of Odin, uncheck "Auto-reboot" (you need to have auto reboot disabled in order to successfully install TWRP). Press 'Start'.
5) Once the Odin status changes to a green "Pass", the installation is complete.
At this point, your phone will still be in Download Mode screen. For this step only, you will need to do two steps back to back. First, press and hold Vol.Down+Home+Power in order to get the phone out of the Download Mode screen.
As soon as the screen changes, press Volume UP+Home+Power.
You will see TWRP load.
That's it. You have successfully loaded TWRP.
From here on out, you will need to press Vol. Up+Home+Power in order to boot into TWRP. If you reflash your phone back to stock firmware using Odin, you will lose TWRP and will need to repeat these steps in order to install TWRP again.
Click to expand...
Click to collapse
Could you provide a link to the latest version of twrp?
Joslem said:
Could you provide a link to the latest version of twrp?
Click to expand...
Click to collapse
http://bfy.tw/KPwS
For Root SC02HOMU1CRH5
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
no-verity-opt-encrypt-6.0.zip
Magisk-vXX.X.zip
From: https://itok01.com/2018/09/23/root-sc-02h/
Global Rom for SCV33/SH-02H 8.0
https://drive.google.com/uc?id=1MiYK-VSYLRH_9T43sYbfgfvvKqqwRJjO&export=download
Go to Recovery and run "graphic test" > "Format Data" > ReBoot.
Install Magisk to root:
https://forum.xda-developers.com/showpost.php?p=77942910&postcount=14
DariasLuc said:
For Root SC02HOMU1CRH5
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
no-verity-opt-encrypt-6.0.zip
Magisk-vXX.X.zip
Click to expand...
Click to collapse
it works, thank you very much!!
S7 Edge Docomo sc-02h lost imei after factory reset
Sorry for being off topic, but please cam someone help me out in the regard that my S7 Edge Docomo sc-02h lost imei after just the factory reset. Any recommendation what i can do to get it back as my sim signals are now gone as well that means i cant make any calls or msg whatsoever.
Thanks in advance
usmann93 said:
Sorry for being off topic, but please cam someone help me out in the regard that my S7 Edge Docomo sc-02h lost imei after just the factory reset. Any recommendation what i can do to get it back as my sim signals are now gone as well that means i cant make any calls or msg whatsoever.
Thanks in advance
Click to expand...
Click to collapse
you just need working 3G sim card to fix your imei... after put 3g sim card to your phone and reboot imei will appear and you can use your normal sim again!
everyonesweird said:
This thread is for Japanese s7 edge scv33 that’s being booted up with SC-02H firmware after carrier unlocking.
I need help in order to compile all of these tweaks into an Odin flashable file so that users can simply flash it and make the changes.I would also like to add App-lock feature and international Samsung keyboard with secondary symbol in but can’t seem to make it work. So, if you are interested or have tried, please let me know.....
Click to expand...
Click to collapse
Very thank, im removed almost bloat of AU. But, what happen if i dont have CSC folder? and how to add Vietnamese laguage to SCV33 (AU) stock rom?
audioqueso said:
This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)
Click to expand...
Click to collapse
I am also struggling about this. I think the problem only concerns TWRP or Root. However I think the problem is TWRP, because when I flash stock rom, nfc ok. Next, i flash TWRP (not root yet), nfc has been disabled now. So i think TWRP causes this problem. However, if i reflash stock recovery, everything remains unchanged, NFC is still turned off. so it is very contradictory.
Now I think of a test, after installing all (root), backing up all android. Then flash again with stock rom, check NFC. Finally, restore the backup. The goal is to completely remove the TWRP from the process but still root the device. I hope it will work. Will try if i have the time
Hello everyone, lets root your ulefone power 5 and if you want: flash another rom. I'm kinda new here so don't mind if I'm telling things in a stupid way.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Ok, first of all, massive shout out to @gamr13 and @Dukino and @CarelMinnaar for providing some of the files.
Original threat: https://forum.xda-developers.com/android/help/ulefone-power-5-twrp-root-t3848501/
Link to the website I copied and translated the guide from: https://www.chinahandys.net/android-9-auf-dem-ulefone-power-5-anleitung/
Code:
If you are using any custom rom on your phone, I strongly
recommend reflashing your whole phone with the original
firmware provided by ulefone. I'll add the link.
I assume you know how to flash, otherwise search on youtube or
request it and I'll add a guide.
Most files you may need and worked in my case:
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
More files in the spoiler below.
Let's begin!
First of all, make sure your phone is recognized by your pc and use a good cable. (the original one broke pretty quickly in my case)
Next, go to system and search for 'build number'.
Tap it untill it says: you are now developer.
Go to developer options and enable: OEM unlocking. Then power your phone off.
Next, download the fastboot and adb zip file I provided. If you already use adb and fastboot, download the recovery zip and you know how it works.
Extract the 'android' folder and put it on the root of your system disk (mostly /C).
Next, go to your command prompt and type: cd \android
Now you start your phone in bootloader. Press and hold volume up and power and let your phone cycle untill you enter bootloader.
Select 'fastboot'.
Plug your phone into your pc and type in the command prompt: fastboot devices
Now you should see the serial number of one device (in my case it was something like ABCD1234567890). If not, install some fastboot drivers and use device manager to select the fastboot driver for your phone.
Then, type: fastboot oem-unlock
Select Yes on your phone and let it reboot.
Re-enter fastboot on your phone.
To be sure: fastboot devices
Flash your recovery using: fastboot flash recovery TWRP_3.2.3_Ulefone_Power_5_AND_5S.img
Then, you need (maybe not but just do it) to reboot straight into bootloader. So press volume up and power untill it shows the bootloader, and then select recovery.
Now your phone may be encrypted or something like that. Select 'Wipe' and accept.
Next, put your gsi (A only, arm64), gapps and/or your decrypt file on your sdcard and flash it!
Known bugs:
- VoLTE - I needed to use a simcard from a different provider to get calling working.
- Hotspot
- Seems sticky to 2.4G?
- MTP not working in recovery
- When waking up your device you may encounter some weird behaviour. Just wait a second and it's gone.
Spoiler: The old guide
Files:
https://mega.nz/#!N2hijYAB!0LLshTYgW...SUfOKpV5BELo4A (seems to be down and dated)
or
http://www.mediafire.com/folder/55lxwzgdd938t/ulefone_power_5
or
https://drive.google.com/drive/folders/1totRbNzS1RBeSO66WW2O0hG2kPGbGERl?usp=sharing
So, the method.
1.) In the files above you will find a file ulefone power 5 twrp root. Extract it and find the map called SP_Flash_Tool. Open this and run the flash_tool.exe. Please download the firmware.zip and the flashtool.zip and extract them. Put the decrypt.zip on your sdcard. (in some cases you need also the 'MT65xx_USB_VCOM_DRIVERS.zip' to install properly)
2.) Once opened the flashtool.exe, go into the options menu, click the connection tag and make sure USB is selected. make sure its set to Full speed and auto detect.
3.) Browse through the map sp flashtool and use the MTK_AllInOne_DA.bin file as the DA file (may be selected by default).
4.) Select the scatter file found in the firmware folder with all the .img files. Its called: MT6763_Android_scatter.txt
5.) While unplugged, hold the volume up and power button to load the phone into it's bootloader mode.
(if your phone is bricked in any screen skip this step) Turn your phone totally off.
6.) Set the SP flash tool to download only and press the download button to start the download.
7.) Plug your phone in and as expected, nothing will happen.
8.) Now, hold the volume up and power button continuously. Keep holding it until the SP Flash tool starts start downloading and the bottom bar loads things. Be sure you immediately loose the buttons, otherwise it soft-bricks itself so you have to start the download again.
9.) Be patient and wait until you get the green check mark, then unplug your phone.
10.) Boot directly back into bootloader. (vol. up and power, hold it untill you get the fastboot screen. Sometimes it takes up to 4 reboots), select and boot recovery.
11.) Now it's all for you! Put something on your sdcard and flash it. Mine seems to be broken so I used an usb stick, wich is working fine. MTP is not working in the recovery.
12.) CarelMinnaar published the new decrypt file, wich I thrust more than the previous russian one. Put it on your sdcard, do a full wipe and install. This should ban the forced encryption.
12.)
A.) For root: flash the magisk .zip file from the files above or search on the internet for the right one.
Thanks to @gamr13
1. Reboot to TWRP
2. MAKE A FULL BACKUP (every partition checked)
3. Mount System and Vendor
4. Go back to the main screen
5. Advanced > File Manager
6. Go to Vendor
7. Go to the "lib" folder
8. tap libdirect-coredump.so and Copy File
9. Go to /system/lib
10. paste the file in here
11. Go to /vendor/lib64
12. Copy libdirect-coredump.so
13. Paste in /system/lib64
14. Install Magisk
15. Reboot
16. Go to Magisk > Download > Search for "SafetyPatch" by hackintosh5
17. Reboot and enjoy
Click to expand...
Click to collapse
B.) 1. For another rom: search overhere for a system.img Download the A only variant. I'll keep you updated below. I am not using this phone frequently anymore, so updates may come later. @gamr13 will keep you updated
2. Wipe cache, dalvik cache, data and System.
3. Select flash .img and flash the .img at your System.
4. Flash magisk or other mods.
5. There may be some bugs. Sms was not working on the phh treble for me. The launcher crashed also.
13.) Boot up
14.) Enjoy! Feel free to ask anything.
Got some pm's asking what to do if stuck on boot/recovery, this video explains the return to stock process. In short: start spflashtool, select the scatter file in the stock firmware, select download only, firmware upgrade or download and format. Plug your cable in. Then click start, and press vol. up and power until you hear the 'new device found' sound on your pc and let it go. Then just reboot.
Feel free to use his files or mine. Doesn't really matter.
Working gsi images
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Thanks to @gamr13 :
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...309-UNOFFICIAL-treble_arm_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
Android 11
Havoc os
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Not the quickest, but looks nice with the pixel inspired interface. No extra bugs found.
Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.
oes20 said:
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Click to expand...
Click to collapse
Does Magisk work for you on these GSIs?
gamr13 said:
Does Magisk work for you on these GSIs?
Click to expand...
Click to collapse
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience
oes20 said:
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience
Click to expand...
Click to collapse
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.
gamr13 said:
Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.
Click to expand...
Click to collapse
It is a problem, I know. We can't do anything than reporting these problems to the Magisk team and hope for help. In my case, Magisk worked for root, but not for the modules. I got also knocked out of Snapchat because of Magisk. Just one of those little things that are part of our development hobby
gamr13 said:
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.
Click to expand...
Click to collapse
In my case I got root acces working in Magisk. I apologize for that part about the vendor. You are right about that. I am trying my best to share my experience. I am no expert in anything.
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Android 10 and TWRP...
Me. I tested 10 different roms of Android 10 and none works correctly .. I always stay on the Android logo that lights up in a loop. if you find information and manipulations or roms that work and are stable, send me the link or download. Thank you. And if you also find a new TWRP custom 3.3.0 or 3.3.1, put the download here. Thanks ?
gamr13 said:
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.
Can not install ANDROID 10 AOSP v201 !
Hello, I tested all versions of Android 10 phhusson and none works ..
phhusson offers to do this manually but I do not understand where to put it and how to run it!
phhusson: "need to manually setprop ro.skia.ignore_swizzle true"
If you have a solution to my problem, tell me here because I'm tired of Android 9 .. I'd like to upgrade to the latest version and not bother with this Android 9 .. Thanks
Android 10 GSIs currently do not work with the Ulefone Power 5.
gamr13 said:
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.
Click to expand...
Click to collapse
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!
fernseher said:
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!
Click to expand...
Click to collapse
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP
PetroChina said:
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP
Click to expand...
Click to collapse
This!
A guy was able to install Android 10 with another TWRP
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD
PetroChina said:
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD
Click to expand...
Click to collapse
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!
gamr13 said:
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!
Click to expand...
Click to collapse
I will tell you everything, I must first test it personally and after the upload on Mediafire.
In my opinion, I hope that the scienceillements of the TWRP will not be there
I have the files but I can not install it because it did not explain very well the steps ..
http://www.mediafire.com/file/eqzhwznxxr9qlsf/TWRP_3.3.1_UlefoneP5.img/file
http://www.mediafire.com/file/1sf9mi9qlcv5ari/no_encryption_mod.zip/file
He told me this and I do not understand much and it is not clear enough... : no encryption mod first before install latest twrp if your phone doesnt boot from old twrp to twrp 3.3.1
I am not responsible for bricked devices, what you do with this information is your responsibility not mine.
Wanted to post this to help people who were stuck like me for a while. I recently discovered a file type called gsi, which from what I've understood is basically a universal rom. I will not be linking any of them but a quick google search got me havoc os and descandent.
*Prerequisites:
-Odin 3.0 and up
-Pc with galaxy m21 drivers and data usb-c cable
-TWRP see other posts
-Custom rom and disable dm-verity of some kind possibly also opengapps
-At least some knowledge and/or experience with rooting, flashing, etc.
1. Go to sammobile and find firmware for SM-M215F and choose you region. You will need to make an account, but won't need the payed subscription, just choose free option. (or if you have already have it skip this step).
! This will be a backup for a fresh install in case something goes wrong !
2. Put all the zip files on an sd-card by going into twrp and connecting the usb cable.
3. Wipe everything by doing a format data.
4. Install the os of your choice, followed by dm-verity then optionally opengapps and root (i don't recommend it at the moment but your choice)
5. wipe cache and delvic
6. reboot to system
! In case it went wrong, you want oneui or any other reason to back out (data will be lost still but phone will work) !
extract all files from the downloaded firmware
open odin and start download mode on phone (press vol up + down + power and connect usb)
put the file beginning with ap in odin in ap, bl in bl cp in cp.
put home in csc and leave userdata empty
start, reboot will take a while.
Thanks for sharing