I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
Related
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
steam374 said:
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
Click to expand...
Click to collapse
What is required for root work?
Root adds a binary file and some scripts to the /system partition
What happens when you flash a system.img?
Everything in the /system partition is wiped and replaced with the contents of the system.img
So, basically as long as I flash super su in twrp I'll be good to go?
steam374 said:
So, basically as long as I flash super su in twrp I'll be good to go?
Click to expand...
Click to collapse
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
danarama said:
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
Click to expand...
Click to collapse
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
steam374 said:
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
Click to expand...
Click to collapse
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
danarama said:
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
Click to expand...
Click to collapse
Okay! Thank you very much! This is the help I needed.
steam374 said:
Okay! Thank you very much! This is the help I needed.
Click to expand...
Click to collapse
No probs
danarama said:
No probs
Click to expand...
Click to collapse
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
steam374 said:
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
Click to expand...
Click to collapse
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
danarama said:
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
Click to expand...
Click to collapse
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
steam374 said:
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
Click to expand...
Click to collapse
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
danarama said:
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
Click to expand...
Click to collapse
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
steam374 said:
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
Click to expand...
Click to collapse
Hey, don't worry. We prefer "noob" questions to "noob-help-me-i-screwed-up" requests
Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
mrkhigh said:
Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Pkt_Lnt said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
mrkhigh said:
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
Click to expand...
Click to collapse
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Pkt_Lnt said:
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Click to expand...
Click to collapse
That's what I thought.
Thanks for the links,
But I'm still looking for TWRP flashable if anyone knows of one?
This should be a relatively easy thing so I'm surprised it doesn't exist
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
leo5111 said:
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
Click to expand...
Click to collapse
TWRP can flash a stock image if someone creates it. Unless there is something odd about the nexus, but I doubt that. The only thing that shouldn't be flashed stock would be recovery.
I don't think I need to use some toolkit... adb and fastboot commands are simple enough.
I was hoping to avoid needing a PC at another persons house, I mean that is kinda the point of twrp.
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
If I owned the device I would make it for you guys. It seems something that is lacking that is really handy.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Google has done that for you already. Just unpack the archive you choose and the four images are in there.
https://developers.google.com/android/images
I thought we've already decided I cannot flash these images with TWRP....
mrkhigh said:
I thought we've already decided I cannot flash these images with TWRP....
Click to expand...
Click to collapse
http://www.droidviews.com/now-flash-image-files-using-twrp-2-8-4-0/
Different Google search gave this. I can find nothing else on TWRP site or G+
Appears you can also use FlashFire.
Thanks for the help.
OP could flash one of the stock lite ROMs in the development forum and get the TWRP-flashable stock ROM he's looking for. Danvdh and tupac4u both offer one that is nothing more a debloated stock ROM.
TWRP is able to flash system images from 3.0.2 and on. Just unpack the archive and select install img. Remember to flash stock kernel and newest radio and bootloader too (bare in mind that flashable bootloader is harder to find. You might have to find older one and update the files inside on your own). Afterwards flash stock recovery and lock bootloader with a zip. Now you can just reboot it. It's not that hard.
Lawstorant said:
....bare in mind that flashable bootloader is harder to find....
Click to expand...
Click to collapse
For Nexus 6 https://forum.xda-developers.com/showthread.php?p=59728002/
Thank you.
I went ahead and simply flashed him 100% stock via flash and fastboot.
This is probably resolved now, just adding info though. I had flashed stock 7.1.1 zip downloaded from google via twrp 3.0.3.0. It removed twrp itself too and I was back on stock.
mrkhigh said:
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Click to expand...
Click to collapse
Try the app FlashFire.
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
First flash this file and then Rom. That's right?? Or its other way around
karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..
Wouldn't this procedure downgrade some performance on the device?
Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs
Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk
puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..
snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk
it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)
I went to codeworks page:
There are 4 files for the x522 in firmware and 4 in modems. I am assuming the "19s" firmware is for India so is the "20s" for the US?
But the 4 files in the modem section is confusing, which one/one's are for the US model x522? here is the link for the modems https://host.llamasweet.tech/codeworkx/lineage/s2/
Thanks
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
leo221 said:
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
Click to expand...
Click to collapse
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
veda1 said:
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
Click to expand...
Click to collapse
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
leo221 said:
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
Click to expand...
Click to collapse
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
veda1 said:
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
Click to expand...
Click to collapse
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now?
Click to expand...
Click to collapse
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
Click to expand...
Click to collapse
Yep its still happening. Tried to flash it right now and it says "can't read" error.
veda1 said:
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
Click to expand...
Click to collapse
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
leo221 said:
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
Click to expand...
Click to collapse
Updated script according to the video, still not flashing, says "cannot read error"
veda1 said:
Updated script according to the video, still not flashing, says "cannot read error"
Click to expand...
Click to collapse
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
leo221 said:
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
Click to expand...
Click to collapse
Unbelievable! It actually worked after the 2nd attempt. Even got the 21s update. Thanks :good:
The original question is still unanswered about which one is the correct firmware for the US model amng the firmware provided by codeworks, hopefully someone knows that and will share in interest of others that might have the same problem.
Thanks again @leo221 for providing a clear and easy solution.
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
I think yes, but I'm not sure
Was wondering the same thing, does anyone know if the red magic 3 is A only or an A/B device. I'm pretty sure it's A only, but I couldn't find any documentation online.
Its A only i think.
Hum... So Project Treble should work ?
That is interesting !
If I could install Resurrection Remix to this device and provided everything works it would become really almost perfect.
If anyone wants to try... If not I'll do it myself when I have time (in 2 or 3 days)...
Regards.
If the device has treble support, meaning a vendor partition it should work no problem, a/b partitioning is really not required for treble.
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
trepKep said:
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
Click to expand...
Click to collapse
So, this means its not working.. Sad Story.
florian-m19 said:
So, this means its not working.. Sad Story.
Click to expand...
Click to collapse
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
trepKep said:
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
Click to expand...
Click to collapse
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
em902566 said:
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
Click to expand...
Click to collapse
I'll keep that in mind
trepKep said:
I'll keep that in mind
Click to expand...
Click to collapse
Hey, did you try it again?
florian-m19 said:
Hey, did you try it again?
Click to expand...
Click to collapse
No, I was busy. But I'm trying right now
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
trepKep said:
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
Click to expand...
Click to collapse
Hmm then we must wait for a custom Rom..
florian-m19 said:
Hmm then we must wait for a custom Rom..
Click to expand...
Click to collapse
Yeah, a one plus 7 pro port would be nice
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Bryceicle1971 said:
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Click to expand...
Click to collapse
Many people have faced the issue and they have recovered their device. Look for all solutions available.
danishajaz said:
Many people have faced the issue and they have recovered their device. Look for all solutions available.
Click to expand...
Click to collapse
I have. 7 weeks an counting an no working cell yet. I bought an Mi9 an no issues with it. Easy to reinstall firmware. The red magic 3 is the most difficult to repair cell I have ever encountered. I wish they had something like miflashpro for it
Treble is working from chinese ROM with twrp make sure image is A/B because this device is A/B