Database Users

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.

Aospa rom 6.0.1

it's finally released for our z3c!!!
http://get.aospa.co/official/aries
I believe need to unlock bootloader first before flashing so take note.

AWESOME!!! Thanks for the information!

Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

juliopw said:
Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
Click to expand...
Click to collapse
I actually have no idea what to do. I'm on a locked bootloader and I have never unlocked and flashed a custom rom on my z3c.
Was just, sharing some info and hoping people would test

matthiastan5 said:
it's finally released for our z3c!!!
http://get.aospa.co/official/aries
I believe need to unlock bootloader first before flashing so take note.
Click to expand...
Click to collapse
Thanks for info.

For anyone who already running this rom, how is it? Does the baseband and camera work (no fisheye effect)?

Arch9 said:
For anyone who already running this rom, how is it? Does the baseband and camera work (no fisheye effect)?
Click to expand...
Click to collapse
Neither one nor the other. All other things seems working fine.

juliopw said:
Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
View attachment 3786599
Click to expand...
Click to collapse
I get the same error 7 when trying to install PA. Ive tried modefying the install-script as you did but then i get error 6.
I flashed stock D5803_23.5.A.0.575_R11D_Nordic Generic_1288-5411.ftf and then flashed recovery to TWRP via fastboot but i still get the same error 7 when trying PA after that.
My next attempt is to install that NUT dual recovery and try flash PA after that.

Camera and modem not working

Got it installed (finally...). You need a working TWRP recovery.
What's working:
- WiFi
- Paranoid OTA seems to work; no further build available to try (doubt that it will work without recovery though; see below)
Not working:
- RIL (so no phone or SMS)
- camera
BT and GPS not tested yet.
To be able to flash you need to
- modify updater-script located in META-INF/com/google/android/updater-script (which is actually a text file) of the ROM zip
- open it in a text editor
- replace "aries" with "z3c", save it somewhere (delete .txt if it's saved with this extension; filename must be "updater-script")
- open the zip with 7zip (recommended; dunno if it works with other archivers)
- replace the updater-script with your version in the zip
- place the zip onto your device
- enter recovery
- Factory Reset (no need for a full wipe)
- flash it
- flash MM Gapps directly afterwards (OpenGapps not recommended - use Slim Zero Gapps instead)
- if you want root, flash SuperSU BEFORE rebooting (see below)
Recovery will be lost and can't be installed with TWRP Manager or Rashr after flashing (Didn't work for me - please report if you got it working and if so - how. Maybe with fastboot, didn't try that yet)
Happy flashing...
I'm sure issues will be fixed quite fast in later builds as everything works already in latest Carbon ROM (find it on testing.myself5.de). Maybe @Myself5 can help with that...(?).

juliopw said:
Camera and modem not working
View attachment 3786769View attachment 3786770View attachment 3786771View attachment 3786772
Click to expand...
Click to collapse
I flashed and it's same with you.It's not okay for daily driver.Also it overheats a lot.

Nice, they said they already fixed the mobile radio bug internally and will be releasing a new build soon

radio is fixed and currently fixing camera

From PA's official Google+ post:
We are also announcing that with the help of Sony and their Open Devices Project we will be able to support all 22 Xperia devices on the SonyXperiaDev GitHub Instance. This initial Sony release is for the Shinano family, but the Rhine, Yukon and Kitakami platforms are expected to follow shortly. This is really exciting news for us and it allows us to give you the Android experience we all love on a much wider range of devices.
Click to expand...
Click to collapse
If this is the case, maybe the camera will actually be usable? What do you think guys?
P.S. We should contact a moderator to move this thread to General forums, this is not development.

where is the zip file ?

ultraaslan88 said:
where is the zip file ?
Click to expand...
Click to collapse
It's removed for the meantime
That's because it had so many bugs
Wait for some more days for a better build

Anyone have mirror for last version?

Can i flash this rom on my z3c with SliMM 1.9?

GabrielVacker said:
Can i flash this rom on my z3c with SliMM 1.9?
Click to expand...
Click to collapse
You need unlocked bootloader for this

dont Found file
Wysyłane z Compacta za pomocą Tapatalk 2

Galaxy S4 Play Edition (GT-I9505G) and Lineage OS 15.1

Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.

Did you check the updater script to ensure the phone's model # is included?

audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.

fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.

audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.

I guess the only other thing would be to try different versions of TWRP.

audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.

Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.

audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.

Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.

audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.

To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.

audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?

The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.

audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I have EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?

There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.

It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.

audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.

Finally Android pie

I followed this guy's post so I'm just going to link his directions over here
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here
https://drive.google.com/file/d/1Wth0N14bKM1WM2VGXdJN91fPBXzdnsCQ/view?usp=drivesdk
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet

bugs
dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
There are following bugs on honor 7x:
1. Hotspot not working.
2. Usb connecetion to pc is charge only can use to transfer files.
Also the camera has too much noice.
there maybe more but these are all that I finded.

itsnikhilkadyan said:
There are following bugs on honor 7x:
1. Hotspot not working.
2. Usb connecetion to pc is charge only can use to transfer files.
Also the camera has too much noice.
there maybe more but these are all that I finded.
Click to expand...
Click to collapse
USB does work you have to enable under developer settings also and the pie nav bar works enable it in gesture

camera
dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
Is the Camera functional?

zagingi said:
Is the Camera functional?
Click to expand...
Click to collapse
it is very functional, if you mean by the stock aosp cam.

i saw a video on youtube like 5 days ago ... i hesitated posting because i couldn't verify if it's really the 7x or not but it appeared that he was running pie
Great news

How does honor view 10 roms runs in Honor 7x?

dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
VOLTE working ?

karti16 said:
How does honor view 10 roms runs in Honor 7x?
Click to expand...
Click to collapse
I don't know but I'm using like a secondary and honestly it's the best rom I used I think so far I really like the havoc os because I play mc5 and to me that one ran the game the best but this honor view 9 pie is running exceptionally well and it plays the game great I can't wait for pie to be optimized for the honor because it's gonna be perfect

I need to unlock bootloader. Got any working gcam? Honor 7x camera is showing unrealistic colour.

is VoLTE working ?

can not install always saying error 7 and that the Rom is not for my device...

Hi new to this phone and flashed rros from the openkirin site using just fastboot so have a couple questions about installing this ROM. First question is the link to the recovery isn't even for a honor 7x but guessing that doesn't matter anymore on a treble enabled phone and do you flash it to the ramdisk? Then after you do get it flashed do you install the ROM as a zip or do you extract it to install as a image? Thanks for the help guys kinda crazy thinking you will have twrp and stock recovery on a phone

dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
the 2 drive links you posted are broke, they are being broken with "..." "drive.google.com/drive/folde...fY?usp=sharing" "drive.google.com/open?id=18u...QgwleMIOjsZd7S"

please use the quote function...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wrong place to ask this question
MOD EDIT

darkmage1991 said:
the 2 drive links you posted are broke, they are being broken with "..." "drive.google.com/drive/folde...fY?usp=sharing" "drive.google.com/open?id=18u...QgwleMIOjsZd7S"
Click to expand...
Click to collapse
I'll reupload now it's this guy @crayonicle being wierd ASF like how many more times you want me to @crayonicle you damn @crayonicle

BigDiqSeitz said:
can not install always saying error 7 and that the Rom is not for my device...
Click to expand...
Click to collapse
I reuploaded the one with that check remove should flash through now

dcraffam said:
I'll reupload now it's this guy @crayonicle being wierd ASF like how many more times you want me to @crayonicle you damn @crayonicle
Click to expand...
Click to collapse
hahahaha you just want more number counts in your thanks meter so you can be "cool"
please delete your spams, it's getting annoying, i am the one who originally posted it, what right do you have to come and take it for your own?

crayonicle said:
hahahaha you just want more number counts in your thanks meter so you can be "cool"
please delete your spams, it's getting annoying, i am the one who originally posted it, what right do you have to come and take it for your own?
Click to expand...
Click to collapse
Really. So like ........
.

Bricked my Realme 2 PRO

Hi,
So I unlocked the bootloader, installed the official twrp 3.2.30 available on this thread. These are the things I did
1. Wipe>format data>Typed "Yes"
2. Swipe to factory reset
3. Flashed a GSI ROM (PE ROM) It didn't boot
4. Flashed "disable-encryption -RMX1801.zip" and booted again but same result
5. Flashed another GSI rom (AOSP EXTENDED) It showed up the logo but was loading forever
6. Tried another GSI rom but it doesn't even show logo basically same Realme bootloop
*** I did take a twrp backup BACKUP> SYSTEM, VENDOR, DATA,BOOT, RECOVERY, EFS" (Just in case) I don't remember whether I took this backup before "formatting data or after that.
Now,
1. I can restore TWRP back up but it doesn't boot same problem.
2. I tried installing 3 different gsi 9.0 roms but no result.
3. I download the stock realme 2 pro firmware but don't really know how to flash it with some type of pc recovery.
How do I get back to stock? Or be able to boot any rom which is available right now?? There are only GSI ROMs but no regular roms otherwise I could have flashed it.
Any help wold be appreciated.
UPDATE: THIS IS IMPORTANT (SOLUTION) So after fiddling with every other possible alternative, I solved this by simply installing the twrp by anabhi and main thing is "boot+magisk+patch.img" so after installing both of these, I again try restoring the twrp backup and simply installed flashed the "boot+magisk+pagth.img" after that it booted fine. So my guess was right that I needed a file something similar to "lazy flasher" for Xiaomi devices which I was missing. I tried flashing that official twrp along with "disable_encryption_RMX1801.IMG" in the same above process but it doesn't work.
So finally I booted back into Color OS and now I'm going to try and flash a gsi image and try again.
I would like to thank all of you guys who quickly replied and tried to help which is the best part I love about XDA. YOU GUYS ARE AWESOME and you inspire me to type and spend some good time typing and helping others as well. Cheers!!

bad news is that there is no official tool to flash stock rom yet but you can go to oppo service center and get it flashed stock rom for free.

Thetpcguy said:
Hi,
So I unlocked the bootloader, installed the official twrp 3.2.30 available on this thread. These are the things I did
1. Wipe>format data>Typed "Yes"
2. Swipe to factory reset
3. Flashed a GSI ROM (PE ROM) It didn't boot
4. Flashed "disable-encryption -RMX1801.zip" and booted again but same result
5. Flashed another GSI rom (AOSP EXTENDED) It showed up the logo but was loading forever
6. Tried another GSI rom but it doesn't even show logo basically same Realme bootloop
*** I did take a twrp backup BACKUP> SYSTEM, VENDOR, DATA,BOOT, RECOVERY, EFS" (Just in case) I don't remember whether I took this backup before "formatting data or after that.
Now,
1. I can restore TWRP back up but it doesn't boot same problem.
2. I tried installing 3 different gsi 9.0 roms but no result.
3. I download the stock realme 2 pro firmware but don't really know how to flash it with some type of pc recovery.
How do I get back to stock? Or be able to boot any rom which is available right now?? There are only GSI ROMs but no regular roms otherwise I could have flashed it.
Any help wold be appreciated.
Click to expand...
Click to collapse
maybe the same problem. https://forum.xda-developers.com/realme-2-pro/help/please-help-restore-t3893602 I got a good answer, even though I had never tried it because I went to the service center before getting an answer

Zaibuluk said:
maybe the same problem. https://forum.xda-developers.com/realme-2-pro/help/please-help-restore-t3893602 I got a good answer, even though I had never tried it because I went to the service center before getting an answer
Click to expand...
Click to collapse
Hi, Thanks a lot for your reply!!
Are you saying that the service centre guys can fix this? I mean flash stock rom? Because I unlocked bootloader and flashed twrp recovery. I formatted data and all. Do you think they have the tool to put stock rom again??

prince1995 said:
bad news is that there is no official tool to flash stock rom yet but you can go to oppo service center and get it flashed stock rom for free.
Click to expand...
Click to collapse
Hi, Thanks for the fast response. Do you really think they can put back stock rom? If they have such a tool to restore stock rom then why wouldn't they already release it to general public? I'm not really hopeful that they have such tool to actually put back the stock rom. I know they have lot of proprietary stuff but can you confirm this?

Zaibuluk said:
maybe the same problem. https://forum.xda-developers.com/realme-2-pro/help/please-help-restore-t3893602 I got a good answer, even though I had never tried it because I went to the service center before getting an answer
Click to expand...
Click to collapse
I forgot to ask, How many days or how much time did they take to flash stock rom? And Btw which region or place you are from if don't mind me asking?

Thetpcguy said:
I forgot to ask, How many days or how much time did they take to flash stock rom? And Btw which region or place you are from if don't mind me asking?
Click to expand...
Click to collapse
Your phone can be flashed with the Stock ROM at the service center. It would take a 1 day at the most, but, most definitely less than that if they have the OS at hand with them.
My suggestion would be that you could wait till the full Kernel Source is released and official ROMs are released for the RM2Pro and flash those ROMs. It's the safer alternative.

Thetpcguy said:
Hi, Thanks a lot for your reply!!
Are you saying that the service centre guys can fix this? I mean flash stock rom? Because I unlocked bootloader and flashed twrp recovery. I formatted data and all. Do you think they have the tool to put stock rom again??
Click to expand...
Click to collapse
Thetpcguy said:
Hi, Thanks for the fast response. Do you really think they can put back stock rom? If they have such a tool to restore stock rom then why wouldn't they already release it to general public? I'm not really hopeful that they have such tool to actually put back the stock rom. I know they have lot of proprietary stuff but can you confirm this?
Click to expand...
Click to collapse
Thetpcguy said:
I forgot to ask, How many days or how much time did they take to flash stock rom? And Btw which region or place you are from if don't mind me asking?
Click to expand...
Click to collapse
Your questions are quite meaningful there are 2 types of bricking hard brick & soft brick.
soft brick can be fixed by flashing some other roms or using official rom flasher.
hard brick can be fixed using a hardware called as JTAG which will be done by formatting the whole emmc storage as well as using some electrodes to reset the motherboard.
if you are having 4/6gb ram version then no problem but i doubt it for 8gb variant
but still as promised by realme bootloader unlocking rooting wont void your warranty it wont take more than 1-2 days to fix
so dont worry rush to nearest service center now:fingers-crossed:
if i was helpfull hit the thanks button please:good: btw i am from india, odisha, bhubaneswar

prince1995 said:
Your questions are quite meaningful there are 2 types of bricking hard brick & soft brick.
soft brick can be fixed by flashing some other roms or using official rom flasher.
hard brick can be fixed using a hardware called as JTAG which will be done by formatting the whole emmc storage as well as using some electrodes to reset the motherboard.
if you are having 4/6gb ram version then no problem but i doubt it for 8gb variant
but still as promised by realme bootloader unlocking rooting wont void your warranty it wont take more than 1-2 days to fix
so dont worry rush to nearest service center now:fingers-crossed:
if i was helpfull hit the thanks button please:good: btw i am from india, odisha, bhubaneswar
Click to expand...
Click to collapse
Hi, Thanks for the reply again.
I would like to correct one thing that rooting does void warranty. Realme only said that flashing custom roms/ unlocking bootloader is allowed under warranty but not rooting. BTW I didn't root it. I just unlocked, flashed twrp and tried flashing custom rom which didn't work so I ended up here.
Mine is 4gb/64 variant and it's a soft brick because the fastboot is working, twrp is also installed. The twrp restore or custom rom flashing is also going well without any errors but only unable to boot into system as it gets in the boot loop.
Yeah, the last resort would be to visit service centre but here the service is normally slow and most of them don't understand such things.
Anyway looking for a solution right here. I'm guessing that something is blocking the device from booting. I even saw bootlogo of GSI ROMs. I don't know it could be some encryption thing? or May be when I formatted the data, the vendor partition is wiped as well which is important for us to install GSI IMAGE.
But still why wouldn't the TWRP restore boot up properly??

Thetpcguy said:
Hi, Thanks for the fast response. Do you really think they can put back stock rom? If they have such a tool to restore stock rom then why wouldn't they already release it to general public? I'm not really hopeful that they have such tool to actually put back the stock rom. I know they have lot of proprietary stuff but can you confirm this?
Click to expand...
Click to collapse
actually I can flash it if I only know the Msmdownloadtool pass (the OFP extension is really new to me). I tried using Qfil and failed, when my cellphone was totally dead there wasn't even a logo for charging the battery when I tried it. which gave me hope, the detection of HS-USB QDLoader 9008 in Qfil. I am sure the service center can fix it because it is still detected by the computer, I said my cellphone suddenly died! finally they flashed again and in less than an hour. now twrp already installed magisk is installed just waiting for development :Hai:Hai

Thetpcguy said:
Hi, Thanks for the reply again.
I would like to correct one thing that rooting does void warranty. Realme only said that flashing custom roms/ unlocking bootloader is allowed under warranty but not rooting. BTW I didn't root it. I just unlocked, flashed twrp and tried flashing custom rom which didn't work so I ended up here.
Mine is 4gb/64 variant and it's a soft brick because the fastboot is working, twrp is also installed. The twrp restore or custom rom flashing is also going well without any errors but only unable to boot into system as it gets in the boot loop.
Yeah, the last resort would be to visit service centre but here the service is normally slow and most of them don't understand such things.
Anyway looking for a solution right here. I'm guessing that something is blocking the device from booting. I even saw bootlogo of GSI ROMs. I don't know it could be some encryption thing? or May be when I formatted the data, the vendor partition is wiped as well which is important for us to install GSI IMAGE.
But still why wouldn't the TWRP restore boot up properly??
Click to expand...
Click to collapse
I will look into this issue & comeup with something. mean while i think customer care is the best bet i hope they will reset it within a day.
i would suggest you try to wipe everything even internal storage put the rom on a sdcard/OTG & flash it from there.
the same kind issue arrised with my moto g(1st gen) this occurred because the device needed to be rooted already to flash some custom rom properly but mine wasn't hence i did get bootloop.

Stok recovery lazım

So, can you please give some time to this unbricking thing and provide a better solution with links. specially with that "boot+magisk+patch.img" part. It'd be really helpful. Thanks

Bro how can I fix this problem
Bro how can I fix this problem it's not booting it's give me a error the current image boot /recovery have been destroyed can not boot bro please help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Please help
Bricked my realme 2 pro after flashing twrp.img and boot.img. After that I also tried r2x2 reacovery. But no effect. It stuck in logo. Please suggest any way

I unlocked the bootloader of my Rear 2 pro 4/64. And installed twrp but after the installation I'm stuck with a bootlppo. What can I do now pls help!!!?

I got the same problem before with my realme 2 rmx1809...the easiest way to flash stock rom is to flash stock recovery.img first and then flash ozip file from official realme website...to get the stock recovery.img is to decrypt and extract ozip file using the ozip decryptor that are available on github

Bootloop stuck please help asap!!
I was trying to install custom rom but I didn't took back up and wiped every thing on internal memory and also flashed stock recovery of realme 2 pro LOCKED the bootloader also I was hoping that I would be able to install stock rom by realme . But now am stuck at bootloop only realme logo appers
Basically I only have stock recovery on my phone and nothing else in the internal no OS installed bootloader is also locked so am not able to install twrp recovery to please help me install any rom .I am stucked due to lockdown no Service center is open. Please help asap??? I can't leave without my phone in this lockdown