Hey,
I was trying to install omnirom on my U9200 (on my PC I have ubuntu).
All of this is new to me so I just went to follow the instructions;
-flash recovery TWRP
-boot TWRP
-TAKE BACKUP! of what? naaah....
-wipe everything
Now Im supposed to "Flash ROM", but wait, what? Getting errors "unable to mount device" on my PC. I have the omnirom boot.img in my home folder and nothing on this mobilephone.
-'fastboot' commands always respond <waiting for the device>
-Cant open the mobile on my PC as an external drive, so cant transfer data.
-I can boot to TWRP
Anything I can do?
kennyriot said:
Hey,
I was trying to install omnirom on my U9200 (on my PC I have ubuntu).
All of this is new to me so I just went to follow the instructions;
-flash recovery TWRP
-boot TWRP
-TAKE BACKUP! of what? naaah....
-wipe everything
Now Im supposed to "Flash ROM", but wait, what? Getting errors "unable to mount device" on my PC. I have the omnirom boot.img in my home folder and nothing on this mobilephone.
-'fastboot' commands always respond <waiting for the device>
-Cant open the mobile on my PC as an external drive, so cant transfer data.
-I can boot to TWRP
Anything I can do?
Click to expand...
Click to collapse
You can install a rom via ADB sideload if you're on TWRP 2.3+
Luckily Ive got 2.4.4
adb shell
error: device not found
adb sideload rom.zip
error: closed
"Unable to mount U9200"
"Unable to mount MTP device"
So it kinda shows up but doesnt respond.
Out of luck?
You don't need adb shell. Have you started adb sideload in twrp? Then checked device manager if it's installed correctly?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Great! You need to start it from the advanced menu first.
Got omni installed now. So what else do I actually need? In the omni thread there are GApps, camera and superuser files but I cant get them to install through the same method.
Anyone has an idea on why is sideload not working for installing other .zip files? Is there another way?
Also its getting annoying when my pc all the time complains "unable to mount". Any ideas on that one?
And one more. Theres no option to enable USB Debugging, is this a problem?
Im trying to find out about these things all the time but...
edit -
Also the adb commands are not working.
error: device not found
Omni rom is working?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Omni rom is working?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Yes its working. Its really stripped down and Id like to install GApps and other stuff but these commands are not working.
I went out for a couple of hours and had to click on 250 error messages "unable to mount" when I came back. Its charging tho...
Have you enabled USB debugging?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
Go to info and press "build number" 7 times to enable developer options. Then go to developer options and enable usb debugging
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Have you enabled USB debugging?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
Go to info and press "build number" 7 times to enable developer options. Then go to developer options and enable usb debugging
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Thank you so much!
And also kinda LMAO @ this secret cheatcode. Like some old nintendo game or something.
Related
Hello Guys,
So i first had the CyanogenMod 10 Nightly (Latest version installed) at my HTC One X.
I had some issue's that my HTC was randomly rebooting so i decided let's try another custom rom.
So i downloaded this one: [07-12] [ROM] CyanogenMod 10 - Endeavor Unleashed | 029 | UNIFIED HBOOT | 4.2.1
After i downloaded it i followed instructions like i dod before for any other custom rom.
After it was installed the phone rebooted and came at the sim lock screen.
I typed in my numbers i had to but than it gave me errors like system stopped working etc.
So i thought hm a broken rom or something.
But unfortunately i have not backed up any custom or default ROM.
So now i really need your help guys.
Is there any easy way to acces my sdcard in fastboot or recovery mode?
As i can't use my phone at all right now.
Thanks guys.
Greetings PhoeniX_NL
Go into storage in recovery and mount sd-card storage while connected via usb to computer
Sent from my Quad-core OneX Beast
Gormsen said:
Go into storage in recovery and mount sd-card storage while connected via usb to computer
Sent from my Quad-core OneX Beast
Click to expand...
Click to collapse
Hello Gormsen,
Thanks for your reply. :good:
I am in recovery mode with the clockworkmod..
I selected mounts and storage.
Than mount /sdcard
But my pc doesn't detect it if a sd-card storage or any other storage option.
I am running windows 7 x64 at my main computer.
Also i tried the option mount USB storage.
But it gives me this error: E:Unable to open ums lunfile.
PhoeniX_NL said:
Hello Gormsen,
Thanks for your reply. :good:
I am in recovery mode with the clockworkmod..
I selected mounts and storage.
Than mount /sdcard
But my pc doesn't detect it if a sd-card storage or any other storage option.
I am running windows 7 x64 at my main computer.
Also i tried the option mount USB storage.
But it gives me this error: E:Unable to open ums lunfile.
Click to expand...
Click to collapse
Don't select the first option that says sdcard, go to the buttom of the list and selct that one, can't remember it's name, but I think it's usb storage or something like that. Then your pc should detect it at once
Edit:
Sorry, didn't read your post right. Hmmm.. really don't know what's causing that. Do you have the latest HTC drivers installed on your computer?
Sent from my Quad-core OneX Beast
What recovery are you using, that error seems to stand in line with an older version of the cwm recovery ?
And yes you have to go to
Mounts & storage - mount as USB (at the bottom of that menu)
MarcelHofs said:
What recovery are you using, that error seems to stand in line with an older version of the cwm recovery ?
And yes you have to go to
Mounts & storage - mount as USB (at the bottom of that menu)
Click to expand...
Click to collapse
Hello MarcelHofs,
Well not sure if the version of cwm recovery is the latest one available:
It says: v5.8.1.8
But like you could see in my post it gives the error: E:Unable to open ums lunfile.
Thanks again guys for your help and time.
Hope we can sort it out together :good:
You can find the latest official version of CWM in the Development section, that's an older one
tomascus said:
You can find the latest official version of CWM in the Development section, that's an older one
Click to expand...
Click to collapse
Hello tomascus,
Well how to get that file onto my phone as the usb storage won't work?
PhoeniX_NL said:
Hello tomascus,
Well how to get that file onto my phone as the usb storage won't work?
Click to expand...
Click to collapse
What are you talking about man? You don't need to copy recovery over to your sdcard. Just download it and flash it through fastboot.
tomascus said:
What are you talking about man? You don't need to copy recovery over to your sdcard. Just download it and flash it through fastboot.
Click to expand...
Click to collapse
Hello,
Well i tried this:
adb devices
But there are no devices listed at all.
Tried different pc's and usb ports.
Am i missing sonething?
PhoeniX_NL said:
Hello,
Well i tried this:
adb devices
But there are no devices listed at all.
Tried different pc's and usb ports.
Am i missing sonething?
Click to expand...
Click to collapse
Is your phone in fastboot mode? Hold power and volume down until you get to a screen. Then select fastboot using power button and it should read fastboot usb.
Sent from my HTC One X
download this zip and extract,
and put this file in the same extracted folder.
get into fastboot mode and open cwm.bat
Vcek said:
download this zip and extract,
and put this file in the same extracted folder.
get into fastboot mode and open cwm.bat
Click to expand...
Click to collapse
Hello Vceck,
Wow finally we are there .
This worked perfect and i can acces the sdcard trough my pc now.
Made the mistake of wiping all data on my SGS3 (AT&T), rooted, etc.
I'm in TWRP (2.3.3.1) and I want to load a new ROM .zip file via USB cable from my Macbook (OSX).
How can I do this?? Tried mounting internal storage, but nothing happened. I'm basically bricked until I can get another Zip on the phone! Help please!!
You dont have a backup on the phone you can restore or a rom you downloaded that you can flash?
If you have odin (if available for mac) you can use that to put an odin flashable rom onto the phone.
˙ıııs ʎxɐlɐb bunsɯɐs ʎɯ ɯoɹɟ ʇuəs
Odin isn't available for Mac.
I have ROMs to install, but they're on the Mac, and not on the phone..... it is wiped (except for the TWRP recovery).
Hog Milanese said:
Odin isn't available for Mac.
Click to expand...
Click to collapse
ODIN is not available for MacOS X, but you can use another software called Heimdall (http://www.glassechidna.com.au/products/heimdall/) to flash a stock ROM into your phone.
Another way to make a (custom) ROM available to flash in TWRP would be to use a microSD card. Use a microSD card reader connected to your computer, and copy your desired ROM into the microSD card. Then, place the microSD card into your phone. TWRP should be able to read the content of your microSD card, and flash the ROM.
Finally, a third way -- I never used that, though -- would be to use ADB sideload capability to sideload a ROM into your phone using ADB. More info about this in the TWRP site (http://teamw.in/ADBSideload).
I don't think you can USB mount your phone into your computer and manage the internal and external storages from your computer while in TWRP.
Or... Get adb for Mac and just do adb push <zip> /sdcard/<zip>
Then navigate to it in TWRP and install.
Sent from my SGH-I747 using xda premium
Android File Transfer. You're Welcome. :good:
BAM1789 said:
Android File Transfer. You're Welcome. :good:
Click to expand...
Click to collapse
That's not useful at all. That is one of the worst pieces of software ever.
Sent from my SGH-I747 using xda premium
d3athsd00r said:
Or... Get adb for Mac and just do adb push <zip> /sdcard/<zip>
Then navigate to it in TWRP and install.
Click to expand...
Click to collapse
BAM1789 said:
Android File Transfer. You're Welcome. :good:
Click to expand...
Click to collapse
But these two solutions need a running ROM, right? Or can you connect to your phone through ADB or through MTP while you are in TWRP?
Because Hog Milanese's problem is he wiped his ROM and does not have a ROM in his phone right now. Taking a quick look at TWRP's options, I did not find a way to MTP-connect the phone to a computer nor enable ADB (except for the ADB sideload command) while in TWRP... They work when in ROM, but not when in recovery.
Hog Milanese said:
Made the mistake of wiping all data on my SGS3 (AT&T), rooted, etc.
I'm in TWRP (2.3.3.1) and I want to load a new ROM .zip file via USB cable from my Macbook (OSX).
How can I do this?? Tried mounting internal storage, but nothing happened. I'm basically bricked until I can get another Zip on the phone! Help please!!
Click to expand...
Click to collapse
Grab an SD card, out pop it out of your phone, copy zip, plug back in, reboot recovery do it mounts your SD and flash away.
Sent from my SGH-I747 using xda premium
ADB is on by default in TWRP. I've pushed many files to it while in recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
BAM1789 said:
Android File Transfer. You're Welcome. :good:
Click to expand...
Click to collapse
Does not work in TWRP.
theineffablebob said:
Does not work in TWRP.
Click to expand...
Click to collapse
Did this problem ever get solved? I have a few roms on my Mac, but can't get them onto my device because I don't have a ROM installed but I am in TRWP recovery
I don't know the commands to push a zip to my computer through sideload
---------- Post added at 06:51 PM ---------- Previous post was at 06:48 PM ----------
Drakeskakes said:
Did this problem ever get solved? I have a few roms on my Mac, but can't get them onto my device because I don't have a ROM installed but I am in TRWP recovery
I don't know the commands to push a zip to my computer through sideload
Click to expand...
Click to collapse
Oh yeah, I can't use a microsd because I am using an HTC one, but I feel like sideload process should be the same
Same situation-MAC without microSD on an original kindle fire
Drakeskakes said:
Did this problem ever get solved? I have a few roms on my Mac, but can't get them onto my device because I don't have a ROM installed but I am in TRWP recovery
I don't know the commands to push a zip to my computer through sideload
---------- Post added at 06:51 PM ---------- Previous post was at 06:48 PM ----------
Oh yeah, I can't use a microsd because I am using an HTC one, but I feel like sideload process should be the same
Click to expand...
Click to collapse
I can't figure a way to get this to work. I'm on a macpro I have TWRP on an original Kindle fire. (TWRP was rooted with a crappy windows 7 desktop that I got rid of.) No roms are currently loaded on the kindle. I can't get the MAC to recognize the Kindle.
I have tried "Android File Transfer" <- worthless... I have also tried my wife's Win10 laptop. <-less worthless but no hope. It seems like the old ways of forcing the driver wont work on Win10.
I'm a little bummed out about how software is forcing hardware to be obsolete.
If the device has TWRP, there is an option to mount data partition?
audit13 said:
If the device has TWRP, there is an option to mount data partition?
Click to expand...
Click to collapse
It has a data partition, but there is no way to access the hard drive on the kindle. I am in the process of making a fastboot usb cable to test and see if I can access it on a Mac. I'll let you know how it goes.
FWIW - the following worked for me - downloading and running AndroidFileTransfer.app on macOS Sierra with my Nexus6 connected via USB booted into TWRP v3.1.0 - file transfer worked without issue. Not sure if newer versions fixed past problems reported by others, but this was working without any work - very grateful to the person who mentioned the androidfiletransfer app!
I was facing same issue... What I found ---
> adb doesn't work while in recovery mode
I was able to copy ROM from Mac to phone by following below steps:
1) Go to fastboot mode
2) fastboot boot recovery.img (any twrp image) -- android file transfer should be able to detect device now as twrp has adb enabled and phone is not in recovery mode
3) Copy your Rom to your phone
4) Fom TWRP : reboot>recovery
5) Install custom ROM and reboot to system
Hope this helps out.
Ok I was in the TWRP and hit wipe all system data in the sdcard So I have nothing loaded on phone so I have no OS at all now... I am totally lost on how to get it back up and going I see something about adb sideload but what in the world is that and how do I start.... From scratch on a new windows 7 PC ....
PLEASE HELP ME... WIFES PHONE AND IT HAS BEEN HOURS HER PHONE BEING DOWN....
theitguys said:
Ok I was in the TWRP and hit wipe all system data in the sdcard So I have nothing loaded on phone so I have no OS at all now... I am totally lost on how to get it back up and going I see something about adb sideload but what in the world is that and how do I start.... From scratch on a new windows 7 PC ....
PLEASE HELP ME... WIFES PHONE AND IT HAS BEEN HOURS HER PHONE BEING DOWN....
Click to expand...
Click to collapse
Just "google" how to adb sideload...
Maybe you will have to reinstall Stock firmware with the kdz updater then root/unlock again...
Sent from my AOSP on geeb_att_us using xda premium
hastedp reduplicated
Have googled it and get different types using the command prompt maybe I am doing something wrong. Is SDK actual software?
theitguys said:
Have googled it and get different types using the command prompt maybe I am doing something wrong. Is SDK actual software?
Click to expand...
Click to collapse
Your phone was in "USB debugging mode" when you reboot in recovery?
Btw, i'm not very familiar with adb command...if i was you, i just reinstall the clean stock firmware using the kdz updater...it takes about 5-10 minutes and it's done. But, it will probably erase all your data. You've been warned!
Sent from my AOSP on geeb_att_us using xda premium
Yes it was in debugging. I was in recovery and doing a clean up of cache and hit wipe data and then lost it all.. went in to look for roms on internal storage gone
theitguys said:
Yes it was in debugging. I was in recovery and doing a clean up of cache and hit wipe data and then lost it all.. went in to look for roms on internal storage gone
Click to expand...
Click to collapse
You formated the "System" or just "data"?
Sent from my AOSP on geeb_att_us using xda premium
All of it system not a thing on storage besides some random folders
theitguys said:
All of it system not a thing on storage besides some random folders
Click to expand...
Click to collapse
Did you try to reboot? Or it says "No OS installed"?
If you didn't format the System partition, it should boot...but your data will be gone...
Sent from my AOSP on geeb_att_us using xda premium
---------- Post added at 11:45 PM ---------- Previous post was at 11:18 PM ----------
Here some steps to "kdz-ing"
Use the KDZ Updater with the latest firmware version of your phone...
First, download and install the latest lg driver. (your phone must be unplugged when installing)
Second, download the LG E970 kdz.
Third, "google" and install the kdz updater.
Fourth, put your phone in "Download mode" by pressing both volume keys and plug into usb port (wait 2-3 seconds, your computer will load the driver)
P.S: to shutdown the phone, hold the power button for about 15 seconds after you should be able to enter in "download mode"
Fifth, open the kdz updater and select "3GQCT" in type...and "CS_Emergency" in phone mode. Then browse & select the kdz you've just downloaded...and press the Launch button. It should take about 8-10 minutes to complete...your phone will reboot around param.94 then you can unplugged it and let it boot normally.
Finally, make a "factory reset" to erase all previous data and plug your phone to wall charger to gave him some fresh blood.
Give us some feedback & good luck :good:
Sent from my AOSP on geeb_att_us using xda premium
Need the KDZ file for my E971 from Rogers
The same thing happened to me but for the life of me, I cannot find the KDZ file I need anywhere. I have the E971 from Rogers. Anybody knows where I could find the KDZ file for my E971 É
Thanx
$10 paypal to who can help me solve this
Here's the deal people,
My GNex was slowing down and acting all funny with stock 4.3 after about 6 months
I finally decided to try out a 4.4.2 ROM
I had TWRP on the phone so I said I'd just copy the Zip to the root folder along with the Gapps
Long story short, I accidentally wiped the storage.
Then I said no biggie, and figured that I'd just mount the USB to my laptop and transfer the Zip file of the ROM I wanted over to the storage.
BUT when ever I tap on mount USB nothing shows up in the devices.
Now I have nothing to transfer the files to.
I have windows 8 on the computer I'm currently using if that matters.
Forgive me people. I am not an avid flasher like I was when windows phone 6 was still around. So spare the insults . Just need my phone running so I can contact my loved ones
Galaxy Nexus uses MTP instead of Mass Storage mode, so you can't mount it as usual.
However, there's an "ADB sideload" option that lets you sideload a ROM from your PC using the ADB command (if you have the drivers installed, in the command prompt window, just type "adb sideload *THE-PATH-TO-YOUR-ROM-FILE*").
Find out more with Google
throwback1718 said:
$10 paypal to who can help me solve this
Click to expand...
Click to collapse
We Chinese don't use Paypal
Sent from Google Nexus 4 @ CM11
AndyYan said:
Galaxy Nexus uses MTP instead of Mass Storage mode, so you can't mount it as usual.
However, there's an "ADB sideload" option that lets you sideload a ROM from your PC using the ADB command (if you have the drivers installed, in the command prompt window, just type "adb sideload *THE-PATH-TO-YOUR-ROM-FILE*").
Find out more with Google
We Chinese don't use Paypal
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
agh I have read that the drivers don't work on windows 8 PC's . But I'll try
I flash my phone usually 2 or 3x per 12 months. so please pardon me if I forget some things...
In addition, the phone has nothing on it but TWRP
so no OS is on it at the moment. and no USB mounting.
I think USB mount is used for mounting USB flash drives attached through USB OTG.
The essentials. Contains ADB, fastboot and USB drivers from the Android SDK (should work on 8 and 8.1).
ADB_usb-driver.zip (8.79 MB)
To transfer files within TWRP, you need to use adb. Start by installing the driver. To verify for successful driver installation, type in:
Code:
adb devices
It should show you a "List of devices attached" and there's at least 1 item in the list.
Then copy the zip you want to flash into the same folder as adb. Let's say the file is named rom.zip. To "push" it to the phone, use the following command:
Code:
adb push rom.zip /sdcard/rom.zip
After it has finished "pushing" the file, just tap "Install" in TWRP and the zip file should be there!
You can now proceed flashing the ROM of your choice.
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
cmstlist said:
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
Click to expand...
Click to collapse
THis is my issue now. I was able to get the GNex wugfresh toolkit
I was able to push the original 4.4.2 ROM that I wanted over to the device. But It keeps saying failed at the install point.
Good thing I came back to read this post. Thanks. Ill try to flash by fastboot
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
I keep hitting these damn road blocks. Im sure I have many people calling and texting me.
Can you temporarily put the SIM in another operable phone to get your calls and texts?
Not sure about the fastboot error. You'd need to download a Google stock ROM image directly from them, and fastboot flash the system and boot partitions. This should be enough for a reboot to regenerate the user data partition. You cannot flash the custom ROM in fastboot unless a version has been made available in that format.
Sent from my Nexus 5 using Tapatalk
throwback1718 said:
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
Click to expand...
Click to collapse
Might as well use another non-Win8 computer, drivers are hard to mess with.
Sent from Google Nexus 4 @ CM11
---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------
cmstlist said:
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
Click to expand...
Click to collapse
Is that so?
Sent from Google Nexus 4 @ CM11
AndyYan said:
Is that so?
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Yes, why would I say it if it were not my experience that it is so?
On Nexus devices, a userdata wipe from the bootloader often leaves it in a state where custom recovery cannot write to data. Booting once into a bootable ROM typically fixes this.
Sent from my Nexus 7 using Tapatalk
cmstlist said:
Yes, why would I say it if it were not my experience that it is so?
On Nexus devices, a userdata wipe from the bootloader often leaves it in a state where custom recovery cannot write to data. Booting once into a bootable ROM typically fixes this.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I mean, is it true that after wiping all partitions (data, cache, dalvik, system, internal storage) in recovery, you cannot sideload a ROM as usual? What error does the phone give? And why does wiping breaks partition table, when all it does is *independently* formatting all partitions?
Sent from Lenovo Erazer Z500 @ Android-x86 4.3
AndyYan said:
I mean, is it true that after wiping all partitions (data, cache, dalvik, system, internal storage) in recovery, you cannot sideload a ROM as usual? What error does the phone give? And why does wiping breaks partition table, when all it does is *independently* formatting all partitions?
Sent from Lenovo Erazer Z500 @ Android-x86 4.3
Click to expand...
Click to collapse
I don't have all the answers to that. Wiping data in custom recovery should not be an issue because TWRP & CWM are both designed to keep /sdcard intact and erase the rest, which means it's just deleting files not formatting the whole partition. What I'm saying has to do with when you're in *fastboot* and you either factory reset, reflash userdata.img or wipe userdata.img, or unlock the bootloader.
On my GNex in this situation, circa 1.5 years ago, TWRP gave an error in which it thought the data partition was encrypted. CWM did not give an error but any files I attempted to write did not actually stick. One boot into a working ROM fixed it.
I have also observed that after a fastboot wipe, it starts booting into the ROM, possibly displays the Android "unpacking" screen, and then resets to the Google splash screen one more time, and then the second boot is the successful one. I have no idea if it has to do with permissions, formatting, or whatever else, I just know that it happens.
throwback1718 said:
THis is my issue now. I was able to get the GNex wugfresh toolkit
I was able to push the original 4.4.2 ROM that I wanted over to the device. But It keeps saying failed at the install point.
Good thing I came back to read this post. Thanks. Ill try to flash by fastboot
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
I keep hitting these damn road blocks. Im sure I have many people calling and texting me.
Click to expand...
Click to collapse
Your 4.4.2 ROM install most likely failed due to outdated TWRP. You must install twrp 2.6.3.2 via fastboot first, then you should be able to install and get going.
Let me know if you need links to anything
---------- Post added at 05:11 AM ---------- Previous post was at 05:10 AM ----------
Also, next time don't "wipe/format data" in twrp. Do factory reset. (Unless they changed the damn name again on us lol)
Thanks to Nakum for the assistance. (Nakum can be found at drnakum on Yuforums or at dr.nakum on XDA) and to Mr.Anish for telling us that the latest TWRP recovery works.
Ok guys, so Nakum succesfully managed to root the device and I was able to do so as well. The Procedure is similar to Yureka, except you use the latest TWRP version and the latest chainfire SU binary 2.46.
This method can be done using a Hot boot or by flashing. If you want to retain the original recovery, do it by hotboot. If you want a vustom recovery, then flash it.
Here is a noob friendly guide.
1) Enable Developer Option (Go to Settings-> About Phone -> Tap on Build number 7 times)
2) Go to Developer Option and disable Update Recovery
3) Enable Android Debugging
4) Install the 15-Second ADB driver file (http://forum.xda-developers.com/showthread.php?t=2588979)
5) Download adb+fastboot zip (https://www.androidfilehost.com/?fid=95916177934556622)
6) Download Su binaries (https://download.chainfire.eu/696/SuperSU)
7) Copy UPDATE-SuperSU-v2.46.zip to an SD card
8) Download TWRP (https://s.basketbuild.com/uploads/devs/vishal_android_freak/yu/yureka/TWRP_V2.8.7.0_YUREKA.img)
8) Connect Phone to PC and navigate to the folder where you have abd+fastboot
9) Shift+right click -> Open command prompt
Type : adb devices
If your device is connected you will get it in connected devices
Type : adb reboot-bootloader
Your phone will restart into bootloader.
Type : fastboot -i 0x1ebf oem device-info
If your bootloader is unlocked, it will say "True", else it will say "false". If it is False, then do the next step
Type : fastboot -i 0x1ebf oem unlock
WARNING : All your userdata will be GONE! Now you can root your phone in two ways
Method 1 : If you want to retain the Original Recovery - Hot boot
Type : fastboot -i 0x1ebf boot TWRP_V2.8.7.0_YUREKA.img
This will launch TWRP on your device. Navigate to where you saved the UPDATE-SuperSU-v2.46.zip file. Flash it, wipe Cache, Reboot and you are rooted!
Method 2: If you want to flash Custom Recovery - Flash
Type : fastboot -i 0x1ebf flash recovery TWRP_V2.8.7.0_YUREKA.img
Your Cyanogen recovery will be replaced with TWRP. Then, unplug your device, hold volume up+down+power to boot into recovery, navigate to where you saved the UPDATE-SuperSU-v2.46.zip file. Flash it, wipe Cache, Reboot and you are rooted!
Hit thanks/like if this helped
Hope this helps! If you guys need any clarification, feel free to ping me!! Have fun!
EDIT : For those stuck in a bootloop! After flashing TWRP, go to Wipe and hit Format Data...then reboot to recovery (everything will be mounted by now) and flash the chainfire SU binaries. Reboot and everything should work fine. The phone may be stuck in the "Cyanogen" screen for a goot 5-10 mins before the apps start loading...so stay patient.
why i cant make nanddroid backup ??
/data cant be mount :/
---------- Post added at 03:17 AM ---------- Previous post was at 03:00 AM ----------
my phone now stuck in boot loop :/
what to do
---------- Post added at 03:58 AM ---------- Previous post was at 03:17 AM ----------
guys recovery is not opening n i cant boot the phone in fastboot or in bootloader
plzzzz help
---------- Post added at 04:57 AM ---------- Previous post was at 03:58 AM ----------
when do factory images will be released guys ?
i guess thats the only way to boot my device now :'(
---------- Post added at 05:01 AM ---------- Previous post was at 04:57 AM ----------
can anyone can pull the original cwm recovery from the yureka plus n upload ?
Wow wow champ...chill. Tell is what you did exactly and I will tell you how to recover your phone.
Btw this is for the others....just to show that rooting works.
This method works. But I got some bug with the TWRP installation in one of the phones. It wasn't able to reboot the phone or switch it off via recovery. So I think I'll probably try reinstalling the recovery. On the second device, this method worked flawlessly. A third one will be arriving later, by next week. I'll probably try installing CWM next time. If possible, make a video, or give more info in the steps to help people figure out if they performed the steps correctly or not, because the phone has been recently launched, and there's not a lot of information about it on the internet. Anyways, many thanks for the guide! CHEERS!
---------- Post added at 06:29 AM ---------- Previous post was at 06:12 AM ----------
Also, If you could add some information on how to reset the phone to its stock settings, and stock recovery, that would be great. I wasn't able to fix the TWRP problem by reinstalling it. So I would like to go through all the steps from the start again.
And I managed to soft brick my device, when I tried CWM on it. Is there a way I can enter download mode manually I mean by button combinations?
---------- Post added at 07:53 AM ---------- Previous post was at 07:40 AM ----------
I fixed it, but the recovery is still not working like it should. It did work on the other device though. I don't know what the issue is. Need to figure out a way to go back to stock recovery.
rakave said:
Wow wow champ...chill. Tell is what you did exactly and I will tell you how to recover your phone.
Click to expand...
Click to collapse
I'm skipping the adb part.
- First rebooted the phone In bootloader via adb
- Then unlocked the boot loader
(i noticed in bootloader device
Tampered was true even though i just got my device and box was sealed may be this could be the reason of brick?)
- Then flashed(not booted) twrp from above link.
- Then rebooted in to recovery
- Tried to take back up but it didnt work (mounting /data failed)
- Then used pen drive via otg to flash superuser ( it flashed but only on /system, /data was again failed to mount)
- Then restarted
- but after yu logo phone restart it self in to twrp then format /cache then restart again
Then this goes forever
Can u help to boot my phone again
Only
Yesterday i got it n now its soft bricked
Sent from my Galaxy Nexus using xda premium
Found the solution...!!!!!!!!!1
Hey guys.... I also tried rotting my Yureka plus and after following everything, I get stuck on the bootloop... after wasting 3 hours on net, I tried some steps myself and it fixed the issue.
Let me tell you the steps which I did:
Switched off my Yureka.. took the memory card out....
rebooted to TWRP recovery, I went to "wipe" > "format data"..
Data was successfully foramtted.
ALL DONE!!!!!!!!!
Now, you will be able to mount data and flash SuperSU without any issues...
It can take 4 to 5 minutes for the phone to start up (on the "Cyonogen" logo").
If you are experiencing issues, you can email me at asksree24by @ gmail.com
If you are stuck in a bootloop, just format data and everything will work. Let it load for a while. Dont worry...it stays in the cyanogen logo for a good 5-10 mins easily.
Thank you so much
Now its booting
Sent from my Galaxy Nexus using xda premium
Viola!!!!! I must try to root my device now...! Was waiting for confirmation on this guide...!!!
Sent from my YU5510 using Tapatalk
what type of data will get wiped? and Will I not be able to get OTA 5.1 after rooting
Guys,
Please tell whether my installed apps and organized Screens like grouping app shortcuts in folders will also get deleted or gets reset? Will all installed apps go away? or Do I need to re-login after unlocking bootloader?
If possible, Please elaborate that what kind of User-Data will get wiped?
and Will I not be able to get OTA 5.1 version update after rooting?
Thnx
Works great for me thnx buddy
last step remaining help me......
Sir, i have unlocked bootloader it shows true in tampered and unloacked.. but shows false in "charger screen enabled"..
and i am not able load TWRP img file in any of the method given below..
HELP ME
need assistance
rakave said:
Thanks to Nakum for the assistance. (Nakum can be found at drnakum on Yuforums or at dr.nakum on XDA) and to Mr.Anish for telling us that the latest TWRP recovery works.
Ok guys, so Nakum succesfully managed to root the device and I was able to do so as well. The Procedure is similar to Yureka, except you use the latest TWRP version and the latest chainfire SU binary 2.46.
This method can be done using a Hot boot or by flashing. If you want to retain the original recovery, do it by hotboot. If you want a vustom recovery, then flash it.
Here is a noob friendly guide.
1) Enable Developer Option (Go to Settings-> About Phone -> Tap on Build number 7 times)
2) Go to Developer Option and disable Update Recovery
3) Enable Android Debugging
4) Install the 15-Second ADB driver file (http://forum.xda-developers.com/showthread.php?t=2588979)
5) Download adb+fastboot zip (https://www.androidfilehost.com/?fid=95916177934556622)
6) Download Su binaries (https://download.chainfire.eu/696/SuperSU)
7) Copy UPDATE-SuperSU-v2.46.zip to an SD card
8) Download TWRP (https://s.basketbuild.com/uploads/devs/vishal_android_freak/yu/yureka/TWRP_V2.8.7.0_YUREKA.img)
8) Connect Phone to PC and navigate to the folder where you have abd+fastboot
9) Shift+right click -> Open command prompt
Type : adb devices
If your device is connected you will get it in connected devices
Type : adb reboot-bootloader
Your phone will restart into bootloader.
Type : fastboot -i 0x1ebf oem device-info
If your bootloader is unlocked, it will say "True", else it will say "false". If it is False, then do the next step
Type : fastboot -i 0x1ebf oem unlock
WARNING : All your userdata will be GONE! Now you can root your phone in two ways
Method 1 : If you want to retain the Original Recovery - Hot boot
Type : fastboot -i 0x1ebf boot TWRP_V2.8.7.0_YUREKA.img
This will launch TWRP on your device. Navigate to where you saved the UPDATE-SuperSU-v2.46.zip file. Flash it, wipe Cache, Reboot and you are rooted!
Method 2: If you want to flash Custom Recovery - Flash
Type : fastboot -i 0x1ebf flash recovery TWRP_V2.8.7.0_YUREKA.img
Your Cyanogen recovery will be replaced with TWRP. Then, unplug your device, hold volume up+down+power to boot into recovery, navigate to where you saved the UPDATE-SuperSU-v2.46.zip file. Flash it, wipe Cache, Reboot and you are rooted!
Hit thanks/like if this helped
Hope this helps! If you guys need any clarification, feel free to ping me!! Have fun!
EDIT : For those stuck in a bootloop! After flashing TWRP, go to Wipe and hit Format Data...then reboot to recovery (everything will be mounted by now) and flash the chainfire SU binaries. Reboot and everything should work fine. The phone may be stuck in the "Cyanogen" screen for a goot 5-10 mins before the apps start loading...so stay patient.
Click to expand...
Click to collapse
Hi... Can I install ROMs available for yureka
Hey guys, when I tried downloading asphalt 8 on this device, it showed that this app isnt available in your region but my region on the google acc is set right. I also tried clearing the app data for playstore and re-installing play services but it doesnt seem to work. Can anybody please help me?
seriousia said:
I'm skipping the adb part.
- First rebooted the phone In bootloader via adb
- Then unlocked the boot loader
(i noticed in bootloader device
Tampered was true even though i just got my device and box was sealed may be this could be the reason of brick?)
- Then flashed(not booted) twrp from above link.
- Then rebooted in to recovery
- Tried to take back up but it didnt work (mounting /data failed)
- Then used pen drive via otg to flash superuser ( it flashed but only on /system, /data was again failed to mount)
- Then restarted
- but after yu logo phone restart it self in to twrp then format /cache then restart again
Then this goes forever
Can u help to boot my phone again
Only
Yesterday i got it n now its soft bricked
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Okay the same thing happened with me yesterday with my friend's yuphoria but i managed to get it to work after 2 hours of hit and trial methods, first of all you will need to install the stock recovery(debuggable) for the phone and then do a factory data reset and then flash the twrp recovery again and then wipe data, cache, dalvik and everything in the advanced wipe section. this will erase everything on the device, even the rom(at least in my case it said 'no OS installed'). Since there in no custom rom available for the device currently, you will have to download the stock rom (fastboot version) and have to flash everything using fastboot.
Good luck
udayaggarwal1980 said:
Okay the same thing happened with me yesterday with my friend's yuphoria but i managed to get it to work after 2 hours of hit and trial methods, first of all you will need to install the stock recovery(debuggable) for the phone and then do a factory data reset and then flash the twrp recovery again and then wipe data, cache, dalvik and everything in the advanced wipe section. this will erase everything on the device, even the rom(at least in my case it said 'no OS installed'). Since there in no custom rom available for the device currently, you will have to download the stock rom (fastboot version) and have to flash everything using fastboot.
Good luck
Click to expand...
Click to collapse
Ty bro but its already solved
Device was getting stuck because /data partition was not mounting
But after formating /data partition ohone booted perfectly
Sent from my YU5510 using xda premium
Very o
seriousia said:
Ty bro but its already solved
Device was getting stuck because /data partition was not mounting
But after formating /data partition ohone booted perfectly
Sent from my YU5510 using xda premium
Click to expand...
Click to collapse
Okay!!! so are you happy with the phone now?? is it a good buy after root?? do you have any complaints now about battery and heating.. I actually purchased the device and returned it becoz of the poor battery performance and lag in transitions. so how is it now??
I'm stuck over here as well mate, what am I supposed to do next? Please Help :crying:
---------- Post added at 03:02 PM ---------- Previous post was at 02:54 PM ----------
rakave said:
If you are stuck in a bootloop, just format data and everything will work. Let it load for a while. Dont worry...it stays in the cyanogen logo for a good 5-10 mins easily.
Click to expand...
Click to collapse
How can I do that bro? my phone keeps restarting again and again, it restarts right back into TWRP.