Could someone give me a super quick guide on how to get this on my phone? I coming from years of Samsung phones and never owned a Sony before or know anything about it. I have CM on all my Samsung devices for years and simply want a CM ROM in the Z and get it done with with. I picked up a 99% like new second-hand Ultra Z LTE C6833 today, has stock 5.02 and I don't have a clue how to get this flashed in the easiest and simplest way possible. As for locked or not bootloader, I also don't have a clue. First step which is to install TWRP I immediately got stuck because the links posted are dead (teamw.in/project/twrp2/219)
Without wanting to waste anyone's time, if someone could give me the simplest and most painless info on how to get the Z flashed, I'd be super appreciative. The threads on this phone are in the hundreds at this point and I read all sorts of very confusing and contradictory info. I worry to kill or brick it immediately before I even get started.
Thanks much in advance
Read. Thats my tip.
Every sony device past 2011 works the same way.
Look at different xperia forums, for example at the Z1 section, Z2, Z3 etc.
Look at the rooting guides. Unlock guides. Ta backup guide. Just read and read.
Dont just look at the first guide and jump right in.. read first.
Explore the Xda forum. You will find the guides im talking about. im on my phone.. a bit difficult to post links atm
Much good information can be found here
http://forum.xda-developers.com/crossdevice-dev/sony
You can check if the bootloader is unlocked or locked by opening the dialer and entering *#*#7378423#*#*. Then tap "Service Info" and then "Configuration". It'll either say "Bootloader unlocked: Yes", or "Bootloader unlock allowed: Yes/No". If it says NO on the latter, then you can't unlock the bootloader and you're pretty much screwed. Bell Canada devices have locked bootloaders, and I believe it's the same with UK O2. Chances are that you can unlock it, but you could of course be really unlucky.
If you can unlock the bootloader, then your Ultra will pretty much behave like a Nexus device when it comes to rooting and stuff like that. Just flash a custom kernel with recovery, like NUT's Dual Recovery (with CWM and TWRP), then flash SuperSU, and you'll have recovery and root. Next step is to flash CM12.1 and you're done. It's very easy once you have recovery.
Klaos3000 said:
You can check if the bootloader is unlocked or locked by opening the dialer and entering *#*#7378423#*#*. Then tap "Service Info" and then "Configuration". It'll either say "Bootloader unlocked: Yes", or "Bootloader unlock allowed: Yes/No". If it says NO on the latter, then you can't unlock the bootloader and you're pretty much screwed. Bell Canada devices have locked bootloaders, and I believe it's the same with UK O2. Chances are that you can unlock it, but you could of course be really unlucky.
If you can unlock the bootloader, then your Ultra will pretty much behave like a Nexus device when it comes to rooting and stuff like that. Just flash a custom kernel with recovery, like NUT's Dual Recovery (with CWM and TWRP), then flash SuperSU, and you'll have recovery and root. Next step is to flash CM12.1 and you're done. It's very easy once you have recovery.
Click to expand...
Click to collapse
Thanks MUCH for the detailed info!
I checked the bootloader info as you said and it's not unlocked, but can be done. It seems a daunting task but let me start by trying to get it done. Hopefully I won't screw-up the phone. I'm searching how to do it as there seem to be several ways.. After I complete the unlocking (let's hope) I'll report back and try jump on the next steps. Probably will have some follow-up doubts or questions.. this is all a very different and more complex process than the Samsung devices I've owned that never required any of this crazy gymnastics..
Anyway, thanks again very much and keep you posted!
VeEuzUKY said:
Thanks MUCH for the detailed info!
I checked the bootloader info as you said and it's not unlocked, but can be done. It seems a daunting task but let me start by trying to get it done. Hopefully I won't screw-up the phone. I'm searching how to do it as there seem to be several ways.. After I complete the unlocking (let's hope) I'll report back and try jump on the next steps. Probably will have some follow-up doubts or questions.. this is all a very different and more complex process than the Samsung devices I've owned that never required any of this crazy gymnastics..
Anyway, thanks again very much and keep you posted!
Click to expand...
Click to collapse
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Klaos3000 said:
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Click to expand...
Click to collapse
Hello I am new to Sony too and I have a question. If I unlock the bootloader root flash custom roms and then decide to get back to stock and lock the bootloader will my warranty be voided?
Sent from my C6833 using Tapatalk
mike13ftw said:
Hello I am new to Sony too and I have a question. If I unlock the bootloader root flash custom roms and then decide to get back to stock and lock the bootloader will my warranty be voided?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Yes, and that's why it's a good idea to backup your TA folder, which contains the DRM keys. Once you unlock the bootloader, these keys disappears, and that's why it's a good idea to make a backup of them. There are a couple of tools that does this for you, and you can find them in the cross-development section.
Klaos3000 said:
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Click to expand...
Click to collapse
Thank you very much!
Well so far EVERYTHING HAS BEEN A TOTAL NIGHTMARE! Nothing I try to do works!
First I installed flashtool, latest version. Im running Windows 7 64bit. It was a nightmare to get flashtool downloaded and installed. After I finally got it installed, ot took another hour updating itself and syncing stuff. When it finally finished and while holding down the Volume Down key I connected the phone to the PC via USB cable, Immediately I get an error of device driver errors. flashtool gives me also several errors. Then I tried to install the Flashtool-drivers-1.1-20130911. Then another problem, the drivers dont install at all with a message "DPinst.exe cannot execute on your operating system". That's it, finished! When I go to the Windows Device Manager, all I see is an exclamation mark under S1 Service.
So then I tried the FastBoot method. Also no luck. While holding down the Volume Up key I connected the phone to the PC via USB cable, the phone's blue light turns on, and again I get a DRIVER NOT INSTALLED ERROR. My computer refuses to recognize the phone and the device driver is never installed . The Windows Device Manager shows an exclamation mark under S1Boot FastBoot.
Then I tried the Sony way and installed the Android SDK!!!!! Immediately I find I need to download more crap, thie time the JRE Development Kit! Takes me 3 hours do download this with my useless internet connection. At this point I am already ready to throw my laptop out the window and break the stupid phone in a million pieces!
But then, there is the next problem. After all downloaded and installed, before I can even started I get stuck again, because Im supposed to go to the android SDK folder c:\android-sdk\extras\google\usb_driver and replace/install the fastboot drivers “android_winusb.inf”.. well, I dont have an extras or google or usb_driver folder on my SDK installed folder! NOTHING! THIS IS ALL RIDICULOUS!
Finally I searched everywhere on the internet for other possible Ultra Z drivers. I ft to Sony's own site and found Xperia Z Ultra (C6833, C6806, and C6843) drivers, Xperia Z Ultra (XL39h) drivers, Xperia Z Ultra (SOL24) drivers, Xperia Z Ultra (SGP412) drivers and others.. this is all crazy what a nightmare of mess and miss-information everywhere about this phone! Anyway, I tried all of them. None works.
I am so frustrated and desperate. My God! Cant get anything done. Nothing.................................. I cant believe this..
UPDATE: I give-up. Ive spent the whole day and downloaded and installed GIGS of apps and software and drivers. Nothing communicates with this useless phone. Im done.
Could anyone give me advice if its there is an alternate way to, root install a recover and flash this piece of **** phone without unlocking the bootloader which basically I cant do? If not, it will fly out the window asap, I cant deal with this ridiculous drama. Years of handling and flashing all sorts of hardware COMBINED, never gave me 1/10th of the misery and headaches this hardware has given me in one day. Xperia, never again..
By the way, Sony's "AMAZING" PC Companion app is so great and fantastic that it doesn't even have an uninstaller! No joke! Once in the computer, crawling endless directories with all sorts of files, drivers and registry entries, it will NEVER come out again. All is amazing..
You did the opposite of what I advised you to do. You did not read correct guides.
Q:Ask yourself what do you want to achieve?
You wrote in your first post "if someone could give me the simplest and most painless info on how to get the Z flashed".
Q:My counterquestion is why? Is your phones software unstable? Are you curious to learn to modify the devices software?
A:If your device is unstable. Please do a factory reset.
Q:Are you curious to learn how to modify the software?
A:Then collect information. Read. Set a timer for how long you will spend learning. Let say 45 minutes.
When 45 minutes has passed. STOP.
Take a break. Do something else and continue the next day. Repeat until you are confident to try a simple operation
For example: learn how to use adb and fastboot. Learn the commands. What they do.
I can not stretch enough how important it is to read and learn before you jump into things.
I do not see why I or anyone here should help you to unlock your bootloader. Because you do not have a clear purpose or knowledge how to do this.
VeEuzUKY said:
UPDATE: I give-up. Ive spent the whole day and downloaded and installed GIGS of apps and software and drivers. Nothing communicates with this useless phone. Im done.
Could anyone give me advice if its there is an alternate way to, root install a recover and flash this piece of **** phone without unlocking the bootloader which basically I cant do? If not, it will fly out the window asap, I cant deal with this ridiculous drama. Years of handling and flashing all sorts of hardware COMBINED, never gave me 1/10th of the misery and headaches this hardware has given me in one day. Xperia, never again..
By the way, Sony's "AMAZING" PC Companion app is so great and fantastic that it doesn't even have an uninstaller! No joke! Once in the computer, crawling endless directories with all sorts of files, drivers and registry entries, it will NEVER come out again. All is amazing..
Click to expand...
Click to collapse
That what I did for the drivers and work just fine .Try it
Edit: forgot to post link http://forum.xda-developers.com/showthread.php?t=2095087
Sent from my Xperia Z Ultra using Tapatalk
SÜPERUSER said:
You did the opposite of what I advised you to do. You did not read correct guides.
Q:Ask yourself what do you want to achieve?
You wrote in your first post "if someone could give me the simplest and most painless info on how to get the Z flashed".
Q:My counterquestion is why? Is your phones software unstable? Are you curious to learn to modify the devices software?
A:If your device is unstable. Please do a factory reset.
Q:Are you curious to learn how to modify the software?
A:Then collect information. Read. Set a timer for how long you will spend learning. Let say 45 minutes.
When 45 minutes has passed. STOP.
Take a break. Do something else and continue the next day. Repeat until you are confident to try a simple operation
For example: learn how to use adb and fastboot. Learn the commands. What they do.
I can not stretch enough how important it is to read and learn before you jump into things.
I do not see why I or anyone here should help you to unlock your bootloader. Because you do not have a clear purpose or knowledge how to do this.
Click to expand...
Click to collapse
Just to briefly correct you: I'm the type of guy that has NEVER gotten a virus on a computer. I'm the type of guy that has rooted, flashed and played around with phones for many years with more or less degree of difficulties, but always successful. I'm the type of guy that has helped many many people in this community with their hardware, when I know how. I'm the type of guy that has knows many things about the works of Samsung devices that I have used for many years and have never had an issue learning what's needed. I am the type of guy always ready to offer friendly advice when someone is in need of something I may offer help with. Finally, I am the kind of guy that has a Dell laptop, running Windows 7 64bit, that by whatever reason refuses to install the proper drivers for the Ultra Z, or the kind of guy that maybe has a flawed Ultra Z. After all, it's a second hand unit and about 2 years old, despite that it looks new.
So, the only thing this type of guy can do, is 1) try a different computer to see if the communications with the phone work, and if not, check the phone because obviously that's where the only place the problem can come from. To try different USB cables and do phone resets, that I did today several times. I learned those basics the first day of my flashing life, long long ago.
There is NOTHING to read or learn or do, when there is no communication between the phone and the computer that connects to it. You seem not to understand the very basics of the problem here is not lack of reading, instead is only lack data flow between devices.
Anyway, thanks for the constructive advice!
2 extra things: all the tools, apps and drivers you have suggested, I have them all. All the procedures, steps, folders where stuff is and goes.. I've done all. I learn very quickly. The issue is none of that.. the issue is, no driver for this phone will install on my laptop, for whatever reason. Is that simple.
And then there is another issue.. for you, and most people on XDA, downloading and getting "stuff" is a breeze. But not me. Where I am, XDA is blocked, and even with a VPN, hardly works. To reply to you or just log-in, sometimes is an hour. And most file hosts? Mega? Rapidgator.net? Zippy share?.. a few hundred others? Well.. they doesn't work. Uploaded.net.. Mediafire.. Google Drive.. AndroidFile Host, and just about everything else, all DON'T WORK. All blocked. So are blocked most of the VPNs now. So, while for you, go here, get this, download that, is all a piece of cake, for me, is not. Most things to get download are truly a nightmare. And when it comes to download a ROM or any 2 or 3 hundred Mg files, sometimes takes me days of endless wait and interrupted downloads. I live in a crazy country called China, where all Google stuff, Android included, is forbidden, and all around it.. XDA included.
So, talk is easy. But when access to simple and basic information is so difficult to get and everything comes at a premium, life is really a bit more complicated than maybe you can imagine. So...... yeah, help is very much appreciated indeed, in the same way I am always willing to help others when I can, without calling out their lack or reading or question their abilities to follow my advice
Alright, that was quite painful to read, not because of something wrong you wrote, but because I've been there too. I don't know what device you had prior to the Ultra, but just forget what you learned from that device.
Just sit down, relax and figure out what you're trying to do, and then how to maybe achieve it. Yes, I do understand that your laptop doesn't cooperate at all, but that's just technology. Of course it won't work when it should. We've all been there.
1. Set up your computer to be able to communicate with your Ultra. Installing the SDK is overkill since the only thing from the SDK you need is Fastboot and ADB drivers. You can easily install those two by installing this tiny tool that does it for you.
Fastboot and ADB is now installed.
2. Install Flashtool. You've already done this. Connect your Ultra and open Flashtool. Flashtool should grab and set things up for the Z Ultra automatically. This should only take 5-30 seconds. Not three hours. The device should still be powered on at this stage.
3. Okay, now you have Flashtool installed, and it recognizes your Ultra. Next step is to go to that Sony site I linked to, to get the unlock key. Fill in the required info, and you'll get the key sent on your email. Don't misplace it.
4. Go back to Flashtool, hit the "BLU" button, paste the key in, and that's it. Don't set the device into fastboot or flashmode until Flashmode asks you to do it. Fastboot can be active and connected forever, but Flashmode will disconnect by itself after a minute or so.
5. Your bootloader is now unlocked. This means that you're free to do whatever you'd like to do with it. Xperia devices do not come with a default recovery system, so we'll have to flash a custom kernel that includes a recovery. You can find them in the dev section. Once you've flashed or hotbooted a custom kernel with CWM or TWRP, you're free to root by flashing SuperSU, and flash whatever ROM you'd like to flash.
It's very easy to deal with Xperia devices once you have things set up (mainly Flashtool), and the basic steps are:
- Unlock bootloader (one time thing)
- Flash custom kernel
- Done
It's the same procedure as Nexus devices, only that we have to use special tools to unlock our bootloaders, while Nexus' use one command in a terminal. The issue here though is the tools, and not the process, and I feel your pain. I really do. It would've been so much easier if I could just show up at your door, do it for you, and leave
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
VeEuzUKY said:
And then there is another issue.. for you, and most people on XDA, downloading and getting "stuff" is a breeze. But not me. Where I am, XDA is blocked, and even with a VPN, hardly works.
Click to expand...
Click to collapse
Then let's make it easier? My upload speeds aren't an issue, so please point to a site that I can upload the tools too, which you then can download from at proper speeds
Klaos3000 said:
Alright, that was quite painful to read, not because of something wrong you wrote, but because I've been there too. I don't know what device you had prior to the Ultra, but just forget what you learned from that device.
Just sit down, relax and figure out what you're trying to do, and then how to maybe achieve it. Yes, I do understand that your laptop doesn't cooperate at all, but that's just technology. Of course it won't work when it should. We've all been there.
1. Set up your computer to be able to communicate with your Ultra. Installing the SDK is overkill since the only thing from the SDK you need is Fastboot and ADB drivers. You can easily install those two by installing this tiny tool that does it for you.
Fastboot and ADB is now installed.
2. Install Flashtool. You've already done this. Connect your Ultra and open Flashtool. Flashtool should grab and set things up for the Z Ultra automatically. This should only take 5-30 seconds. Not three hours. The device should still be powered on at this stage.
3. Okay, now you have Flashtool installed, and it recognizes your Ultra. Next step is to go to that Sony site I linked to, to get the unlock key. Fill in the required info, and you'll get the key sent on your email. Don't misplace it.
4. Go back to Flashtool, hit the "BLU" button, paste the key in, and that's it. Don't set the device into fastboot or flashmode until Flashmode asks you to do it. Fastboot can be active and connected forever, but Flashmode will disconnect by itself after a minute or so.
5. Your bootloader is now unlocked. This means that you're free to do whatever you'd like to do with it. Xperia devices do not come with a default recovery system, so we'll have to flash a custom kernel that includes a recovery. You can find them in the dev section. Once you've flashed or hotbooted a custom kernel with CWM or TWRP, you're free to root by flashing SuperSU, and flash whatever ROM you'd like to flash.
It's very easy to deal with Xperia devices once you have things set up (mainly Flashtool), and the basic steps are:
- Unlock bootloader (one time thing)
- Flash custom kernel
- Done
It's the same procedure as Nexus devices, only that we have to use special tools to unlock our bootloaders, while Nexus' use one command in a terminal. The issue here though is the tools, and not the process, and I feel your pain. I really do. It would've been so much easier if I could just show up at your door, do it for you, and leave
Click to expand...
Click to collapse
Klaos3000, you are great. Difficult to find words to thank you the time you take to try help me out. Really much appreciated. It's almost 1AM my local time here and tomorrow I will give a try to all you suggest me step by step. If I run into additional difficulties, I will try use another computer. Maybe is my specific laptop with my windows installation that is being stupid with the Ultra Z hardware. I have installed endless drivers for HTC, LG and mainly Samsung phones and tabs, and have never had any difficulty.. just last week I installed drivers for a friend's new Galaxy Tab S2, got a recovery in, got it rooted and manually cleaned of a lot of useless samsung system bloat stock apps and crap, all about 20 minutes. Hard to understand why with an Xperia phone, things are so complicated. Anyway, tomorrow will follow your advice and report back.
Again, thanks a lot for your help
Klaos3000, despite being so late, I decided to give this another try and follow your steps.
But I Immediately run into similar problems.. I CANNOT get drivers installed.
1. I have downloaded and installed Minimal ADB and Fastboot as you suggested.
2. I have flashtool-0.9.19.7 installed and did the 0.9.19.8 upgrade by updating the x10flasher.jar file.
3. Now you suggest I connect my phone and open Flashtool. But connect my phone how? Boot it up? USB debugging on or off? Or you mean connect the phone turned off and then on press Volume up? Or press Volume down?
I tried all this, and again I get a device driver error. Because there are NO DRIVERS installed for the phone. This is same problem as before. And if I go to the drivers folder inside Flashtool and try install the drives, I immediately get an error that they cant be installed in my operating system.
I am completely stuck as before in this very simple step.
Attached screnshots when I enter Flashmode:
And this is what happens when I try install drivers from C:\Flashtool\drivers:
And if I try go to FastBoot Mode with the phone's blue light on (Volume up + connect USB Cable) this is what I get:
UPDATE:
I have finally unlocked the bootloader, using the Fastboot method! I still could not get the Flashtool drivers to recognize my phone, but the FastBoot ADB drivers installed without a problem. 2 things Ive learned with this experience I want share with anyone in the future that has similar difficulties:
1) I switched to a friend's old laptop with Windows XP. Under XP, FastBoot ADB drivers installed at the first time and absolutely zero problems.
2) I used a USB 2.0 port! If connected to a USB 3.0 port, another cascade of new problems immediately arise.
So that's it. I want thank VERY MUCH everyone in this thread that was so kind to try and help me as much as possible. I would not have gotten this done with it
My next step is to install a recovery from:
http://forum.xda-developers.com/showthread.php?t=2261606
But I only see downloadable versions for looked bootloaders. Also, I want to flash a custom CM based ROM next and see a warning regarding Unlocked Bootloader with CyanogenMod, AOSP and OmniRom that the kernel needs be repack to replace the built in recovery with XZDualRecovery or things will either not work at all or require unexpected operating instructions. So again, I am extremely confused as what files to choose and what to do and worry to look for the wrong thing and worry to make a catastrophic mistake. And also I have no idea what method I should use:
- ZU-lockeddualrecovery2.8.21-RELEASE.flashable
- ZU-lockeddualrecovery2.8.21-RELEASE.installer
Thanks again for the advice and the feedback in all this
Related
Okay, so I waited patiently for Lollipop to drop on the Z Ultra C6833 in Singapore -- but apparently this is almost the only country which will not be getting the OTA (I can't even get them to answer on Twitter or FB whether this is true). So, I finally followed Sony's instructions to unlock the bootloader. That succeeded. But then I was presented with a language-selection screen after the subsequent boot which I wasn't expecting, and since I thought I just wanted to just go down into recovery and not set up a refresh ROM, I powered off the device without proceeding through the language selection screen.
Apparently, that was a bad call because I've been in a bootloop since then which triggers after a freeze in the swishy boot animation. I flashed the TWRP recovery image I found on these forums, but no go. The volume up/down tricks have never put me into a recovery environment, and the only thing I can succeed in doing still is putting it into fastboot. Sony PC Companion's recovery process won't complete because it detects foreign software (probably the TWRP recovery, right? -- but where do I get stock recovery, and would that even work anyway? And Emma let me in once, but subsequently refuses to respond to the supplied configuration INI file (I'll try to fully reinstall this thing later).
I love this phone. Best phone I've ever had. My plan is up and I *could* get a new phone, but I don't want to move on! I want my Z Ultra. So, someone hold my hand, please. I am even willing to pay a bounty (via PayPal) for a live chat if that is what it takes to get someone knowledgeable to help me in a timely fashion. I live in Singapore (UTC+8), and I do biphasic sleeping, so I'll also be awake between 1:30am and 4:00am my time. Thanks in advance for **any kind of help!**
Sincerely,
Hopeful and anxious expat in Singapore
Edit: I will pay $60 USD by PayPal to the individual who can provide a productive resolution (preferably write here and be available over chat so I can learn from you -- PM me for Hangouts, Skype, VSee, or Firefox Hello contact details). A "productive resolution" does not mean necessarily that we will fix my phone. It may mean that we conclude definitively that we can't. I will take this thing into the Sony Service Centre and give them my money if I have to, but I'd rather give it to one of you fine folks. I only want to give a few more hours to this. I've already been phoneless for two days.
New information in the continuing saga
Reinstalling Emma didn't help, nor did putting customization.ini in creative locations or pasting the developer mode line from that INI file into other INI files within the Emma directories. So I gave up on Emma until I can get to another computer.
After a user kindly uploaded this SIN file (http://forum.xda-developers.com/xperia-z-ultra/general/bootloader-devices-real-recovery-t3117566) to a fileshare for me, I figured out (here https://android.stackexchange.com/questions/65058/why-custom-roms-are-zip-filed-than-made-as-ftf) that "FlashTool" is not the same as Sony's "flashtool" Emma, so I installed it. It wanted me to put the phone in flashmode -- so I held volume down while plugging in the cable, which never before displayed anything different on the screen, nor a green LED which I've read elsewhere I should be seeing (e.g. http://www.theandroidsoul.com/sony-xperia-z-ultra-flash-mode-51769/). But despite the lack of visual clues, FlashTool told me it connected to flashmode and the flash succeeded. It didn't seem to help at all, though, as I still get the bootloop just as before and I still can't access a recovery mode.
That means that I can apparently get into both fastboot and flashmode, which I wanted to make special note of. Is it possible to access ADB while the phone is powered off?
just download flashtool, install driver in included in flashtool folder.
download also any FTF, generic zultra, dont care if 3g or lte.
flash it, should resolve the issue.
in flashtool, make sure you dont touch and leave the flash option as default. it will wipe your data, cache and everything.
to be safe, remove sim and sdcard.
More information...
curiouso9 said:
just download flashtool, install driver in included in flashtool folder.
download also any FTF, generic zultra, dont care if 3g or lte.
flash it, should resolve the issue.
in flashtool, make sure you dont touch and leave the flash option as default. it will wipe your data, cache and everything.
to be safe, remove sim and sdcard.
Click to expand...
Click to collapse
None of the supplied drivers match the "S1Boot Fastboot" device which comes up in my Device Manager. Also, none of the updated FlashTool Xperia Driver Pack match (http://forum.xda-developers.com/showthread.php?t=2635830), nor the drivers on SonyMobile.com, nor the drivers which come with Sony PC Companion. I didn't have this problem on my other Windows 10 machine, but just in case that is an issue, I'm downloading the Android SDK 1.2.1.1 Beta to see if I get any mileage out of that.
I attempted to flash the FTF supplied here (http://forum.xda-developers.com/showpost.php?p=60958777&postcount=3) but I got the following messages:
INFO - Opening device for R/W
INFO - Start Flashing
INFO - Checking header
ERROR - Processing of loader.sin finished with errors.
INFO - Ending flash session
ERROR -
ERROR - Error flashing. Aborted
INFO - Device connected in flash mode
Click to expand...
Click to collapse
Then I used XperiFirm to download my original .108 firmware and attempted to flash it but got the same errors as above.
Download flashtool
I assume you're on windows 8.1/8 you have to disable driver signature enforcement. Then install the drivers than flashtool will detect your phone.
Flash ftf
You will need to re-root, and you can unlock the bootloader.. After that flash away. Remember to install recovery and back up ta. I'm a noob at this and did it for the first time a few weeks ago, so I know you can do it.
Rockin' and rollin'
RealityFails said:
I assume you're on windows 8.1/8 you have to disable driver signature enforcement. Then install the drivers than flashtool will detect your phone.
Click to expand...
Click to collapse
I'm on Windows 10 -- I wasn't getting any errors, so DSE didn't even occur to me. I disabled it and was able to re-flash stock. Still, I struggled with getting a recovery installed, but after several attempts, and started from scratch a few times, one of them finally stuck. After that, I installed a custom ROM and things are running perfectly.
Thanks!
David
mypetocean said:
I'm on Windows 10 -- I wasn't getting any errors, so DSE didn't even occur to me. I disabled it and was able to re-flash stock. Still, I struggled with getting a recovery installed, but after several attempts, and started from scratch a few times, one of them finally stuck. After that, I installed a custom ROM and things are running perfectly.
Thanks!
David
Click to expand...
Click to collapse
Download rashr and it will have recoveries for you
Disappointment with the Service Center
By the way, when I decided I had been too long without an operating phone (before I got the DSE tip), I took the phone to a Sony Mobile Service Center and had them diagnose it. They concluded that there was a hardware failure rather than a software failure (which would require some 300 SGD to repair). I declined, returned to the office, saw the message about DSE, and was immediately successful in reflashing stock. I took it back to the Sony Mobile Service Center and had them confirm that there was in fact no hardware issue -- and that their diagnosis was incorrect. Thanks for the help folks!
Hello,
I just jumped on a good deal for Xperia Z5 (E5823) with software issue. Device boots up to the Xperia logo screen and hags there. I am preparing myself for flashing but hoping a simple hard reset might solve the problem. What should my steps be? I already downloaded Flashtool and did some reading on the forum to get myself familiar with the process. Looks like I will need to download FTF file (I am in US, prefer to have unbranded with minimal carrier bloat) and can use your advice on which version/file to start with. Ideally I would want to root as well, but for now more concerned about restoring back to stock. I did read that Lollipop has a better performance, but open to suggestions for whatever is easier/stable. Any guidance/advice is appreciated (with links to tools or downloads if avail). Is there a way to tell what version # along with region/customization I have installed now?! Should I try the Sony Companion software?
For the record, I have successfully flashed custom ROMS on various Samsung/LG devices, as well as Nexus 4/5. Therefore, feel pretty confident this should not be impossible or any harder. Thanks A LOT.
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
coolmen777 said:
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
Click to expand...
Click to collapse
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
I gladly would, except that I am not very comfortable using it due to lack of experience and available zips for my Z5 compact. Can you point me to that info and how to make zips to flash and what to start with? I am willing to try it.
Also, how can I check if my boot loader is unlocked? Can't seemed to find a command to use. Thanks again.
Any pointers for zips or how to flash a rom through fastboot? Thanks.
coolmen777 said:
Any pointers for zips or how to flash a rom through fastboot? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
civicsr2cool said:
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
Click to expand...
Click to collapse
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
coolmen777 said:
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
Click to expand...
Click to collapse
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
civicsr2cool said:
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
Click to expand...
Click to collapse
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
coolmen777 said:
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
Click to expand...
Click to collapse
Come to think of it without getting into the phone to enable unlocking the bootloader I don't think you would even be able to do that. Even if the drivers weren't installed the phone should go into flash mode. I had a hard time with my first attempt with flash tool at getting into flash mode. If you hold power and volume up you should be able to power down the phone completely then hold volume up while plugging in. The problem I had was my PC has a few different USB ports and I was using one that was meant for charging and it wouldn't go into flash mode, tried a different port and it went well after that.
Failed: remote command not allowed ???
This error is because you have not enabled OEM Unlocking from the Developer Option.
If you have enabled it but still receiving the error then you have not unlocked bootloader properly.
There is no need to unlock bootloader for flashing official sony firmwares. It is pretty simple. If you are facing any problems then please feel free to message me.
my email : [email protected]
#coolmen777
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
coolmen777 said:
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
Click to expand...
Click to collapse
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
civicsr2cool said:
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
Click to expand...
Click to collapse
Thanks, not very encouraging given the fact that Sony USA supposedly doesn't currently have a service center to repair international phones (closed their TX center). Are there other countries (Canada or UK) which have less stringent policies of needing invoice (for proof of purchase) and can simply go off of manufacture date from the IMEI or device info? Thanks again.
I beat my head against this for about eight hours yesterday and am at my wit's end. Thanks in advance for any help.
The short version: After rooting my Blue VIvo 5, installing a few apps and setting Nova Launcher as my launcher, I started getting some errors. Apps would fail mysteriously or not launch at all. Reinstalling the apps didn't help. I tried to take an OS update that the phone said was available, but when I tried to update it said the system was damaged and I couldn't install the update.
Well, I thought naively, I'll just remove all my user data and start over. That will restore the original ROM and I'll just start over, right?
BIG mistake.
Now when I try to start up my phone the sequence goes like this:
1. I get a popup that says "Unfortunately, Carefree Launcher has stopped."
2. After clearing that popup I can choose my language.
3. Next I go tot he screen where I choose my wireless connection. Choosing the connection works, but the next screen where I put in my password only allows me to speak - there's no keyboard option. The only time during the process I really laughed was when I saw what Google's voice recognition software tried to enter for the wifi password.
4. I managed to get the password entered by using the OTG dongle and a USB keyboard. After that, though, it goes to the "Checking for updates" screen, at which point it tells me "Unfortunately, Google Play Services has stopped." Then it loops back to the "choose your network" screen.
5. Lather, rinse, repeat.
I managed to get TWRP installed and running, but the stock ROM file I found on another thread (BLU_V0050UU_V09_REPAIR.zip) won't install. SP Flasher (which I also tried) throws a message about a mismatched baseband unit of some kind, and TWRP says there's a file called META-INF/com/google/android/update-binary missing from the archive.
So here I am, asking the community what I can do short of laying out $200 for another phone. I might be able to install the AOSP or CM12 ROMs that are in this forum, and I might do that if I have to replace the phone anyway, but if there's a way to restore the phone to its initial OOB state, I would love to know how to do it.
Again, thanks for any help you can give me.
Update, 16 hours later: I had a flash of inspiration this morning. Since it looked like at any rate I was going to have to get another phone I went ahead and ordered the replacement for same-day delivery. It arrived this afternoon, I unboxed it, set it up and backed it up with "adb backup". Then, I tried to restore the backup onto the bricked phone.
You guessed it. I never saw a notification that the backup was loading. It was the same wifi network, check for updates, broken google play loop again.
So unless someone has a brilliant idea as to how to restore the original firmware, I am going to keep the old bricked phone around and try installing aosp or cm12 on it, whichever looks like it's further along. Maybe both. Why not?
Anyway cheers.
Do you not know how to use SP Flash Tool?
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
victorvscn said:
Do you not know how to use SP Flash Tool?
Click to expand...
Click to collapse
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
victorvscn said:
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
Click to expand...
Click to collapse
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
NerdFire said:
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
Click to expand...
Click to collapse
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it.
NerdFire said:
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
Click to expand...
Click to collapse
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
victorvscn said:
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it..
Click to expand...
Click to collapse
No worries, I didn't take offense.
victorvscn said:
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
Click to expand...
Click to collapse
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
Good to hear!
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
where can I find the stock Rom ? Can you Share link please?
Well, I tried all the "one-click" apps (I don't care if they sell my info) and none work so far...
So it's time to consult XDA. Did it years ago, doin' it now. I'm new here, but you will be happy to know I read all the rules.
Time to fix this chinese piece of crap! This is the only device I own, and I can post all the processor and system info if needed. IDK if the bootload is unlocked or not, but a guy in another post for another RCA tablet mentioned he owned this same one and they said he might not need to unlock it. So IDK. NOTE I HAVE RCT6513W87 WITH NO "M" ON THE END. DIFFERENT MODEL.
So first, what am I gonna need? USB M-2-M?
I don't have any experience using ADB, however.
Don't really know what I'm doing so far.
BUMP
BUMP
BUMP BUMP
BUUUUUUMP
@Lootron
Did you try Dr Fone?
I suggest you consult this thread for more information on rooting with or without one click tools:
https://forum.xda-developers.com/canvas-juice/how-to/guide-unlocking-bootloader-rooting-t3705781
HIT THANKS IF FOUND USEFUL
I just spent the last few hours attempting to connect it to my Windows 10 PC. Nothing. 100% Impossible. Modified registry, edited drivers, tried modified google drivers but it kept saying "Windows has determined that you already have the best drivers for this device" trieda few workarounds for that. Damn, really want this rooted but it seems impossible.:crying:
Lootron said:
I just spent the last few hours attempting to connect it to my Windows 10 PC. Nothing. 100% Impossible. Modified registry, edited drivers, bla, bla, bla. END QOUTE]
Yeah, been there. However there should be a way. There's a five second window of opportunity when you have the USB connected, have the PC in the device manager. I'm willing to bet most of the process is the same when it comes to accessing the device according to Smartman Vartans tutorial for the RCA Viking Pro. I have that, the version before it and I have the Galileo, Build Number (RCT6513W87-ANDROID6.0-V21-V1.23.30-W02). It's about time I do something with it. His method is incredibly complex from the looks of it. But I'm willing to get root at least. Sounds like it's time for experimenting. Okay, I'm in. I'll see if I can pull some resources. Enable Developer settings (tap build 7 times). In The Developer settings turn it on. Turn on OEM Unlocking (to unlock the Bootloader). Turn on USB Debugging. Go down to Select USB configuration and make sure it's at MTP.
---------- Post added at 12:23 AM ---------- Previous post was at 12:07 AM ----------
[/COLOR]The Viking Pro used a SP splash tool to see the device , I've heard it works on this. Also listed was a driver. I'll go look for the frimware hopefully we both have the same. Then there's one thing that's been making me wonder. The Viking Pro uses the exact same motherboard and components as the Acer Icona, which has current 8.0 firmware. I don't see why for the life of me why I can't float that firmware in the RCA. It's an idea. But here's the Viking Pro link,
https://forum.xda-developers.com/android/general/firmware-rca-viking-pro-rct6303w87dk-t3325158
Click to expand...
Click to collapse
I feel forced to leave a note here. Stuck on some double reply mode. Where's the delete button?
Wow!
Hey thanks, I saw you on another forum (unless Casper Young is a common name?) and you said something about usb serials being locked, but I will defintely look into this! THX!
EDIT: BTW, my build number is V08- 1.15.20
I'll bet that's me, and my actual name. Howdy Thar. Yes USB Serials appear locked by manufactuer. When I dig into the data section of my rooted Viking Pro I happened to notice they were somehow locked and I was unable to follow the pathway. I can still try. But what I think you're trying to do is gain access via USB, correct? I talked to Smartman Vartan long ago and we have one interesting delima. Okay so we can gain access, but then what? It's not like we can just throw anything in it. I have 3 different devices The Maven Pro, the Viking Pro (both are rooted) and I got this Galileo Pro. Long story short, I was looking for compatible firmware. Went old school, look at the specs. Not the ordinary ones you find anywhere, the real specs. Go here, https://www.productchart.com/tablets/11121 sign up, yeah, WOW! Okay so I compare a few things, (I'm off exploring the Viking Pro), didn't have the galileo yet. Now, come to find out, the Viking has the same exact motherboard and components as the Acer Icona 10.1 (I forget which specific one). Hmmmm, now that's intresting. Can I, just toss it in there? I don't see why not. Others here suggest otherwise. I don't flash anything without back-up That's item #1 we need if you're gonna follow along. #2? The SP Flash Tool. I have those. Now I gotta open this puppy up and check out the motherboard. Gimmie a couple days I'll get back.
I wish we could use Odin3 but here's what I got For starters. I'll write out the tutorial if I get anywhere. How to run the SP Flash Tool:
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Current SP Flashtool: https://drive.google.com/open?id=1JzB5tzTvQYOGpVfhZNKY22_N-nD-jtDA
Firmware: https://drive.google.com/open?id=1zB1waSYM0iwdobu0jdxP1WJD6r1F8-XI
MTK Drivers: https://drive.google.com/open?id=1wRdulyOKLgeT_VWbhM9tm1-hqtgSL_BD
How to install the drivers:https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Rooting
If your intention is only to root the device you must first enable Developer Settings and then enable OEM unlock which gives you access to the Bootloader. Now you can flash in a custom recovery and then you will be able to root the device. You cannot do so by any other means. It will reject any attempt to root unless the Bootloader is unlocked!
Casper Young said:
If your intention is only to root the device you must first enable Developer Settings and then enable OEM unlock which gives you access to the Bootloader. Now you can flash in a custom recovery and then you will be able to root the device. You cannot do so by any other means. It will reject any attempt to root unless the Bootloader is unlocked!
Click to expand...
Click to collapse
Ok, I have everything, I THINK I installed the drivers, but I am waiting for it to charge to be sure. Can you be a little more clear on your instructions here? Do I flash the firmware? What order do I do everything? Custom Recovery first? Firmware first? How do I unlock the bootloader when it STILL doesn't regonize the device in ADB?
BTW, I installed the drivers by the SmartmanVartan method.
Lootron said:
Ok, I have everything, I THINK I installed the drivers, but I am waiting for it to charge to be sure. Can you be a little more clear on your instructions here? Do I flash the firmware? What order do I do everything? Custom Recovery first? Firmware first? How do I unlock the bootloader when it STILL doesn't regonize the device in ADB?
BTW, I installed the drivers by the SmartmanVartan method.
Click to expand...
Click to collapse
How do I flash the firmware? SmartmanVartan's method?
MTK drivers
Lootron said:
How do I flash the firmware? SmartmanVartan's method?
Click to expand...
Click to collapse
You have Windows 10 right?
Read this:
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
Casper Young said:
You have Windows 10 right?
Read this:
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
Click to expand...
Click to collapse
Yesterday, I tried flashing the firmware you linked to, and well, RIP. Bricked. Yours had build number .22, while I needed .15. So now I don't know if I can fix it. BTW Drivers worked and everything else. Did "fastboot oem unlock" and got to the "Do you want to unlock bootloader?" page, BUT the volume keys weren't programmed into it so you can't confirm nor deny. The bootloader needs to patched.
But before I get there, I need you to find a firmware that has .15 in the middle like this: x.15.x
Please, you are my only hope.
PS: I contacted Bogram, who patched the bootloader on the viking pro. If I can get the right firmware, then I can send it to him so he can patch it and I'm there. IF HE DOES IT.
TIA!
Brick
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)
EDIT: When flashing, it never said completed. I waited for a really long time and then clicked stop. I really don't know too much of what I'm doing
Woouch!
Lootron said:
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)[END QOUTE]
Wow try slowing down a bit. Sorry to hear your having difficulties with your tablet. I didn't expect you to flash it yet. No-one has provided anything to flash into it yet, I thought we were going to go looking. I'm hoping there can be a way to get past a brick. I've been reluctant to flash any of my devices for exactly the reason that you're dealing with. I didn't think to post what my firmware build number was, I'll edit that in.
I'll look for your firmware or ask RCA for it. This might take a bit. What color light is showing. And somehow try getting it to boot to recovery. Where you can reset it. Thats where the back-up is supposed to go also. There can be a variety of combinations to get there. Isn't there a reset hole to the left and a little below the micro sd slot. You may have to have it docked to get to recovery (the Viking Pro is like that). I'll do some research and see what I can find.
Click to expand...
Click to collapse
Casper Young said:
Lootron said:
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)[END QOUTE]
Wow try slowing down a bit. Sorry to hear your having difficulties with your tablet. I didn't expect you to flash it yet. No-one has provided anything to flash into it yet, I thought we were going to go looking. I'm hoping there can be a way to get past a brick. I've been reluctant to flash any of my devices for exactly the reason that you're dealing with. I didn't think to post what my firmware build number was, I'll edit that in.
I'll look for your firmware or ask RCA for it. This might take a bit. What color light is showing. And somehow try getting it to boot to recovery. Where you can reset it. Thats where the back-up is supposed to go also. There can be a variety of combinations to get there. Isn't there a reset hole to the left and a little below the micro sd slot. You may have to have it docked to get to recovery (the Viking Pro is like that). I'll do some research and see what I can find.
Click to expand...
Click to collapse
Whoops. Yeah I'm sorry, I've always been a bit hasty. I have looked for my firmware, but would RCA give it to you? I forgot to say my processor is MT6513. Not MT6127.
Well, thanks for spending so much of your time for me though. You have been very helpful. For me, bricking it was a learning experience. I learned a LOT about how android works messing with this tablet, and come on, it was a crap-let I only decided to
"hack" it once we ordered a new one (The keyboard doesn't work anymore)
The day I did it, I got frustrated I couldn't unlock the bootloader, so I wanted to do something else, without thinking about it. LOL. Well, more learning for me!
The only light it ever does it bright blue, and it no longer does it without being plugged into the outlet. Oddly enough, I didn't think to use the reset button, and in device manager it still shows up as preloader device, even though I suspected to be the preloader to be corrupted. There really shouldn't be a reason it won't start now. Also for some reason, ADB never has regonized this device, unless in fastboot mode.
Click to expand...
Click to collapse
Lootron said:
Casper Young said:
Whoops. Yeah I'm sorry, I've always been a bit hasty. I have looked for my firmware, but would RCA give it to you? I forgot to say my processor is MT6513. Not MT6127.
Well, thanks for spending so much of your time for me though. You have been very helpful. For me, bricking it was a learning experience. I learned a LOT about how android works messing with this tablet, and come on, it was a crap-let I only decided to
"hack" it once we ordered a new one (The keyboard doesn't work anymore)
The day I did it, I got frustrated I couldn't unlock the bootloader, so I wanted to do something else, without thinking about it. LOL. Well, more learning for me. [End Qoute]
Welcome to the place where you gotta play it safe. Yes RCA does provide the firmware, here;s your like for that.
https://stockromfiles.com/download-rca-stock-rom/
Now what I don't understand is why RCA implies there's no different versions of the software and you have a possible bricked device. I have a few articles that say even if your bricked you can flash in the software. Here's the tutorial for using the SP flash tool and another software location. The Tutorial makes me wonder though because if you look at steps 1, 2 and 3 they're questionable, especially #3. I'll get back to you in a bit, gotta chore to do.
https://stockromfiles.com/rca-rct65...323c6df5dcc913b1e77a5c8f2bbfe10#comment-53815
Oh, and you have yet to learn about playing with Androids These RCAs don't count. They're completely different from flashing a Samsung Galaxy or any other Androids.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
What procedure are you using to unlock? The WTF process is the one that I believe has worked the best for most people... and that doesn't have anything special on the phone screen, so I'm thinking you're using some app or script?
dsk1000 said:
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
Click to expand...
Click to collapse
Yea, I'm following that one. I read somewhere about AMD PCs causing problems. My phone shows when I use adb devices. So should I be a little more patient or what?
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
schwinn8 said:
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
Click to expand...
Click to collapse
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
dsk1000 said:
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
Click to expand...
Click to collapse
Some people had to use 2 or 3 computers. An older one with Intel CPU works best (especially if it has USB 2.0), but yes an AMD can work. As noted by @schwinn8 Ryzens are no go. One guy was upset because he had superfast gaming computer and we kept telling him to try another computer. He borrowed his brother's mediocre laptop and BOOM, worked. Another guy dug some old laptop out of his closet and it worked.
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
Also, try the steps mentioned in Wtf troubleshooting section.
Other than that you may have to mess around in the device manager section to see if the phone is detected properly or not.
(if there's a problem with the driver the device will show up as unknown android device or something)
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
You said "patient"... just to reiterate, this process doesn't take longer on a computer that says "waiting for device". It's a fast process, so if it's not happening within a few seconds, it won't work on that setup, period. Don't waste your time waiting - get another machine/cable/etc (check the troubleshooting steps to find other possible issues... the computer is usually the biggest problem to overcome, but the most successful).
Good news, i unlocked my phone and installed twrp, then i had to stop the process (wtf)
i still need to make a backup in TWRP and flash two more files from wtf notes. I cannot seem to be able to reboot into TWRP from ADB. thanks in advance
The oem is greyed out in developer mode and says its unlocked. Idk?
Glad to hear you got it unlocked.
In the WTF post it says that the developer mode may remain grayed out after being flipped... this is normal. It comes back after some time. Of course, you don't want to toggle it again anyway, since you're unlocked...
When i go to use an app to boot into twrp..it tells me its not rooted.
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Used getvar..unlocked.
Well its done..used an old hp A6 with linuxmint. I found linux to be straightforward and easy when trying to root my phone. No jumping thru hoops and juggling stuff.
Any recommendations for remodeling the phone? Boot to twrp..roms..ect?
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Bootloader unlocked is not rooted. It's just the prerequisite to being rooted. Then you install TWRP custom recovery and then use that to flash Magisk. It's all in the WTF Instructions. Also be sure to use the version of Magisk in the WTF Instructions, at least initially.
Thanks..ive got magisk from the instructions. It wants to update..should?
Once you are booted into Android, you can update Magisk to some degree. I forget the last version I had but I recall I could go to 20.x or something without issue. But there is always a risk of having issues if you update to the latest version... so be prepared to go back to the one on the WTF thread if the phone has issues. In other words, don't do this last minute or without a PC to work from... because it could fail.
The only time you have to use the old Magisk is during that first boot with it... once you're booted through, you have been able to update to newer versions. But unless you need some specific feature of the newest version, I might suggest leaving it alone...
I read somewhere..when i upgrade on US 998 20b, i need to move up to 20c?
Also, do i use the "twrp version. 20c"?