<removed>
I think Moto Moto don't like us
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
gregory678 said:
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
Click to expand...
Click to collapse
Propably you patch wrong boot image, try to extract from your device stock
tys0n said:
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
Click to expand...
Click to collapse
It's not universal path so i BOLD the path to change
[email protected] said:
It's not universal path so i BOLD the path to change
Click to expand...
Click to collapse
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
tys0n said:
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
Click to expand...
Click to collapse
Edited
[email protected] said:
Propably you patch wrong boot image, try to extract from your device stock
Click to expand...
Click to collapse
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
It should work. I've patched boot after every update without problems.
XT1941-4
Sent from my moto one
[email protected] said:
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
Click to expand...
Click to collapse
I would like to, but is there some way of backing up stock ROM? I know that current version of TWRP has some issues with /data partition, that's why I ask .
And what about installing this ROM? Would I need to use that TWRP we have now? Is it safe?
tys0n said:
It should work. I've patched boot after every update without problems.
XT1941-4
Click to expand...
Click to collapse
Well, you have different software channel, I think that's the only reason why it works for you and it doesn't work for me . OPENEU seems to be bulletproof. (I have XT1941-4 too)
Someone correct me if I'm wrong, maybe for someone with OPENEU it does work.
I Request close due to failures
Related
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
A lot of post are about being 5.x.x and can't access recovery mode but I am on 4.5.3 and I have flashed TWRP before on this firmware. I used the CM-11 rom and realized it's only Android 4.4.4 and needed Android 5.x.x well i flashed back to stock fire os and the stock firmware still 4.5.3
MY problem:
When i boot into recovery mode it just shows "Amazon" and reboots back to stock OS, I have root and flashify it just won't boot into recovery. Any help?
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
detesto said:
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
Click to expand...
Click to collapse
What version of FireOS?
If you're on 4.X root it and flash a working recovery with dd.
Rortiz2 said:
What version of FireOS?
If you're on 4.X root it and flash a working recovery with dd.
Click to expand...
Click to collapse
I'm on 5.6.1.0, I've found no way to root without recovery.
detesto said:
I'm on 5.6.1.0, I've found no way to root without recovery.
Click to expand...
Click to collapse
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Rortiz2 said:
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Click to expand...
Click to collapse
Not without recovery, all the guides require to flash an update via adb on recovery
detesto said:
Not without recovery, all the guides require to flash an update via adb on recovery
Click to expand...
Click to collapse
Sorry for the late reply.
There's ONE solution.. It's not easy...
You can flash recovery with aftv-tools but IDK the recovery adress. Maybe @bibikalka can help us?
detesto said:
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
Click to expand...
Click to collapse
detesto said:
I'm on 5.6.1.0, I've found no way to root without recovery.
Click to expand...
Click to collapse
Rortiz2 said:
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Click to expand...
Click to collapse
detesto said:
Not without recovery, all the guides require to flash an update via adb on recovery
Click to expand...
Click to collapse
Rortiz2 said:
Sorry for the late reply.
There's ONE solution.. It's not easy...
You can flash recovery with aftv-tools but IDK the recovery adress. Maybe @bibikalka can help us?
Click to expand...
Click to collapse
Unfortunately, the aftv-tools were patched a while ago, sneaky Amazon updated boot0 on firehd 2014 via some hidden data in either LK or TEE1. So that method won't work.
So without a recovery or root there are really no options.
Now, there is always the path to trigger the BootRom mode via some contacts (as on other models), but nobody spent the time yet to figure that out:
https://forum.xda-developers.com/fire-hd/general/diy-fire-hd-6-7-bootloader-unlock-t3894996
Pinging @k4y0z and @xyz` for completeness.
bibikalka said:
Unfortunately, the aftv-tools were patched a while ago, sneaky Amazon updated boot0 on firehd 2014 via some hidden data in either LK or TEE1. So that method won't work.
So without a recovery or root there are really no options.
Now, there is always the path to trigger the BootRom mode via some contacts (as on other models), but nobody spent the time yet to figure that out:
https://forum.xda-developers.com/fire-hd/general/diy-fire-hd-6-7-bootloader-unlock-t3894996
Pinging @k4y0z and @xyz` for completeness.
Click to expand...
Click to collapse
Dang. So there's no pic of the board? For see what points can be..
Rortiz2 said:
Dang. So there's no pic of the board? For see what points can be..
Click to expand...
Click to collapse
Plenty of good pics:
https://forum.xda-developers.com/fire-hd/help/jtag-t2933430
Also, one user tried to find the contacts, but was not successful. xyz' indicated where he thought the contacts might be:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
bibikalka said:
Plenty of good pics:
https://forum.xda-developers.com/fire-hd/help/jtag-t2933430
Also, one user tried to find the contacts, but was not successful. xyz' indicated where he thought the contacts might be:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Click to expand...
Click to collapse
Nice pics. Maybe with root you can easy brick it an enter to bootROM mode no?
Code:
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/dev/zero of=/dev/block/mmcblk0boot0
echo 'EMMC_BOOT' > /dev/block/mmcblk0boot0
md5sum /dev/block/mmcblk0boot0
Rortiz2 said:
Nice pics. Maybe with root you can easy brick it an enter to bootROM mode no?
Code:
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/dev/zero of=/dev/block/mmcblk0boot0
echo 'EMMC_BOOT' > /dev/block/mmcblk0boot0
md5sum /dev/block/mmcblk0boot0
Click to expand...
Click to collapse
But if I have root already, why would I mess with Bootrom??? I don't have amonet for this device, so I would essentially brick a working tablet
bibikalka said:
But if I have root already, why would I mess with Bootrom??? I don't have amonet for this device, so I would essentially brick a working tablet
Click to expand...
Click to collapse
Yep, you're right.. It needs to be ported to MT8135 and it qould be difficult... The only user that knows how to do it is @k4y0z.
He needs the tablet for test it.
reedradar said:
A lot of post are about being 5.x.x and can't access recovery mode but I am on 4.5.3 and I have flashed TWRP before on this firmware. I used the CM-11 rom and realized it's only Android 4.4.4 and needed Android 5.x.x well i flashed back to stock fire os and the stock firmware still 4.5.3
MY problem:
When i boot into recovery mode it just shows "Amazon" and reboots back to stock OS, I have root and flashify it just won't boot into recovery. Any help?
Click to expand...
Click to collapse
I managed to get the stock Amazon recovery on to the fire tablet on 5.6.10 using EX Kernel Manager and from there could sideload the OS i needed to get back in to TWRP.
My phone is an Honor View 10 model BKL-L04 (American model) build 8.1.0.133 (C567GT).
These are the steps that I used to remove the stock firmware and recovery and replace them with something more to my taste. I did < 1% of the actual work here, I'm just putting everything that I did in once place so that other people may not have to look so hard to find answers.
Requirements
View 10 - If you don't have one then you're in the wrong place. Do NOT follow these directions for any other phone as both the directions and the links are specific to the model mentioned above.
Cash/PayPal - Most of us don't have the skills to pry out the bootloader unlock code ourselves so we must pay someone who does. God knows the manufacturer isn't going to help us out here
SD Card - You can probably get this done purely on internal storage, but weren't you going to put in a nice, big SD card anyway?
SD Card Writer (optional) - You'll need a way to load files onto the card prior to flashing. IMHO getting an SD card writer is the simplest way, but to each their own.
Unlocking
This guy will get you an unlock code for your View 10 for $22 (USD). Order a Bootloader Unlock Code, select the Huawei option "with IMEI", put BOTH of your IMEI numbers in the comments field, submit it and pay via PayPal. I got a code in about an hour. Once you have the code you can follow these directions to perform the unlocking process. If you need a bit more help getting though it then try this guide.
Flash Recovery
Don't use the official TWRP images. As of Dec 8, 2018 neither 3.2.1-0 nor 3.2.1.-1 worked for me (-0 dropped to fastboot after a few seconds and -1 caused a bootloop when entering recovery). Use the latest unofficial image from this page. Directions included. More detailed directions can be found here but make sure to use the TWRP image from the first link.
Copy Zips
Now pick out a ROM (I went with LineageOS 15.1) and copy all the zips you need to your SD card. The list probably includes the ROM itself, gapps, and some type of su/root package. Put them all on your card.
Flash ROM
If you're going with LIneageOS 15.1 as I did then this guide should get you the rest of the way. It has the links for the ROM itself as well as gapps and the su package. Again, be very careful to match exactly your phone model and architecture (arm64 for the View 10) when grabbing these packages.
Extras
You can find the latest stock firmware image for the BKL-L04 here. Be damn sure your phone matches mine before you use it! If you need to pull out the stock recovery for any reason, you can use the update extractor to do this (grab recovery_ramdisk), then flash it the same way you flash TWRP.
Good luck and have fun! I'll try to help if you get stuck but the real knowledgeable people are those that wrote the articles I've linked to.
Cheers!
- E
Is "twrp_bkl_0.7.img" the latest one?
As of Dec 9 I believe it is, yes.
Eimafn said:
As of Dec 9 I believe it is, yes.
Click to expand...
Click to collapse
It installed but it keeps saying unable to unmount system so I can't backup or flash a new rom.
MikeyJay530 said:
It installed but it keeps saying unable to unmount system so I can't backup or flash a new rom.
Click to expand...
Click to collapse
I didn't have that issue when I was first flashing the ROM, but I do now. If you're having it prior to flashing your ROM would it be because you didn't wipe & format beforehand? The guide I linked in step 5 leads you through this procedure if you need it.
As far as the unmounting error, I think that's something we'll have to live with until the issue is corrected in TWRP.
- E
Eimafn said:
I didn't have that issue when I was first flashing the ROM, but I do now. If you're having it prior to flashing your ROM would it be because you didn't wipe & format beforehand? The guide I linked in step 5 leads you through this procedure if you need it.
As far as the unmounting error, I think that's something we'll have to live with until the issue is corrected in TWRP.
- E
Click to expand...
Click to collapse
Then how can I flash a custom rom?
MikeyJay530 said:
Then how can I flash a custom rom?
Click to expand...
Click to collapse
I think it works if you wipe/format first. The guide I linked walks you through this.
Eimafn said:
I think it works if you wipe/format first. The guide I linked walks you through this.
Click to expand...
Click to collapse
I did wipe/format first lol still messed up
MikeyJay530 said:
I did wipe/format first lol still messed up
Click to expand...
Click to collapse
Hmm. Well, you can either try one of the official builds (here) or wait for the guy doing our customized build to fix this issue. You might even post a note on this thread describing your issue so that he can track how many people are having it.
Sorry I couldn't be more help. The View 10 is not the easiest phone to work with by a long shot.
- E
MikeyJay530 said:
I did wipe/format first lol still messed up
Click to expand...
Click to collapse
You should do it from emui settings not from twrp .
miststudent2011 said:
You should do it from emui settings not from twrp .
Click to expand...
Click to collapse
What do you mean?
MikeyJay530 said:
What do you mean?
Click to expand...
Click to collapse
You have told that you have formatted your device, if you have formatted it from twrp it will cause issues, you should format it from emui system settings.
miststudent2011 said:
You have told that you have formatted your device, if you have formatted it from twrp it will cause issues, you should format it from emui system settings.
Click to expand...
Click to collapse
No I need to do it in TWRP if I want to install a custom rom...lol
MikeyJay530 said:
No I need to do it in TWRP if I want to install a custom rom...lol
Click to expand...
Click to collapse
Seriously you are laughing at me for trying to help you ?
I need to do it in TWRP if I want to install a custom rom --> Where did you get it ?
Currently available TWRP are buggy and are causing issues.
miststudent2011 said:
Seriously you are laughing at me for trying to help you ?
I need to do it in TWRP if I want to install a custom rom --> Where did you get it ?
Currently available TWRP are buggy and are causing issues.
Click to expand...
Click to collapse
Noooo I'm laughing because I'm confused lol I got the twrp from the link on this thread.
MikeyJay530 said:
Noooo I'm laughing because I'm confused lol I got the twrp from the link on this thread.
Click to expand...
Click to collapse
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
miststudent2011 said:
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
Click to expand...
Click to collapse
I'm wanting to flash Pixel Experience though.
---------- Post added at 08:21 AM ---------- Previous post was at 08:06 AM ----------
miststudent2011 said:
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
Click to expand...
Click to collapse
Also, how do I get TWRP off my phone so I have EMUI recovery back?
MikeyJay530 said:
I'm wanting to flash Pixel Experience though.
---------- Post added at 08:21 AM ---------- Previous post was at 08:06 AM ----------
Also, how do I get TWRP off my phone so I have EMUI recovery back?
Click to expand...
Click to collapse
Download full firmware package from firmware finder and extract recovery from update.app and flash it ,
BTW what is your current phone state ?
miststudent2011 said:
Download full firmware package from firmware finder and extract recovery from update.app and flash it ,
BTW what is your current phone state ?
Click to expand...
Click to collapse
Is there a guide for that? Sorry I'm new with this phone. My phone is unlocked.
MikeyJay530 said:
Is there a guide for that? Sorry I'm new with this phone. My phone is unlocked.
Click to expand...
Click to collapse
What is your phone current state, you have just flashed only twrp or any other changes ?
did you format your phone through emui settings before flashing twrp ?
what build are you on currently ?
Hello everyone, I have recently flashed new custom ROM on my device - Realme 7 rmx 2151 and everything went as planned. I used unlocking and flashing guide new from XDA webpage... I flashed PixelPlus UI3.9 from here, XDA ... I was really loooking forward to try new things etc... and do not know where I messed up but can not turn ON Wi-Fi and BLUETOOTH. Please any advice ? Thank you in advance...
Could be a problem with the rom,try to flash evolution x to see if that works
Ok. thank you for advice, I will do that within a next two hours. lets try...
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Try restoring the persist partition.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Were you on a.87 before flashing the ROM?
SubwayChamp said:
Try restoring the persist partition.
Click to expand...
Click to collapse
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
OrthodoxOxygen said:
Were you on a.87 before flashing the ROM?
Click to expand...
Click to collapse
Not sure buddy, but honestly can say either 87 or 91....
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
OrthodoxOxygen said:
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
Click to expand...
Click to collapse
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
SubwayChamp said:
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
Click to expand...
Click to collapse
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
RobertoSt25 said:
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
Click to expand...
Click to collapse
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
RobertoSt25 said:
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
Click to expand...
Click to collapse
You don't need to uy a new one. You just need to reflash the correct firmware, and then reflash the ROM you're trying to use after that.
SubwayChamp said:
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
Click to expand...
Click to collapse
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
alright I will do that, what would you recon, how to flash it ? I mean the best and the easiest way to do that...? Thank you very much.
RobertoSt25 said:
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
Click to expand...
Click to collapse
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
SubwayChamp said:
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
Click to expand...
Click to collapse
lovely, you are No,1, I will do that exactly the way you described. Thank you very much for that.
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
RobertoSt25 said:
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
Click to expand...
Click to collapse
You just need to flash a.87 back onto your device. Did you need to follow an elaborate guide to unlock your phone's bootloader, or did you just submit an application via the DeepTest APK? I need to know this in order to link you the correct files to flash.
BEWARE
Has this changed, or is it still unsafe? I'm just getting back to checking on on rooting the GN2200 and I am on the C.11 update currently.
DemonLoader said:
Has this changed, or is it still unsafe? I'm just getting back to checking on on rooting the GN2200 and I am on the C.11 update currently.
Click to expand...
Click to collapse
I tried rooting c11 and I ended up bricked.
Could you make a rom backup of your device so i can un brick un mine
If you can guide me in the current set of utilities, I certainly can. I just don't stay that current until I'm ready to utilize, is all.
Im learning now
You have to be rooted to backup the firmware
I would never try to root a newer phone if it didn't support custom recovery like TWRP in-case something goes south.
immortalwon said:
I would never try to root a newer phone if it didn't support custom recovery like TWRP in-case something goes south.
Click to expand...
Click to collapse
There is custom recovery for this device. Buts its tricky to get it installed. The guide was deleted when the forum police banned scarlet wizard who wrote the guide
Have you tried installing KernelSU, and simply booting from fastboot in order to get your backups? Then once you have them, you can play with rooting again? I just learned of KernelSU this year, and I think it's a remarkable tool for getting our backups before flashing anything.
bricklife4me said:
BEWARE
Click to expand...
Click to collapse
def works flash this magisk patched A12 boot!
A12 C.11 magisk patched boot (working ON (GN2200) ONLY!!!!)
halloweenm925 said:
def works flash this magisk patched A12 boot!
A12 C.11 magisk patched boot (working ON (GN2200) ONLY!!!!)
Click to expand...
Click to collapse
Ya i got rooted too. I don't know what happen the first time
bricklife4me said:
Ya i got rooted too. I don't know what happen the first time
Click to expand...
Click to collapse
Do you just flash the boot img, or is there some thing else aso?
yacopsae said:
Do you just flash the boot img, or is there some thing else aso?
Click to expand...
Click to collapse
Fastboot flash boot <patches boot.img>
I dont need to disable dm-verity or anything? I just want to make sure before I try to flash a patched boot.img
Why remember them?
Damn they band Scarlet for real?
Use the script in the other thread
CoryBlaze said:
Damn they band Scarlet for real?
Click to expand...
Click to collapse
Yes they bannned my original account
mobile_sensei said:
Why remember them?
Click to expand...
Click to collapse
Cause that was a very fun forum
bricklife4me said:
Use the script in the other thread
Yes they bannned my original account
Click to expand...
Click to collapse
You still alive, how would I flash my IMEI back I lost it during the brick, but used your guide to restore my brick but IMEI is on back of the phone my carrier suspended my account because I didn't have the IMEI do you know how permanent add back