Related
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
I flashed my phone with kate_global_images_7.5.19_20170519.0000.00_6.0_global in order to unlock the bootloader via mi unlock. The phone has successfully connected to mi cloud and can be located on the i.mi.com website. If I go into developer options and tap on the button to bind the phone to my account for unlocking it just keeps telling me to try again in another couple of minutes. This seems to be a really common problem and I haven't been able to find a solution. Any ideas? Thanks.
Same here. Been waiting for 5 days now after getting permission. Still fails to bind. This whole official unlock way is a total POS. It even says after you are granted permission you can unlock right away but that's not true at all. I also have SE and dev rom btw.
maybe try to flash miui 8 via fastboot..
i used fastboot rom miui 8 , miflash (not xiaomiflash) ver 2016, and unlock ver 1.1..
Augesvarer said:
maybe try to flash miui 8 via fastboot..
i used fastboot rom miui 8 , miflash (not xiaomiflash) ver 2016, and unlock ver 1.1..
Click to expand...
Click to collapse
MIUI 8 what? The dev rom 7.x is MIUI 8. Do you mean dev or stable? I was on MIUI 8 stable before but it didn't help.
my issues, evrytime i flashed miui rom, my imei isn't showing up (i need to official unlock to flash lastest los)
i tried some rom dev 7.x.x.x , but i cant login mi account via wifi.
then, i flashed this rom with miflash 2016 (mine is kenzo)
http://en.miui.com/thread-439892-1-1.html
and it works, i can unlock my phone without imei..
Augesvarer said:
my issues, evrytime i flashed miui rom, my imei isn't showing up (i need to official unlock to flash lastest los)
i tried some rom dev 7.x.x.x , but i cant login mi account via wifi.
then, i flashed this rom with miflash 2016 (mine is kenzo)
http://en.miui.com/thread-439892-1-1.html
and it works, i can unlock my phone without imei..
Click to expand...
Click to collapse
I think the "can not bind" problem is specific to Kate. The IMEI problem with your Kenzo phone is probably a separate issue.
dwl99 said:
I flashed my phone with kate_global_images_7.5.19_20170519.0000.00_6.0_global in order to unlock the bootloader via mi unlock. The phone has successfully connected to mi cloud and can be located on the i.mi.com website. If I go into developer options and tap on the button to bind the phone to my account for unlocking it just keeps telling me to try again in another couple of minutes. This seems to be a really common problem and I haven't been able to find a solution. Any ideas? Thanks.
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
it work perfectly and i have successfully unlock my kate and flash latest LOS.
abe_long said:
Try this
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
it work perfectly and i have successfully unlock my kate and flash latest LOS.
Click to expand...
Click to collapse
Thanks for the reply but I need to have the latest dev ROM to allow LineageOS to flash - it checks for the most recent firmware.
dwl99 said:
Thanks for the reply but I need to have the latest dev ROM to allow LineageOS to flash - it checks for the most recent firmware.
Click to expand...
Click to collapse
Yes i know.first you use the older version miui to unlock the bootloader.after that just reflash to latest dev rom.make sure you checked CLEAN ALL.it will not lock your bootloader.
abe_long said:
Yes i know.first you use the older version miui to unlock the bootloader.after that just reflash to latest dev rom.make sure you checked CLEAN ALL.it will not lock your bootloader.
Click to expand...
Click to collapse
Thanks, I tried this but got stuck in a bootloop.
dwl99 said:
Thanks, I tried this but got stuck in a bootloop.
Click to expand...
Click to collapse
At which step does the bootloop come..?i also having bootloop after flash the twrp but it can be solve by flash the lazy flash zip
abe_long said:
At which step does the bootloop come..?i also having bootloop after flash the twrp but it can be solve by flash the lazy flash zip
Click to expand...
Click to collapse
I flashed kate_global_images_6.7.14_20160629.0000.25_6.0_global_1b43c8f07f and then started to get bootloops. I didn't get as far as flashing TWRP.
dwl99 said:
I flashed kate_global_images_6.7.14_20160629.0000.25_6.0_global_1b43c8f07f and then started to get bootloops. I didn't get as far as flashing TWRP.
Click to expand...
Click to collapse
After flash,try to wipe data and cache in recovery.then reboot your device.if after 5 min still looping,try to force reboot.
abe_long said:
After flash,try to wipe data and cache in recovery.then reboot your device.if after 5 min still looping,try to force reboot.
Click to expand...
Click to collapse
I thought of that but I couldn't get the phone to boot into recovery - Power and Vol+ opened a screen with a picture of the phone with a cable being plugged into it rather than recovery
dwl99 said:
I think the "can not bind" problem is specific to Kate. The IMEI problem with your Kenzo phone is probably a separate issue.
Click to expand...
Click to collapse
Just try unlocking via mi unlock and tell us ignore the message
Androbots said:
Just try unlocking via mi unlock and tell us ignore the message
Click to expand...
Click to collapse
Doesn't work - complains that the deivice isn't bound to the account
There is no point trying anything. Nothing works. I have a 3 month long email chain with xiaomi support, which ended by them saying I should contact the direct seller. Basically they washed their hands. I ended up sending my device to a guy, who has a xiaomi service licence, and he managed to unlock it officially with his code.
If you cannot bind your account and device for two weeks with multiple tries, you should just give up on the "mainstream" unlock procedure. It will never work, and the only thing that comes out of it is slowly bulding rage.
It's not worth it.
smash1986hu said:
There is no point trying anything. Nothing works. I have a 3 month long email chain with xiaomi support, which ended by them saying I should contact the direct seller. Basically they washed their hands. I ended up sending my device to a guy, who has a xiaomi service licence, and he managed to unlock it officially with his code.
If you cannot bind your account and device for two weeks with multiple tries, you should just give up on the "mainstream" unlock procedure. It will never work, and the only thing that comes out of it is slowly bulding rage.
It's not worth it.
Click to expand...
Click to collapse
Sounds like good advice. My Note 4 has arrived now so I think I'll just flash the stock MIUI ROM & ebay it.
smash1986hu said:
which ended by them saying I should contact the direct seller
Click to expand...
Click to collapse
What if I bought it directly from their online store? Do I contact them back?
Hello everyone, let me just go ahead and say that I'm a total noob in the android customization thing but I somehow manage to install Lineage OS on my L03 and at the time I thought it was done and I didn't messed anything up but somehow that backfire on me.
So right now my HAM 2 is on a boot-loop, it kept staying the Lineage OS loading screen and once it was done and show the device setup screen for like 3 seconds it goes black and load again.
I've tried everything to fix it, from reinstalling an older version of Lineage, install CM13, wipe all data cache and dalvik ( and yes I have install gapps everytime I install any custom ROM, and finally after looks around the web I thought It might be the power button that making it acts weird but when after cleans it with rubbing alcohol (70%) It's still happening.
Now I have 2 options, first is to downgrade the firmware ( I'm not sure if it safe and how to do it) and seconds is to downgrade or delete TWRP ( newest version on HAM2).
Please, if anyone knows how to fix this. Help me. I got this device from amazon and it'll be a hassle trying to claim warranty on it since I have unlock it's boot-loader and install a custom ROM.
Thanks in advance.
Im not trying to be an asshole but does no one know how I can fix this?.
Bl4ckAir said:
Im not trying to be an asshole but does no one know how I can fix this?.
Click to expand...
Click to collapse
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
divhandyman said:
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
Click to expand...
Click to collapse
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Bl4ckAir said:
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Click to expand...
Click to collapse
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
divhandyman said:
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
Click to expand...
Click to collapse
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Bl4ckAir said:
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Click to expand...
Click to collapse
Yes use ADB.
https://www.youtube.com/watch?v=OwY-K6-pmJU&feature=youtu.be
Bl4ckAir said:
Please, if anyone knows how to fix this.
Click to expand...
Click to collapse
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
hola
have you managed to solve it?
I have the same problem!!!
please help
Douglas_27 said:
have you managed to solve it?
I have the same problem!!!
please help
Click to expand...
Click to collapse
Hi, Douglas I have managed to solved it. Please tell me the step you have taken and I'll maybe able to help you.
Does it work for L01 the latest TWRP
EndlessFall said:
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
Click to expand...
Click to collapse
I tried the latest TWRP from MDMower but got stuck in a boot loop after I flashed it and went to turn off the phone to go into recovery mode.
i mistakingly delete a file on my huawei mt2-l02 and since then when i power on it will stuck on startup anyone with solution
Hi, I managed my Pixel 6 to unlocked but I can't root it with Magisk, I've tried many times to patched the boot image but I'm not sure if I got the right one. My build number is SD1A.210817.036
Can anyone guide me through this?
Thank you.
Here is a guide:
[CLOSED] Firmware is out! Get your root on!
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image. Any update method can be...
forum.xda-developers.com
trai_th said:
Hi, I managed my Pixel 6 to unlocked but I can't root it with Magisk, I've tried many times to patched the boot image but I'm not sure if I got the right one. My build number is SD1A.210817.036
Can anyone guide me through this?
Thank you.
Click to expand...
Click to collapse
Did you already disable Verified Boot?
V0latyle said:
Did you already disable Verified Boot?
Click to expand...
Click to collapse
i followed this mostly 80% and i tried myself 20%. the way i did the patched file, i used another mobile to patched it and then copy to p6 folder then patched.
Root Google Pixel 6/Pro via Magisk Patched Boot [Android 13]
In this comprehensive tutorial, we will show you detailed steps to root your Pixel 6 device by flashing the Magisk patched boot.img.
www.droidwin.com
trai_th said:
i followed this mostly 80% and i tried myself 20%. the way i did the patched file, i used another mobile to patched it and then copy to p6 folder then patched.
Root Google Pixel 6/Pro via Magisk Patched Boot [Android 13]
In this comprehensive tutorial, we will show you detailed steps to root your Pixel 6 device by flashing the Magisk patched boot.img.
www.droidwin.com
Click to expand...
Click to collapse
I would recommend against that - always use the same device you're going to use the boot image on.
Please refer to my guide here.
V0latyle said:
I would recommend against that - always use the same device you're going to use the boot image on.
Please refer to my guide here.
Click to expand...
Click to collapse
I've tried to do that many times but it won't work for me...
trai_th said:
I've tried to do that many times but it won't work for me...
Click to expand...
Click to collapse
What exactly are you having problems with?
You said you followed 80% of the instructions; what did you NOT do?
V0latyle said:
What exactly are you having problems with?
You said you followed 80% of the instructions; what did you NOT do?
Click to expand...
Click to collapse
my laptop doesn't recognize my mobile phone I don't know why, Maybe the W11 so i trued on W10 then it's connected. after that i followed the step in that website.
trai_th said:
my laptop doesn't recognize my mobile phone I don't know why, Maybe the W11 so i trued on W10 then it's connected. after that i followed the step in that website.
Click to expand...
Click to collapse
You need the Google adb driver.
vandyman said:
You need the Google adb driver.
Click to expand...
Click to collapse
I'm on root now
trai_th said:
my laptop doesn't recognize my mobile phone I don't know why, Maybe the W11 so i trued on W10 then it's connected. after that i followed the step in that website.
Click to expand...
Click to collapse
Install this driver (as @vandyman said) for W11.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Lughnasadh said:
Install this driver (as @vandyman said) for W11.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Click to expand...
Click to collapse
thanks i just got it rooted
trai_th said:
I'm on root now
Click to expand...
Click to collapse
Glad it worked out.
I went through the same issue with Windows 11 and the Pixel 6. The Google driver was needed.
On another note; I have been using Windows 11 DEV the last few months and having fun with my Pixel 5 A12-beta without the Google driver.
The only answer I can come up with.
Is the difference is in the Pixel 6s chip set.
vandyman said:
Glad it worked out.
I went through the same issue with Windows 11 and the Pixel 6. The Google driver was needed.
On another note; I have been using Windows 11 DEV the last few months and having fun with my Pixel 5 A12-beta without the Google driver.
The only answer I can come up with.
Is the difference is in the Pixel 6s chip set.
Click to expand...
Click to collapse
no idea, man.
I am facing a weird issue with fastboot not detecting my device.
USB is fine (as in I have other USB-C based devices, and they are detected just fine and am able to flash images just fine with them), ADB is fine, including all commands like sideload, etc...
I just get hung on <waiting on device> when I boot to bootloader mode... I am sure it's possible that I am simply doing it wrong... I generally just run adb reboot bootloader on other devices, and boom I was in fastboot mode.
What I'm trying to do is go back to stock... I'm on The Developer Preview 2 for 13 at the moment and am finding some deal breaking issues with a couple apps that I need.
kevp75 said:
I am facing a weird issue with fastboot not detecting my device.
USB is fine (as in I have other USB-C based devices, and they are detected just fine and am able to flash images just fine with them), ADB is fine, including all commands like sideload, etc...
I just get hung on <waiting on device> when I boot to bootloader mode... I am sure it's possible that I am simply doing it wrong... I generally just run adb reboot bootloader on other devices, and boom I was in fastboot mode.
What I'm trying to do is go back to stock... I'm on The Developer Preview 2 for 13 at the moment and am finding some deal breaking issues with a couple apps that I need.
Click to expand...
Click to collapse
May be a driver problem. Do you have the latest of this installed?
why not show exactly what you are trying to do and what you get. copy paste what you see. then check version numbers of the tools you are using.
Lughnasadh said:
May be a driver problem. Do you have the latest of this installed?
Click to expand...
Click to collapse
had a previous version installed. will check when I fire th PC back up tomorrow
Lughnasadh said:
May be a driver problem. Do you have the latest of this installed?
Click to expand...
Click to collapse
It was exactly that. Going to have to bookmark that. I thought I had the latest installed (it was latest as of December lolol)
I do appreciate the help mate, now back to stock Rom for me... (got sick of A13 DP2's issues), plus now I can finally root this thing
kevp75 said:
It was exactly that. Going to have to bookmark that. I thought I had the latest installed (it was latest as of December lolol)
I do appreciate the help mate, now back to stock Rom for me... (got sick of A13 DP2's issues), plus now I can finally root this thing
Click to expand...
Click to collapse
Awesome! Glad you got it going
Lughnasadh said:
Awesome! Glad you got it going
Click to expand...
Click to collapse
You and me both lololol
I've been around these rooms a long long time, and this is the first device I've ever had issues like this with. Usually it's been a USB cable or port, but never a 3 month old driver lol
Now, that I'm back to stock, and rooted... maybe I can get some dev going