Develop Bugs

[Q] No recovery anymore, Phone OK

In the process of trying to flash a new firmware to a GIO I somehow managed not to be able to acess the recovery menu anymore. Right now the Phone is rooted, booting fine into stock ROM, download mode is working but no recovery menu. While trying to boot with power and home button it just shows the Samsong logo for ages.
I tried to flash a new recovery several times due to the fact that the stock recovery is only able to apply update.zip and not able to select any custom filename. So I installed su and a new recovery this way. After realizing that there is no recovery anymore I did it using ODIN and download mode. I tried several recovery images from cwm to stock, but everytime the same.
What did I miss?
How to do a dalvik/cache reset outide revovery menu and not doing a full hard reset?
Would a hard reset help?
TiA,
longInt

Guess their are commands to do it with ADB, phone can still go on so thats fine
Download adb
Connect phone to pc
Open command prompt , cmd.bat
Type
Adb
Su
Reboot recovery
Try if it works...
You can also flash recovery with ODIN, cwm v5 can be flashed with odin
Sent from my GT-S5660 using xda premium

I did already
Flashed cwm-5.0.2.7-ext4+rfs-odin.tar.md5 using ODIN without problems, but as I said, no recovery menu available/accessible. BTW: Do I've todo anything after ODIN triggered the reboot? I just remove the phone and try to access recovery menu...
I do not have adb available at the moment, Sorry. Will try tommorow, but I guess this will not show something different!?
Thx!

Terminal emulator?
Code:
su
Reboot recovery
Sent from my HTC Sensation

OK; will try the Terminal emulation soon. But also when trying "Reboot to recovery" from inside ROM Manager it just hangs showing the SAMSUNG Logo. Did I flash the right recovery in terms of the ext4 thing?
TiA

voetbalremco said:
Adb
Su
Reboot recovery
Click to expand...
Click to collapse
This results in a black screen and the phone not booting anymore (just showing the Samsung logo). I'm pretty sure the stock rom is booting again after flashing cwm again (had this before). Doing this now...
Any other ideas, tipps?
TiA

OK, guys, time for new proposals. Whichever way I try to get into recovery it fails. Reflashing recovery brings the phone back, but how to go into recovery!? I even tried to boot recovery using my GS3 Toolkit with the same negative result just to prove there is no way to reach recovery.
Isn't there a need to flash cache and dalvik or something else after flashing recovery!? How?
TiA

Try flashing a full stock rom with odin, so everything is gone, kernel, su etc...
If still not, live with it or bring it to a service center
Sent from my GT-S5660 using xda premium

OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...

exact same problem
longint2 said:
OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...
Click to expand...
Click to collapse
I have the exact same problem as you. Same phone as you, phone rooted fine, tried installing CWM now can't get to recovery with the same symptoms as you. Holding Power+Home results in a hanging Samsung logo and no longer being able to boot at all. Removing the battery doesn't help. Reflashing allows me to boot normally but still not recovery mode (download mode accessible all the time). Rebooting from ROM manager usually results in "RAMDUMP mode arm9" instead of recovery (wtf).
Tried different CWM versions recommended for Gio, some older some newer, some with different filesystems.
Tried different methods for installing recoveries (from SD card in the original recovery mode the first time, and from ODIN)
Tried different methods of reaching recovery mode (key combination on boot, reboot from terminal, reboot from ROM manager).
Tried doing "firmware update" with (lol) Kies
Seriously no idea how to solve it, it's exactly the same as the problems in this thread. Advice from friends and these forums has so far not helped, but hopefully someone will discover an answer soon?
Things I don't think are related:
I have hardly any space left on the phone
My battery life has now been reduced to 2 hours average (woohoo!)

Have you tried installing stock rom via Odin? It installs stock recovery itself, and then you would be able to see what happens when you are trying to acces recovery

Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
---------- Post added at 08:23 AM ---------- Previous post was at 08:17 AM ----------
Follow step by step:
Make sure you do it from a PC on which you haven't already installed Samsung USB drivers or KIES.
1. Install Samsung usb drivers.
2. Open Odin and boot phone into downloading mode.
3. Browse Gio.ops and xxxxxxxx.tar file and start flashing.
Sent from my GT-S5660 using Tapatalk 2

nope…
pakistanish said:
Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
Click to expand...
Click to collapse
I doubt this is the problem because the first time I tried flashing CWM was not with Odin (I'm not a Windows user) but from the stock recovery as shown in the video tutorial on this forum. I think I'll try wojtek267's suggestions and reflash the stock rom when I get my USB cable back.

Tried a lot more things, none of them worked
Sorry for double-posting, but this is long.
Update:
I got a USB cable. I tried a lot of stuff that also doesn't work. That's what's covered in this post:
This doesn't work. Naturally the first part doesn't work because it says boot into recovery and I can't do that. Ignoring that and continuing from step 5 does just as little. At the bottom of this post I've written what Odin does.
This also doesn't work, it's basically the same thing.
Tried reinstalling stock ROM as suggested. No difference in results. List of ROMs I've tried at bottom of post.
Tried using Odin from a different PC, as suggested. More on this at bottom of post.
Tried flashing using flash_image in adb. More about that at bottom of the thread.
Tried to get fastboot to work. I get an infinite < waiting for device >. More on that at bottom of the post.
Tried to factory reset the phone using both the menu option in settings, and the dial code, both result in the phone turning off and then starting up with a blank black screen that stays there forever.
Tried taking the battery out a thousand times, seriously why is this suggested so often?
List of Recovery ROMs I've tried:
signed_cwm-5.0.2.7-flashablezip-ext4only.zip
cwm-5.0.2.7-ext4only-odin.tar.md5
cwm-5.0.2.7-ext4+rfs-odin.tar.md5
stockrecovery-DXKT4-odin.tar.md5
All coming from this thread.
Also one or two others from blog about clockworkmod etc.
The point is it has no effect because as far as I can tell it isn't even flashed anyway.
Flashing from fresh PC failed
What I mean by this is:
I took a different PC
did a fresh install of windows on it
installed the Samsung drivers using the Kies CD
put the phone in download mode (VolDown+Home+Power)
start Odin, select OPS and tar.md5 file
connect phone
run Odin
nothing special happens…
What Odin does:
copy image to phone → success
disconnect from COM port and wait for reboot
start countdown timer
at this point phone reboots normally (not recovery or anything) and nothing special happens, the Odin timer eventually time's out and the operation is finished
Update: added actual output from odin as an attachment.
I'm not sure but I don't think the above is what Odin is typically supposed to do.
The odin I'm using is 4.42 for Gio and comes from the threads linked to in the first 2 bullet points linked above.
How flash_image fails
I have tried using both adb and terminal emulator on phone. Root access is given to the emulator via superuser app. This is what I do:
Code:
su
cd system
flash_image recovery recovery.img
This is what I get:
Code:
error scanning partitions: No such file or directory
recovery.img is located in /system/recovery.img
flash_image is located in /system/bin/flash_image with proper chmod setting of 755.
It makes no difference if I mount the system as read/writeable or not.
The flash_image I'm using comes from CyanogenMod wiki, here.
My best guess here is that the reason flash_image finds no recovery partition is that there isn't one. I certainly don't see one. And this would also explain why the phone does nothing (black screen or samsung logo) when you try to boot to recovery.
Please dear God somebody tell me that one of you has seen this before and knows a solution for this?
According to this thread the partition where recovery.img resides is /dev/block/bml9, but how do I get my CWM recovery.img on that partition? Do I cat? dd? What? Is there any partition (e.g. that one, or /system or anything) that I should format to something strange before this will work?
Issues with fastboot
2 problems with this. First one is, how exactly do you get into "fastboot" mode on the phone? I don't even know if it can. I have uncovered the following startup key-combos:
recovery mode (Home+Power) does not work, so now just a blank screen
download mode (VolDown+Home+Power)
ramdump arm9 mode (VolUp+Home+Power)
emergency download mode (VolDown+VolUp+Home+Power)
LK Little Kernel Mode (VolUp+VolDown+Power)
blank screen (VolUp+Power)
blank screen (VolDown+Power)
regular boot (Power) doesn't work after attempting hard reset, only results in samsung logo and inability to boot
None of these seem to be fastboot mode, so I guess it's more complicated than that.
Other problem is I'm using Linux and I've read I'll need to configure Udev to detect the phone ID used when in fastboot mode.
I've read that some people who couldn't flash with flash_image in adb were able to flash using fastboot so I'm hoping for that.
Summary
As you guys can see I've really tried a lot of things. Everything I can think of, and everything I could find on XDA and the rest of the web. I have had no success. Like OP's topic title says, I still have a working phone. When Hard Reset fails and the phone becomes unbootable I can make it bootable again by using Odin to fail at flashing a recovery.
So the phone actually works fine. The problem is I can't get to recovery mode and therefore can not flash CyanogenMod (all CyanogenMod threads say to flash ClockworkMod Recovery before CyanogenMod).
Please can somebody help me with this, I don't know what else to try.
Edit: hey pakistanish, thanks for the suggestions, if I don't install the USB drivers from the Kies CD then where am I supposed to get them from?

Bump?
Nobody able to help with this?
Am I in the wrong sub-forum or something?

One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Good luck,
Darkshado

very nice try, still no cigarre
Darkshado said:
One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Click to expand...
Click to collapse
Hi thanks for the helpful advice! I tried that now. Backed up the current bml9 to sdcard with dd and then dd'd my recovery.img over it; it seemed successful. I restarted the phone to recovery mode and it just hangs at the Samsung logo like normal. This thread confirms that /dev/block/bml9 is indeed the recovery partition, however replacing it seems to have no effect.
I have never heard of ddms or logcat, what do they do and do you have download links?

I still have the same issue, thx for any advices.

LG E980 PhilZ Touch Recovery BootLoop Fix (HOW TO GET DEVICE BACK TO USABLE STATE)

Download the zip from this link http://s000.tinyupload.com/index.php?file_id=70581848454313738691 . After that mount USB in PhilZ and copy over the zip file to your phone. Then flash the zip file and your boot loop should be fixed. The fix is originally by @fosunite and was posted on the PhilZ page.

Why is the file size so big?

arifqur said:
Why is the file size so big?
Click to expand...
Click to collapse
I put several ROMs in it that I modified to work with the old recovery which I also modded...all is in the zip make sure to read the readme

or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.

rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
That's basically what the tutorial says but it also has modified CM11 zips that will be flashable in twrp 2.6.1.0

This is a simpler guide for those who have trouble with terminal based solutions
Sent from my LG-E980 using Tapatalk

philz bootloop
rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
I am having this same issue. everything was going fine with it when I booted into recovery from rom toolbox, but the first time I booted into philz with the power vol up and home it looped and I cant get out of it. This TWRP method that you mention what version of TWRP should I dl and please someone help soon my phone is out of commission.

rjmxtech said:
Hi all,
I recently figured out how to get an LG E980 back to a usable state after being stuck in a recovery loop due to a user or random system error from the PhilZ Touch Recovery (CWM/TWRP combo) and put CyanogenMod on it instead of having to flash back to stock.....the following link is directed to a zip file with a read me inside of it along with some files that have been modified to work with the recovery I have included in the zip file.
------HERE IS THE ZIP FOLLOW THE README INSIDE IT OR RISK BRICKING YOUR DEVICE------
******I am not responsible for anything that may happen to your device while following this guide, before following it, and after following it.......by downloading the zip file and following the steps you take all responsibility for anything that may possibly happen to your device at any time before, after, or while following this guide!!!!!!!!!!!!!!!!!!!!!!******
Click to expand...
Click to collapse
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.

droidbrain said:
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
did the flashing take a few seconds? are the files you are flashing on the SD card? if the answer is yes to both, you need to move the files you want to flash to the internal storage, then flash them. Personally i prefer CWM to flash and go back to TWRP if i ever get stuck on a recovery bootloop(reboot to system, fix root when prompted).

I did fix that issue without his files.
droidbrain said:
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app

fosunite said:
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app
Click to expand...
Click to collapse
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.

droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app

droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik

fosunite said:
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
ricco333 said:
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik
Click to expand...
Click to collapse
That is exactly what I did. Only boots into twrp.

droidbrain said:
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
That is exactly what I did. Only boots into twrp.
Click to expand...
Click to collapse
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik

ricco333 said:
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik
Click to expand...
Click to collapse
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.

droidbrain said:
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.
Click to expand...
Click to collapse
What I would do in your case is restore back to stock using LG Flash Tools and then start over with FreeGee and install the recovery from there and see if your trouble clears.
Erik

Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app

fosunite said:
Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
How do I do that?

droidbrain said:
How do I do that?
Click to expand...
Click to collapse
Better is that u should read this topic on the OP in the following link:
http://forum.xda-developers.com/showthread.php?p=44983841
[Guide][Stock Roms] Return Back To Stock AT&T & International
Sent from my LG-E988 using XDA Free mobile app

[ROOT] N5206 v150108 - v150312 root method with working wireless

Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.

Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.

Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?

Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.

Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.

Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?

It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.

Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.

Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?

Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.

Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.

Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/

cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip

You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk

can this root work with Chines n5207

Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...

I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...

YUreka PLUS ROOTED!

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.

failed to flash ob 10 and can only boot into recovery now

Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.

Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.

You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?

zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).

SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.

After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .

zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.

I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.

Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.

Did you manage to fix it? I have the same probem.