OK to start off this thread is meant to continue the work done in the thread here huawei-ascend-xt2-h1711 their were some good people working on stuff their but most seem to have moved on.
I decided to pick up the Elate this week from Best Buy and thought it might be time to start a new thread on rooting and restoring the Cricket version of this phone.
Rooting the H1711z Huawei Elate
First step is to unlock your bootloader at Huawei here > https://emui.huawei.com/en/unlock_detail
Well it seems Huawei is no longer unlocking the bootloader so you need to pay DC Unlocker to unlock your bootloader
follow the instructions posted here >> https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Also please make a backup of your own boot.img as soon as you flash TWRP before flashing the patched _boot.img provided
~Huge thanks to @aslezak for these instructions~
Root instructions: (I used Magisk Manager v5.5.3 boot.img patching to create the boot.img)
here is the stock boot.img for the Elate H1711z
I am not responsible if you brick your device. I didn't brick mine, but if you don't type the correct commands you could be in trouble
Copy this patched_boot.zip to your sdcard. You can download it from the device directly if that's easier. Insert the sdcard into the phone if it wasn't there already (e.g. if you downloaded from a computer).
Reboot phone into fastboot. The easiest way is, if phone is on, unplug phone from USB, hold power button / select "Power Off". Hold VolDown+Power. Phone will boot into fastboot mode.
(skip this step if you've already flashed TWRP) Flash TWRP into your recovery partition. The link was provided in an earlier post by yuweng twrp-xt2-v3.img
plug usb cable in (from phone to computer). From your computer / cmd.exe window, cd \adb:
fastboot devices #make sure computer adb/fastboot sees your device
fastboot flash recovery twrp_xt2_v3.img
Boot into TWRP. From the above step, you should "fastboot reboot", immediately unplug phone from USB, then
With the phone unplugged from the computer, hold VolUp+Power. Release power after the device reboots. It might take a couple tries .. select reboot from eRecovery if that starts instead. Alternatively you can boot into recovery through adb via "adb reboot recovery".
Tap "Keep Read Only" when TWRP starts.
Tap "Install", then tap "Install Image" at the bottom. Browse (Up a Level) then "external_sd"
If you unzipped the patched_boot.zip you will see patched_boot.img here. Select it.
Select "boot" (uncheck "recovery") partition to flash.
Swipe to confirm Flash
Tap "Reboot" once it's completed.
You should be rooted!
Note: if Magisk Manager does not appear in your list of installed applications, download & install it from here latest Magisk Manager. Without this, you won't be prompted to allow root!
Click to expand...
Click to collapse
Note: Magisk Manager will update you to version 16 on first run, it's OK to update in fact feel free to flash it in recovery before you reboot if you want it.
A couple notes about twrp_xt2_v3.img
when you start TWRP choose keep system read only - Unless your planing to restore a backup then choose to make system writable
You cannot backup or restore /data (it's encrypted so don't even try)
Do not use Wipe / factory reset or format data unless you have a good working backup of your userdata partition that you dd to your external_sd yourself see below
From TWRP / adb shell
paste these commands
dd if=/dev/block/bootdevice/by-name/userdata | bzip2 -9f > /external_sd/userdata.img.bz2
to restore--> bzip2 -dc /external_sd/userdata.img.bz2 | dd of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system | bzip2 -9f > /external_sd/system.img.bz2
to restore--> bzip2 -dc /external_sd/system.img.bz2 | dd of=/dev/block/bootdevice/by-name/system
again thanks go to aslezak
When choosing a backup always prefer the image instead of the stock files (system image - custom image - vendor image are best )(Never choose both system and system image at the same time it's too big and a waste of time and space)
when you exit TWRP do not choose to install the twrp app
Also be sure and thank aslezak for his post here > https://forum.xda-developers.com/showpost.php?p=75115521&postcount=286
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Restoring your phone to Stock
We now have the B120 Stock dload update See here >> https://forum.xda-developers.com/showthread.php?p=76902495&highlight=dload#post76902495
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this will completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Extra's By Request
Here's the XT2_Stock_Rom and XT2_Magisk_ Rom here > https://androidfilehost.com/?w=files&flid=266256
If you like to try my CleanRom for the Elate I uploaded it here >> Elate.CleanRom.v2.zip
flashing instructions are the same as the stock file above
here's whats added/removed
Apps deleted from /Data/hwinit/:
Google Editor Slides
Google Editor Sheets
Google Editor Docs
Apps deleted from Cust:
the entire h1711 folder
AT&T Remote Support
myAT&T
AT&T Visual Voicemail
AT&T Hot Spots
Google Talkback
OMACP
Apps deleted from System:
Amazon shopping
App select
Call Protect
CricketWiFiManager
Device Help
Deezer
Facebook
Facebook App Installer
Facebook app manager
Gmail
Google Duo
Google Chrome
Google Drive
Google Maps
Google Play Photos
Google Play Video
Google Play Music
Google Text to Speech Engine
Ignite
Lookout
myCricket
Protect Plus
Setup & Transfer
Added
FX Root File Manager (as a system App)
Magisk V16 (as a system App)
QuickBoot Reboot (as a system App)
I didn't include Xposed because it's useless without a decrypted Data partition
Note: To remove the Cricket bootanimation, use the FX File Manager with root permission and rename
..\system\version\special_cust\H1711z\cricket\us\media\bootanimation.zip" to bootanimation.zi_ and reboot
I got tired of seeing the error in twrp_v3 about not mounting patch_hw and fixed it ->> Here
you can unzip it and flash it to recovery with TWRP or fastboot
NOTE: added by scrungydoolittle I had a problem with the bz2 image. I prefer to not run it through bz2
dd if=/dev/block/bootdevice/by-name/userdata /external_sd/userdata.img
to restore--> dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system /external_sd/system.im
to restore--> dd if= /external_sd/system.img of=/dev/block/bootdevice/by-name/system
Of course, the downside is you need a fairly large external sd card.
@scrungydoolittle Please edit you post and remove the Quote of the first post
also the file you posted is not for this phone please remove the link
as to you having problems with the bz2 image they work fine if you follow the instructions
I instructed the user to create their OWN backup of userdata before they format / wipe their data partition
this file most likely contains the users IMEI and should not be shared.
clsA said:
@scrungydoolittle Please edit you post and remove the Quote of the first post
also the file you posted is not for this phone please remove the link
as to you having problems with the bz2 image they work fine if you follow the instructions
I instructed the user to create their OWN backup of userdata before they format / wipe their data partition
this file most likely contains the users IMEI and should not be shared.
Click to expand...
Click to collapse
O.k. I removed the link. It was for the H1711 AT&T phone as it turns out.
And I don't think that image has the IMEI in it, because it is clearly the /system image, and I don't think that data is stored in that partition.
Otherwise all of the posted system images would have the same issue...
scrungydoolittle said:
O.k. I removed the link. It was for the H1711 AT&T phone as it turns out.
And I don't think that image has the IMEI in it, because it is clearly the /system image, and I don't think that data is stored in that partition.
Otherwise all of the posted system images would have the same issue...
Click to expand...
Click to collapse
Thanks ...yeah the userdata contains the IMEI not the system.img
Sent from my LG-H910 using Tapatalk
I would not share a userdata backup unless it was after a factory reset and before I entered any personal account information or data. Agree with you on that
I'd love to see a reliable reference that says userdata contains the IMEI or if you know specifically where it's stored, because l thought IMEI is stored in a totally different partition.
clsA said:
Thanks ...yeah the userdata contains the IMEI not the system.img
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
divineBliss said:
I would not share a userdata backup unless it was after a factory reset and before I entered any personal account information or data. Agree with you on that
I'd love to see a reliable reference that says userdata contains the IMEI or if you know specifically where it's stored, because l thought IMEI is stored in a totally different partition.
Click to expand...
Click to collapse
IMEI is stored in data/data/com.android.phone
Thank you
Found the IMEI in
/data/data/com.android.phone/shared_prefs/
com.android.phone_preferences.xml on my H1611 after your post.
I'm guessing the IMEI is copied from another partition, but the fact that it's in /data is news to me.
I wonder if the IMEI is in the above file after a factory reset , but I'm not planning to find out anytime soon .
People, be careful sharing your userdata partition backups and other sensitive data containing partition backups out there - unless of course you don't give a crap about security - which you should preface up front so as to not mislead uninformed people of the risks involved in sharing those sensitive data partitions.
clsA said:
IMEI is stored in data/data/com.android.phone
Click to expand...
Click to collapse
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
clsA said:
Restoring your phone to Stock
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Click to expand...
Click to collapse
freedomwarrior said:
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
Click to expand...
Click to collapse
Nice.
What partitions does this install?
And can you make this for the H1711 At&T phone?
freedomwarrior said:
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
Click to expand...
Click to collapse
No don't use this on the XT2
I / you need system/boot/recovery/ and cust.img files from a XT2 to build it.
Sent from my LG-H910 using Tapatalk
clsA said:
No don't use this on the XT2
I / you need system/boot/recovery/ and cust.img files from a XT2 to build it.
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
If I send you (or point you to )
system
boot
recover
and cust images could you create one?
The image for system is available, a patched bootloader that installs magisk, an unpatched boot loader, the recovery and e recovery are the same.
I'd like to see 2 flashable zips.
1. that does stock
2. that installs twrp and magisk.
I have all those, but I'm not sure how to make the zip. Is it simply a matter of opening it in a zip prgram and replacing the mentioned image files
with appropriate ones?
scrungydoolittle said:
If I send you (or point you to )
system
boot
recover
and cust images could you create one?
The image for system is available, a patched bootloader that installs magisk, an unpatched boot loader, the recovery and e recovery are the same.
I'd like to see 2 flashable zips.
1. that does stock
2. that installs twrp and magisk.
I have all those, but I'm not sure how to make the zip. Is it simply a matter of opening it in a zip prgram and replacing the mentioned image files
with appropriate ones?
Click to expand...
Click to collapse
I have the Stock system.img and erecovery.img
put the others in a google drive and I'll build them
clsA said:
I have the Stock system.img and erecovery.img
put the others in a google drive and I'll build them
Click to expand...
Click to collapse
Here is the cust.img I just pulled from my XT2 using the dd command.
https://drive.google.com/open?id=1euUHZiJrzfyUVNqgOT76rTk45clPwv9F
Here is a copy of the stock boot I have had sitting on my hard drive.
https://drive.google.com/open?id=1-dAJuwgYdM9F3fBn4dU3x9s74SucocBP
And here is a copy of patched boot (with magisk) if you need it.
https://drive.google.com/open?id=1Tfb7zkcX6auoYEVnMLKDN6tibfzHSPEW
And thank you in advance for doing this! :good:
freedomwarrior said:
Here is the cust.img I just pulled from my XT2 using the dd command.
https://drive.google.com/open?id=1euUHZiJrzfyUVNqgOT76rTk45clPwv9F
Here is a copy of the stock boot I have had sitting on my hard drive.
https://drive.google.com/open?id=1-dAJuwgYdM9F3fBn4dU3x9s74SucocBP
And here is a copy of patched boot (with magisk) if you need it.
https://drive.google.com/open?id=1Tfb7zkcX6auoYEVnMLKDN6tibfzHSPEW
And thank you in advance for doing this! :good:
Click to expand...
Click to collapse
Files are uploading now > https://www.androidfilehost.com/?w=files&flid=257749
Instructions are the same
Backup anything on internal storage it will be wiped
To Install
1) Download and copy the Rom to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / your_rom.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Click to expand...
Click to collapse
after flashing the Magisk rom install the magisk manager and update to v16 (or whatever the newest is)
Awesome! Thank you so much for these. They will definitely come in handy! Much Appreciated!! :good::
clsA said:
OK to start off this thread is meant to continue the work done in the thread here huawei-ascend-xt2-h1711 their were some good people working on stuff their but most seem to have moved on.
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
I decided to pick up the Elate this week from Best Buy and thought it might be time to start a new thread on rooting and restoring the Cricket version of this phone.
Rooting the H1711z Huawei Elate
First step is to unlock your bootloader at Huawei here > https://hwid5.vmall.com/CAS/portal/...ndex&loginChannel=22000000&reqClientType=2023
Also please make a backup of your own boot.img as soon as you flash TWRP before flashing the patched _boot.img provided
~Huge thanks to @aslezak for these instructions~
Note: Magisk Manager will update you to version 16 on first run, it's OK to update in fact feel free to flash it in recovery before you reboot if you want it.
A couple notes about twrp_xt2_v3.img
when you start TWRP choose keep system read only - Unless your planing to restore a backup then choose to make system writable
You cannot backup or restore /data (it's encrypted so don't even try)
Do not use Wipe / factory reset or format data unless you have a good working backup of your userdata partition that you dd to your external_sd yourself see below
From TWRP / adb shell
paste these commands
dd if=/dev/block/bootdevice/by-name/userdata | bzip2 -9f > /external_sd/userdata.img.bz2
to restore--> bzip2 -dc /external_sd/userdata.img.bz2 | dd of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system | bzip2 -9f > /external_sd/system.img.bz2
to restore--> bzip2 -dc /external_sd/system.img.bz2 | dd of=/dev/block/bootdevice/by-name/system
again thanks go to aslezak
When choosing a backup always prefer the image instead of the stock files (system image - custom image - vendor image are best )(Never choose both system and system image at the same time it's too big and a waste of time and space)
when you exit TWRP do not choose to install the twrp app
Also be sure and thank aslezak for his post here > https://forum.xda-developers.com/showpost.php?p=75115521&postcount=286
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Restoring your phone to Stock
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this will completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
By request I have also added the XT2_Stock_Rom and XT2_Magisk_ Rom here > https://www.androidfilehost.com/?w=files&flid=257749
Click to expand...
Click to collapse
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
scrungydoolittle said:
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
Click to expand...
Click to collapse
Really ?? You quoted the first post again
Flashing a Rom will never relock your bootloader
All 3 roms wipe TWRP
Sent from my LG-H910 using Tapatalk
@scrungydoolittle,
I was going to say the same.. .. The reason for clsAs comment is.. .
It's considered bad practice to post the OP or any other long posts unnecessarily. It makes it extremely difficult and annoying for others to wade past the huge quoted post to see what you said.
You can just quote the relevant part of a post (as I did below), refer to post 1 as the OP, or put a link to the post you are referring to.
Hopefully this explanation will get you to edit your last post and reconsider quoting long posts in the future.
Thanks
PS: Consider the fact that some of us read forums via email, XDA forum app, and browsers on mobile devices which have limited screen real estate and require more scrolling than a large desktop monitor.
clsA said:
Really ?? You quoted the first post again
...
Click to expand...
Click to collapse
I'm hoping for some help in rooting my Elate. I was able to get the unlock code from Huawei. I downloaded the ADB and Fastboot drivers from the Android Tutorials page.
ADB recognizes my device when in normal mode. But when I reboot into Bootloader mode, the device is not recognized. It does not show up in Windows device manager and the command "adb devices" is null. I can't get past this point which is clearly a driver problem.
I also have installed and uninstalled Hi-suite a number of times.
Does anyone have any advice? Thanks.
Related
CWM 5.8.0.9 for Huawei MediaPad
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
I don't know how much this CWM version improves over the existing one by segler11.
However these build were more aimed at compiling and testing the new kernel sources.
I have tested compiling with both arm-eabi-4.4.0 and arm-eabi-4.4.3 with success on Ubuntu 10.04.
This is experimental, however with the new kernel sources it will just be a matter of time.
I have compiled the kernel included in this CWM recovery image but I didn't recompile the complete image.
I took as base Pyramid CWM 5.8.0.9 and I replaced the files from those found on a stock C232B005 kernel.
As the default build configuration I have used the /proc/config.gz of a C232B005 running kernel.
I have tested this CWM to be able to backup these partitions (I have not tested "restore" yet, just checked the tar archives):
boot.img - 12.582.912 (match 12Mb)
recovery.img - 16.777.216 (match 16Mb)
data.ext4.tar
cache.ext4.tar
system.ext4.tar
custom.ext4.tar
as you can see my hand tweaks to "recovery" require the name of "cust" partition to be "custom" instead but I believe this is a no issue while you backup and restore with the same CWM. Suggestions welcome.
BUGS:
data & time on archives are wrong
mount USB storage does not work
adb not enabled in recovery mode
Formats and Wipes do not work don't use them
The "busybox hwclock" applet doesn't work to set the hardware clock of our device.
The "adb shell" is not active while in CWM recovery, I don't know why and this was my objective so if you have suggestion please help.
As usual flash both "recovery" and "recovery2" partitions using "fastboot" and one of the attached CWM recovery:
Code:
fastboot flash recovery recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot flash recovery2 recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot reboot
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
.:HWMOD:.
.
Reserved CWM HWMOD
This version seemed to work better for me.Tnx dude!
john9 said:
This version seemed to work better for me.Tnx dude!
Click to expand...
Click to collapse
Thank you for trying it.
Remember to absolutely avoid formatting or wiping partitions.
If you need to format/wipe do it ONLY after reinstalling the original "recovery.img" in both "recovery" and "recovery2" partitions and then reset the device from:
"Settings -> Backup and reset -> Factory reset"
ATTENTION !!! You can safely do a wipe or factory reset only after reinstalling the original recovery image.
Sorry for insisting but I don't want to create problems on users devices and I know those operations will create problems.
.:HWMOD:.
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
cmstlist said:
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
Click to expand...
Click to collapse
Thank you for trying it. I wanted to compile/test a kernel with new sources in a CWM.
Yes, in our device the internal memory "/mnt/sdcard" is also mapped under "/data/share".
Unfortunately I don't have the skills (yet) to build a complete recovery image from scratch,
so what I did was just compiling the kernel part of the recovery image, using the new sources.
Then I simply hex tweaked the "recovery" executable of a 5.8.0.9 Pyramid CWM (HTC Sensation).
So, in conclusion, I have no control over what is copied during the backup process of those partitions.
Though I could control which partition is processed by removing them from "fstab", but there is no gain into it.
We will have to wait somebody with the specific knowledge, or maybe I will have some time to learn once I return from holidays.
.:HWMOD:.
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
after_silence said:
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
Click to expand...
Click to collapse
well done
HI, can anyone share buckup from working device created by CWM.?
Thanks to all.
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
.dredd. said:
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
Click to expand...
Click to collapse
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
hwmod said:
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
Click to expand...
Click to collapse
The main reason for use of CWM would be to have the possibility of flashing update zips from CWM... but I am afraid of messing up my device... to understand: no problem if I have to reflash the rom but I would not want to cause mistake which could be repaired only by service.
fastboot is always available if something goes wrong and if you flash cwm you wont be able to install official roms because cwm will overwrite stock recovery
so i was stupid and wiped data and cache - then remembered that it said not to - how do i fix this paperweight? i tried fastbooting all the usual partitions (system, boot, userdata, cache, etc) but still nothing - i can get to fastboot but i cant flash any dload updates. any suggestions are greatly appreciated.
flash stock recovery (2 files) from zipped rom via fastboot and then you should be able to flash stock rom
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
byt3b0mb said:
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
Click to expand...
Click to collapse
The time needed to reformat and rewrite all the firmware partitions (the first time) will be between 10-15 minutes.
Be patient and give enough time to the device to execute all the needed processes.
When the device finally boot it need to completely regenerate dalvik-cache (the first time).
So try again as instructed above, rewrite "BOTH" partitions named "recovery" and "recovery2", both using the same "recovery.img" file found in the latest stock Huawei firmware.
Now extract the stock Huawei firmware archive on your PC and copy the "dload" folder on an empty formatted SDCard, then insert the SDCard in the MediaPad reboot it and wait until success or failure message.
If you wiped partitions you will have to wait more time (20-30m). It may be that after waiting a while a message about "Encryption not possible" could appear, just say no to encryption and let it reset the device.
It already happened to some of us so hope you are also able to recover your tablet.
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
byt3b0mb said:
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
Click to expand...
Click to collapse
First time restoration takes time on both moments during the 1st Huawei log and even during animation.
Trying to recover a partition that was wiped takes much longer for the OS to show the error.
When I tried wiping "data" and rebooted the device I recall I went for a long walk and when I returned the device was showing the "Encryption failure / Reset" message (about half an hour later).
So I can only suggest that when you retry you wait at least that amount of time (30 min.) with charger connected, whatever happens leave it alone until it display or ask you do something. Let me know if it works when you have tried.
Download links do not work for me. Can you upload in mediafire please?
Hi everyone,
I successfully flashed CWM 6.0.4.7 on my 501L X1. This is thanks to the great folks at android-hilfe.de who compiled the links and most importantly the talented people at huafans.cn who created it.
This is NOT my work but I am sharing it for everyone's benefit. It helps if you can read Chinese though
Source forum: http://huafans.cn/forum-323-1.html
NEW
For 4.4.2 - 2014-10-08
https://drive.google.com/file/d/0B8-peidjMwx4ZUo3enVGOFVqckE/view?usp=sharing
For 4.2.2
Recovery link on android-hilfe: http://www.android-hilfe.de/root-cu...diapad-x1/601335-cwm-mediapadx1-download.html
Instructions:
Download and unzip the file recovery_cn.img.zip
Place the recovery_cn.img or recovery_cn_4.4.2.img onto the root folder of your SDcard
Install Flashify from the Playstore
Run Flashify and tell it to flash Recovery image > Choose a file > navigate via the file manager and choose the img file.
Execute, and reboot to Recovery to enjoy your new recovery.
A brief translation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Main Menu:
1. Reboot Device
2. Choose ZIP to flash
3. Clear Data/Factory Reset
4. Clear Cache
5. Backup / Restore
6. Microsd functions
7. Advanced Functions
2. Choose ZIP to flash
a. Choose file from /sdcard (ie internal)
b. Choose file from /storage/sdcard1 (ie external)
c. Choose from last used location
d. Enable ADB Sideload (!!!!!!!!!)
e. Do not use signature verification
f. Back to previous menu
3. Clear Data/Factory Reset
a. No
b. Yes - clear all user data
c. Back to previous menu
4. Clear Cache
a. No
b. Yes - clear cache
c. Back to previous menu
5. Backup / Restore:
a. Backup to /sdcard (ie internal)
b. Choose from /sdcard which backup you would like to restore
c. Delete backups from /sdcard
d. Choose from /sdcard using advanced options
e. Backup to /storage/sdcard1 (ie external)
f. Choose from /storage/sdcard1 which backup you would like to restore
g. Delete backups from /storage/sdcard1
h. Choose from /storage/sdcard using advanced options
i. Released unused space from backup (not sure what this does)
j. Choose default backup format (tar, gzip etc)
6. Microsd functions - I am not sure what this does, it lists a bunch of locations
7. Advanced Functions
a. Reboot into Recovery
b. Reboot into Bootloader
c. Shutdown device
d. Clear Dalvik Cache
e. Report Errors
f. Zipalign ????
g. Don't know what this is
If anyone else can help, this will be great.
Great news
If it really works, it's the beginning of "rom makers" !!:good:
Best translation in English!
Kindly yours from an old man:angel:
joytest said:
Hi everyone,
I successfully flashed CWM 6.0.4.7 on my 501L X1. This is thanks to the great folks at android-hilfe.de who compiled the links and most importantly the talented people at huafans.cn who created it.
This is NOT my work but I am sharing it for everyone's benefit. It helps if you can read Chinese though
Source forum: http://huafans.cn/forum-323-1.html
Recovery link on android-hilfe: http://www.android-hilfe.de/root-cu...diapad-x1/601335-cwm-mediapadx1-download.html
Instructions:
Download and unzip the file recovery_cn.img.zip
Place the recovery_cn.img onto the root folder of your SDcard
Install Flashify from the Playstore
Run Flashify and tell it to flash Recovery image > Choose a file > navigate via the file manager and choose the img file.
Execute, and reboot to Recovery to enjoy your new recovery.
A brief translation
Main Menu:
1. Reboot Device
2. Choose ZIP to flash
3. Clear Data/Factory Reset
4. Clear Cache
5. Backup / Restore
6. Microsd functions
7. Advanced Functions
2. Choose ZIP to flash
a. Choose file from /sdcard (ie internal)
b. Choose file from /storage/sdcard1 (ie external)
c. Choose from last used location
d. Enable ADB Sideload (!!!!!!!!!)
e. Do not use signature verification
f. Back to previous menu
3. Clear Data/Factory Reset
a. No
b. Yes - clear all user data
c. Back to previous menu
4. Clear Cache
a. No
b. Yes - clear cache
c. Back to previous menu
5. Backup / Restore:
a. Backup to /sdcard (ie internal)
b. Choose from /sdcard which backup you would like to restore
c. Delete backups from /sdcard
d. Choose from /sdcard using advanced options
e. Backup to /storage/sdcard1 (ie external)
f. Choose from /storage/sdcard1 which backup you would like to restore
g. Delete backups from /storage/sdcard1
h. Choose from /storage/sdcard using advanced options
i. Released unused space from backup (not sure what this does)
j. Choose default backup format (tar, gzip etc)
6. Microsd functions - I am not sure what this does, it lists a bunch of locations
7. Advanced Functions
a. Reboot into Recovery
b. Reboot into Bootloader
c. Shutdown device
d. Clear Dalvik Cache
e. Report Errors
f. Zipalign ????
g. Don't know what this is
If anyone else can help, this will be great.
Click to expand...
Click to collapse
joytest said:
Hi everyone,
I successfully flashed CWM 6.0.4.7 on my 501L X1. This is thanks to the great folks at android-hilfe.de who compiled the links and most importantly the talented people at huafans.cn who created it.
This is NOT my work but I am sharing it for everyone's benefit. It helps if you can read Chinese though
Source forum: http://huafans.cn/forum-323-1.html
Recovery link on android-hilfe: http://www.android-hilfe.de/root-cu...diapad-x1/601335-cwm-mediapadx1-download.html
Instructions:
Download and unzip the file recovery_cn.img.zip
Place the recovery_cn.img onto the root folder of your SDcard
Install Flashify from the Playstore
Run Flashify and tell it to flash Recovery image > Choose a file > navigate via the file manager and choose the img file.
Execute, and reboot to Recovery to enjoy your new recovery.
A brief translation
Main Menu:
1. Reboot Device
2. Choose ZIP to flash
3. Clear Data/Factory Reset
4. Clear Cache
5. Backup / Restore
6. Microsd functions
7. Advanced Functions
2. Choose ZIP to flash
a. Choose file from /sdcard (ie internal)
b. Choose file from /storage/sdcard1 (ie external)
c. Choose from last used location
d. Enable ADB Sideload (!!!!!!!!!)
e. Do not use signature verification
f. Back to previous menu
3. Clear Data/Factory Reset
a. No
b. Yes - clear all user data
c. Back to previous menu
4. Clear Cache
a. No
b. Yes - clear cache
c. Back to previous menu
5. Backup / Restore:
a. Backup to /sdcard (ie internal)
b. Choose from /sdcard which backup you would like to restore
c. Delete backups from /sdcard
d. Choose from /sdcard using advanced options
e. Backup to /storage/sdcard1 (ie external)
f. Choose from /storage/sdcard1 which backup you would like to restore
g. Delete backups from /storage/sdcard1
h. Choose from /storage/sdcard using advanced options
i. Released unused space from backup (not sure what this does)
j. Choose default backup format (tar, gzip etc)
6. Microsd functions - I am not sure what this does, it lists a bunch of locations
7. Advanced Functions
a. Reboot into Recovery
b. Reboot into Bootloader
c. Shutdown device
d. Clear Dalvik Cache
e. Report Errors
f. Zipalign ????
g. Don't know what this is
If anyone else can help, this will be great.
Click to expand...
Click to collapse
Possibly a daft question but will this work on the 7D-503L (the Chinese model)?
DrHRH said:
Possibly a daft question but will this work on the 7D-503L (the Chinese model)?
Click to expand...
Click to collapse
You're from Malaysia as well right?
Anyway, this came from the Chinese huafans forum, so it should work with the 503L, and even the 501u. If you can read Chinese, you may check it out.
didn't work with my 501u on the tw 4.4.2 firmware,
jaiong said:
didn't work with my 501u on the tw 4.4.2 firmware,
Click to expand...
Click to collapse
Mine was still on B003 4.2.2. I installed with no problems via the Flashify app.
5 backup and restore
joytest said:
Mine was still on B003 4.2.2. I installed with no problems via the Flashify app.
Click to expand...
Click to collapse
Dear Sir,
So far I did not try installing the Chinese recovery. I would like to do a full back-up BUT I don't see in your translation how to go "Back to previous menu" in Chapter 5 to reboot device.
Any suggestion, and did you try to back-up yours?
Kindly yours from an old man:angel:
bvannier said:
Dear Sir,
So far I did not try installing the Chinese recovery. I would like to do a full back-up BUT I don't see in your translation how to go "Back to previous menu" in Chapter 5 to reboot device.
Any suggestion, and did you try to back-up yours?
Kindly yours from an old man:angel:
Click to expand...
Click to collapse
Sorry missed that.
The last option showing
+++++ 返回上一级+++++
means "back to previous"
This is in the last line of every chapter
Yes I did successful backup. Will try restore sometime tonight.
Sent from my SM-N9005 using Tapatalk
No boot recovery...
I did step after step exactly what you did, but it doesn't reboot in Chinese recovery.
Download recovery_cn.img, put it in My internal SD, then flash with Flashify then try to boot with Flashify menu.
I stay with The Huawei Logo on for 1 or 2 minutes then boot normally.
The only difference is that you flash recovery from 4.22 and I did from Kitkat Maj 102
Kindly yours from an old man:angel:
joytest said:
Sorry missed that.
The last option showing
+++++ 返回上一级+++++
means "back to previous"
This is in the last line of every chapter
Yes I did successful backup. Will try restore sometime tonight.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
bvannier said:
I did step after step exactly what you did, but it doesn't reboot in Chinese recovery.
Download recovery_cn.img, put it in My internal SD, then flash with Flashify then try to boot with Flashify menu.
I stay with The Huawei Logo on for 1 or 2 minutes then boot normally.
The only difference is that you flash recovery from 4.22 and I did from Kitkat Maj 102
Kindly yours from an old man:angel:
Click to expand...
Click to collapse
Hi bvannier,
In Flashify, there is an option to reboot to Recovery directly.
On the top right of Flashify, click the 3 squares menu.
It will show you options for
Reboot
Reboot recovery <== click this
Reboot bootloader
Settings
Premium details
Usage Statistics
Share this app.
Reboot recovery
Think you but it's what I did already. I flash again the recovery file with Flashify but still no luck, no recovery menu on start up when clicking on Reboot recovery option.
Kindly yours from an old man:angel:
joytest said:
Hi bvannier,
In Flashify, there is an option to reboot to Recovery directly.
On the top right of Flashify, click the 3 squares menu.
It will show you options for
Reboot
Reboot recovery <== click this
Reboot bootloader
Settings
Premium details
Usage Statistics
Share this app.
Click to expand...
Click to collapse
bvannier said:
Think you but it's what I did already. I flash again the recovery file with Flashify but still no luck, no recovery menu on start up when clicking on Reboot recovery option.
Kindly yours from an old man:angel:
Click to expand...
Click to collapse
I'm not sure why it won't work for you, as @zertux in the other thread could do it, and so have several others in my home forum.
At worst, try the Vol Up + Power combo after you have shut down.
However, make sure you are PLUGGED IN VIA USB TO A PC. For some strange reason, getting to Recovery and Fastboot modes on this device needs you to have your device connected to a PC.
Stock recovery
joytest said:
I'm not sure why it won't work for you, as @zertux in the other thread could do it, and so have several others in my home forum.
At worst, try the Vol Up + Power combo after you have shut down.
However, make sure you are PLUGGED IN VIA USB TO A PC. For some strange reason, getting to Recovery and Fastboot modes on this device needs you to have your device connected to a PC.
Click to expand...
Click to collapse
Dear sir,
Back to you this morning, and I might need your advice/help because Vol Up + Power combo after you have shut down does NOTHING!
Did you, by any chance, backup the original previous Stock Recovery in Flashify?
If yes, would you be kind enough to send it to me?
That would be fair!
Kindly yours from an old man:angel:
bvannier said:
Dear sir,
Back to you this morning, and I might need your advice/help because Vol Up + Power combo after you have shut down does NOTHING!
Did you, by any chance, backup the original previous Stock Recovery in Flashify?
If yes, would you be kind enough to send it to me?
That would be fair!
Kindly yours from an old man:angel:
Click to expand...
Click to collapse
Bonjour.
I'm at work now, let me transfer via dropbox or gdrive in evening.
My timezone is GMT +8
Hi all try this dropox link. This is stock recovery from Western Europe B003 ROM.
https://www.dropbox.com/s/k018o3cfpkn6eds/recovery.img?dl=0
Sent from my Mediapad X1 7D-501L using Tapatalk HD
THINK YOU
joytest said:
Hi all try this dropox link. This is stock recovery from Western Europe B003 ROM.
https://www.dropbox.com/s/k018o3cfpkn6eds/recovery.img?dl=0
Sent from my Mediapad X1 7D-501L using Tapatalk HD
Click to expand...
Click to collapse
As I am running kitkat B102, is it safe to flash this recovery from B003 ROM?
Kindly yours from an old man:angel:
CWM Recovery loop
Hi!
I have Mediapad X1 7d-501u and I successfully change stock recovery with this CWM v6.0.4.7. But now I have problem, because I cannot start Android, there is loop, so when I turn on device it goes into CWM Recovery. How is this possible? Thank you for all suggestions.
Jozef
I might help you
jozefhalaga said:
Hi!
I have Mediapad X1 7d-501u and I successfully change stock recovery with this CWM v6.0.4.7. But now I have problem, because I cannot start Android, there is loop, so when I turn on device it goes into CWM Recovery. How is this possible? Thank you for all suggestions.
Jozef
Click to expand...
Click to collapse
Dear sir,
If you still have this loop problem, if you can boot in bootloader there is a way to get back to your original recovery and then start Android like it was before.
Kindly yours from an old man:angel:
Here are the great advices from fellows that help me to get back to my original recovery
First : download and install "Huawei update extractor"
Second : download and install on your desktop : android-sdk-windows-1.6_r1 (Google is your friend)
Third : open your previous update.app with "Huawei update extractor" then extract previous recovery.img and copy it into Tools folder from "android-sdk-windows-1.6_r1"
Fourth : hold shift and right clic on fastboot folder for open a command
type fastboot flash recovery recovery.img (you can paste in fastboot cmd window with right click)
click enter and VOILA
From Joytest :
you can extract the recovery.img from an update.app with the "Huawei update extractor" search on google.
ive the same issue i extract the recovery from YOUR ORIGINAL ROM and flash with fastboot (flashify dont work) and all its done
the fastboot command is: fastboot flash recovery recovery.img
From Bypass83
put the recovery.img inside the fastboot folder
hold shift and right clic on fastboot folder for open a command
type fastboot flash recovery recovery.img (you can paste in fastboot cmd window with right click)
click enter and fastboot wait for your device
put your phone in fastboot mode holding up and power (or down and power ) for 5sec
it enter in fastboot mod now you can connect to your computer
fastboot must automaticaly begin flashing .
don't worry if you find its quick its normal
have a good trie
Thinks to Benny888 for images
HOPE IT WILL HELP like They did for me
Solved
to bvannier:
YOU SAVED THE DAY!!!
Thank you your suggestion works. When I tried to install ROM by CWM, there was error message "E:footer is wrong". I tried all ROMs I found (for 7D-501u). But with original recovery I was able to install the ROM and it works now.
Thank you!
Jozef
@bvannier you have nicely summarised the steps to recover from a faulty recovery. I would like to post this to Lowyat page 1 with your permission.
Hi Guys,
I'm hoping someone can help me here with unbricking my daughters Nabi 2 tablet.
The long story short is that I've tried to update to the latest OTA with TWRP 2.3.3.0 (Nabi 1.9.37) and gapps installed in the past (in order to have google play services).
After downloading the OTA and successfull file verification it booted into TWRP mode and this is when things went wrong...
As I wasn't sure about how to even leave the TWRP mode I have hit few things by accident (I think one of them asked me if I want to wipe my ROM and I said YES + when I was after that trying to reboot the tablet it gave me a warning saying something like "you have no OS installed - are you sure to reboot?).
Now, of course due to my stupid actions it doesn't work - stuck on Nabi boot logo and when I try to pres Volume+ and Power together it gives me the screen with 4 options to choose from (Boot Normally, Fastboot Protocol, Recovery Kernel, Forced Recovery) but I still can't select/move the highlighted item. All what I'm able to do now is to power it off by holding the power button pressed for couple seconds.
Based on your experience here - is there anything that can be done or is it a "real brick" and we need to buy something new for her?
Thank you for any suggestions.
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
termostat1000 said:
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
Click to expand...
Click to collapse
Try sections 9 and 10. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
termostat1000 said:
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
Click to expand...
Click to collapse
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
aicjofs said:
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Click to expand...
Click to collapse
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
termostat1000 said:
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
Click to expand...
Click to collapse
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
aicjofs said:
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
Click to expand...
Click to collapse
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
termostat1000 said:
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
Click to expand...
Click to collapse
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
aicjofs said:
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
Click to expand...
Click to collapse
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
termostat1000 said:
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
Click to expand...
Click to collapse
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
aicjofs said:
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
Click to expand...
Click to collapse
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
termostat1000 said:
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
Click to expand...
Click to collapse
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
aicjofs said:
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
Click to expand...
Click to collapse
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
termostat1000 said:
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
Click to expand...
Click to collapse
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
aicjofs said:
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
Click to expand...
Click to collapse
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
termostat1000 said:
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
Click to expand...
Click to collapse
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
aicjofs said:
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
Click to expand...
Click to collapse
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
termostat1000 said:
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
Click to expand...
Click to collapse
Your thanks is enough Glad we got it sorted and a happy kid!
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Reserved
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
cland216 said:
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
Click to expand...
Click to collapse
Hell yeah. Glad I could help somebody! I've been wanting to give back to the wonderful XDA community for a while as a long time lurker. Also, I'm hoping to get a newer version of the stock rom and a stock recovery.img so you can go back to 100% factory stock for an OTA. I'm pretty proud of myself (being noobish) figuring this out.
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
klaudio_tv said:
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
Click to expand...
Click to collapse
Are you referring to "extracting" the recovery img? You only need to do it if you're running the stock recovery.
If so, I think I have screwed the command. Make sure you're in adb shell (in recovery on the watch) and then type "cat /proc/mtd" (with the space in front of cat) without the quotes in order to locate the recovery partition.
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
Hopefully this works
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
klaudio_tv said:
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
Click to expand...
Click to collapse
Since the OP helped me, here's my chance to give back..
By no means do I know what hell I'm doing, but I know enough to be dangerous. If you're ready to live dangerously, follow these steps (which worked for me):
1. Go into TWRP on the watch and connect it usb to your computer. Using TWRP file manager, copy the update.zip from CACHE to sdcard\Download.
2. On the computer, browse to Zenwatch internal memory Downloads folder and copy the update.zip file to your computer.
3. Unzip the file on your computer using 7zip.
4. Navigate to \META-INF\com\google\android\ and look for updater-script.
5. Edit updater-script in Notepad++.
6. Delete the lines starting with getprop. This turned out to be lines 2 thru 5.
7. Delete the lines starting with apply_patch_check. This turned out to be lines 10 thru 176
8. Save changes to updater-script then in Windows Explorer highlight all of the files and folders that you unzipped, right-click them and click on 7zip --> Add to update.zip
9. Copy the new update.zip to the Zenwatch internal memory, Downloads folder, overwriting the original update.zip
10. Flash the update.zip file with TWRP.
11. Reboot TWRP to Bootloader.
12. On your computer, goto adb folder where you have fastboot files, and using command prompt type:
fastboot erase cache
fastboot erase misc
fastboot reboot
These steps worked as I was stuck on the June 1, 2016 Android security patch on my Wren Zenwatch. These steps helped me get to the September 1, 2016 security patch.
I managed to update my watch to the September 1 security patch using Cland216's method. But I am unable to update further using the method above. Does anyone have any info on how to update further? Or has any zip files to flash?
If we could get someone to upload the watches stock recovery that would solve all issues.....Why has noone done this for this model yet?
Sent from my OnePlus X using XDA Labs
I'm unable to create a backup file
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
TWRP :
Could not mount /data
When I try to mount /data , I unable to /data
HOLY ****
Dude.. Let me just say...
YOU ARE THE ****ING ABSOLUTE BEST.
I am now going to make a backup, and save it to my computer, google drive, dropbox, icloud, and every other ****in place I can to make sure this never happens again. Thank you!!!!
Nicholas6706 said:
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Click to expand...
Click to collapse
I spoke just a bit too soon, now it is hanging on that animation with the 4 dots. Any suggestions?
NEVERMIND, I AM UP AND RUNNING!! WOOHOOOO
Below you'll find an unofficial semi-bootleg version of TWRP for the Mate 20 X. I say bootleg because I took @Pretoriano80's P10 lite build and modified it for our devices.
Credits: teamwin, @Pretoriano80, @ante0
Testers: @cflynt
Download: Download TWRP for Mate 20 X
Installation guide:
Welcome to the TWRP installation guide for the Mate 20 X. Keep in mind that installing this REQUIRES you to format your data and remove encryption in order for TWRP to read your /data partition and be able to create backups, so backing up your internal storage is recommended if you want to keep anything from it. This will factory reset your device as well.
Flashing TWRP to the eRecovery ramdisk partition is recommended as it allows you to have both Magisk root and TWRP simultaneously. Otherwise, you can flash between Magisk and TWRP when you need it by flashing this image to recovery_ramdisk. This guide will focus on eRecovery installation.
Magisk root and ADB/a terminal app is REQUIRED for the installation of TWRP as fastboot does not allow flashing of erecovery_ramdisk partition.
Backing up your original eRecovery:
The easiest way to accomplish this is to download "partitions backup & restore" from the google play store, and using that app to back up "erecovery_ramdisk." However, you can also accomplish this with adb by running the command "dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/sdcard/erecovery_ramdisk_stock.img" with your device hooked up to a computer. If you are backing up your internal storage, do it after creating this backup. Otherwise, copy this backup to a safe location on your computer.
Booting to TWRP: Booting into TWRP requires a different button combination.
-Booting to TWRP is as simple as getting to the standard boot splash "corruption" screen. When you see this, it will be followed by instructions to hold volume UP for three seconds. Doing this will boot you into TWRP or eRecovery, depending on which one you have installed. With the phone connected to a power source, USB or AC, reboot/boot the phone holding volume UP. Once the standard corruption screen is displayed, release and hold the volume UP key again.
Booting to Magisk root:
-Booting to Magisk root requires the same volume UP key combination, but the phone must NOT be connected to a power source (USB or AC), OR you must use the "adb reboot recovery" command. Reboot/boot the device holding volume UP. This will display the standart boot splash "corruption" screen but will NOT show the standard instructions for booting into eRecovery. It will simply show a "your device is booting" message under the "corruption" message.
Booting to Magisk root from TWRP: the Reboot>Recovery option in TWRP does NOT reboot the device back into TWRP. This is used to boot Magisk root.
-From TWRP, tap the Reboot button followed by Recovery. Normally, the device would boot back into TWRP, but since TWRP is installed to the eRecovery partition and Magisk is installed to the normal recovery partition, it reboots to Magisk root instead.
Booting back into TWRP from TWRP: Using the Reboot>System option in TWRP will get you back to the standard corruption boot splash screen where you can use the "Booting into TWRP" instructions above to get back into TWRP.
-From TWRP, tap the Reboot button followed by System. This will reboot the device normally, giving you the standard corruption screen followed by a normal boot WITHOUT Magisk root. Use this option only if you plan on rebooting back into TWRP with the "Booting into TWRP" instructions above. Otherwise, use the Reboot>Recovery option to get you back into a rooted system.
Modifying system from TWRP: This device uses "System as root" file structure, so it's a bit different to modify system from TWRP.
-Go to the mount option in twrp and mount "System_root" From here, you'll need to browse /system_root NOT /system in order to make changes to system.
*******************INSTALLING TWRP TO ERECOVERY*******************
Flashing TWRP to eRecovery ramdisk:
-Hook your phone up to a PC.
Step 1.
Start by copying the TWRP image to your internal storage OR nm card. Rename it to "twrp.img" to make typing the next command easier.
Step 2.
Using ADB or a terminal app, gain SU access and run the following command: "dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk"
Step 3.
Reboot your phone into TWRP by following the "Booting to TWRP" instructions above.
Step 4.
Once you are in TWRP, you will need to format data, as TWRP cannot read encrypted storage on this device yet. Do this in the "wipe" "Format Data" section of TWRP.
Step 5.
Once data is formatted, copy the fstab.kirin980 file from this package to your internal storage or nm card.
Step 6.
Go to "mount" in twrp, and mount Vendor.
Step 7.
Use TWRP file manager in the "advanced" section of TWRP to copy fstab.kirin980 from your internal storage or nm card to /vendor/etc. This will overwrite the original fstab.kirin980 file and replace it with our modified one removing forced encryption so that the system won't try and re-encrypt your device on boot.
Step 8.
Reboot>Recovery to get back into a rooted system, which is now factory resetted.
DO NOT USE ANY OF THE TWRP SUGGESTIONS TO INSTALL ROOT TO YOUR SYSTEM. Disable the notice to install root by going into TWRP settings and unchecking the relevant box.
Great work! @freeza
Can you expand on step 2...
"Using ADB or a terminal app, gain SU access..."
How does one "gain" SU access? Opening a terminal app on the phone and entering SU in command prompt comes back with permission denied even though I am booted under the previous root method.
n1tro said:
Can you expand on step 2...
"Using ADB or a terminal app, gain SU access..."
How does one "gain" SU access? Opening a terminal app on the phone and entering SU in command prompt comes back with permission denied even though I am booted under the previous root method.
Click to expand...
Click to collapse
Are you sure you're booted with magisk root? If so, open the magisk manager and go to > superuser and make sure shell is allowed for root. If you're using a terminal app, then make sure that's allowed.
Sent from my EVR-AL00 using Tapatalk
freeza said:
Are you sure you're booted with magisk root? If so, open the magisk manager and go to > superuser and make sure shell is allowed for root. If you're using a terminal app, then make sure that's allowed.
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Took a few tries typing in SU before it triggered the Magisk Grant Permission prompt to come up. I granted permission. But entering in the command gives me a permission denied.
Attached screenshot
Magisk permission
n1tro said:
Attached screenshot
Click to expand...
Click to collapse
You want to use app launcher in phone manager or battery settings to turn off emui optimization of magisk manager so it'll be allowed to run in the background to prompt for su. Also try entering just su in the terminal first to get the # prompt instead of $, then enter the dd command
Sent from my EVR-AL00 using Tapatalk
freeza said:
You want to use app launcher in phone manager or battery settings to turn off emui optimization of magisk manager so it'll be allowed to run in the background to prompt for su. Also try entering just su in the terminal first to get the # prompt instead of $, then enter the dd command
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Seems not all terminal apps are created equal. Even with permissions enabled, issuing the SU command did bring it to a # prompt but kept it at $.
Downloaded and installed Material Terminal from the playstore and it works.
n1tro said:
Seems not all terminal apps are created equal. Even with permissions enabled, issuing the SU command did bring it to a # prompt but kept it at $.
Downloaded and installed Material Terminal from the playstore and it works.
Click to expand...
Click to collapse
Glad you got it sorted [emoji16]
Sent from my EVR-AL00 using Tapatalk
freeza said:
Glad you got it sorted [emoji16]
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
1 problem cleared, another one starts.
I followed the instructions wiping the data and copying the 1 file over under the vendor directory. Phone boots up in setup menu. I go through everything (skipping setting up wifi) and when I finish selecting to use gestures or nav buttons, the phone goes back to the beginning of the setup screen.
Guess, I will try to wipe everything and load the custom rom you guys made
n1tro said:
1 problem cleared, another one starts.
I followed the instructions wiping the data and copying the 1 file over under the vendor directory. Phone boots up in setup menu. I go through everything (skipping setting up wifi) and when I finish selecting to use gestures or nav buttons, the phone goes back to the beginning of the setup screen.
Guess, I will try to wipe everything and load the custom rom you guys made
Click to expand...
Click to collapse
When you wiped data, did you do it from the WIPE screen in TWRP and select Format Data? Should prompt you to type in YES when you do so. Otherwise if you are doing an ADVANCED WIPE it is only formatting data without the Media part. YOU MUST get this part right and then copy over that new fstab.kirin980 file using the TWRP File Manager. If you didn't get this right then your Data Partition will still be encrypted.
Hope that helps.
Chad
cflynt said:
When you wiped data, did you do it from the WIPE screen in TWRP and select Format Data? Should prompt you to type in YES when you do so. Otherwise if you are doing an ADVANCED WIPE it is only formatting data without the Media part. YOU MUST get this part right and then copy over that new fstab.kirin980 file using the TWRP File Manager. If you didn't get this right then your Data Partition will still be encrypted.
Hope that helps.
Chad
Click to expand...
Click to collapse
I wiped the data from the main screen and got a prompt to type YES to continue. I think the setup screen loop issue is coming from all the Huawei stuff I got rid of using the adb procedure in the other thread. Maybe I got rid of some 1st time setup file. In any rate, I got the custom ROM you guys made and installed it and everything works again.
O
n1tro said:
Attached screenshot
Click to expand...
Click to collapse
What is your dpi?? lmao
antiochasylum said:
O
What is your dpi?? lmao
Click to expand...
Click to collapse
340.
I normally have it at 320 but noticed I was making more mistakes on the shrunken keyboard.
n1tro said:
340.
I normally have it at 320 but noticed I was making more mistakes on the shrunken keyboard.
Click to expand...
Click to collapse
How did your set it? The typical lcd_density didn't trigger anything for me.
antiochasylum said:
How did your set it? The typical lcd_density didn't trigger anything for me.
Click to expand...
Click to collapse
It's in a messed up location. Go and edit the local.prop file located in /product/etc/prop pathway. That's the only thing that needs to be set. All the other files and locations are red herrings.
Guys, maybe this is a dumb question... but can i Flash SuperSU directly from the TWRP ?
filip_pine said:
Guys, maybe this is a dumb question... but can i Flash SuperSU directly from the TWRP ?
Click to expand...
Click to collapse
SuperSU is more suited for older phones and no longer being worked on so no more updates/support? https://www.androidpolice.com/2018/0...p-development/ it's also been removed from Play Store.
Magisk is used for root now https://www.xda-developers.com/magisk-vs-supersu/ and there is a thread how to install here
How can I update software?
Now 185, but 195 comming.