It's been three years since i changed phones and I naively thought that things had gotten easier.
But nope. Still a mess of stiching together various incomplete "guides" from around the web only
to end up with a phone stuck in a boot-loop.
It's a Galaxy S9. Using Odin I've been able to install TWRP 3.3.1-0.
With that I tried installing both Carbon ROM as well as Havoc OS each followed by Open Gapps 8.
In some of the "guides" there was mentions of no-verity, so I've tried adding that in various steps.
Still, the only thing that works reliably is power+bixby+up to enter twrp. It's the only way I've found
to power down the phone.
Very grateful for any suggestion.
I've thought about installing the ROM using Odin, but I'm afraid that I would lose twrp.
From TWRP boot into download mode and use Odin to flash stock.
Or download soldier ROM and flash that in TWRP. It's based on stock ROM.
basicreece said:
From TWRP boot into download mode and use Odin to flash stock.
Or download soldier ROM and flash that in TWRP. It's based on stock ROM.
Click to expand...
Click to collapse
Thanks for taking the time to reply - I appreciate it!
Just to be suuuper clear: Should I flash the ROM the same way as I did twrp? Option AP and F. Reset time?
And why stock ROM? That's where I came from. Ultimately I want a custom ROM (preferably Carbon or Havoc).
Is this a step towards that?
Sam Sunk said:
Thanks for taking the time to reply - I appreciate it!
Just to be suuuper clear: Should I flash the ROM the same way as I did twrp? Option AP and F. Reset time?
And why stock ROM? That's where I came from. Ultimately I want a custom ROM (preferably Carbon or Havoc).
Is this a step towards that?
Click to expand...
Click to collapse
Flashing stock will return your phone to the way it was when you bought it, having to flash TWRP etc all over again
When flashing stock you flash all 4 sections together and do not change any settings in Odin
CSC = Reset phone
HOME CSC = Do not reset
Only use one or the other
You will need to use CSC if you have TWRP / Custom installed
If you are wanting a custom ROM flashed from TWRP you should wait for someone else who knows why it won't flash to help you as I have just kept stock on my S9 so don't know what's wrong
You do know you flash the custom ROM zip using TWRP right? Copying it to your SD card then choosing it from TWRP itself, not using Odin
*Detection* said:
You do know you flash the custom ROM zip using TWRP right? Copying it to your SD card then choosing it from TWRP itself, not using Odin
Click to expand...
Click to collapse
That's exactly what I did. I used Odin to install twrp and then tried to install the custom ROM with twrp. That's when the wheels came off and the phone got stuck booting.
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Sam Sunk said:
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Click to expand...
Click to collapse
Then you should follow the guides on this XDA S9 forum instead, then you know they are for the S9
Sam Sunk said:
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Click to expand...
Click to collapse
you still bricked?
In TWRP did the internal storage maybe say 0mb? Tat happens when you dont abort the factory reset after OEM unlock. If it is that than just go to advanced wipe, pormat your data to fat2 and then back to fat4
Hey there, I had the exact same problem over the past 2 days - so I feel your frustration.
I have a 9604f (galaxy s9) , and there are different types so you may have to see if yours is different. I also used ressurrection remix OS. Short version is:
1. Get resurrection remix (final version for starlte)
2. Get gapps (for 8.1 arm64)
3. Get magisk
The above 3 are all on the post for the official resurrection remix on this site with the header -[ROM] [OFFICIAL] [6/01/18] ResurrectionRemix 6.0 for S9/S9+ (Exynos)
4. Download the BRE5 vendor. I used a link that went to a mega.nz site and it worked. So I'm sure you'll be able to find one. I can't post links cause this is my first post.
5. Boot into twrp
6. Format data in wipe section of twrp
7. Wipe dalvik, cache, data, system.
8. Install in this order -do not reboot or wipe anything. Just install.
(I) BRE5 vendor
(II) resurrection remix ROM
(III) gapps
9. DONT WIPE cache, and reboot into the OS
10. If you want root -just go back into twrp once you have set up google, apps etc. And then install the magisk zip.
update
Not bricked any more.
The advice from @basicreece to install soldier worked. I made a second attempt to install Carbon afterwards but that resulted again in a twrp-only device. Now I'm back on soldier.
Perhaps I'll give @Madsikhey's instructions a go later.
To show my gratitude for all the help in times of darkness I'd like to give back and I'll let @basicreece decide:
1. Donation to XDA
2. Donation to EFF
3. A beer/coffee for yourself (PayPal)
Answer me in a PM.
Madsikhey said:
Hey there, I had the exact same problem over the past 2 days - so I feel your frustration.
I have a 9604f (galaxy s9) , and there are different types so you may have to see if yours is different. I also used ressurrection remix OS. Short version is:
1. Get resurrection remix (final version for starlte)
2. Get gapps (for 8.1 arm64)
3. Get magisk
The above 3 are all on the post for the official resurrection remix on this site with the header -[ROM] [OFFICIAL] [6/01/18] ResurrectionRemix 6.0 for S9/S9+ (Exynos)
4. Download the BRE5 vendor. I used a link that went to a mega.nz site and it worked. So I'm sure you'll be able to find one. I can't post links cause this is my first post.
5. Boot into twrp
6. Format data in wipe section of twrp
7. Wipe dalvik, cache, data, system.
8. Install in this order -do not reboot or wipe anything. Just install.
(I) BRE5 vendor
(II) resurrection remix ROM
(III) gapps
9. DONT WIPE cache, and reboot into the OS
10. If you want root -just go back into twrp once you have set up google, apps etc. And then install the magisk zip.
Click to expand...
Click to collapse
Hello, Iám also having the same problem. I got all the files needed but the BRE5 Vendor file, could anyone link it plz? Iám using a G960F (S9).
Haxomen said:
In TWRP did the internal storage maybe say 0mb? Tat happens when you dont abort the factory reset after OEM unlock. If it is that than just go to advanced wipe, pormat your data to fat2 and then back to fat4
Click to expand...
Click to collapse
Thanks :good::good::good:
I have somewhat same problem. Rooted my S9 original OS and it worked fine. After power off the phone is in bootloop and the only way to shut the phone off is to boot in the twrp and reboot-->shut off.
And the only way to get to the twrp is power+volume up+bixby button combination.
I made a thread about my problem, it's here
Problems with rooting Galaxy S9 (Android 10 Exynos SM-G960F)
Hi, this is My first post here, so be gentle. My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine. Yesterday I decided to root it (there are a few features that need root and I...
forum.xda-developers.com
Now I'm stuck and I need a help to proceed. What i should do to get the phone open again? Would it be a good idea to flash lineageOS now, or is there a way to reset the phone back to original?
I can open trwp or download mode, but cannot boot to the OS.
Related
Hey guys. I'm going crazy for days. I tried to root my T805 and something went wrong. After rooting and after the reboot there appeared many many error massages like "Google service stopped" or "android..... stopped". You can't really skip them because they are coming over and over and over. After some time it rebootes by itself and voila same issue... makes it unuseable. So right here nothing special I thought. Just flash the stock rom over it with odin and you will be fine. But whatever kind of rom or firmware I tried to flash I'm getting the same issues. Plus after every flash I got stuck at the Samsung logo incl. some vibrations in intervals. So when I get stucked (over 20 min) I have to force shutdown it and yeah it starts and hello error messages.
I rooted and flashed so many smartphones and tabs and I've never seen a problem like that. Please oh please try to help me. Probably I'll donate you some dollars for the perfect hint or solution, I'm really desperate.
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
mihailrusia said:
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
Click to expand...
Click to collapse
Yes. Every time I'm flashing I wipe befor and after it. And after I tried LineageOS the same happend with the error messages . But now after flashed stock ROM again it seems now that I'm totaly stuck at the Samsung logo. Even when I try to reboot and reflash I get stucked at the logo with these vibrations.
Thanks for your reply.
Ok now I'm not stucked at the logo but get the error messages again...
Are you flashing the last firmware and system and data are on ext4?
mihailrusia said:
Are you flashing the last firmware and system and data are on ext4?
Click to expand...
Click to collapse
Yes I'm flashing the latest. About the filesystem... I'm not sure. Where can I look at the filesystem? In Recovery? What I reached in the last houres: I flashed LineageOS again WITHOUT Opengapps. And boom ist startet pretty well but yea now I have no google playstore and such stuff. Now I'll try to flash the opengapps stock over the ROM using the TWPR.
Edit: I looked at the filesystem, it's ext4
You can view the partitions with DiskInfo
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=es
Install the pico gapps
So now I flashed opengapps stock again and I'm now stucked again in at the Samsung logo. I have to hard reboot now and yeah I think there will be the error messages. But I'll try the Pico version of opengapps like you said.
Edit: I didn't have to hard reboot it. It booted by itself after some minutes but yea with the errors. After some errors it shutsdown and reboot... and so on.
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
mihailrusia said:
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
Click to expand...
Click to collapse
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Metero said:
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Click to expand...
Click to collapse
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
Thanks for searching. I'll try this next. (Give me some minutes )
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Metero said:
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Click to expand...
Click to collapse
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
thejase said:
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
Click to expand...
Click to collapse
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Metero said:
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Click to expand...
Click to collapse
Try using https://forum.xda-developers.com/ga...olkit-unified-android-toolkit-galaxy-t2998205
This should take you back to stock as if the tab was new. It has many many features, including rooting the tablet for you. It runs in windows ( hopefully you have). Habben Sie einen guten Tag! (is this right? I love German but I am just learning)
Hello dear friends,
I had been using some custom roms for a while like lineage os, cm, resurrection etc.Then i wanted to change it to a 4.4 rom.Once i flashed a stock rom by odin.Then i tired to use Eclipse.I have been using it without a problem.But now i want to upgrade the phone again.
-And i tried to flash different roms but i have the same problem.It passes SAMSUNG screen and shows ROM's flash.But it stucks in there.It keeps moving but nothing more.The rom doesn't start the homescreen.I tried to factory reset, wipe cache and dalvik cache.But they also doesn't work at all.I wait about half and hour or 1 hour, Once i tried to let it work overnight even.But doesn't work.Now i try to flash Cosmic OS but the problem still exists.I have a Eclipse rom backup and i restore it and it works.I use TWRP recovery on the phone.
-So what the problem might be?How can i fix it?
I recommend flashing back to the latest stock ROM, factory reset, and start over with TWRP.
audit13 said:
I recommend flashing back to the latest stock ROM, factory reset, and start over with TWRP.
Click to expand...
Click to collapse
Thank you it worked.I just want to explain the steps to give some information for the others who got the same problem.
-Connect the phone to the pc and flash a stock rom by odin or heimdall in linux
-Then wait for the rom to start.
-Open stock recovery mod (not TWRP or CWM Recovery)
-Format all data
-Flash a custom recovery (I use TWRP)
-And flash the custom rom as instructions.
And it works for me.Thank you again.
stranger_88 said:
Thank you it worked.I just want to explain the steps to give some information for the others who got the same problem.
-Connect the phone to the pc and flash a stock rom by odin or heimdall in linux
-Then wait for the rom to start.
-Open stock recovery mod (not TWRP or CWM Recovery)
-Format all data
-Flash a custom recovery (I use TWRP)
-And flash the custom rom as instructions.
And it works for me.Thank you again.
Click to expand...
Click to collapse
Glad you got it working.
Thanks for posting your method.
same problem
i'm gettin the same problem...
in download mode there are few lines as follows:
odin mode
prduct name:gt-n7100
current binary:Custom
System Status:Custom
knox warranty void: 1
AP SWREV: A2
PLSSS HELP
ShubhamS156 said:
i'm gettin the same problem...
in download mode there are few lines as follows:
odin mode
prduct name:gt-n7100
current binary:Custom
System Status:Custom
knox warranty void: 1
AP SWREV: A2
PLSSS HELP
Click to expand...
Click to collapse
Which rom you are using to flash?
Is the rom exactly for your phone model? (For eg, N7100 rom cannot be used for N7105)
thomas140 said:
Which rom you are using to flash?
Is the rom exactly for your phone model? (For eg, N7100 rom cannot be used for N7105)
Click to expand...
Click to collapse
Yep ...it's for N7100 only.... DotOs 7.1.2 by Santosh
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
stranger_88 said:
Hello dear friends,
I had been using some custom roms for a while like lineage os, cm, resurrection etc.Then i wanted to change it to a 4.4 rom.Once i flashed a stock rom by odin.Then i tired to use Eclipse.I have been using it without a problem.But now i want to upgrade the phone again.
-And i tried to flash different roms but i have the same problem.It passes SAMSUNG screen and shows ROM's flash.But it stucks in there.It keeps moving but nothing more.The rom doesn't start the homescreen.I tried to factory reset, wipe cache and dalvik cache.But they also doesn't work at all.I wait about half and hour or 1 hour, Once i tried to let it work overnight even.But doesn't work.Now i try to flash Cosmic OS but the problem still exists.I have a Eclipse rom backup and i restore it and it works.I use TWRP recovery on the phone.
-So what the problem might be?How can i fix it?
Click to expand...
Click to collapse
Stranger_88....try doing a complete advanced wipe using Twrp..and then install a rom
You said DotOS 7.1.2, it is custom rom and I think it needs to be install using TWRP. And also, need to perform wipe in TWRP before reboot. Otherwise, it will stuck at Samsung logo boot loop.
Solved
thomas140 said:
Which rom you are using to flash?
Is the rom exactly for your phone model? (For eg, N7100 rom cannot be used for N7105)
Click to expand...
Click to collapse
Dude I got it working. Use Heimdall in Linux , my phone was detected in Heimdall and I followed the simple instructions there and flashed a new rom.
I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.
We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...
Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!
You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"
ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me
I just find out that this rom https://forum.xda-developers.com/p8...m-lineageos-17-1-huawei-p8-lite-2017-t4064121 could be installed on our device wtih minor changes.After installing all things you will need to install stock recovery and wipe cache and try to do factory reset(i tried to but i got error massage) then you will successfully boot into rom
Contributors
@DarkJoker360
I can confirm that this works like a charm, here I posted the instructions for those who want to install it!
Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help ?
Momo745040 said:
Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help
Click to expand...
Click to collapse
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick
A big job ahead ?. I will try and I will tell you if it works thank you for your answer. One last question is there a way to keep a custom recovery because sometimes magisk's module causes a botloop (sorry for my bad English ?)
lucsi said:
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick
Click to expand...
Click to collapse
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk
Momo745040 said:
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk
Click to expand...
Click to collapse
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
Thanks you very much for your help!
I'll try this weekend (I don't have time in week).
I will come back to say if it worked
Has anyone tried these github projects to unlock the bootloader of his Honor (6X) or Huawei Device?
Maybe it is possible to accelerate these programs by using cuda cores on nvidia graphic card(s).
https://github.com/SkyEmie/huawei-ho...ock-bootloader
https://github.com/Martazza/Huawei-Bootloader-Unlocker
lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
I managed to find a compatible recovery but when I flashed everything and I did a factory reset from the erecovery the phone restarts and it displays the logo lineageOs for 5 seconds then it restarts and the screen remains black then it restarts and displays the logo then it restarts in erecovery telling me that the memory has been seriously damaged.
I think I will give up here([emoji28])but anyway thank you for your help [emoji106].
Envoyé de mon BLL-L22 en utilisant Tapatalk
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
Click to expand...
Click to collapse
Have you followed all these instructions?
matyrock said:
How can there be such awesome people? It works in my Honor 6X! And it's fully de-googled man this is just perfect! Thank you very much for this...
These are the steps (thanks @DunoCZ) I followed if an Honor 6X user want to install this ROM:
- *Upgrade to EMUI 8!*
- *Remove the saved fingerprints and Google Accounts just in case*
- Flash the TWRP recovery from @Dil3mm4
- Format cache, dalvik cache, data and system: TWRP -> Wipe -> Advanced Wipe
- Flash the ROM via TWRP (you can try with fastboot but it already works with TWRP): TWRP -> Install -> Install Image
- Resize the system partition: TWRP -> Wipe -> Advanced Wipe -> System -> Resize (DO NOT FORMAT!)
- (Optional) Install GApps, Magisk
- (Required) Install patch
- Reboot and wait
Click to expand...
Click to collapse
D0ping said:
Have you followed all these instructions?
Click to expand...
Click to collapse
i did and the diffferent thing i did is to flash back stock recovery as mentioned by op, wipe the cache and then flash huaweitwrp.im provided by lusci
i edited my post above
Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Edit: Figured it out. apparently my gapps was somehow broken. Downloaded a fresh arm64-ogapps and all is working now
Darkitz said:
Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Click to expand...
Click to collapse
follow my guide here, this is how i managed to get it work, make sure you flash the rom with your CLEAN STOCK rom
Raxul said:
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse
Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse
Ok let me make it simple for you.
1. Flash stock Oreo Rom (no need to boot it)
2. Flash TWRP by Dilemma in fastboot.
3. Go to recovery and wipe data by typing yes to decrypt data partition (if not already decrypted)
4. Go to fastboot and flash system.img
5. Reboot to recovery and resize system partition
6. Flash GApps
7. Flash los patches zip
8. Flash disable Dm verity patch
9. Flash magisk-phh zip in the end.
10. Reboot and wait.
I used these steps to flash different GSIs/ROMs and it works perfectly.
I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20
victorgrey999 said:
I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20
Click to expand...
Click to collapse
You need to resize the partition
flash android10 arm 64
lucsi said:
You need to resize the partition
flash android10 arm 64
Click to expand...
Click to collapse
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?
victorgrey999 said:
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?
Click to expand...
Click to collapse
Mine is ok. battery backup is ok.
Antutu ~96K point
You can install kernel management app to tweak the CPU freq
Hey guys,
It's nice to see preloader is received and I installed first time when I find it. Currently when I press Power+Up, it will have a DOS-like menu for me to choose, It occured after I installed preloader. At his point, can I install TWRP and then root? Will this DOS-like menu be replaced after TWRP? After installing TWRP, do I need to wipe data etc? I have heaps of apps and games installed, and I try not to do so.
My andorid is 9 and Chinese+Global Rom
Thanks
idog8818 said:
Hey guys,
It's nice to see preloader is received and I installed first time when I find it. Currently when I press Power+Up, it will have a DOS-like menu for me to choose, It occured after I installed preloader. At his point, can I install TWRP and then root? Will this DOS-like menu be replaced after TWRP? After installing TWRP, do I need to wipe data etc? I have heaps of apps and games installed, and I try not to do so.
My andorid is 9 and Chinese+Global Rom
Thanks
Click to expand...
Click to collapse
For the rom to work the way it is supposed to, you have to wipe everything except sd card. So you can backup those apps to sdcard or not. I advise you wipe everything, because it might bring you problems if you don't wipe them.
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
soleali said:
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
Click to expand...
Click to collapse
What popular rom did you tried, for how much time and what bugs you ve encountered?
Im on Global Rom and it seems quite stable. Just want root but scare of hard-bricking, I had this before and paid $30 for online services.
soleali said:
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
Click to expand...
Click to collapse
Why don't you install official TWRP? Also after installing, when you boot up with power+UP, still have preloader menu, then choose recovery to enter TWRP?
idog8818 said:
Why don't you install official TWRP? Also after installing, when you boot up with power+UP, still have preloader menu, then choose recovery to enter TWRP?
Click to expand...
Click to collapse
At first I installed LR TWRP but couldn't boot into custom OS. Then I installed Orangefox and I was able to boot. Yes pre-loader was already there... I guess pre-loader goes away when you flash any official MIUI rom as this happened with me. After flashing the Indian ROM again I had to flash pre-loader and recovery files.
Raresh T said:
What popular rom did you tried, for how much time and what bugs you ve encountered?
Click to expand...
Click to collapse
Cesium OS. Overall its a good os, much stable and can be definitely used as a daily driver except for the fingerprint sensor issue. If you try to wake up device using fingerprint, it freezes and never displays the screen even when the power button is pressed. You have to restart the device to make it workable. Its a known bug.
soleali said:
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
Click to expand...
Click to collapse
What exactly I need to do after installing twrp and first time in it. I read other posts saying tip something and even format data etc.
idog8818 said:
What exactly I need to do after installing twrp and first time in it. I read other posts saying tip something and even format data etc.
Click to expand...
Click to collapse
Just install Magisk and load any custom os of your choice when you are done installing twrp. Remember, some roms require a specific version of recovery and Magisk installation also needs to be done carefully. Good Luck!
soleali said:
Just install Magisk and load any custom os of your choice when you are done installing twrp. Remember, some roms require a specific version of recovery and Magisk installation also needs to be done carefully. Good Luck!
Click to expand...
Click to collapse
I did this 2 months ago, after "just install Magisk" It's hard bricked, and $30 to ask for online service to unlock.
did anyone tried flashing treble roms on the phone ? perhaps they work a bit better.
idog8818 said:
I did this 2 months ago, after "just install Magisk" It's hard bricked, and $30 to ask for online service to unlock.
Click to expand...
Click to collapse
Oh. What about the pre-loader? Didn't you install it in the first place?
soleali said:
Oh. What about the pre-loader? Didn't you install it in the first place?
Click to expand...
Click to collapse
When I bought this phone, there was no pre-loader yet, and not much users know it's so easy to brick.
idog8818 said:
When I bought this phone, there was no pre-loader yet, and not much users know it's so easy to brick.
Click to expand...
Click to collapse
In a new phone there is no pre-loader installed.