Related
* Your warranty is now void.
I am not responsible if this causes your device to be bricked, for the planets to align, monkeys take over the earth, nuclear war, missed sexual favors or whatever nonsense ensues due to your device not working. Please do some research if you have any concerns before flashing.
By using this recovery you agree to these terms!
Click to expand...
Click to collapse
Clockworkmod Advanced 5
http://d-h.st/BNT
Bugs
-cwm runs in background while charging(Fixed)
-tell me?
Install
(requires unlocked bootloader)
Code:
fastboot flash recovery recovery.img
To enter CWM(or stock recovery) turn off and then hold vol up+power
https://github.com/KainXS/android_device_huawei_y301a2/tree/cwm
Credits
ShabbyPenguin - Phandroid
KINGbabasula
CNexus
Would you be able to port CWM to a Huawei G526-L22?
Specs are similar to this Vitria(Y301-A2).
Tried this .img but can't mount /cache/recovery etc
extendcommand threw up failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache
(no such file or directory)Yet that path/directory is present in file explorer.Any assistance would be much appreciated.
The device has been discounted to AU$99 so a lot of geeks have grabbed them and are looking for mods
As is the norm for android heads ;|}Regards from Down Under
Gomax
gomax said:
Would you be able to port CWM to a Huawei G526-L22?
Specs are similar to this Vitria(Y301-A2).
Tried this .img but can't mount /cache/recovery etc
extendcommand threw up failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache
(no such file or directory)Yet that path/directory is present in file explorer.Any assistance would be much appreciated.
The device has been discounted to AU$99 so a lot of geeks have grabbed them and are looking for mods
As is the norm for android heads ;|}Regards from Down Under
Gomax
Click to expand...
Click to collapse
do you have the original recovery backed up
and can you run these commands while its booted in android with adb
cat /proc/partitions (info on partition sizes)
run ls too
and did you just take the image and flash it without modifying it.
Was sent the image by a developer, who has sent a revised version which works.
Thanks for your interest.
good to hear:good:
but did you really flash the recovery without modifying anything and it booted on the 526
KainXSS said:
good to hear:good:
but did you really flash the recovery without modifying anything and it booted on the 526
Click to expand...
Click to collapse
Both versions booted OK.
The first didn't mount external card.
gomax said:
Both versions booted OK.
The first didn't mount external card.
Click to expand...
Click to collapse
wow if it booted unmodified at all, these devices must be extremely similar minus the screen, hopefully kernel source pops up for one of them, guess the recovery fstabs were different though
edit
the link is gone?
I requested the source code for the vitria a month ago and huawei just released it
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=17935
I had time to play around with it and build it, did not boot though, wanted to clean it up some but yesterday I broke my hand so there might not be updates for a while.
how did you get the unlock password for this device? im on their website but it doesn't list this device....
mattlowry said:
how did you get the unlock password for this device? im on their website but it doesn't list this device....
Click to expand...
Click to collapse
sorry it took so long to answer but I got the unlock password from huawei by emailing them, I haven't worked on this device solidly in a while.
you might be able to also flash recovery with adb also, if you wanna try it let me know because I unlocked my bootloader before using adb but when I try it works.
remembered to upload cwm advanced 5
also have cwm 6.0.4.7 and advanced 6 but I need to fix a nasty bug with it.
forgot to add if someone were to upload the recovery.img's and a partition layout for the g526 or G740 I can more than likely try to get cwm and cwm advanced running on them.
had to change the vitria recovery to mount by name instead of block number, changed font also.
added source
KainXSS said:
sorry it took so long to answer but I got the unlock password from huawei by emailing them, I haven't worked on this device solidly in a while.
you might be able to also flash recovery with adb also, if you wanna try it let me know because I unlocked my bootloader before using adb but when I try it works.
Click to expand...
Click to collapse
Yes, it takes a few email exchanges with [email protected], but I got my unlock password in couple of days from them.
Great job, OP, works like a charm.
Finally got my unlock from Huawei after a week, and just in time! I lost my old HTC G2 (its somewhere in the kitchen, i swear!) and needed a replacement phone fast.
Enter the Vitria. installed CWM and did a full backup, then installed titanium backup and started ripping out bloatware and live wallpapers and other crap.
I have to say, i REALLY hope development of Cyanogen continues for this device, its hard enough leaving CM7 to go to jelly bean. If there's anything i can assist with with a backed up/bootloader unlocked device, let me know. Or buy you enough beer to last a weekend so you can get this compiled
Flashify
I did something different, I flashed with flashify but I realize now I shouldn't have, it reboots but has a signature error before rebooting, I sure hope there will be cynogen mod or something because this phone has a data connection problem, once data goes off it won't come back on until restart and sometimes all bars without data goes off too and then have reboot too, good phone but needs work, glad to see someone out there doing something, thanks.
OK, I think I know how to fix, but I don't have the correct IMG to fix since I have already corrupted it by flashing with flashify.
Does anybody have the recovery.img and the boot.img from a working stock for this phone?
by having a good recovery.img, I can flash with flashify and get it back to working correctly, this is what I did to fix a similar problem from flashing CWM to my LG G2 and worked.
Update, downloaded stock ROM and the recovery and boot img where there so I flashed recovery.img with flashify and everything good.
Just wondering, anybody has a recovery of their Vitria that already has CWM working properly on it, I wonder if that recovery.img contains proper CWM to be flashed to another Vitria?
this is not for the h882l, it might work on that one but I don't know.
if you try to flash without having the bootloader unlocked, it won't work, you will get a crc signature failure error every boot even if you use adb or a flashing app, after unlocking you can use adb, not sure about flashify(never tried it).
CRC Signiture Error
KainXSS said:
this is not for the h882l, it might work on that one but I don't know.
if you try to flash without having the bootloader unlocked, it won't work, you will get a crc signature failure error every boot even if you use adb or a flashing app, after unlocking you can use adb, not sure about flashify(never tried it).
Click to expand...
Click to collapse
Yes CRC Signiture Error, but the bootloader is unlocked, I use T-Mobile with phone, but only problems I see with this phone is connecting to Data all the time, I end up having to turn data off then back on then it is usually fine sometimes it has problems still, I did pay a service to get the bootloader unlocked with a code so it is unlocked.
Would like to see a nice ROM built for this phone, I haven't the slightest clue to do so, Cyanogen mod would be fine.
Did try to install CWM but could not do so, is this the touch or regular version of CWM you have listed?
Keep up the good work, thanks.
Arctic Prodigy said:
Yes CRC Signiture Error, but the bootloader is unlocked, I use T-Mobile with phone, but only problems I see with this phone is connecting to Data all the time, I end up having to turn data off then back on then it is usually fine sometimes it has problems still, I did pay a service to get the bootloader unlocked with a code so it is unlocked.
Would like to see a nice ROM built for this phone, I haven't the slightest clue to do so, Cyanogen mod would be fine.
Did try to install CWM but could not do so, is this the touch or regular version of CWM you have listed?
Keep up the good work, thanks.
Click to expand...
Click to collapse
I also use tmobile on mine and I have data problems too but haven't tried to fix it yet, don't have the time but your bootloader is unlocked right, your not confusing sim unlock with bootloader unlock right, also your using fastboot to install right.
I am not working on cyanogenmod for the vitria though, it needs a device tree and the kernel needs to be updated for it too, on mine I just run with a custom rom based on stock and a custom kernel for overclocking and stuff, thats enough for me.
Maybe sim unlocked, but thought was bootloader unlocked, I paid to get phone unlocked, they sent a code and I am able to use t-mobile sim card on MetroPCS phone, as for bootloader, it is rooted and says unlocked if that is what you mean, I have SuperSu installed, I used Framaroot as suggested.
Yes I can get into fastboot mode.
Hmm, to verify if bootloader is truly unlocked, how would I go about getting to that to verify for certainty?
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.
EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central
CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.
tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.
I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.
Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.
Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?
Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
Hey fellow users,
I own a Galaxy S6 on Bell in Canada that's been rooted and updated to Arrow Rom 10.0
Everything was working fine, and I decided that I wanted to try playing Super Mario Run and also try another game, but they won't show as my phone is rooted.
After reading on Google about hiding root, I decided to try Hide My Root, and proceeded to use it.
Didn't work, so I decided to reboot my phone, and now it won't boot. I have already tried wiping Data, Dalvik, and regular Cache, and my phone gets stuck at the Samsung logo
Any ideas guys?
Only thing I can think to do is try to reinstall Arrow Rom 10.0 and hope for the best
Any answers will be appreciated
Thank you!
Vorde1 said:
Hey fellow users,
I own a Galaxy S6 on Bell in Canada that's been rooted and updated to Arrow Rom 10.0
Everything was working fine, and I decided that I wanted to try playing Super Mario Run and also try another game, but they won't show as my phone is rooted.
After reading on Google about hiding root, I decided to try Hide My Root, and proceeded to use it.
Didn't work, so I decided to reboot my phone, and now it won't boot. I have already tried wiping Data, Dalvik, and regular Cache, and my phone gets stuck at the Samsung logo
Any ideas guys?
Only thing I can think to do is try to reinstall Arrow Rom 10.0 and hope for the best
Any answers will be appreciated
Thank you!
Click to expand...
Click to collapse
You need to flash latest version of SuperSu via TWRP and it should let it boot up again. You have to becareful with some of these root hiding apps as SuperSu is patched in boot and if anything goes wrong you get this issue. Hopefully refreshing SuperSu fixes otherwise you probably will need to reflash rom
sofir786 said:
You need to flash latest version of SuperSu via TWRP and it should let it boot up again. You have to becareful with some of these root hiding apps as SuperSu is patched in boot and if anything goes wrong you get this issue. Hopefully refreshing SuperSu fixes otherwise you probably will need to reflash rom
Click to expand...
Click to collapse
Thank you very much for the idea. I have another issue now though lol.
I am running TWRP and I cannot get it to mount anything via USB on the computer.
It will not allow me to do it. Any ideas? Do I have to adb sideload?
Vorde1 said:
Thank you very much for the idea. I have another issue now though lol.
I am running TWRP and I cannot get it to mount anything via USB on the computer.
It will not allow me to do it. Any ideas? Do I have to adb sideload?
Click to expand...
Click to collapse
I'm not 100% sure but sounds like you need to remount the partitions, I think there's command adb remount but id advise you research the proper commands as I've never done it before.
Actually I'm sure you can remount partitions in TWRP as well but you'll have to check as again it's been a while since I've been had to do it
sofir786 said:
I'm not 100% sure but sounds like you need to remount the partitions, I think there's command adb remount but id advise you research the proper commands as I've never done it before.
Actually I'm sure you can remount partitions in TWRP as well but you'll have to check as again it's been a while since I've been had to do it
Click to expand...
Click to collapse
Been looking up some information. Looks like I will have to use my own computer to run an ADB server and then basically inject the zip files I need into the phone. Joy... lol
Got everything working. Ended up having to reflash the ROM to my phone, but it's all good now. Thank you so much for your help!
Hi everyone, sorry im new here don't know exactly where to post this so i just did it here, anyway i own a Samsung Galaxy tab A 6, SM-T280 and i tried to root it and flash it with TWRP. Basically it didn't go as planned because now i can't load into the stock firmware and when i try to it loads to the messed TWRP screen with blue/red line screen. I can only go into download mode pretty much. I have tried to flash my original stock firmware back with odin but its not working as in nothing really happens. I have also tried many times to flash with different TWRP downloads and used different odin versions and downloads but nothing works. I have searched for 2 days and have not found a fix. If there is a way to completely wipe the device and restore the original stock firmware i'd be fine doing that as i had previously backed up all my stuff.
Hope to hear back from you guys
Same problem, but mine is a SM-P585 (Galaxy A6 with S-Pen). Haven't been able to find anything related to solving this. Everything pertaining to this problem is for the SM-T58x versions. Have TWRP come up with a solution for the other phones? Version 3.3.3.0 hasn't made a difference.
the_watchmann said:
Same problem, but mine is a SM-P585 (Galaxy A6 with S-Pen). Haven't been able to find anything related to solving this. Everything pertaining to this problem is for the SM-T58x versions. Have TWRP come up with a solution for the other phones? Version 3.3.3.0 hasn't made a difference.
Click to expand...
Click to collapse
Hi, cheers for the reply anyway, I fixed the problem and ended up going from root to non-root. I believe the reason was it wasn't the most up to date TWRP file. I found a video on YouTube and the guy linked a working TWRP flash file. I found another video and it showed me how to correctly create my stock ROM files then execute them on my tablet via Odin and it worked. If you want I can link you the video on how to correctly create the zip files and folders to flash back your stock ROM.
Tony7860 said:
Hi, cheers for the reply anyway, I fixed the problem and ended up going from root to non-root. I believe the reason was it wasn't the most up to date TWRP file. I found a video on YouTube and the guy linked a working TWRP flash file. I found another video and it showed me how to correctly create my stock ROM files then execute them on my tablet via Odin and it worked. If you want I can link you the video on how to correctly create the zip files and folders to flash back your stock ROM.
Click to expand...
Click to collapse
hi,
can you help me with the link ? i'm facing the same issue.
alchemis said:
hi,
can you help me with the link ? i'm facing the same issue.
Click to expand...
Click to collapse
Here is the video name (can't post links) samsung android 8.0.0 fix .lz4 error on Odin
He has links in the description to stock firmwares, find your devices specific one and just follow the tutorial from there.
?Hope this helps
Tony7860 said:
Hi everyone, sorry im new here don't know exactly where to post this so i just did it here, anyway i own a Samsung Galaxy tab A 6, SM-T280 and i tried to root it and flash it with TWRP. Basically it didn't go as planned because now i can't load into the stock firmware and when i try to it loads to the messed TWRP screen with blue/red line screen. I can only go into download mode pretty much. I have tried to flash my original stock firmware back with odin but its not working as in nothing really happens. I have also tried many times to flash with different TWRP downloads and used different odin versions and downloads but nothing works. I have searched for 2 days and have not found a fix. If there is a way to completely wipe the device and restore the original stock firmware i'd be fine doing that as i had previously backed up all my stuff.
Hope to hear back from you guys
Click to expand...
Click to collapse
connect to pc by USB cable and use this ADB command : "adb reboot devices".
ayoob_tg said:
connect to pc by USB cable and use this ADB command : "adb reboot devices".
Click to expand...
Click to collapse
No, that isn't the solution, that isn't even a valid adb command.
There is this command:
"adb devices"
And this command:
"adb reboot"
But there is no such thing as "adb reboot devices"
Sent from my SM-S767VL using Tapatalk