Related
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
Hi,
I get TWRP running on phone , but when I boot into recovery , I always get the Standard Recovery, only option being a factory reset. Have opted for this factory reset and that is exactly what I get, no TWRP :crying:
Thanks
Also if you reboot to recovery through TWRP itself, it won't stick? If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
MickyFoley said:
If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
Click to expand...
Click to collapse
Thanks,
Yes rooting is where I want to go by means of TWRP and flashing these
Marshmallow custom kernel for root — Link | File: STOCK-20a-ROOTED.zip (16.5 MB)
Click to expand...
Click to collapse
I did have Twrp running on this phone but had to reinstall the full 6.00kdz to get out of a bootloop and since then TWRP won't sick.
thanks
More than one way to skin a cat. went HERE chainfire Systemless Root 2.61 using Running TWRP from PC
Update on getting TWRP to stick. ......... I had success using following
adb reboot bootloader
Click to expand...
Click to collapse
fastboot flash recovery twrp-2.8.7.0-h815.img
Click to expand...
Click to collapse
When done, execute “fastboot reboot”
Click to expand...
Click to collapse
This happened to me, too. Here is what i did:
Boot your device into fastboot mode via adb, straight up boot to recovery ("fastboot boot twrp-2.8.7.0-h815.img"), transfer the recovery image to your device, then flash it from within TWRP (there is an option for that within the normal install menu, its called "install image" or something like that). Hope this helps, it did for me.
Edit: Just realized you already found a solution. Never mind.
Ive the same problem. I unlocked the bootloader by the official procedure. Then i tried to flash twrp but it doesnt install truly. It always appear the stock recovery. I tried also clockrecovery but nothing. No recovery wants to get installed. Pls help me i want a custom rom on my g4
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery and then flash STOCK-20a-ROOTED
chester2011 said:
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery
Click to expand...
Click to collapse
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
setaf said:
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
Click to expand...
Click to collapse
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
chester2011 said:
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
Click to expand...
Click to collapse
Also u had problem with the 3.0 ? Ill update you later
setaf said:
Also u had problem with the 3.0 ? Ill update you later
Click to expand...
Click to collapse
yep.. but currently running with xposed and g4 tweaksbox (paid version) nicely
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
flash twrp version 3.0.2.0
setaf said:
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
Click to expand...
Click to collapse
you can upgrade twrp with the twrp manager from playstore (once youve got twrp and root of course)
Important: official TWRP does NOT backup the EFS partition correctly while this one does. Do NOT restore an EFS backup that you did not take on the same build of TWRP as the one you're currently using. You will lose IMEI
Get support here: https://discord.gg/UF9qnts
Same as official twrp but
Built with latest lineageOS trees
Built with latest kernel with ext4, f2fs, exfat and sdfat driver
Thanks a lot to @jcadduono for the exfat upstream
Undervolting
Supports signature verification for lineageOS official zips
Supports signature verification for haruhirom official zips
Built with GCC 8 for maximum speed
Support for backing up, restoring and flashing system image zips
Manifest: https://github.com/GlassROM-devices/platform_manifest_twrp_lineageos
Toolchain: https://bitbucket.org/anupritaisno1/aarch64-linux-gnu/overview
FPSUsername said:
You can flash a recovery using fastboot (
Code:
fastboot flash recovery recovery.img
).
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
anupritaisno1 said:
Also guys twrp can be flashed on locked bootloaders
If you are on a locked bootloader you must make sure that you ALWAYS flash twrp while booted into Android, using the dd command
Code:
dd if=recovery.img of=/dev/block/bootdevice/by-name/recovery
If you use the twrp flasher while on a locked bootloader you're just dumb
Click to expand...
Click to collapse
https://glassrom.pw/recovery.img
All sources (kernel source, device tree, etc) are bundled in the manifest. Please don't ask for separate sources just read the manifests
Just an FYI: official twrp builds are built by a bot, oneplus 2 doesn't have a twrp maintainer and nobody is reviewing the code that goes into twrp for our device
You really shouldn't use the official twrp builds
no comments, that means no issues. good job
Twrp 3.2.0 was released today so a new build for that is out
Please test and report bugs
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Sent from my OnePlus2 using XDA Labs
sanjeetkumar495 said:
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Click to expand...
Click to collapse
I did, it works.
sanjeetkumar495 said:
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot:
Code:
fastboot flash recovery recovery.img
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
FPSUsername said:
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot (
Code:
fastboot flash recovery recovery.img
).
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
Adding these to the main post
Also guys twrp can be flashed on locked bootloaders
If you are on a locked bootloader you must make sure that you ALWAYS flash twrp while booted into Android, using the dd command
Code:
dd if=recovery.img of=/dev/block/bootdevice/by-name/recovery
If you use the twrp flasher while on a locked bootloader you're just dumb
FPSUsername said:
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot:
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
sanjeetkumar495 said:
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Then use the locked bootloader method
sanjeetkumar495 said:
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Use Flashify.
Deleted
Sad to say but this twrp doesnt come close to the latest official. I experienced lag and slow rates.
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
sujju said:
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
Click to expand...
Click to collapse
If your phone is rooted, you might want to give flashfire or flashify a try.
erzherzog said:
If your phone is rooted, you might want to give flashfire or flashify a try.
Click to expand...
Click to collapse
It's not rooted..
sujju said:
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
Click to expand...
Click to collapse
You must patch the rom to provide SuperSU's binaries at boot with oxygenos recovery and a signed boot.img
After booting you have to flash twrp using dd
Instructions for doing so are in the haruhirom thread
This definitely isn't for beginners
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Could you share your twrp? Thanks!
Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?
mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work
mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option
mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.
aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
rendez2k said:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
Click to expand...
Click to collapse
If your phone boots back to bootloader on reboot, you did something wrong. Reflash system imgs and start over.
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
rendez2k said:
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
Click to expand...
Click to collapse
Yes. If you don't want your data wiped, open the install.bat file and take off the -w.
Did you unlock your bootloader correctly? Unlock critical? I believe the pixel 2 xl is the only phone where that has to be done.
Boot into bootloader and fastboot flash recovery.img again, once your in recovery, flash the recovery.zip from your storage again, then reboot recovery.... its happened to me, usually when I switch slots, all I have to do is reflash recovery.
Also note, If I am trying to boot at that point (rather than flash a ROM), I usually just flash the kernel and magisk and I'm good to go.
Thanks all! I flashed the patched boot.img again and it seems to be working OK
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
rendez2k said:
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
Click to expand...
Click to collapse
Yes you do loose twrp after flashing the boot.img. the reason being that stock recovery resides in the boot.img. So when you flash it, bye..bye twrp! Why not just fastboot twrp, then once in twrp, flash the twrp installer zip, then flash your custom kernel(if used) then flash the magisk zip for root. :good:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
rendez2k said:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
Click to expand...
Click to collapse
No. Flash kernel is just the kernel, the boot.img is from the factory image. Flash the zip version of Flash kernel in twrp, then flash magisk.zip :good:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
DON'T DO THAT! You'll bootloop for sure!! Do what the post below says, and what I told you earlier!
Pyr0x64 said:
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
Click to expand...
Click to collapse
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
rendez2k said:
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
Click to expand...
Click to collapse
There is no solution for that. Xposed always fails SafetyNet.
Is Xposed worth having these days? Are people still actively developing useful mods?
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I think it's worth it, for the following apps:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Fuse8499 said:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Click to expand...
Click to collapse
No problems with TWRP here. Maybe you are flashing to the wrong slot.
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I keep hoping Xposed will go die in a fire. It causes more problems than it solves, to the point ROM developers will tell you not to bother reporting issues with it installed. Rovo knows his stuff, but his creation has caused more damage to custom ROM development than Cyanogenmod did in its last three years.