Related
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Hello,
I download from the ASUS website the firmware with version "V10.4.2.18 Only for WW SKU (Android 4.1)" and the pop-up for update de firmware appear normally to me.
Then, the TF201 restarted and since then does not passes through the ASUS Logo.
I Was on 4.0.0.3, firmware 9.4.2.28 and tried to upgrade to a superior version (my mistake as I can see now).
Even when restarting with Power + VOL DOWN the only thing that appears is :
----......................
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.2.28-20120525" A03
Checking for android ota recovery
Booting recovery kernel image
-----------
And stays here forever... No option with the 3 icons, so I can choose USB... And neither the VOL UP during this process does nothing...
Anyone can help?
Thanks in advance
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
sl0mar said:
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
Click to expand...
Click to collapse
I installed the drives and the PC recognizes the TF-201.
But it seems that fastboot can't recognize the tablet.
Well, I didn't get so far...
But I still want to try, but I'm a little lost...
Any help?
what you see when u run fastboot devices ?
inbg said:
what you see when u run fastboot devices ?
Click to expand...
Click to collapse
From my PC device manager I can see the asus transformer Prime APX Interface and is saying that "This device is working properly.".
However, every command that I sent from fastboot the result is always the same:
< waiting for device >
I'm completely out of ideas to get this back to work...
THATS BAD do u have working adb ?
No i don't...
HOW to Reserruct from APX mode^
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
logicmate said:
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
Click to expand...
Click to collapse
Logicmate, seems there is no help how to unbrick the tf201 in APX mode...
Did you get lucky meanwhile?
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
I have the same problem
Shaiden said:
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
Click to expand...
Click to collapse
I know it's been 4 years but did you find any solution to this? I'm asking because I have the same problem. I decided to downgrade to Remix OS 1.5 in order to root (I have tried 5 rooting apps with no success) but my device refuses to enter fastboot protocol. The whole idea was since I can't find a way to root the damn thing in its current state maybe I can manage it with its older OS version. All this just to turn it to android root apps "testing ground" device. Oof.
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Bump
RobinHood16 said:
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Click to expand...
Click to collapse
Bump!
Yes please!
I tried RCA to see if they would at least update the tablet and turn on the FM receiver. They claim it doesn't have it. I'm pretty sure it has both the FM and a GPS receiver built in. I think I also found a "clone", the DigiLand DL721-RB appears to be the same hardware.
What I'm trying to do is simply enable all the features the hardware has. The Atom x3 is supposed to have pretty much all the standard stuff, my RCA RCT6973w43 (on sale at Walmart right now for $37) does OTG nicely, but if I had the FM also it would be perfect for a tablet based car stereo. If anyone figures it out and can get the FM and or GPS going, I'd be tickled.
I just bought a couple of these for 25 bucks. I would very much like to get them rooted. Any news on if the method for the other Rca's works?
No good. I attempted to root the Voyager III with One Click Root, and it told me it was unrootable for the time being.
Any clues yet?? everyone owns this tablet figured there'd be a root already for this one.
i read where someone tried to root the 43 using 42, and it bricked the tablet, so i'm reluctant to try it. don't know if the 42 and the 43 had the same processor, or what makes them so different it would cause that to happen. maybe we can get a bump.
keep finding tons of people looking for root, but not dice so far. i've only got one cuz they were sold out. actually bought the display model. wish i had more than one so i could experiment. 8(
I'd been able to install twrm halfway then it fails signature verification.
Just got one of these! Bump
yes bump!!!! I can't believe this hasn't been rooted yet. is it because it's an intel x86 architecture?? I'm guessing it would require someone to compile the code for sudo/su/root to run on it??
anything yet?? 8(
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
just as a quick notei found this guys.
http://specdevice.com/showspec.php?id=7920-d3ef-0033-c5870033c587
it's an alco tablet with the same model # as the voyager 3 RCT6973W43.
weird thing is it appears to have a quadcore arm processor, and not an intel atom.
i heard there was a root for the alco from twitter profile @srsrOOT, but they haven't responded yet.
no clue if this will help at all. I would imagine if the alco has an arm proc, and the rca has an intel then we'd need a different su/sudo binary for the RCA because the RCA runs on a CISC processor, and the ARM is a RISC. hope there's some clues here. hit us back with any info you find. 8(
look here
bump
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
TimmyP said:
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
Click to expand...
Click to collapse
Did you guys unlock the boot loader yet?
Code:
adb reboot fastboot
fastboot flashing unlock
If so, you can try and boot the cwm recovery I use on mine(RTC6873W42) to get a root shell. (if the kernel drivers were the same it would actually be full recovery enviroment) And with that root shell you could pull your boot.img . The expected result of the fastboot boot command is an attempted boot to cwm recovery except the screen will be blank, and adb will give root shell access.
Code:
fastboot boot v31-test-rca-recovery-cwm-ramdisk-20170709-2052.img
https://www.androidfilehost.com/?fid=961840155545581102
And with the pulled boot.img you can make the recovery fully boot by swapping the kernel, then manually change some rc files in the ramdisk folder of the boot.img the allow it to be rooted.
When you get that far, and if you need help, just ask.
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
RobinHood16 said:
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
Click to expand...
Click to collapse
That connect disconnect is expected when Intel drivers for fastboot not installed. I will link you to my write up on how to install
https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt
Read the document and follow directions in the driver install section. If trouble let me know
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
RobinHood16 said:
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
Click to expand...
Click to collapse
Sorry this is giving you such trouble,
but if you cant get the drivers to work, then you hae no way to know if these files will not work on your device.
If you are refering to the "tools" then, yes they will not work, as I coded them to not work if build numbers are not matched. But I never suggested tring the "tools". just the unlock and "fastboot boot" steps
again , If you cant get windows drivers to install then , thats as far as you can go.
I had a pictoral 'guide' for doing it, but cant find it right now.
In that case, my only recourse is to give up. It seems to me that they have made this tablet absolutely unrootable.
i managed to unlock bootloader
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
seasonednovice said:
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
Click to expand...
Click to collapse
Did you attempt my directions at the end . To boot the modified cwm , to get adb root shell?