Hi,
I flashed successfully CM 12 on my Yureka. Managed to install TWRP recovery; I installed CM recovery, flashed root.zip file, and then installed flashify and thus installed TWRP recovery.
However, Stock ROM email app dont work for hotmail as push. Hence, installed PacMAN and one more before I went to Blisspop ROM.
Both these ROMs take APN settings of both SIM as same. and Bliss POP ROM started giving me process.android.com error that I could hardly operate the phone. when I went to recovery, to my surprise, the TWRP recovery was missing
I must also mention here that while I was installing Bliss POP, I did wipe Dalvik Cache, internal storage and media.
so, I went to fastboot mode, installed cyanogen recovery and flashed CM 12 again. My phone is working fine now. However I want to install a Custom ROM s
And Hence since last 48 hours I have been trying to install TWRP recovery with no success.
I have now realised that on fastboot command for unlocking bootloader, it shows waiting for device. Tried Yureka all in one tool for CM 12, no luck
I have tried to install PDA net, it works fine
on Device Manager, ADB interface is shown properly.
I have deleted the drivers, and when machine is rebooted, it again installes ADB interface.
But I cant unlock the bootloader.
I am nearly certain it is a problem with my drivers for Yureka.
Searched, googled since two days, but no luck.
Can anyone help me who went through similar issues please?
I locked boot loader using all in one tool and then unlocked the bootloader again. and yes, it worked
Related
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Nikodominiko said:
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Click to expand...
Click to collapse
So I managed to fix the problem. When you root this phone or in fact just flash a custom recovery like TWRP, it changes the model of the phone, If you unroot the phone you won't be able to receive OTAs anymore even if you are on stock ROM, you'll always get an error at the end of the update even if you do it manually, if you are dumb like me and didn't make a backup of your stock system, you won't find any help on the internet more than to install a custom ROM and learn to live with the errors and bugs. I did not want that so to be able to get the phone to its factory state, what I did was this:
1. Download: stock recovery image for Le s3 x522 (official, you can find it anywhere), LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip, twrp_s3.img (the chinese TWRP recovery) and S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
2. Save those zips to the root of the phone, obviously the .img files you are going to flash them through your PC
3. Put the phone in bootloader mode. command: fastboot flash recovery recovery.img (the official recovery)
4. fastboot boot twrp (the chinese one)
5. From this step what I did was pure luck
6. wipe cache and dalvik and install LeEco_X522_5.8.019S_OTA.zip
7. wipe cache and dalvik and install bootloader-20S-s2.zip
8. wipe cache and dalvik and install S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
9. Reboot
How and Why did this worked I don't know, I am a noob but please try if you find yourself in the same situation as I was, you don't lose anything with trying, if this doesn't work don't blame me, this worked for my phone.
Greetings friends!
Thanks for putting this guide together, I am in a similar situation in that I reverted to stock everything (1. Installed YDSS chinese twrp, 2. Installed S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip. This flash was supposed to have installed the stock recovery and overriden the ydss twrp, but didn't, I had to manually flash that after. Everything came back smooth but my updates also failed at recovery.
I am wondering where you got the LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip & twrp_s3.img from?
Nice to hear you finally got it to work ! Aren't the X520 and the X522 the same phone ? Why official ROMs are not compatible ?
Hi - so I unlocked my bootloader, installed TWRP no problem. However I boot into TWRP abd select ADB Sideload - but it will not load. Installed via OTA/USB instead - tried flashing Lineage and AICP - both start the boot process but never complete. Lineage boot me back to TWRP, AICP just stuck on loading screen. Tried cleaning cache etc etc still no dice. Any ideas anyone where Im going wrong....I was previously on the latest stock rom.
Fortunately I can still access TWRP and bootloader etc fine.
Thanks!
Voipboy01 said:
Hi - so I unlocked my bootloader, installed TWRP no problem. However I boot into TWRP abd select ADB Sideload - but it will not load. Installed via OTA/USB instead - tried flashing Lineage and AICP - both start the boot process but never complete. Lineage boot me back to TWRP, AICP just stuck on loading screen. Tried cleaning cache etc etc still no dice. Any ideas anyone where Im going wrong....I was previously on the latest stock rom.
Fortunately I can still access TWRP and bootloader etc fine.
Thanks!
Click to expand...
Click to collapse
You must be missing some steps before flashing, like "FORMAT" your data partition instead of just wiping it.
read the instructions more carefully next time