Related
I'm so mad right now. I had Gingerbread VeggieTab RC1 installed and it was working fine. I selected the reboot option since it was acting kind of wonky what with the market crashing constantly. Upon Startup, I got those 3 frickin' birds looking at me. I've been in this situation before, where I can't access the birds. So I instantly turn to this tutorial here: http://viewsonic-gtablet-for-dummies><.webs><.com/nvflash.htm (remove '><'s)
I've already installed APX drivers so I thought, no big deal, right? Wrong. You see, when I plugin the gTablet, in "devices and printers", it's under 'unspecified' at the bottom, looking like an idiot labeled "APX." Clearly I'm infuriated here. When I try and access nothing happens. You cannot see the gTablet as a storage device.
Then, I thought, "Well, what if I installed the APX Drivers again?" So I opened up device manager, uninstalled 'NVIDIA USB Boot-recovery driver for mobile devices', and then restarted. Good, so now APX is showing up as unsuccessful and looks like it should in the guide. Was I in the clear? Noooo. I installed the USB driver software, ez pz etcetera. It basically got me in a full loop. "NVIDIA USB Boot-recovery driver for mobile devices" shows up again, and it's still displayed as APX.
I'm sorry if I'm acting REALLY distressed but it's very urgent that I fix this in the next 3 hours. I am also aware that it could probably work if I used another computer but this is the only one I got. SO PLEASE, PLEASE, XDA, HELP ME!
I take no responsibility for people deviating from my the procedures I listed. I'll explore some options and will get back to you later.
Have you powered down completely? Sometimes it in apx mode and the tab looks like its off. Hold power for 20 seconds and then plug into computer and then hold power volume down(-). This will insure your PC is reading apx as it becomes available. Good luck
goodintentions said:
I take no responsibility for people deviating from my the procedures I listed. I'll explore some options and will get back to you later.
Click to expand...
Click to collapse
I never said your procedure didn't work, it did. What I am saying is that in your procedure the driver only works the first time you use it and not any time after that. The same driver didn't allow me to use it a second time and the resulting times after that.
Uh...common sense dictates that you only need to install the driver once.
Actually, let me edit my website.
Here is a quick fix for you.
Download virtualbox and run a linux virtual machine on your system. Nvflash actually works better in linux.
Added by edit.
Oh, I see what's wrong. That driver is for apx mode, not the storage device. Goodness. The page even said for nvflash.
If you want your pc to recognize your gtab's internal storage device, you need to have the right kernel. Again, this is all explained on my website.
goodintentions said:
Uh...common sense dictates that you only need to install the driver once.
Actually, let me edit my website.
Here is a quick fix for you.
Download virtualbox and run a linux virtual machine on your system. Nvflash actually works better in linux.
Added by edit.
Oh, I see what's wrong. That driver is for apx mode, not the storage device. Goodness. The page even said for nvflash.
If you want your pc to recognize your gtab's internal storage device, you need to have the right kernel. Again, this is all explained on my website.
Click to expand...
Click to collapse
Oh my god, I was like "what the hell does he mean "you only need to install it once...it's already installed and--" and then I realized it...****. Wow, I feel stupid.
Can I say a few things?
1. Instead of flashing "You only need to update driver once!" can you say "If this is the 2nd time you are doing this, skip to step 3 and then skip to Part II".
2. I realize this is the 2nd time you've corrected me with this, but still. It makes me really frustrated when you talk so condescendingly. I would be happy if you talked to me person to person, thank you. If there weren't dummies like me, your site wouldn't get any traffic
Now then. I ran everything the same. When I boot up, though, the screen gets stuck at the "N" part of tapntap where its loading. Then it just runs for a while, repeats the TAPNTAP screen, and does this several times before it just turns off. Does this mean I really have to repartition
(1) I'll change my website to your words. Thanks for the advice.
(2) This is the way I talk in real life all the time. I've been described as the king of sarcasm. My "girl friend" is a therapist. She's working with me on this issue.
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Added by edit.
You should have seen the original version of my site. It sounded exactly like me in real life. After some emails suggesting I change a few things before I face a class action lawsuit for upsetting a whole class of people (mainly dummies) I started doing some major overhauls based on their suggestions.
3 birds only; NO cwm, NO nvflash!
This is the closest forum I have found to my "issue"
I recently used nvflash to "update" to 1.2 branch with cwm. Worked fine and I installed cyanogenmod 7.0.3 (yes, the one that is meant for 1.2 branch). THAT started up seemingly fine.
Then I did a complete shut down and now I only get to the 3 bird screen. Won't acknowledge anything when I hold the Power and volume + button; when I try to connect to the PC it recognizes the device, but as soon as I try to do the nvflash to either 1.1 or 1.2 builds (I have successfully done both builds with this device; soft bricked before I understood what version I had, I'm a noob) it opens momentarily on the computer screen and shuts down. I have tried this on two different computers. I haven't seen anything that quite addresses this issue; it seems like most people can get into cwm. So... Help?
Couple sidenotes: the 1.1 and 1.2 nvflash folders I have had on my computer DO have cwm included. Also, I am currently following the recommendation to leave the tablet on until the battery is completely dead (and until it won't even begin to start up anymore) if all else fails, then start it up again. It didn't specifically say what that would accomplish... I'm giving it a shot though. Thanks for your help in advance!
drigg07 said:
This is the closest forum I have found to my "issue"
I recently used nvflash to "update" to 1.2 branch with cwm. Worked fine and I installed cyanogenmod 7.0.3 (yes, the one that is meant for 1.2 branch). THAT started up seemingly fine.
Then I did a complete shut down and now I only get to the 3 bird screen. Won't acknowledge anything when I hold the Power and volume + button; when I try to connect to the PC it recognizes the device, but as soon as I try to do the nvflash to either 1.1 or 1.2 builds (I have successfully done both builds with this device; soft bricked before I understood what version I had, I'm a noob) it opens momentarily on the computer screen and shuts down. I have tried this on two different computers. I haven't seen anything that quite addresses this issue; it seems like most people can get into cwm. So... Help?
Couple sidenotes: the 1.1 and 1.2 nvflash folders I have had on my computer DO have cwm included. Also, I am currently following the recommendation to leave the tablet on until the battery is completely dead (and until it won't even begin to start up anymore) if all else fails, then start it up again. It didn't specifically say what that would accomplish... I'm giving it a shot though. Thanks for your help in advance!
Click to expand...
Click to collapse
I have flashed my Gtab more times then I can think of, and also installed many custom mods. The only best solution that I can give you is if you can get into CWM you need to partition the drive (2048-0). Then after that is complete Fix Permissions and mount USB. Connect USB to computer and transfer the mod you are trying to install. Remember that when using a 1.2 mod you have to be using CWM v.3.0.2.8. That's the only one that I would trust in. You can download it off the web.
I hate humble pie... thank you for your hard work, your site helped an old man stop his hair from getting grayer...
Thanks for the "for Dummies" site!
goodintentions said:
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Click to expand...
Click to collapse
I bricked my gtab good, but [code red] pulled me thru. GRACIAS!
"OMG THIS IS SO GREAT!"
"WOW! YOU ROCK AND I WANT TO HAVE YOUR BABIES!"
"THIS IS THE BEST THING EVER!"
"THANKS FOR THIS!"
You saved my a$$.
Thank you SO much
goodintentions said:
(1) I'll change my website to your words. Thanks for the advice.
(2) This is the way I talk in real life all the time. I've been described as the king of sarcasm. My "girl friend" is a therapist. She's working with me on this issue.
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Added by edit.
You should have seen the original version of my site. It sounded exactly like me in real life. After some emails suggesting I change a few things before I face a class action lawsuit for upsetting a whole class of people (mainly dummies) I started doing some major overhauls based on their suggestions.
Click to expand...
Click to collapse
THANK YOU!
Thank you thank you thank you thank you.
I can't say thank you enough for your awesome work.
I've created many step-by-step tutorials for dummies on other subjects, so I know it's very time consuming, etc.
Thank you SO much.
my boss bought us new g tablets to use for work, and i brick it the same day i got it!
your code red procedure just saved my butt.
(now, going to try flashing cyanogenMod again! lol)
*edit*
*edit2*
i guess i wasnt holding down the volume button long enough.
once i held it down longer, recovery mode started ok.
Lately my HTC One shut off while typing on it and it was dead.
Holding power for 10 seconds (and any of the combination with the volume buttons) did not help.
And when you connect it to the power does not even had the red led indicating that is charging.
If you connect it to a PC you get prompted to install the QHSUSB_DLOAD drivers.
So the phone is dead but not really completely dead.
Clearly that QHSUSB_DLOAD is a Qualcom hook that could be use to debug and probably re-flash the phone. The question is what is this tool and how do you use it?
I think there is some sort of standard way to recover across phone (maybe not all with a Qualcomm but I am sure that the protocol is the same among a few processors).
There are a few examples out there:
[UNBRICK] HTC Unbricking Project - http://forum.xda-developers.com/showthread.php?t=1627886
DLOADTool - https://github.com/posixninja/DLOADTool
http://xiaomi.eu/community/threads/ultimate-cure-to-the-qhsusb_dload-of-mi2-s.20567/
And a lot of info about HTC internal here: http://tjworld.net/wiki/Android/HTC/Vision
So I wonder if anybody here has some idea about the tools and how to use to resurrect HTC phones and in particular the HTC One (M7).
Camicia said:
If you connect it to a PC you get prompted to install the QHSUSB_DLOAD drivers.
So I wonder if anybody here has some idea about the tools and how to use to resurrect HTC phones and in particular the HTC One (M7).
Click to expand...
Click to collapse
First: Wrong thread. Mod will likely move it to Q&A. (Hopefully not before I'm done trying to post this to help you out)
This normally occurs if you have a modified hboot meant for downgrading your device via RUU or some-such.
Best solution is to plug it in to a Windows 7 (32-bit) machine, and download an RUU.
If you hold the power-button for 15 seconds or so, you should feel it "bump". Basically, it was in a broken fastboot mode and you just put it into RUU mode, but with no on-screen indication of it.
Running the RUU at this point should work but remember: Whenever the RUU utility states "Waiting for Bootloader", you will need to hold the power-button in until you feel the bump again or it moves from "Waiting for bootloader" (should be around 15 seconds, every time).
I've made multiple full conversions on my device and run into this problem periodically before I started flashing rumrunner's hboot prior to conversion.
Hope this helps.
For future reference - some helpful links:
(added to sig)
I cannot feel and "bump" on the phone even if holding the power button actually cycle the phone QHSUSB DLOAD.
No luck. It does not work.
BTW, some of the link in your signature linked to files that Chorme marks as Malware.
Camicia said:
I cannot feel and "bump" on the phone even if holding the power button actually cycle the phone QHSUSB DLOAD.
No luck. It does not work.
BTW, some of the link in your signature linked to files that Chorme marks as Malware.
Click to expand...
Click to collapse
Most of those links are XDA. The others are HTC, RumRunner and such.
By "bump" I meant a vibration. If you are not getting that and the RUU is not detecting your device, I really don't know what else to tell you. This is what has worked for me in the past with that issue (running the RUU with the device plugged in and on and when it says "waiting for bootloader" holding the power button until the RUU continues.)
Sorry I couldn't be of more help.
PhoenixPath said:
Most of those links are XDA. The others are HTC, RumRunner and such.
By "bump" I meant a vibration. If you are not getting that and the RUU is not detecting your device, I really don't know what else to tell you. This is what has worked for me in the past with that issue (running the RUU with the device plugged in and on and when it says "waiting for bootloader" holding the power button until the RUU continues.)
Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Yes, I got what you meant. It seemed worth to try anyway.
The link with the malware was one on rootzwiki. I woudl not be surprise if somebody concatenate a trojan with a RUU.
Camicia said:
Yes, I got what you meant. It seemed worth to try anyway.
The link with the malware was one on rootzwiki. I woudl not be surprise if somebody concatenate a trojan with a RUU.
Click to expand...
Click to collapse
Well, it's been used by countless people with no reports of any trojan or otherwise. I've used it several times myself (I use it every time I convert to get back to T-Mobile stock and make sure OTA's work before moving on to the next conversion). The only reason it isn't a thread here for it is due to politics I try not to get involved in. Just trying to help folks out.
As always though, I do strongly suggest that everyone use their own judgement and that they do not do *anything* with their devices that makes them uncomfortable or that they feel may have unintended consequences.
That said; I use chrome exclusively and haven't seen any warnings from it. Even Google Search isn't reporting issues with the link. If I were you I would check and make sure that you don't have any "helper objects" like toolbars or search-assist add-ons installed as those sometimes hijack page-requests.
Regardless of all of that, I am sorry I could not be of more help. The only time I've seen the DLOAD issue - the above steps fixed it. Seems my experience is not enough to solve this one. Hopefully someone else can pitch in. Best of luck!
Thread closed as duplicate/triplicate/quadruplicate of QHSUSB_DLOAD - What is the protocol?. Please continue the discussion there.
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
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"?