Related
Dear developers,
I have deleted (by mistake) program Launcer from my Smartphone and now it is not going to load. When I turn on it, there is only symbol of IDEOS. After a minute symbol starting to twinkle, but system not loading.
Could you please tell me how can I return to original firmware?
I hope someone will be able to support me.
If the launcher is the problem, you can just install another, or push again the original from a rom via adb. I assume that the device is rooted(I think you cannot delete a system app if isn´t). If you can connect to pc, then possibly you can install a launcher from huawei' s suite(I´m not sure because I don' t use windows and I haven't try this app) or from a android file manager like QtADB, Android commander or Droid Explorer. You can also install it only with adb via windows command prompt:
http://www.brighthub.com/mobile/google-android/articles/37151.aspx
And maybe, if wifi is enabled and connected, you can just install a launcher from market via pc' s web browser:
https://market.android.com/
The Modaco wiki has a list of original firmwares, but no link to Huawei works anymore. However, it is possible to download the latest China Unicom firmware - which does contain english language support. That should at least get you started.
As a new user I can't post links yet, but it is easy to find if you look for u8800 software, and then switch to Chinese.
Put the extracted directory (dload) on an sd card, in the top/root, put it in the phone and then hold volume down and power on.
Note, this will blow everything away to start from scratch so make sure it is what you want. In addition everything will be in Chinese so you need to be able to navigate to the settings to set it to English.
Better ideas? I am a noob myself so no guarantees...
I have unrooted it before to delete some trial games. And deleted Launcher by mistake.
I can't connect via usb now.
I'm afraid if I upgrade firmware, I have less memory because old one will not be deleted. Or maybe I'm wrong?
No, you're not gonna have less memory.
Did you tried to wipe to factory defaults from recovery mode(power button and vol+)?
You will not have less space because an original firware will format everything from boot partition, system and data... Basically , it will give you original software and status like it came from factory ... Like the other user said, jut find it, extract it , put the dload directory to the root of you sd card and hold volume down and start up the phone ... You will see a progress bar and when it is finished , the phone will restart itself, you will have to wait longer due to the creation of new files and there you go
vladislavnm said:
I have unrooted it before to delete some trial games. And deleted Launcher by mistake.
I can't connect via usb now.
I'm afraid if I upgrade firmware, I have less memory because old one will not be deleted. Or maybe I'm wrong?
Click to expand...
Click to collapse
Install recovery first, then you can connect your device to PC using recovery. If you have friend that have X5, copy the launcher. Else, just install Custom ROM.
The old one will be removed if you install custom ROM. If I'm not wrong.
Recovery.
Unplug USB, turn off your phone, press and hold vol + and -, then press power. Hold those three buttons until it turned on and the screen is purple-pink.
Backup all image data(copy). The rest is in the link.
Sorry for my English. Hope you understand what I write..
dancer_69 said:
No, you're not gonna have less memory.
Did you tried to wipe to factory defaults from recovery mode(power button and vol+)?
Click to expand...
Click to collapse
You are magician. it works now.
hmmm... but there is no launcher application - no workspace available. it doesn't want to load as before. strange.
upgrade don't work too. It is cycle repeating of step1/2.
I just tested and found that you can copy the missing apk from bootloader mode. In this mode(power + vol- + vol+ buttons), when connected to pc via usb cable all partitions of device mounted(at least this happens on linux). So, you can navigate to system partition on /system/app folder and copy there the missing launcher' s apk file. You can find this file on a custom' s rom(or on an official' s rooted rom like modaco's roms) update.zip file. It's on system/app folder. I tested this on linux and I could(not as normal but as root user though) copy or delete files from there.
dancer_69, thank you for your support. At my side when I connect via bootmode, there is only flashdrive is visible.
It's really strange that it is not going to upgrade.
I'm able to apply sdcard:update.zip. So maybe if to put this application inside of the card, it could install. but I don't know how to do it.
I finded apk file and tried to install it but it don't receive file because it hasn't some certificate. ???
I think you have 3 options here.
1. flash an official rom(you put the dload folder of rom's zip file on root of sdcard and boot to bootloader mode. The update starts automatic)
2. Use a linux system(maybe a livecd) to access the other partitions.
3. Try to reroot the device from pc, via superoneclick app(you can find it here), so to have access to system again.
but I haven't access to installation program area. nothing!
I have only ability by pressing (vol + and on) to choose install update.zip from flash card.
so.
1. when I runned new firmware from dload it didn't install. it was cycling at first level (1/2)
2. linux is good idea. but I'm not sure that it's will be profitable. maybe I have turned off access to partitions inside of phone
3. I can't install superoneclick as I'm not able to install any application.
I hope we are closer to some geniously idea. I have bought phone yesterday and we haven't service center in our city. So, I need to buy the other one.
This is not so serious problem, it' s not hardware, it´ software related. And I think you cannot turn off access so easy.
The superoneclick is a pc application. You don't need to install something on device(if I remember well, because I use it once before a long time). You can try it.
And you can try linux too.
I don't think that this is a problem that only service can solve it.
What firmware you tried? Try another one. And better try to find the one that you device has(if you know it)
Thank you for positive opinion.
1. Will try to change firmware as you said. Try 2 more firmware from Huawei.
2. Superoneclick needs approval from phone, today night I wasn't able to run it.
3. I'll try Linux too.
dancer_69 said:
This is not so serious problem, it' s not hardware, it´ software related. And I think you cannot turn off access so easy.
The superoneclick is a pc application. You don't need to install something on device(if I remember well, because I use it once before a long time). You can try it.
And you can try linux too.
I don't think that this is a problem that only service can solve it.
What firmware you tried? Try another one. And better try to find the one that you device has(if you know it)
Click to expand...
Click to collapse
Thank you very much for your excellent support. It's work now after trying of other firmware. Everything is excellent now.
I only noticed that battery is no very capacitive.
Please, send me your paypal account, I want to donate you a little.
Hi. id like you all who are sharing your knowledge through this fantastic forum and special thanks to the developers of this website. ive recieved my nook simple touch with glowlight firmware 1.1.5 just 5 days ago and was successfully rooted. then i wanted to add arabic language so i followed the this method which is mentioned in one thread by using the CWM method after rebooting my device got stuck at the screen of downloading the five dots and the screen was flashing without stopping.
i was so irritated knowing nothing to do and searched the net for any solution but at the end i found one sying that you can try the factory recovery by using CWM method.
it worked but now im not able to copy any app to system. file explorer says your device is unrooted.
please what should i do? recover my nook or re root it again.
thanks in advance
You did a factory recovery, therefore it's not rooted anymore.
Something you did before annoyed your Nook.
If the dots are running you can sometimes get a logcat.
You will need to have gotten ADB working already, which requires rooting.
That's a bit of a bind.
A console log might show you something too, but you'd need a shell to run dmesg or to solder in wires to access the UART on the board.
So, what exactly did you do to get Arabic working?
Try doing things in small steps and see where it locks up.
then
thank you Renate for your reply. now what do u think i ve to do whether to root it again directly or ive to make recovery to the system first by using backup because i cant copy any file to system so that ill be able to add arabic fonts.
kamal nook said:
thank you Renate for your reply. now what do u think i ve to do whether to root it again directly or ive to make recovery to the system first by using backup because i cant copy any file to system so that ill be able to add arabic fonts.
Click to expand...
Click to collapse
if ur successfully root ur device again... go to market and download (File manager) and then u open it press up (button at the header) it will make u go to the device root system and before u navigate the program will warn u and then go to the directory u should go for put Arabic fonts and then accept replacement and then restart ur device and it should work
thx
Can someone help me to change my phone's mac id.i hav kitkat ROM.
Plz give detailed steps as I am new to these things.
(Phone rooted)
Abhimanyu_1997 said:
Can someone help me to change my phone's mac id.i hav kitkat ROM.
Plz give detailed steps as I am new to these things.
(Phone rooted)
Click to expand...
Click to collapse
For permanent change, go here.
For temporary change, go here.
Temporary change is easy to do, but MAC id will change once you switch wifi on/off or reboot.
Permanent change, might work or not depending on the kernel, and is surely a complicated process.
So the choice is yours
use Pry-fy
Abhimanyu_1997 said:
Can someone help me to change my phone's mac id.i hav kitkat ROM.
Plz give detailed steps as I am new to these things.
(Phone rooted)
Click to expand...
Click to collapse
you can use app like pry-fy. download it from pay store.
Changing mac id to specific one
gks131 said:
you can use app like pry-fy. download it from pay store.
Click to expand...
Click to collapse
Sry for late reply........Actually i want to change mac id to access a mac is filter network....so i need to change it to a specific mac id(I hav mac id with access to the network)....
Abhimanyu_1997 said:
Can someone help me to change my phone's mac id.i hav kitkat ROM.
Plz give detailed steps as I am new to these things.
(Phone rooted)
Click to expand...
Click to collapse
Detailed Procedure which i found working on my device ( Lenovo A 6000 + )after lots of attempts. Hope it helps someone.
1. Take backup of all data.( Incase of data loss, which i haven't experieced with expeerience of araound 20 times rooting)
2. Root your phone using kingoroot (via PC ) (my preference --you can root any way you want )
3. Check root sataus using root checker app (Its in playstore )
4. Make sure you have Super User (App which guarantees root access) .Its is installed automatically when rooted via Kingoroot software.(Or install it from playstore)
6. Install ESFile Explorer from playstore (again its my preference,you can use any root explorer )
7. Enable root explorer option in ES File Explorer(Grant root access when asked)
8. Directory to change mac id
Device -> sys -> devices -> soc.0 -> a000000.qcom,wcnss -> wcnss_mac_addr.
9.Open the file in ES Note Editor and change the mac to whichever you want.
10. Switch on aeroplane mode and off it.(Then only mac id changes).
Note:-
1. Mac ID is reset when resetted .(Switching wifi on and off doesn't affect)
2. The above procedure works in stock ROM (lollipop and kitkat )
Plz reply if any probs...I figured it out after too many attempts as i am quite new to these things.
Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
IMPORTANT: Read the ENTIRE instructions set before starting, make sure you know what you are getting into. I have been as straight forward as possible with my instructions to assist noobs with the procedure.
Mission Statement
The purpose of this post is to combine the following 4 guides, in an easy to read manner to help people get from a stock Note 4 Version running 6.0.1 to a fully rooted Note 4 running CM13.0
Guides Referenced and Summarized:
[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V] http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
(no title, sub post #1403, describes going from CPD1 to Jasmine with CPF3 and Firmware/Kernel Patch) http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
[ROM] [6.0.1] [UNOFFICIAL] CyanogenMod 13.0 [Jul 24, 2016] http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I will use large chunks from some of these guides, skip some parts not necessary and/or extrapolate/modify on the instructions given within.
Thankx & Achnologments
Main Contributors (I plagiarized, quoted, or sourced)
Robots_Never_Die
hsbadr
Tech Support
BickNasty
Feel like I missed you, it wasn't intentional....PM me and I'll consider adding you, if I feel you actually contributed in some way or I copied your work.
Satisfied Customers (Did my method work for you? Post a reply and let us know, I'll add you to the list)
jwp1299 - 1 hour
Viper-Link
keviinese - 1.5 hours
pfcland - 1.5 hours
Required Apps (Google Play) All Free
Search for and install these apps
eMMC Brickbug Check (free)
Required Downloads (note on version numbers: version numbers I specify are ones available at the time I wrote this guide. For most tool grab the newest version, such as Odin/ADB)
NOTICE Total size of Downloads is approximately 7 GB, some of the links may be slow! Time required may vary due to your network speeds, and luck with speeds from file hosts. (expect several hours)
ADB – minimal_adb_fastboot_v1.4.0_setup.exe
Odin - newest version (3.12.3 at time of writing)
Kingroot - Grab latest stable version, only grab NewKingroot(XXXXX).apk
Samsung USB drivers (windows) - newest version
Bootloader Unlock - samsung_unlock_n4-fix
TWRP - twrp-3.0.2-0-trltevzw.tar.md5
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5
N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)
JasmineROM_v7.0_N910VVRU2CPF3.7z
N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z
Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)
UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)
Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)
XPosed is OPTIONAL, but there are a lot of rooted apps that use the XPosed framework to get more control over your phone. Such as hiding mock locations for example.
NOTE: Internet is REQUIRED for KingRoot to function (grants temporary root, so ADP commands can be executed to unlock bootloader), at one point WiFi will NOT function but internet is still required. So a valid SIM with internet is required (Verizon will definitely work, others might[/] work)
NOTE: The entire installation will take an estimated 1-2 hours. (Not including time spent downloading) All steps are MANDATORY, do not SKIP anything....You've been warned
Install eMMC Brickbug Check (free) on your phone, and RUN IT. Your CID MUST start with 15. If it doesn't I can't help you, and this guide is not for you.
Install the Samsung USB drivers on your windows PC
Backup your phone, if you don't know how.....google it...And learn how, you will want to backup frequently. Every time you get to a point you can boot up into Android, backup...it's safer for you...I will not remind you again, this is on your head.
Disable Encryption on your phone, both the SD card and Device
Disable Samsung Phone Lockout. YOU MUST DO THIS OR ELSE!!!! (Settings > Security > Reactivation Lock)
Do 2 factory resets on your phone, one after another (hold volume up, home button, power when starting to enter recovery mode where you can reset phone). Not required but if you don't, you'll spend an extra hour or two doing this because Kingroot will crash/fail more often.
Boot up your phone in Download Mode (hold volume down, home button, power)
Open Odin3, Click the AP button and select the file N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5, once it checks it, goto options and make sure the Re-Partition is NOT selected. Now click start to flash and downgrade to Android 5.1.1.
Turn on your phone, and let it boot up.
Skip everything possible when setting up your phone. Don't even put in a google account, not necessary
Goto Setings and set the following
Settings > Security > Reactivation Lock = Disabled (EXTREMELY IMPORTANT, VERIFY)
Settings > Security > Unkown Sources = Enabled
Settings > Developer Options > USB debugging = Enabled
Developer options are unlocked by going to Settings > About Phone. Find "Build Number", and start clicking it till you get a message that Developer Options have been unlocked (about 10 clicks I believe, never counted).
Settings > Developer Options > Verify App via USB = Enabled (should be by default, CHECK)
Settings > Lock Screen = None
Settings > Display > Turn off Display = 10 Minutes
Plug your phone into your computer via USB, copy the NewKingroot****.apk to your download directory (samsung-sm-N910V\Phone\Download)
Install ADB onto your Windows PC. Select an easy directory such as c:\ADB
Copy the following file directly into the ADB directory
samsung_unlock_n4-fix
Open up command line interface. Hold windows key & press R key for run, type in "cmd" press enter. Will open a terminal window for you. Type the following commands:
cd\
cd adb (or whatever you named your directory where you installed ADB)
adb devices
This should return a list of devices you have connected, something like:
Code:
List of devices attached
SerialNum device
If no devices are displayed, check you have the Samsung USB drivers installed properly.
Type the following command
adb push samsung_unlock_n4-fix /data/local/tmp/
Got an error? check your spelling (or copy/paste from me), check you put the file into the ADB directory (not just a link), your phone must be on and screen not locked and check you have usb debugging enabled.
BTW: Do NOT CLOSE the window unless I instruct you to!
Install Kingroot on your phone, which you previously moved into your downloads folder, you can find it via My Files app that comes with phone.
Now run KingRoot. Flip down to the bottom and click "Try It", it will run some quick test then give you a button to try to root your phone.
Wait...Wait...Do not worry if your phone restarts, it will go back into KingRoot automatically on reboot. Just sit back and wait, it may fail multiple times and you may have to re-run Kingroot. Just keep trying . Once it succeeds you must do the following IMMEDIATELY AND AS FAST AS POSSIBLE. Kingroot is HIGHLY UNSTABLE.
On the windows PC, back in the command window you left open. Start Typing.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
After the last command it may prompt you to type yes, do so immediately. it won't write on the screen but type yes anyway for it to continue. Once it's done it should automatically start to reboot your phone. Unplug it and pull the battery, wait 5 seconds, put battery back in and plug the phone back in.
This was the initial setup for unlocking your bootloader, you now have to run it AGAIN so turn your phone back on. Repeat steps 22-24, after the 2nd time PULL OUT YOUR SD CARD BEFORE TURNING ON YOUR PHONE
Congratulations you now have an unlocked bootloader, you can close the command window on your PC.
The SD card has a restore point for your phone prior to removing your bootlock. Save it if you want, or plug into your phone and format the 18mb partition you are able to. You must format it on a PC before you can use it again in a phone!!!! Will shut your phone off immediately if you put the SD in without formatting that 18mb partition.
Now reboot your phone into download mode (hold volume down, home and power buttons when turning on)
Open Odin App on your PC, Click the "AP" button and select the file twrp-3.0.2-0-trltevzw.tar.md5 (which you downloaded earlier). Once it does it's check, verify that re-partition is NOT selected in options. Now click start to flash twrp bootloader.
Your phone will restart, re-enter download mode. If you missed it pull cable/battery and try again.
Now extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin, same as you did with twrp. VERIFY THAT RE-PARTITION IS NOT SELECTED IN OPTIONS.
Boot up in recovery mode (hold volume up, home and power when turning on) (note: no longer TWRP since you flashed firmware, will look different again)
"Wipe data/factory reset ", then reboot your phone.
Now repeat steps 9-12 (NewKingRoot should still be in your downloads, but verify anyway) (NOTICE: wifi will NOT work with the CPD1 firmware, but Verizon internet should in case you need internet for some reason, wifi will restore later in guide - Other internet from other providers MIGHT work with proper APN settings)
Install a clean SD card into the phone.
Now repeat steps 15-25. This time you should only need to run the samsung_unlock_n4-fix file once to break your boot. This is what it typically says on successful bootloader unlock: (if you got this message, pull the battery, cable and SD card.)
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceeding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Now boot back into download mode
Flash TWRP via Odin again (I'm summarizing greatly now, as you should by now understand this kind of shorthand)
Ok, now boot up into TWRP recovery mode (vol up, home, power)
Navigate through TWRP menus to create a Backup. Click Backup Button, and swipe to create backup. (this is just so that it creates the directory structure on your phone)
Click the Reboot System button, skip all the setup you can again. (DO NOT INSTALL SUPERSU!!! will cause bootloop)
Extract the "JasmineROM_v7.0_N910VVRU2CPF3.7z" file it will create a directory called "JasmineROM_v7.0_N910VVRU2CPF3".
Plug USB into phone and to computer. Copy the JasmineROM_v7.0_N910VVRU2CPF3 folder into \Internal storage\TWRP\BACKUPS\Phone SN\
Reboot into TWRP recovery
Click the Restore button (DONT start the restore yet!!!), and check that your JasmineROM is listed as a recovery option. (don't recover YET) If it's not there you copied it into the wrong directy, try again before proceeding.
Go back to the main menu, Click the Wipe button. Click the 'Advanced Wipe' button, and wipe the following cache/dalvik/system/data
Go back to Restore (from 2 steps ago) and run the JasmineROM_v7.0_N910VVRU2CPF3 recovery, return to main menu afterwards
Go to wipe, and wipe the cache/dalvik only this time.
Reboot into download mode
Flash the N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z file via Odin
Reboot the system, this will take a LONG TIME. WAIT for it. (if reboot takes >10 min, pull battery and restart)
Once it boots up, skip all the setup again. Copy the CM13, Gapps and XPosed (both zip and apk) to your downloads. Don't unzip anything, not necessary.
Now reboot into recovery go to WIPE and do a factory reset by swiping.
Then goto Install (still in recovery) and install CM13, then Install Gapps.
Reboot your phone, this time you are setting up properly reboot will take a while to optimize your apps depending on Gapps version used. So do all your setup as you want your phone setup. Once that's done, restart the phone in recovery. (if reboot takes > 5 min, pull battery and restart)
Install via TWRP the XPossed.zip file.
Reboot your phone, once on. Navigate via My Files, to downloads and install XPosed.apk
CONGRATULATIONS. You now have a fully Unlocked, Rooted Note 4 Verizon with CryanogenMod 13.0 installed and XPosed Installed.
Suggested Apps
Kernel Auditor [ROOT], will allow you to adjust kernel settings. Such as CPU clock speeds and thermal throttling, if your phone is too hot.
Note: About ROOT[/], you will have root once you finish this guide. But it is disabled by default, you can enable root in developer options (no reboot required when changing). Unlock your developer options again, and scroll down you will see an option to enable/disable root. This allows you to keep turn off during normal use, and only enable it when you need to install an app that requires root. You can always just leave it on all the time, that is your choice.
Note: Some apps on Google PlayStore will become unavailable due to incompatibility (according to google, HA). Such as YouTube Music, you will no longer be able to install it through the store. But you can install it by using an APK site, such as APK Downloader. On this site you find the app you want on play.google.com, copy the HTTP link and put it into the APK Downloader and it will generate a direct download link to the APK file. Copy onto your phone and sideload (ie. install) through file explorer. I don't endorse them, they are just one of many places you can get APK files.
Change Log
7/28/2016
Another success story :good:
Added note about how root works in CM 13.0
Corrected Step 34
Minor text adjustments, for clarification
Made note that wifi doesn't work with CDP1 flash
Added note that you MUST HAVE a valid sim card with internet access for step 35! KingRoot requires internet to function, and Wifi will NOT WORK after flashing CPD1 firmware (incomparable drivers).
Added another note about internet at the top of the instructions, to make sure people are aware.
7/27/2016
Added Bicknasty to the Contributors list - helped resolve issues I had with CM 13.0 kernel & modem.
Added a note to downloads section regarding total size of files downloaded and expected time.
Re-wrote steps 40-48 to make it easier to understand. Adding some steps and explaining in more detail.
Added note at the top to read ALL the instructions once before starting
Added note with the estimated time to perform all the steps
Added note suggesting Kernel Auditor app, and made reference to the fact that some apps on playstore will NOT install from playstore. Suggested APK Downloader for apps not available from store
Added a Success Story Section
Added note on how to enable developer options
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
jwp1299 said:
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Click to expand...
Click to collapse
Probably, but that's the only one I know which is a free download that I'd trust.
JacekRing said:
Probably, but that's the only one I know which is a free download that I'd trust.
Click to expand...
Click to collapse
Alright, still works just a little long. Thanks so much for the guide, working great so far!
jwp1299 said:
Alright, still works just a little long. Thanks so much for the guide, working great so far!
Click to expand...
Click to collapse
How far are you now?
And let me know when you finish, critique my guide. If parts weren't clear enough let me know.
And finally if you run into any issues let me know.
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
Yea I do appreciate the help Bicknasty. I'll add you to contributors list later as helping with cyanogen issues I was having.
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
You know it wasn't so much that it annoyed me it's that there was no concrete guide telling me what to do. It's a thread here, a post there to do a specific thing but they aren't coordinated in a logical way for users to easily find.
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
jwp1299 said:
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
Click to expand...
Click to collapse
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
JacekRing said:
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
Click to expand...
Click to collapse
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
Lol yea, didn't think to mention reading the whole thing first. To me that's a given I always read everything before starting. I'll add a note to read everything.
As to download time, well it is like what 12 gigs in total? Basically 4 full versions of the Android OS at 2 gigs reach plus all the extras.
I'll try to see if I can't explain the twrp recovery of Jasmine better. Only reason you need to do Jasmine is for the 6.0.1 device drivers (such as modem).
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
JacekRing said:
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
Click to expand...
Click to collapse
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
jwp1299 said:
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
Click to expand...
Click to collapse
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
JacekRing said:
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
Click to expand...
Click to collapse
Oh of course, go ahead and add me.
Also, if you do end up making a torrent, i'd be happy to help seed at least for a while. I have pretty good upload and no data caps or anything so it would probably help a bit (anything is faster than that 100 kbps that xda was giving)
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Viper-Link said:
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
Click to expand...
Click to collapse
Not sure what to tell you viper as not enough info. Hope you figured it out...
pfcland said:
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Click to expand...
Click to collapse
Was this after the first time you inputted the adb commands our second? Make sure you pull the SD card after the second time, as it will cause reboots after the second time until you reformat the SD card on your PC. Size will be wrong on PC but size will fix when you reformat the SD card a second time on your phone.
Edit it creates like 20 partitions on the ad card when you do adb, it creates a backup of your phone os.
Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
@HvdW Please check your PMs
Also, there is some inaccuracies in your advice and statements in the above guide.
Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.
SkyHigh76 said:
Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.
Click to expand...
Click to collapse
Yes you do. Once you unlock the bootloader DRM functionality is gone. So on a stock ROM with unlocked bootlader you will need the DRM fix in order to fix the DRM functionality. If you use a custom kernel with the DRM fix already incorporated into it then you do not need to add it again as you are already using it. In either case, it is needed though...
@HvdW
I tidied up your OP. The missing step 2 is down to you. The original posts did not have a step 2, it went from step 1 to step 3.
Nice, I will try this early January, after Christmas
Thank You!
HvdW said:
Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thank you! Excellent step by step baby guide. However <b><i>do</b></i> wish to point out to future people unlocking their bootloader that it is HIGHLY essential that you backup your TA before unlocking the bootloader.
What i did is: unlocked bootloader before i ever sow this post, installed custom stock based rom, red this post, backuped DRM, and DRM found and successfully backuped intact just like it was before unlocking on Z3Compact
OpenGapps 8.0 not working, you need 8.1.0 gapps.
Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?
vinc9876 said:
Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?
Click to expand...
Click to collapse
If u see blue led u are on fastboot.
Try adb fastboot comand after mast see same help comand, now try fastboot device.
Don't worry, take,it easy. GL
Maybe u are flashtool open, close flashtool.
yo7fb said:
Try adb fastboot comand after mast see same help comand.
Click to expand...
Click to collapse
I don't think I understand what you mean.
I think the bootloader is stuck somehow. Maybe something to do with the .291 ROM being incompatible with the bootloader? I'm pretty sure I should see the fastboot screen like so:
EDIT: Got it working!
Had to reinstall adb/fastboot drivers from the flashtool installation.
HvdW said:
Introduction
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.[/hide]
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.
Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.
jhalvico said:
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.
Click to expand...
Click to collapse
Hello.
I'm sadly in same situation as you are (or was). Did everything according to guide but it is 1.5 houre since it started booting.
Do any of you guys have tip what to do?
Btw: thanks for this guide
Edit:
So i managed to get it working by following steps from the Oreo rom page.
the battery on which version lives more?
probably google dialer?
uilino said:
Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.
Click to expand...
Click to collapse
Did you install google dialer? if so, go to
Settings--> Apps¬ifications -->Advanced-->Default apps --> Phone app --> Select "Phone"
Error 7/6 when I try to install ZIP File via TWRP
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?
Hovenzius said:
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?
Click to expand...
Click to collapse
hi, i have got the same problem and i found this solution : https://forum.xda-developers.com/showthread.php?t=2522762
Restore with Xperia Companion
HvdW said:
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Click to expand...
Click to collapse
First thank you for your great post!
I try to restore my data after a successful upgrade and after having saved them with Xperia Companion but I can't succeed to make it detect my phone, so I can't use restore function... Do you know how can I achieve that? Is there some apk to install on the phone in order to make Xperia Companion recognize my phone and make restore function work?
Thanks!
Hi guys,
I have successfully followed this step-by-step:
How-to: root, keep and backup DRM keys, etc. [KitKat/Lollipops/Marshmallow/etc.]
and I also have unlocked the BL.
So, my Z3c has
- DualRecovery installed
(Z3C-lockeddualrecoveryX.Y.Z-RELEASE.installer.zip)
- superSU
- pre-rooted D5803 23.5.A.1.291
- backed-up TA
- unlocked BL
My question:
Do I still need to install Twrp or could I just boot into DualRecovery and flash CARBON-CR-6.1 + gaps from internal storage of phone?
Btw, if it isn't already blatantly obvious, I'm a total noob and without all the fine tutorials wouldn’t have a clue what I was doing.
Thanks for reading.