Hello guys i could really need some help right now.
So i installed OxygenOS 3 Beta and yesterday i wantet to boot in recovery (twrp 2.8.x.x.) but it didnt work so i googled today and found out that you cant boot in twrp when you install OOS 3.
As solution i found a "firstaid" post for the problem ( http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967/page8#post66326903 ) i hope the link will work
So after i ran the firstaid.bat like it is described in the readme.text my OP2 is stook in a bootloop and i still cant enter the Recovery....
I hope somebody can help me because i cant find a solution in the web. ty to all of you
Bomber293 said:
Hello guys i could really need some help right now.
So i installed OxygenOS 3 Beta and yesterday i wantet to boot in recovery (twrp 2.8.x.x.) but it didnt work so i googled today and found out that you cant boot in twrp when you install OOS 3.
As solution i found a "firstaid" post for the problem ( http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967/page8#post66326903 ) i hope the link will work
So after i ran the firstaid.bat like it is described in the readme.text my OP2 is stook in a bootloop and i still cant enter the Recovery....
I hope somebody can help me because i cant find a solution in the web. ty to all of you
Click to expand...
Click to collapse
i was in a similar situation last week,i couldnt boot into recovery though i could use my phone normally.only thing that i could access was fastboot mode. after a lot of online googling this thing fixed my phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
method 3 worked for me...but remember YOU WILL LOOSE ALL YOUR DATA ON PHONE..and restores the phone to factory condution..hope this info helped
Bomber293 said:
Hello guys i could really need some help right now.
So i installed OxygenOS 3 Beta and yesterday i wantet to boot in recovery (twrp 2.8.x.x.) but it didnt work so i googled today and found out that you cant boot in twrp when you install OOS 3.
As solution i found a "firstaid" post for the problem ( http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967/page8#post66326903 ) i hope the link will work
So after i ran the firstaid.bat like it is described in the readme.text my OP2 is stook in a bootloop and i still cant enter the Recovery....
I hope somebody can help me because i cant find a solution in the web. ty to all of you
Click to expand...
Click to collapse
try flashing this recovery: https://www.androidfilehost.com/?fid=24459283995297945
worked for me
unbelievable!!! a small link solved it all
:highfive:
flo071 said:
try flashing this recovery: https://www.androidfilehost.com/?fid=24459283995297945
worked for me
Click to expand...
Click to collapse
Related
Please help needed!!
I'm stuck here for 3 days
Ok I'm going to tell everything I did,,
My Gionee E7 is indian version.
First I rooted my phone with kingo Root.
Than I flashed CWM chinese version.
I upgraded my system to kitkat and changed the recovery to stock.
I used it for a week than some how my music player and gallery were corrupted.
I don't have any rom so I download one but it was in chinese, flashed it to my gionee. than after rooting,,
I flashed the CWM, same I flashed weeks ago
Here my problem started :crying:
The CWM is not starting. I used recoery tool to boot into recovery after boot up it shows black screen. I used every method holding Vol+ and power button but the same result.
than I tired to get back to my stock recovery but it does the same.
flashed many times both recoveries but didn't worked.
I searched a lot and find a TWRP. I flashed it and wow it worked Finally I can boot into recoery mode.
Now I find the Nandroid backup of indian version. I made it a zip and flashed it through twrp.
My phone is back to indian version but its slow, not too much but its slow; camera, gallery and other apps take some time to open. I can't make or rcv phone calls. Now what i did is download the update form System update.
Now i got kitkat rom.zip but twrp failed to install it.
Some one on the internet was saying that its the problem with my Kernel. I have the latest kernel so CWM won't work cuz it uses old kernel and display drivers.
My
android version is 4.2.2
Kernel version is 3.4.0-svn2155
I also got TWRP for lolipop,
and I patched binary_update in my kitkat rom too but TWRP can't flash it
Thats my whooooolllleeeee story. "
I got stuck with this for almost 3 days now I'm damn tired can't do it anymore plz help :crying::crying::crying:
I figured it out by myself
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:
AkashX4686 said:
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:
Click to expand...
Click to collapse
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?
No its not, it is working on 64bit windows very well.
In TWRP factory reset and format system and data, than install
Chinese 4.2 ROM. After that boot it and try it again.
It should work!
bllkarv said:
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?
Click to expand...
Click to collapse
For me...problem!
thereĀ“s a cwm recovery that flashes over the kernel...
i flashed it and than i was unable to go to recovery, every time i tried the phone power off
Solution: Flash the stock boot.img
Use the file according to the Android version...
Help
I just rooted my gionee elife e7. Flashed the chinese recovery which seemed to be the only one which would be compatible. But, while changing a few setting using pimp my rom, the software just stopped working. Errors keep showing up on the screen - "system.ui is not working", "android app is not working", I cannot even go the settings because "settings is not working". Third party apps still seem to work, so, whatsap and stuff continue to function. Doing a factory reset or flashing firmware again seem to be the only viable option.
But, when I try to load up the bootloader using the power and volume keys, it gets stuck on the screen showing the gionee logo and it reads 'fastboot mode' in the bottom left hand side corner. So,
a. can you offer any advice which may be useful ?
b. can you share the link from where you got a TWRP recovery which will work on the Elife ?
c. do you have any idea what exactly went wrong here ?
Any help you can provide will be appreciated because, it's my mausi's phone and I will have a very tough time explaining what really went down here.
Regards,
Hello everyone, I bought a week the OnePlus 2 from the official website, I would like to install the CM13, I tried in every way to flash the recovery mode, but nothing happens, I unlocked the bootloader, tells me the overwrite process He has been successful, but the recovery is always that of the parent. Does anyone have a solution to this problem? Thank you
Then main thing is that you can't boot OOS or hydrogenos after installing TWRP, or else they will replace the recovery back to stock.
pitrus- said:
Then main thing is that you can't boot OOS or hydrogenos after installing TWRP, or else they will replace the recovery back to stock.
Click to expand...
Click to collapse
I realized then how I should proceed after flashing the recovery mode?
kenny72 said:
Hello everyone, I bought a week the OnePlus 2 from the official website, I would like to install the CM13, I tried in every way to flash the recovery mode, but nothing happens, I unlocked the bootloader, tells me the overwrite process He has been successful, but the recovery is always that of the parent. Does anyone have a solution to this problem? Thank you
Click to expand...
Click to collapse
Follow this: https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/
You can use OOS after flashing TWRP (Hybrid TWRP).
Please read the guide in the official CM13 thread, this has been answered to many times already.
pitrus- said:
Please read the guide in the official CM13 thread, this has been answered to many times already.
Click to expand...
Click to collapse
Tanks All!! Solved
You should notice that :
1.twrp 3.0.2.1 [ Latest ] is for O2OS/H2OS beta version ( Marshmallow firmware)
2.twrp 3.0.2.0 is for O2OS/H2OS stable version ( Lollipop firmware)
make sure the firmware version matches your recovery
Too late to post this ... ha!
Hello xda developers this is my second thread sorry for the first one that i made yesterday, I am having a problem with my lenovo k4 note a7010a48
after rooting successfully I proceed to flash rr 7.1.2 but did not flash the gapps now my problem is how to go back on recovery mode to start over again
I already used the power button followed by the volume up down buttons but it is not working like before it is nougat. I only need to get to recovery mode. Please help and thankyou in advance. More power
Does u have root access now and which version of rr u flashed
yes the phone is rooted already and flashed with rr 7.1.2 only need to open recovery mode which is I have no idea
Contact in telegram app 9032015333 I will tell u
i dont know that or how to do that can you teach me please thank you
I have the same issue. Can't enter into recovery and the phone is unable to start.
Same Issue || Don't Know How To Fix
Hi,
I am searching for a possible solution from a day. But could not find a working solution.
After successfully flashing RR-N-5.8.5 (Android N)
Unable to go into recovery.
PROBLEM DESCRIPTION:
1. When Press Vol Up + Vol Down + Power Up
2. Recovery is not loading up
3. Instead it goes in boot loop
4. Normal boot mode and fast boot mode are working perfectly fine
SOLUTIONS TRIED:
1. Flashing recovery again using fastboot mode
2. Flashing different recovery, i.e updated version of recovery
As all recoveries which were available were for marshmallow version. I am not sure but have doubt as android version is updated so the kernel so do recovery also become obsolete in this case ?
Any help is welcome and appreciated
Thanks
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
for fastboot mode and for recovery mode yes i tried it also but thats the problem no recovery mode. I will wait for the solution when it comes i will just store my phone for a while.
Hi Developers,
Is it possible to reset the phone at hardware level? I can't even connect the phone to PC as it keeps on rebooting.
Please note: upgraded to Nougat and wanted to do the second recovery as suggested by mohancm in the post. When the phone rebooted (before flashing the second recovery), the problem started.
Please let me know if any one has a fix/workaround for the issue.
Thanks,
Srihari
1.Download TWRP recovery unzip files.
https://drive.google.com/file/d/0B1CKVcdcbHFPUzFCODVMN0ZfTW8/view
2.Now in folder TWRP\img\ there is the file recovery.img.
3.Download the second recovery for nougat recovery-Nougat.img and put in the TWRP\img folder.
https://androidfilehost.com/?fid=673368273298981920
4.Rename it as the original, recovery.img and replace it.
5.Then connect your phone to usb and select the 3th option from usb debugging message
"Transfer photos(ptp)"
6.run TWRP_Install.bat from TWRP folder
And you are done, had the same problem and I figure this solution, hope it will help.
I cannot locate the transfer photos(ptp)
ok I already done the part I am now on the recovery mode thanks. new problem of mine is after flashing the rom gapps and recovery after reboot it goes back to recovery mode did I miss something on flashing?
ok so i already passed this problem thanks for the help xda community thank you very much but I have this bootloop problem maybe I did a mistake flashing before rebooting sorry i am a noob in this kind of upgrade specially in mobile phones. I will be careful next time after I passed this problem I hope you will help me once again, my phone in bootloop is killing me.
I have same issue... I flashed gapps and my phone is working smoothly... The issue is i can't go into recovery mode... I tried some one tap reboot to recovery apps but all whats happening is phone restarting normally.
For those who can't access recovery mode. You were supposed to flash updated recovery image after flashing rrn rom.
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Should work.
Worst case, restore by flashing stock rom using SP flash tools. And then start all over again.
If you face any issues ping me. Even I had faced this issue and fixed it after a lot of struggle. I can try to help you.
Or you could download Official Twrp App directly from play store, then find A3000 (Air Row) in 'select device' and flash that to recovery, (if your phone is rooted) then you are good to go, go to recovery mode and thats all, your twrp is now has been flashed.
Thank me later??
MisledMew said:
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Click to expand...
Click to collapse
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
firelmnt said:
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
Click to expand...
Click to collapse
Glad it helped
Hi, I'm in a sticky situation
I downloaded a custom recovery (revolution custom recovery) and wanted to install lineage 14.1 on my phone. I installed everything properly and still my phone doesn't get past the startup animation. After that I thought it was because of the recovery so I installed I TWRP (which should be compatible) through the existing recovery. And now. I'm stuck between loading screens and don't know what to do. I managed to get to the erecovery of EMUI and charged up my phone. Since I don't want to break anything else I'm asking for help.
Change data partition to ext4.
How yo recover
Flash sotck EMUI rom from consumer.huawei.com using 3 buttons method. You'll be able yo use your phone, but I think Google services doesn't work (in my case) so try again yo flash lineageOS. Good luck
yazzine said:
Hi, I'm in a sticky situation .........
.......... Since I don't want to break anything else I'm asking for help.
Click to expand...
Click to collapse
Hello dude, ok you got L31 model phone, but, except for Revolution recovery,
you did not give any more info about the firmware you had before flash custom recovery.
Neither info you wrote about lineageOS and other TWRP you tried to flash.
No one can help you without these basically info, so post here...
Best Regards
From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !
Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number
I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!
Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse
Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.
finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed
Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well