There are way too many people to thank individually, but hopefully I linked to all the relevant threads. When you visit those threads, press the thank you.
this comprehensive guide helped me a lot:
https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
Thanks to a lot of helpful info on these forums, I was able to start from the Sony stock rom and end up with a very clean install (mostly no Sony/Google stuff) with root.
I started from a stock 34.1.A.1.198. If you have a higher version, you'll have to downgrade. If you have any sort of data on this phone, back it up as you will likely lose everything. Here is what I did:
Computer Setup (Windows 10):
- disable secure boot in your bios. I had trouble installing stuff without this, YMMV.
http://www.windowspasswordsrecovery...isable-uefi-secure-boot-in-windows-8-1-8.html
- disable windows driver signing:
http://windowsreport.com/driver-signature-enforcement-windows-10/
Use Restart option. (The admin cmd doesn't really work).
- ADB/Fastboot install: see
https://forum.xda-developers.com/showpost.php?p=48915118
- Flashtool:
http://www.flashtool.net/index.php
download 0.9.23.1 and patch to 0.9.23.2
install 0.9.23.1, then replace the x10flasher.jar file by the patch install the drivers in drivers directory: select the common & fastboot- install Sony USB driver:
https://developer.sonymobile.com/downloads/drivers/xperia-x-compact/
Phone setup:
On phone, enable developer
settings->about phone
click Build number 7 timesOn phone, enable usb debugging
settings -> developer -> USB DebuggingConnect phone to USB
allow the computer when askedTest adb:
Open a command prompt on the computer and type
Code:
adb devices
should show a device.Backup TA (DRM keys):
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unzip backupTA_v2
Code:
cd backupTA_v2
backupTA.cmd
- it doesn't always work the first time. Run backupTA.cmd many times until it succeeds. Phone reboots supposedly help.
- reboot phone afterward
check drm status:
dial *#*#7378423#*#* on phone
brings up service menu
Service Tests->Security
Keys should show as "[Key OK][Active]"
FIDO_KEYS: ProvisionedUnlocking bootloader. do this only after backing up TA.
https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
on phone:
settings -> developer -> OEM Unlocking -> enable
asks for pin, it's actually just your normal wakeup pin.Turn phone off. Press Vol Up while plugging into USB cable (do not press power).
check it's working:
Code:
fastboot devices
should show something
use fastboot command from sony:
Code:
fastboot -i 0x0fce oem unlock 0xyyyy
(replace yyyy with whatever code you got)
after unlock, check drm status. It should say "generic error" and FIDO_KEYS won't be provisioned.
reboot the phone and connect to computer for file transfer.
put a memory card in the phone.
Preparing a kernel
Download new kernel: https://forum.xda-developers.com/x-compact/development/kernel-xc-genesis-kernel-v1-01-t3525060
Get XC-GenesisKernel-v1.04-nodrm.zip
Download ta_proc.rar from https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
unrar ta_proc
copy boot.img from the kernel zip to ta_proc directory
copy your TA backup to the ta_proc directory
double click DOUBLECLICKME.bat and choose the files you just copied. It should create new_boot.img
delete old boot.img in that directory and rename new_boot.img to boot.img
start with XC-GenesisKernel-v1.04-nodrm.zip, do not unzip, just drop and drop the new boot.img into that file.
Copy new kernel to the phone's SD card.
download superuser.zip from https://superuser.phh.me/
copy to memory card
this will be used later.
remove memory card.
Put rom 34.2.A.0.311 on the phone:
Xperifirm -- firmware downloading tool
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Run xperifirm and download the "service exchange unit - 34.1.A.1.198" firmware for posterity and latest rom for your region.
I got 34.2.A.0.311.
Use flashtool tools->bundles->create
double click the device, pick X Compact
Fill in the other boxes.
select all the files and ->
create the ftfFlash (big lightning button)
Flash using "flashmode"
under wipe, select everything
flash
follow instructions (vol -, plug in usb cable)Don't reboot the phone after.
Download twrp:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-t3522249
put the phone in fastboot mode (vol +, usb plugin) check with
Code:
fastboot devices
Install twrp:
Code:
fastboot flash recovery twrp_6.0.img
unplug phone
put in the memory card
boot to recovery:
https://developer.sonymobile.com/20...for-a-range-of-unlocked-xperia-devices-video/
At the same time, press the Power button and Volume down until your device vibrates.
Quickly release the Power button, but keep pressing Volume downtwrp will show up. Select the kernel zip to flash. For me, that meant going up one level, then external_sd
install superuser.zip
reboot the phone, but be aware that a few boot loops is not unusual. Be patient, let it finish.
get through "getting started", enable debug
now is a good time to check your DRM keys again via the service menu.
Install busybox
https://f-droid.org/repository/browse/?fdfilter=busybox&fdid=ru.meefik.busybox
with adb:
Code:
adb install ru.meefik.busybox_27.apk
Install phh SU
https://f-droid.org/repository/browse/?fdid=me.phh.superuser
Code:
adb install me.phh.superuser_1033.apk
Run the busybox app on the phone (which does the binary install)
Cleaning the system:
(mostly from this thread: https://forum.xda-developers.com/x-compact/help/apps-safe-to-remove-root-t3549871)
Code:
adb shell
su
cd /
busybox mount -o rw,remount system
Code:
cd /system/app:
rm -rf com.s.antivirus
rm -rf com.facebook.appmanager com.facebook.katana
rm -rf AnonymousData CalendarGoogle Chrome Drive Hangouts
rm -rf com.amazon.mShop.android.shopping Lifelog-3.0.B.4.15-6295567-googlePreloadLive-release
rm -rf EasterEgg com.spotify.music com.sonymobile.xperialounge.services Gmail2 Maps
rm -rf playstationapp newssuite YouTube YouTubeKaraokePlugin YouTubePlugin
rm -rf WikipediaPlugin SomcMovieCreatorRmm-release
rm -rf SemcEmail SomcSketch-live
rm -rf FaceLock GoogleAnalyticsProxy
rm -rf GoogleContactsSyncAdapter GoogleLyricsPlugin
rm -rf GooglePrintRecommendationService GoogleTTS
rm -rf EditorsDocs EditorsSheets EditorsSlides
rm -rf GetMoreClient-standard-release OmaDownload PartnerBookmarksProvider PrintSpooler
rm -rf RemoteControlService SomcPOBox SyncHub-release TopContactsWidget-release
rm -rf com.sonyericsson.xhs com.sonymobile.deqp talkback videoplaceholder videotvsideview
cd /system/prvi-app:
rm -rf com.facebook.system GetMore-standard-release SharedStorageBackup
rm -rf SomcMovieCreator-release GoogleBackupTransport GoogleFeedback
rm -rf com.sonymobile.retaildemo MyXperia-release RcsVideoShare
rm -rf SocialphonebookStub somc-get-to-know-it-release
pm disable-user com.google.android.apps.photos
pm disable-user com.google.android.googlequicksearchbox
pm disable-user com.google.android.tag
pm disable-user com.google.android.videos
pm disable-user com.google.android.webview
pm disable-user com.sonyericsson.updatecenter
pm disable-user com.sonymobile.demoappchecker
pm disable-user com.sonymobile.enterprise.service
pm disable-user com.sonymobile.entrance
pm disable-user com.sonymobile.exchange
pm disable-user com.sonymobile.mwutil
pm disable-user com.sonymobile.phoneusage
pm disable-user com.sonymobile.rcs.settings
pm disable-user com.sonymobile.xperiaservices
pm disable-user com.sonymobile.xperiatransfermobile
pm disable-user com.google.android.music
Disabling more Google stuff:
can replace /system/priv-app/GmsCore/GmsCore.apk with microG version
https://github.com/microg/android_packages_apps_GmsCore
can get rid of Google play by replacing /system/priv-app/Phonesky/Phonesky.apk with FakeStore
https://github.com/microg/android_packages_apps_FakeStore/releases
Download and install f-droid from f-droid.org
Code:
adb install FDroid.apk
install a bunch of FOSS apps
There are way too many people to thank individually, but hopefully I linked to all the relevant threads. When you visit those threads, press the thank you.
first i want to thank you for this. i appreciate this.
why do we have to use the genesis kernel that is including drm patch when this method makes this patch obsolete? is ta_poc deactivating the drm patch within genesis during injecting the TA data?
What happens if i want to update the rom to the latest sony rom? do i have to do always the same steps?
or what happens if completly for example want to try out custom roms like lineage with different kernels etc?
i assume that phh SU is required for root right? is busybox necessary for phh su or just optional? for what do we need busybox? i mean i can clean the rom myself with root explorer.
What is "service exchange unit - 34.1.A.1.198" is this a special rom or can i always use the latest sony stock firmware for germany for instance?
"it doesn't always work the first time. Run backupTA.cmd many times until it succeeds. Phone reboots supposedly help."
Tried over hundred times using "service exchange unit" build 34.1.A.1.198 without success. I rebooted between each 5 tries.
Could you be more specific on how many is "many" ?
... succeeded while writing this ... it 100% fails from linux, but works from windows 10 without problems...
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
x10isrooted said:
first i want to thank you for this. i appreciate this.
why do we have to use the genesis kernel that is including drm patch when this method makes this patch obsolete? is ta_poc deactivating the drm patch within genesis during injecting the TA data?
What happens if i want to update the rom to the latest sony rom? do i have to do always the same steps?
or what happens if completly for example want to try out custom roms like lineage with different kernels etc?
i assume that phh SU is required for root right? is busybox necessary for phh su or just optional? for what do we need busybox? i mean i can clean the rom myself with root explorer.
What is "service exchange unit - 34.1.A.1.198" is this a special rom or can i always use the latest sony stock firmware for germany for instance?
Click to expand...
Click to collapse
This is a firmware used to downgrade, in this case it is useful because it has a vulnerable kernel we can exploit while later versions does not.
Sorry for not responding earlier. I was out.
x10isrooted said:
first i want to thank you for this. i appreciate this.
why do we have to use the genesis kernel that is including drm patch when this method makes this patch obsolete? is ta_poc deactivating the drm patch within genesis during injecting the TA data?
Click to expand...
Click to collapse
There are two versions of the genesis kernel. One has a built in DRM patch, which doesn't require your TA data, but I couldn't get it to work with the FIDO_KEYS. The second version does NOT include the DRM patch. That's where ta_proc comes in. It uses your TA data and makes it available to any kernel. I just happen to like the genesis kernel, but the TA stuff should work with stock kernel as well.
x10isrooted said:
What happens if i want to update the rom to the latest sony rom? do i have to do always the same steps?
or what happens if completly for example want to try out custom roms like lineage with different kernels etc?
Click to expand...
Click to collapse
I think you have to follow the instructions from "Put rom 34.2.A.0.311 on the phone:" forward. I haven't tried it, so be ready for some bumps.
x10isrooted said:
i assume that phh SU is required for root right? is busybox necessary for phh su or just optional? for what do we need busybox? i mean i can clean the rom myself with root explorer.
Click to expand...
Click to collapse
Yes, phh is for root. Busybox is for mounting /system read-write. If you want adb or on-device terminal access with system read-writable, busybox is needed. I'm sure other tools are fine too.
x10isrooted said:
What is "service exchange unit - 34.1.A.1.198" is this a special rom or can i always use the latest sony stock firmware for germany for instance?
Click to expand...
Click to collapse
.198 is the stock rom my phone (and I think the original release) came with. It has the bug that can be exploited and backup your TA. For the final rom, you can use whatever you like. I used 34.2.A.0.311 for my region.
@tuten1000
Hi! Were you able to tingle patch the framework in order to enable signature spoofing ?
I would love to user MicroG in my XC too
https://github.com/ale5000-git/tingle/
NinjaFlood said:
@tuten1000
Hi! Were you able to tingle patch the framework in order to enable signature spoofing ?
I would love to user MicroG in my XC too
Click to expand...
Click to collapse
I didn't use tingle. I just replaced the google apk (/system/priv-app/GmsCore/GmsCore.apk) with the microg apk.
I'm thinking of buying an X Compact. Just to clarify, after successfully performing all the above steps, I should end up with a phone that is both rooted and has access to Sony's DRM features (e.g. improved camera and PS4 Remote Play)?
kirko62 said:
I'm thinking of buying an X Compact. Just to clarify, after successfully performing all the above steps, I should end up with a phone that is both rooted and has access to Sony's DRM features (e.g. improved camera and PS4 Remote Play)?
Click to expand...
Click to collapse
That's correct. Just don't remove some of the Sony/Google stuff you care about.
tuten1000 said:
Preparing a kernel
Download new kernel: https://forum.xda-developers.com/x-compact/development/kernel-xc-genesis-kernel-v1-01-t3525060
Get XC-GenesisKernel-v1.04-nodrm.zip
Download ta_proc.rar from https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
unrar ta_proc
copy boot.img from the kernel zip to ta_proc directory
copy your TA backup to the ta_proc directory
double click DOUBLECLICKME.bat and choose the files you just copied. It should create new_boot.img
delete old boot.img in that directory and rename new_boot.img to boot.img
start with XC-GenesisKernel-v1.04-nodrm.zip, do not unzip, just drop and drop the new boot.img into that file.
Copy new kernel to the phone's SD card.
Click to expand...
Click to collapse
If I want to use stock kernel, I just need to extract boot.img from official sony ftf and use that one instead?
After creating the modified boot.img, can I just use this?
Code:
fastboot flash boot modified-boot.img
fastboot flash recovery twrp.img
and flash the supersu/superuser from twrp?
What to do if there is a security update? Can I just update within the phone, recreate boot img from the new ftf and flash it again?
How about major android update, can we still update from within the phone?
hello everyone, so just to be sure: backup ta - unlock bootloader - flash kernel - flash twrp - flash supersu. is it ok? if i want the stock kernel is the same? or i must to flash this one? and if i want revert back is it possible relock the bootloader for guarranty? thanks in advance
trewelu,
For me, I had troubles with rezipping the XC Genesis kernel. It gave me an unflashable ZIP using TWRP (even with 7-zip) : bootloops, TWRP stopped working... The big stress ! So I just flashed the new_boot.img using the fastboot command you proposed (and then TWRP and SuperSU). What is nice with the TA.img included XC Genesis patched kernel is that you won't have the unlocked message at boot anymore, you recover your DRM and if there is any trouble, you will be able to use Xperia Companion for recovering your phone as an untouched one.
So to answer your question, I think yes, you can use the stock boot.img.
And I don't recommand to use OTA for updating. It's better to use flashtool : you will prevent an unwanted update of the kernel.
If I say something wrong please correct me !!!
trewelu said:
If I want to use stock kernel, I just need to extract boot.img from official sony ftf and use that one instead?
After creating the modified boot.img, can I just use this?
Code:
fastboot flash boot modified-boot.img
fastboot flash recovery twrp.img
and flash the supersu/superuser from twrp?
What to do if there is a security update? Can I just update within the phone, recreate boot img from the new ftf and flash it again?
How about major android update, can we still update from within the phone?
Click to expand...
Click to collapse
I'm on 34.2.A.2.69
I'm failing to backup my DRM keys with the Dirty Cow exploit script. I'm a Linux user.
Do I need to downgrade the firmware? How?
Any help would be appreciated.
NinjaFlood said:
Do I need to downgrade the firmware? How?
Click to expand...
Click to collapse
You do yes, see if there's and old FW in XperiFirm or browse the threads here for an ftf.
trewelu said:
If I want to use stock kernel, I just need to extract boot.img from official sony ftf and use that one instead?
After creating the modified boot.img, can I just use this?
Code:
fastboot flash boot modified-boot.img
fastboot flash recovery twrp.img
and flash the supersu/superuser from twrp?
Click to expand...
Click to collapse
I agree with mhemart that it should work. Please confirm if you try it.
trewelu said:
What to do if there is a security update? Can I just update within the phone, recreate boot img from the new ftf and flash it again?
How about major android update, can we still update from within the phone?
Click to expand...
Click to collapse
Updating from within the phone would overwrite all the changes, so I wouldn't recommend it. Backup your phone and redo the steps. It doesn't take long once you've done it a few times
NinjaFlood said:
I'm on 34.2.A.2.69
I'm failing to backup my DRM keys with the Dirty Cow exploit script. I'm a Linux user.
Do I need to downgrade the firmware? How?
Any help would be appreciated.
Click to expand...
Click to collapse
In addition to downgrading, there is at least one report that dirty cow doesn't work on linux.
See Magissia's post earlier in this thread (https://forum.xda-developers.com/showpost.php?p=71877283&postcount=3)
Spockman89 said:
hello everyone, so just to be sure: backup ta - unlock bootloader - flash kernel - flash twrp - flash supersu. is it ok? if i want the stock kernel is the same? or i must to flash this one? and if i want revert back is it possible relock the bootloader for guarranty? thanks in advance
Click to expand...
Click to collapse
In order:
1. Backup TA
2. Unlock phone
3. Flash new rom
4. Flash twrp
5. Flash kernel. There is at least one report from mhemart that you can flash the modified kernel then twrp.
6. Flash superuser, install busybox and superuser apk
I don't know of anyone who has managed to relock their X compact.
Is there a particular reason you suggest to unlock before updating to the latest rom. What I did is to backup my ta/drm then update using ota because I'm always scared the first time I need to root a phone and then I unlocked and flashed all the different images.
I will precise that twrp was already installed when I flashed the modified kernel but twrp didn't work because I was using an old version not compatible with nougat.
mhemart said:
Is there a particular reason you suggest to unlock before updating to the latest rom. What I did is to backup my ta/drm then update using ota because I'm always scared the first time I need to root a phone and then I unlocked and flashed all the different images.
Click to expand...
Click to collapse
No real reason. I guess I just like to take control as quickly as possible. All the interesting stuff needs an unlocked bootloader, so there is no point if the device can't be unlocked for some reason.
tuten1000 said:
I don't know of anyone who has managed to relock their X compact.
Click to expand...
Click to collapse
I'm pretty sure I did when I first tinkered with mine as I got rid of the annoying "can't be trusted" boot message, got it now though as I am unlocked but if the phone no longer tells you about the trust issue you would assume you've relocked it.
Hey, I just ordered a refurbished Xperia X Compact. Sadly nobody sells the XXC in Canada with a usable Sony warranty, and Sony Canada will not service US warranties, and Sony USA will not service in Canada... so refurb ended up being my only option. At least it comes with a 90 day guarantee.
So anyway I have no idea what firmware version it will come with. What is the highest that still supports backing up the TA partition?
EDIT: Also the use of superuser.zip from superuser.phh.me - is this just the author's choice vs SuperSU, Magisk etc? Or is there a specific reason this one works really well with Xperia?
Related
Hi,
I've recently purchased a Huawei Mediapad Tablet running honeycomb 3.2.
I would like to root this tablet but am unable to find any guides on the web.
Any pointers and guides would be much appreciated.
Thanks
bump for you interested to know as well
Yeah, I also bought mediapad last 2 weeks, this honeycomb really unstable, hang/reboot very often. And when I switched to full resolution 1280x800, you can feel lagging. Disappointed with stock ROM.
i want to root huawei mediapad su302,please,thanks
Same here...
Just picked on up tonight, not bad hardware but the os needs a kick in the a$$.
Lets get this going people, time is a wasting!
I have beginner modding skills if anyone wants to help me start this?
Recently, I read some reference from some Chinese Forum..
There are Rooted ROMs... and tutorials about how to root by youself..
If you decide to create a rooted rom by yourself..
You need a Linux environment to do that...
Here's how I did mine...
1. First of All, download the latest ROM from Huawei official site..
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3779&tb=0
2. Unzip it, you'll have a folder "dload"
3. Extract the file" system.img.ext4" from the Update.zip
4. Copy the "system.img.ext4" into your Linux Environment..
5. mount the image file like these...
#mkdir /mnt/tmp
#mount -o loop system.img.ext4 /mnt/tmp
6. put the "superuser" binary into the path /mnt/tmp/xbin
#cp su /mnt/tmp/xbin
7. Assgin the correct permission to the su binary
#chmod 6755 /mnt/tmp/xbin/su
8. Unmount the path and copy the system.img.ext4 into the original Update.zip
#umount /mnt/tmp
9. Put the "dload" folder into the root directory of a Micro-SD
10. Power Up your mediapad, when it vibrates, press and hold Volume Down until you see the Android icon, and it will try to flash the new ROM.
11. After everything is done, Look for Super User from Market, you'll see.
--
For su binary.. you can find it here http://androidsu.com/superuser/
Here's the product of all the above steps...
http://www.multiupload.com/0WPLQILCGH (114.73MB)
(I was using the official ROM dated 26 November..
and Put the su binary Together the superuser app into the system directory.
nothing else I have done to the ROM..)
You can also flash the system.img.ext4 into your mediapad directly via fastboot
to activate the fastboot mode of mediapad..
1. Connect your mediapad to your Computer with USB cable
2. Power up the mediapad with Volume Up button press and hold until your computer sense it and install the correct driver for it.
3. Direct flash your mediapad like this..
fastboot flash system system.img.ext4
then, reboot your mediapad..
you'll have your apps un-touched, while you have the latest system. enjoy~!
--
Fastboot, extracted from the Android SDK..
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
squide said:
3. Direct flash your mediapad like this..
fastboot flash system.img.ext4
.
Click to expand...
Click to collapse
I had to use fastboot flash system system.img.ext4
last rom with root + busybox + some app
http://uploading.com/files/53f162e9/dload.rar/
I can now run my favourite titanium backup.
squide said:
Here's the product of all the above steps...
http://www.multiupload.com/0WPLQILCGH (114.73MB)
(I was using the official ROM dated 26 November..
and Put the su binary Together the superuser app into the system directory.
nothing else I have done to the ROM..)
You can also flash the system.img.ext4 into your mediapad directly via fastboot
to activate the fastboot mode of mediapad..
1. Connect your mediapad to your Computer with USB cable
2. Power up the mediapad with Volume Up button press and hold until your computer sense it and install the correct driver for it.
3. Direct flash your mediapad like this..
fastboot flash system.img.ext4
then, reboot your mediapad..
you'll have your apps un-touched, while you have the latest system. enjoy~!
--
Fastboot, extracted from the Android SDK..
Click to expand...
Click to collapse
Thanks. Manage to root my mediapad without losing the installed apps.
Btw use this link to get the fastboot
http://dl.google.com/android/android-sdk_r13-windows.zip
squide said:
5. mount the image file like these...
#mkdir /mnt/tmp
#mount -o loop system.img.ext4 /mnt/tmp
Click to expand...
Click to collapse
Which distro are you using?
I'm having some problems writing to the image after mounting it as a loop back for Ubuntu 10.4
just a question about this device as GSMarena shows GSM support does it mean the you can use it as a phone.
freeko2 said:
just a question about this device as GSMarena shows GSM support does it mean the you can use it as a phone.
Click to expand...
Click to collapse
It's been discussed quite a bit in the Hardwarezone forum. I cannot post a link yet, so just google for 'mediapad hardwarezone forum'.
You need to install the HuaweiMediaPadPhone.apk which you can request from those in the forum. You can also find the link for Mediafire on the forum.
Once you install the apk, you will get the standard Phone and Messaging apps which you can use to make phone calls over GSM and also SMS. Working well for me.
venomrat said:
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
I had to use fastboot flash system system.img.ext4
Click to expand...
Click to collapse
Thanks. I had a lab full of Linux systems, so I tried to put the 'su' in myself. Thanks to this fastboot procedure, I have a rooted system with no apps lost.
venomrat said:
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
I had to use fastboot flash system system.img.ext4
Click to expand...
Click to collapse
So did you Root it with a PC?
Could you give me some info on how you did this?
I have sdk r13 & fastboot (is 1.img the file I need to flash?)
It's quite easy. just ensure.
1. Your Android SDK is installed correctly
2. Mediapad Fastboot USB driver is detected
3. get the correct system.img.ext4
4. Ensure fastboot works before issuing the flash command
by doing this you would not lose the current installed apps as this would only flash the
updated system plus root binary. After doing so please download superuser from android market
the flash process take less than 10 minutes.
btw i use this command
fastboot flash system system.img.ext4
yup i use a pc to this.
disclaimer:
there's risk of bricking your mediapad. do it at your own risk.
Thanks,
I might try this.
Where can I find system.img.ext4?
DUH!!!! I unzipped the Hauwei firmware folder update.zip and found it - that's the right one right?
---------- Post added at 02:37 PM ---------- Previous post was at 01:55 PM ----------
Also, I don't know if you saw or not, but I lost 4G connection since I originally had a T-Mobile SpringBoard and flashed the Hauwei firmware to it. Do you think rooting it will allow the 4G again? If so, would it be easy for a 'tard like me to do ?
yup that's the right file. I'm using mediapad.
Probably this rom resources file does not have the 4g icon.
Do you still have the same broadband speed?
Can you please verify this using speedtest?
Here's my recent speeds (3G). I wish I would've saved my 4G tests, but didn't realize I was going to loose all of that.
https://skydrive.live.com/redir.asp...372FEF79249B184B!172&authkey=!AHnxi6Q8Yj6srLQ
Also, what do you know about typing ()()2846579()()+ in the calculator. Can anything really be modified here? I've played around with the preferred frequencies and radio bands, but not sure what's really going on. And I think some of it goes back to a default anyway.
I was hoping that something like no 4G icon was the issue, but looking at the speeds (these are test from an area that I know get 4G speeds). I go to:
Settings >Mobile networks>Network operators>Search networks I only see T-Mo and AT&T 2G & 3G
Hi together,
I'm trying to root my Huawei Vision U8850. There seems to be only very little information about this phone available, and I've had no luck so far trying various methods.
I've tried SuperOneClick 2.3.3, UnlockRoot, DooMLoRD v4 and some other batch scripts, with no avail. The problem seems to be that the phone is running with Android 2.3.7, and most of the tools are using the Zerg Rush exploit, which seems to have been fixed in 2.3.7.
Zerg Rush always returns a "[-] Hellions with BLUE flames" message, which I suppose means that it failed.
Does anybody know a way of how to get root for this phone?
I've found a Chinese(?) forum where they asked the same question it seems, but I couldn't register there without some sort of code. Maybe somebody knows actually Mandarin/whatever.
translate.google.com/translate?hl=de&sl=auto&tl=en&u=http%3A%2F%2Fbbs.huaweifan.com%2Fshouji-15208--2.html resp. bbs.huaweifan.com/shouji-15208--2.html (links not clickable I'm afraid).
Some more information:
Model
HUAWEI-U8850
Android Version
2.3.7
Kernel-Version
Apps_2.6.32.9-perf
Build-Nummer
U8850 V100R001C169B244SP22
// Edit
Rooted firmware (Huawei.Vision.U8850.Rooted.Firmware.V100R001C279B244SP22.Android.2.37.rar):
ww*.mediafire.com/?aaqs7vt7aavv3
I've found a Russian forum with quite much activity regarding the U8850 Vision. Problem is, I don't speak Russian, and registering on that forum requires you to input a Cyrillic CAPTCHA, which of course didn't work with Window's Character Map.
I've tried to translate the instructions on how to get root from this post: 4pda.ru/forum/index.php?showtopic=257207&st=1700#entry14246750
I am however not sure if I understood everything correctly, or if Google Translate was working correctly.
I'm also not sure what exactly the "Russian Channel" firmware will do to my phone (e.g. phone is only in Russion, keyboard is in cyrillic, GPS not working, etc).
The firmware can be found on the official Huawei page (alongside a "Japan softbank" version): huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3812&tb=0
Below is my take on the instruction (which I haven't tried yet). Does this sound plausible to you?
Instructions updated, see below.
Click to expand...
Click to collapse
*** NOTE ***
The forum software won't allow me to post links, and obviously it corrupts text links. So if there appears a space within a link, you have to remove it for the link to work.
Ok, I've successfully performed the root now by creating a custom firmware which includes su, busybox and Superuser.
I've uploaded the firmware here:
mediafire.com/?aaqs7vt7aavv3
To flash the firmware, you will need the "U8850 Upgrade Tool V1.8.4" from here:
ww*.huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDQwNjQ=
This will erase all of your user data, so save anything before you do this. And of course I'm not responsible if anything bad happens to your phone, all I can say is that it worked for me.
The firmware is based on a Slovenian one found here:
johnnyparanoia.blogspot.co.uk/search/label/Huawei%20U8850
I've labelled this method the "Russian Root", because I found the initial instructions on a Russian forum. I've translated the instructions and added anything missing to it.
See below for a detailed instruction on how to create a custom rooted firmware for yourself.
/**
* Russian Root
* Gaining root permissions on the Huawei Vision U8850 with Android version 2.3.7
* Originally posted at 4pda.ru/forum/index.php?showtopic=257207&st=1700#entry14246750
* Translated into English, re-arranged items and added some stuff
* I've also replaced the Russian based firmware with a Slovenian, because it was newer
* Discussion Thread: ww*.handy-faq.de/forum/huawei_u8850_vision_forum/227127-huawei_u8850_vision_root_rooten.html
* Credits go to Sanaes & freedroid
*/
You'll need both Windows and Linux to perform this update (e.g. a second computer, multiboot or a virtual machine).
In Windows:
1) Download the "U8850 Upgrade Tool V1.8.4" from here:
ww*.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3812&tb=0
2) Download the "U8850 (Android 2.3.7)V100R001C279B244SP22(Slovenia TUS Mobil)" firmware from johnnyparanoia.blogspot.co.uk/search/label/Huawei%20U8850 or madmodder.co.uk/huawei/u8850/huawei-u8850-firmware-list.htm and extract the contained firmware (we need the SFC-244M-0-8025-A03.nb0 file)
3) Download nb0-utils.jar from yadisk.cc/d/MbFUvzN6bic
4) Download busybox from yadisk.cc/d/JIWwvYPNblL
5) Download su from yadisk.cc/d/XtZXIL9rble
6) Download Superuser.apk from yadisk.cc/d/7TQNlhsFbm1
The following steps need to be performed under Linux:
7) Create and navigate to the folder where you want copy the downloaded files to (e.g. "sudo mkdir /home/username/u8850/")
8) Create a folder where you want the firmware to extract to: (e.g. "sudo mkdir /home/username/u8850/extracted/")
9) Copy the downloaded files to the folder you just created in step 7), using a usb flash drive or whatever means you have (e.g. "sudo cp /path/where/they/are/saved/*.* /home/username/u8850/")
10) Go to that folder: "cd /home/username/u8850/"
11) Unpack the downloaded firmware into the "extracted" folder, using the following command: "sudo java -Xmx512m -jar nb0-utils.jar unpack SFC-244M-0-8025-A03.nb0 /home/username/u8850/extracted"
- Note #1: if this doesn't work, try to install Java first: "sudo apt-get install openjdk-6-jre"
- Note #2: extracting the firmware requires quite a lot of RAM, hence we added the "-Xmx512m" flag which allows Java to use up to 512 MB of RAM. Make sure your Linux machine has this much RAM available!
12) The extracted file "SF8-0-244M-0002-system.img.ext3" contains the Android file system, so we need to mount this file.
- To mount it, we first need to create a folder in /media/: "sudo mkdir /media/android"
- And then we mount the file to that location: "sudo mount /home/username/u8850/extracted/SF8-0-244M-0002-system.img.ext3 /media/android/"
13) Copy the previously downloaded "busybox" file to /media/android/xbin/: "sudo cp /home/username/u8850/busybox /media/android/xbin/"
14) Change the file permissions to 755: "sudo chmod 755 /media/android/xbin/busybox"
15) Copy the previously downloaded "su" file to /media/android/bin/: "sudo cp /home/username/u8850/su /media/android/bin/"
16) Change the owner and group of that file to root: "sudo chown root /media/android/bin/su" and "sudo chgrp root /media/android/bin/su"
17) And the rights to 6755: "sudo chmod 6755 /media/android/bin/su"
18) Copy the previously downloaded "Superuser.apk" file to /media/android/app/: "sudo cp /home/username/u8850/su /media/android/app/"
19) And change the permissions to 644: "sudo chmod 644 /media/android/app/Superuser.apk"
20) Now unmount the image file again: "sudo umount /media/android"
21) And pack the firmware again into a .nb0 file: "sudo java -Xmx512m -jar nb0-utils.jar pack /home/username/u8850/firmware_rooted.nb0 /home/username/u8850/extracted/"
Now we're finished in Linux, the actual flashing has to be done in Windows.
22) Somehow transfer the newly created firmware_rooted.nb0 file to Windows (e.g. with a USB stick).
23) Unpack and install the "U8850 Upgrade Tool V1.8.4". This will install a "SUT L3" program ("Software Update Tool") and the USB drivers for the U8850 Vision.
24) Connect your phone with a USB cable and use the Software Updater to flash the firmware_rooted.nb0 to the phone.
Don't get (too) nervous during the flashing and booting procedure, it does take quite a while.
After completion, all of your data will be reset and the phone should now be rooted. To check, use e.g. "Root Checker" from the market or any app that needs root rights.
Alternative (original) nb0-utils.jar download location:
dl.dropbox.com/u/1134234/AndroidTeam/utils/nb0-utils.jar
Click to expand...
Click to collapse
Hi,
I would like to ask if there are any problems after rooting (with gps etc.) ?
I also use stock Slovenian firmware and have bought a phone at Mobitel:
Android Version
2.3.7
Kernel-Version
Apps_2.6.32.9-perf
Build-Number
U8850 V100R001C279B244SP26
kingeedorah said:
Hi,
I would like to ask if there are any problems after rooting (with gps etc.) ?
I also use stock Slovenian firmware and have bought a phone at Mobitel:
Android Version
2.3.7
Kernel-Version
Apps_2.6.32.9-perf
Build-Number
U8850 V100R001C279B244SP26
Click to expand...
Click to collapse
I haven't noticed any particular problems which I could connect to the rooting process. Yesterday it did take the phone quite a while before getting a GPS fix, but it has done that before (seems to be a general problem for me, even with AGPS settings), but GPS itself was working fine after that.
I'm also having some issues where the internal partition (resp. the /system/ folder) reports an error that there's no space left on the device, e.g. when trying out AdAway instead of AdFree Android. And the latter was working fine.
Besides that, it's working fine. I can call / be called, camera is working, music is working, radio is working (if you can call that working).
I haven't figured out yet how to install the Clockworkmod Recovery yet though. It's still requiring a valid certificate for the update.zip on the Recovery screen, that hasn't changed.
Hi guys,
U8850 Update Tool crashes when trying to flash a phone with the rooted imaged, works just fine with other images. Anyone else facing this problem ?
spoonium said:
*** NOTE ***
The forum software won't allow me to post links, and obviously it corrupts text links. So if there appears a space within a link, you have to remove it for the link to work.
Ok, I've successfully performed the root now by creating a custom firmware which includes su, busybox and Superuser.
I've uploaded the firmware here:
dl.dropbox.com/u/5387565/Android/Huawei.Vision.U8850.Rooted.Firmware.V100R001C279B244SP22.Android.2.37.rar
To flash the firmware, you will need the "U8850 Upgrade Tool V1.8.4" from here:
ww*.huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDQwNjQ=
This will erase all of your user data, so save anything before you do this. And of course I'm not responsible if anything bad happens to your phone, all I can say is that it worked for me.
The firmware is based on a Slovenian one found here:
johnnyparanoia.blogspot.co.uk/search/label/Huawei%20U8850
I've labelled this method the "Russian Root", because I found the initial instructions on a Russian forum. I've translated the instructions and added anything missing to it.
See below for a detailed instruction on how to create a custom rooted firmware for yourself.
Click to expand...
Click to collapse
---------- Post added at 02:38 PM ---------- Previous post was at 02:09 PM ----------
napalmique said:
Hi guys,
U8850 Update Tool crashes when trying to flash a phone with the rooted imaged, works just fine with other images. Anyone else facing this problem ?
Click to expand...
Click to collapse
Nevermind, it was the filename that confused the Update Tool, changed the filename to a shorter one and it worked, it flashed it, now booting.
need help
I would like to download from
dl.dropbox.com/u/5387565/Android/Huawei.Vision.U8850.Rooted.Firmware.V100R001C279B2 44SP22.Android.2.37.rar
but error come out.
Can you please re upload that file again?
Thank you.
adp71500 said:
I would like to download from
dl.dropbox.com/u/5387565/Android/Huawei.Vision.U8850.Rooted.Firmware.V100R001C279B2 44SP22.Android.2.37.rar
but error come out.
Can you please re upload that file again?
Thank you.
Click to expand...
Click to collapse
Yes, I'm afraid Dropbox doesn't really like public links, they've disabled that feature temporarily for my account. Although I severly doubt I've really reached the limit of 20 GB/day for this single file...
I've uploaded the file to Mediafire now, although I had to split the archive to make that work. I hope it'll live longer there.
mediafire.com/?aaqs7vt7aavv3
Help
spoonium said:
Yes, I'm afraid Dropbox doesn't really like public links, they've disabled that feature temporarily for my account. Although I severly doubt I've really reached the limit of 20 GB/day for this single file...
I've uploaded the file to Mediafire now, although I had to split the archive to make that work. I hope it'll live longer there.
mediafire.com/?aaqs7vt7aavv3
Click to expand...
Click to collapse
Could you please, reupload the rooted firmware is empty the folder in mediafire
spoonium said:
*** NOTE ***
3) Download nb0-utils.jar from yadisk.cc/d/MbFUvzN6bic
4) Download busybox from yadisk.cc/d/JIWwvYPNblL
5) Download su from yadisk.cc/d/XtZXIL9rble
6) Download Superuser.apk from yadisk.cc/d/7TQNlhsFbm1
Click to expand...
Click to collapse
Can you please be kind and upload those 4 files somewhere for i can take them? I searched on google but i don't know how good those files are and i don't want to make something stupid with my phone.
Thanks in advance and keep up the good work!:laugh:
CWM
hi guys
I also installed the pre rooted firmware and cant figure out how to get CWM on there which is how i assume the jelly bean goes on?...
can anyone help... I have just had thing a day and want jelly bean on there soonest!,,
cheers guys...
spoonium said:
Hi together,
I'm trying to root my Huawei Vision U8850. There seems to be only very little information about this phone available, and I've had no luck so far trying various methods.
I've tried SuperOneClick 2.3.3, UnlockRoot, DooMLoRD v4 and some other batch scripts, with no avail. The problem seems to be that the phone is running with Android 2.3.7, and most of the tools are using the Zerg Rush exploit, which seems to have been fixed in 2.3.7.
Zerg Rush always returns a "[-] Hellions with BLUE flames" message, which I suppose means that it failed.
Does anybody know a way of how to get root for this phone?
I've found a Chinese(?) forum where they asked the same question it seems, but I couldn't register there without some sort of code. Maybe somebody knows actually Mandarin/whatever.
translate.google.com/translate?hl=de&sl=auto&tl=en&u=http%3A%2F%2Fbbs.huaweifan.com%2Fshouji-15208--2.html resp. bbs.huaweifan.com/shouji-15208--2.html (links not clickable I'm afraid).
Some more information:
Model
HUAWEI-U8850
Android Version
2.3.7
Kernel-Version
Apps_2.6.32.9-perf
Build-Nummer
U8850 V100R001C169B244SP22
// Edit
Rooted firmware (Huawei.Vision.U8850.Rooted.Firmware.V100R001C279B244SP22.Android.2.37.rar):
ww*.mediafire.com/?aaqs7vt7aavv3
Click to expand...
Click to collapse
My SUT L3 is error
napalmique said:
Hi guys,
U8850 Update Tool crashes when trying to flash a phone with the rooted imaged, works just fine with other images. Anyone else facing this problem ?
---------- Post added at 02:38 PM ---------- Previous post was at 02:09 PM ----------
Nevermind, it was the filename that confused the Update Tool, changed the filename to a shorter one and it worked, it flashed it, now booting.
Click to expand...
Click to collapse
Can you remember what the error message was when the filename was too long? Did it look like this:
Error Code: 0xc60e
Error: Download fail,
Error = SE_ERR_SUT_DETECT_DEVICE_FAIL (0xC60E).
How to install CWM on it?
shub said:
hi guys
I also installed the pre rooted firmware and cant figure out how to get CWM on there which is how i assume the jelly bean goes on?...
can anyone help... I have just had thing a day and want jelly bean on there soonest!,,
cheers guys...
Click to expand...
Click to collapse
Ditto. Should I just flash it with U8850 Upgrade Tool? How can I get CWM on the pre-rooted Jelly Bean ROM?
Hi! I flash the rooted firmware and now it's rooted! Thanks!
In another forum i found the jellybeamV3.zip but i can't enter in recovery to flash that ... any help?
How can i flash now with a zip file? Thanks!
Teovenezia said:
Hi! I flash the rooted firmware and now it's rooted! Thanks!
In another forum i found the jellybeamV3.zip but i can't enter in recovery to flash that ... any help?
How can i flash now with a zip file? Thanks!
Click to expand...
Click to collapse
since you have rooted, you can use it. why would you need jellybeamv3?
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!
I have been experimenting with flashing, etc. and somehow the lockscreen were corrupted and the pattern I was using was not longer valid. I had the fingerprint already setup so I could enter using the rear sensor, but having a corrupted lockscreen is annoying. THis method requires TWRP custom recovery. It is compatible with locked bootloaders and doesn't modify the stock boot or system. It is also compatible with all the AAXON 7 models.
If you have the stock ROM and need TWRP and ADB interface:
A. Setup ADB interface in your PC and device drivers. and connect your terminal to the PC.
B. Setup axon7tool in your computer. Enter into EDL mode by running the command "adb reboot edl" in the command prompt. The terminal will seen to be off.
C. Disable the antivirus and then backup your recovery image using axon7tool running "axon7tool -r recovery". Save the created file in a safe place.
D. Flash tenfar's signed TWRP as a new recovery using axon7tool. It will reboot to system again.
E. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
1. In TWRP , and with the ADB interface properly installed run these the commands from your computer:
Code:
adb devices
adb shell mv /data/system/locksettings.db locksettings.db.old
adb reboot
Now the system will allow you to pass lockscreen without security. In that case you do not need to apply the rest of the steps. Should you continue experimenting issues with the lockscreen, then you should apply the full procedure. Just add the following 2 steps:
2. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
3. When TWRP had fully loaded, run in the command prompt the following commands:
Code:
adb devices
adb shell mv /data/system/gatekeeper.pattern.key gatekeeper.pattern.key.old
adb shell mv /data/system/locksettings.db locksettings.db.old
adb shell mv /data/system/gatekeeper.password.key gatekeeper.password.key.old
adb shell mv /data/system/locksettings.db-shm locksettings.db-shm.old
adb shell mv /data/system/locksettings.db-wal locksettings.db-wal.old
adb reboot
If you want to restore the stock recovery, you just need to rename the recovery-backup.bin file created in step C back to recovery.bin and run the command "axon7tool -w recovery". after that you can enable your antivirus software again. axon7tool can't connect with some antivirus software. I will be editing this OP with links to the procedures required for each step. All of them are in this forums.
Enjoy
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
DrakenFX said:
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
Click to expand...
Click to collapse
Sure! but this guide is intended for people with the stock, unrooted, blocked bootloader who want to remain with a pure stock experience. Usually people without experience rooting devices. This is why I will edit the guide to add all the details to every step.
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
twilighttony said:
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
Click to expand...
Click to collapse
Yes, the procedure deletes everything. If you have problems just do the same also with:
gatekeeper.password.key
locksettings.db-shm
locksettings.db-wal
I have updated the OP just to describe the full procedure.
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Masterjuggler said:
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Click to expand...
Click to collapse
The problem of this method is that it only works if the bootloader is unlocked and the phone has the No-verify patch installed.
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Masterjuggler said:
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Click to expand...
Click to collapse
No-Verify is an additional security system implementend in the kernel. When No-Verify is active, it checks for the signature of the system partition. If the system was modified, then the system won't boot. This is why after unlocking the bootloader you have to apply No-Verify Patch or any package with the integrated patch such as SuperSU. As you can see, it has nothing to do with the app signature or the lockscreen at all.
The method presented in the OP is valid for most Android phones, and the only prerequisite is to have TWRP installed. It is safe and a lot more recommended than patching the system partition. Patching system or kernel should always be your last resort. usually deleting locksettings.db is enough, and it is a general method that works for almost any locking method.
On B25 and have followed all instructions. Seems this method no longer works :/