This rom has been a mess but thankfully i found a solution to this with the help of @darkobas and rest xda members.
This has worked in my case so i am not 100% sure that it will work for sure for you guys nor do i take any responsibility for bricking devices.
This guide is for x720 so you will have to find the corresponding files for your 727 aswell.
So after installing JIU, you have a different bootloader and different radio files.
Here are the steps you have to do in order to restore your device at its former state.
1)Download 23s modified stock
https://mega.nz/#!YYtVBaYQ!jO4KnXNjUP7aM-oSlrSsQPgJTECmepYYuTZabjUThhg
2)Enter TWRP and Wipe everything(all partitions) including format. Reboot to recovery in order to fix errors.
3)Push The rom with mtp and install it.
This will restore your fastboot commands and bootloader.
4)https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Follow this guide. If fastboot format data doesnt work then try instead fastboot format userdata.
5) Reboot, and let it boot up (takes some time)
6) Flash TWRP, wipe everything and install ROM or restore your backup. Reboot.
7)Boot to fastboot and write these 2 commands.
fastboot erase modemst1
fastboot erase modemst2
I think that this can also be done after finishing with the fastboot flashing in step 4 but in my case i did it in the end so i am just writing it here.
In order to check your bands install Network Signal Guru, go to lock bands and then choose LTE.
FINAL NOTES:
BACKUP IMMEDIATELY your EFS partition to avoid this for future cases.
Never Install chinese junk that are not tested , NEVER. There are a lot of enthusiasts in flashing but you need to know when to stop.
Lesson learnt, i hope thats the case for everyone else in here.
I get the message that the partition table doesn't exist on both modem1 and modem2 .Since I have 727 would it be just fastboot erase modem?
What more do you have to loose ? Try it out and tell us the results.
Btw this is tested on 2 devices(x720) and it worked like a charm.
X720 is dual sim and x727 is single sim
testreaper said:
What more do you have to loose ? Try it out and tell us the results.
Btw this is tested on 2 devices(x720) and it worked like a charm.
Click to expand...
Click to collapse
Nope it's just as you wrote it.i misread it.Im still waiting to boot up.ive been on boot animation for a while.I may have to reboot and wipe again.
testreaper said:
What more do you have to loose ? Try it out and tell us the results.
Btw this is tested on 2 devices(x720) and it worked like a charm.
Click to expand...
Click to collapse
I've been having one heck of a time getting my device to boot.Ive redone the steps to make sure I done all right and am stuck on boot animation.Ive tried rebooting to recovery and wiping and still not booting.If it isn't one thing it's another lol.
---------- Post added at 12:12 PM ---------- Previous post was at 11:19 AM ----------
testreaper said:
This rom has been a mess but thankfully i found a solution to this with the help of @darkobas and rest xda members.
This has worked in my case so i am not 100% sure that it will work for sure for you guys nor do i take any responsibility for bricking devices.
This guide is for x720 so you will have to find the corresponding files for your 727 aswell.
So after installing JIU, you have a different bootloader and different radio files.
Here are the steps you have to do in order to restore your device at its former state.
1)Download 23s modified stock
https://mega.nz/#!YYtVBaYQ!jO4KnXNjUP7aM-oSlrSsQPgJTECmepYYuTZabjUThhg
2)Enter TWRP and Wipe everything(all partitions) including format. Reboot to recovery in order to fix errors.
3)Push The rom with mtp and install it.
This will restore your fastboot commands and bootloader.
4)https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Follow this guide. If fastboot format data doesnt work then try instead fastboot format userdata.
5) Reboot, and let it boot up (takes some time)
6) Flash TWRP, wipe everything and install ROM or restore your backup. Reboot.
7)Boot to fastboot and write these 2 commands.
fastboot erase modemst1
fastboot erase modemst2
I think that this can also be done after finishing with the fastboot flashing in step 4 but in my case i did it in the end so i am just writing it here.
In order to check your bands install Network Signal Guru, go to lock bands and then choose LTE.
FINAL NOTES:
BACKUP IMMEDIATELY your EFS partition to avoid this for future cases.
Never Install chinese junk that are not tested , NEVER. There are a lot of enthusiasts in flashing but you need to know when to stop.
Lesson learnt, i hope thats the case for everyone else in here.
Click to expand...
Click to collapse
I can't tell you how much I appreciate you and @darkobas
You two really saved a lot of our butts with this one.I am genuinely appreciative.Thank you.Ive got LTE again thanks to you two.Lesson learned. I've stuffed my kamikaze flashing urges way down deep lol.
I am glad it worked for you pal!
Happy and carefull flashing from now on!
testreaper said:
I am glad it worked for you pal!
Happy and carefull flashing from now on!
Click to expand...
Click to collapse
I usually am a careful person but for some unknown reason I threw caution to the wind in this instance.Ive learned a few valuable lessons here.
Lesson#1 NEVER flash ROMs not meant for your specific device unless it's been tested and dev gives all clear.
Lesson#2 Don't assume that just because you've been flashing since the old G1 days you know everything because chances are that you're horribly mistaken.
Lesson#3 See lessons 1 & 2 and beat them in to your head.
I appreciate y'all's help. Immensely.
What I did a few days ago, was making a full wipe (internal storage etc), repairing partitions, flashing BB72 rom, then moved to AICP and voilà.
Didn't need erase modemst1/2 commands. In my case that solved all the issues. Nevertheless this jubu rom is a mess...
Thes1ev said:
What I did a few days ago, was making a full wipe (internal storage etc), repairing partitions, flashing BB72 rom, then moved to AICP and voilà.
Didn't need erase modemst1/2 commands. In my case that solved all the issues. Nevertheless this jubu rom is a mess...
Click to expand...
Click to collapse
I tried what you did and it didn't work for me.Youre right though,that "Rom" is a mess.The thread was locked .And for good reason.It was giving people problems even the ones who's device it was specifically for.Lesson learned.
bob24260 said:
I tried what you did and it didn't work for me.Youre right though,that "Rom" is a mess.The thread was locked .And for good reason.It was giving people problems even the ones who's device it was specifically for.Lesson learned.
Click to expand...
Click to collapse
So you need erase commands in order to restore bands? Looks like some phones behaved in different ways. To make sure I have all necessary bands (e.g B20) , I locked them one by one in Network Signal Guru app.
Thes1ev said:
So you need erase commands in order to restore bands? Looks like some phones behaved in different ways. To make sure I have all necessary bands (e.g B20) , I locked them one by one in Network Signal Guru app.
Click to expand...
Click to collapse
I needed them for mine because the old baseband was sticking like glue.It worked out though.
bob24260 said:
I needed them for mine because the old baseband was sticking like glue.It worked out though.
Click to expand...
Click to collapse
I'm betting mine will need that too. Since I restored my stock firmware, and have twrp and fastboot playing nice again, would it be advisable to just erase modems and reflash the modem.img or should I do the whole process. I will if needed, that's ok, but I've already formatted and done stock flash then Purity ROM so it should all be right but the modem itself.
No need to reflash modems, just erase.
In reality this command doesnt really erase you modem, they are just cache partitions for the baseband so i advice to give it a try first before doing the process from fastboot.
GL!
edit; if you did the process with fastboot and you flashed your lex727 files i think you will be fine, if not it would be advisable to do that first. But give it a try first since it could work.
benjmiester said:
I'm betting mine will need that too. Since I restored my stock firmware, and have twrp and fastboot playing nice again, would it be advisable to just erase modems and reflash the modem.img or should I do the whole process. I will if needed, that's ok, but I've already formatted and done stock flash then Purity ROM so it should all be right but the modem itself.
Click to expand...
Click to collapse
I agree with @testreaper . Listen to him.Hes pretty smart when it comes to this .He saved a lot us with this.
testreaper said:
No need to reflash modems, just erase.
In reality this command doesnt really erase you modem, they are just cache partitions for the baseband so i advice to give it a try first before doing the process from fastboot.
GL!
edit; if you did the process with fastboot and you flashed your lex727 files i think you will be fine, if not it would be advisable to do that first. But give it a try first since it could work.
Click to expand...
Click to collapse
Thanks! Yeah it would be a shame to wipe everything and do all that if not needed, but if I end up having to, that's ok.
I'll give just the erase command a try.
Oh btw with my sim issue I had, I think it just needed me to take out an pop back in the sim. After I had flashed the x727 modem and it appeared to break sim detection I flashed that stock room and it still didn't work immediately.
I decided to pop out the sim and put it back in, nothing, but I rebooted and it was back. So if anyone has that issue try ejecting sim 1st before all that. It probably worked before and just needed a reset of sorts.
Just got around to trying this out. Just the erase command did the trick (well, after all of the other stuff I tried too).
LTE present and accounted for!
Since I moved to my new place, all of about 300 FEET from a cell tower, my signal has been so much better than my old place if anybody remembers the posts about weak signal and speeds. My old spot had a big metal parking roof right in front of it on the 1st floor. Basically was an anti signal shield.
benjmiester said:
Just got around to trying this out. Just the erase command did the trick (well, after all of the other stuff I tried too).
LTE present and accounted for!
Since I moved to my new place, all of about 300 FEET from a cell tower, my signal has been so much better than my old place if anybody remembers the posts about weak signal and speeds. My old spot had a big metal parking roof right in front of it on the 1st floor. Basically was an anti signal shield.
Click to expand...
Click to collapse
What carrier you have my dude? I got t-mobile and for it to be lte I'm getting pretty crappy performance (maximum of about 35 mbps and like 28 up) I'm rocking turbo v8 but planning to switch to mauro's or omni.
Mazupicua said:
What carrier you have my dude? I got t-mobile and for it to be lte I'm getting pretty crappy performance (maximum of about 35 mbps and like 28 up) I'm rocking turbo v8 but planning to switch to mauro's or omni.
Click to expand...
Click to collapse
I'm also on T-Mobile, in Dallas, TX. It could be just low signal areas. Before I moved where there's a cell tower about 300 feet away across the street, I was getting lower than yours. On this phone the signal meter can be pretty misleading. Try looking in settings > status > sim status and see what the -XX db number is. Lower (more negative) is better signal. I used to get upper -90s to well over -100s but now it's mid -70s to low -80s.
Where can I find the files for the X727 to do this? I tried "Beta 3" and it too wipes the bands and encrypts. Trying to get back to stock.
Edit: used the OP Rom for x720 to follow the guide then flashed x727 modem.
Related
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.bat WITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.bat WITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Anutter226 said:
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.batWITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.batWITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
I imagine it's overkill but you could just switch the active slot and run flash-all again. As a precaution I would recommend booting into the OS after the first flash-all to make sure it flashed ok. If there happens to be some problem like a bad flash or wrong download you want to be sure that the "other" slot is bootable. Otherwise you might end up with a pair of unbootable slots which could get sticky.
Anutter226 said:
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
then you saw that flash-all.bat flashed both slots
V40 said:
then you saw that flash-all.bat flashed both slots
Click to expand...
Click to collapse
Doesn't flash to both slots on mine
canemaxx said:
Doesn't flash to both slots on mine
Click to expand...
Click to collapse
I believe it flashes to one slot and deletes the data on the other as standard
If you guys would read your terminal output after flashing you would know what gets flashed where. People are making this way to complicated. It is a big change from previous devices but once you know the partitions its pretty easy.
One data slot shared by A + B
Slot A & B have separate partitions for
-Vendor
-Bootloader
-Radio
-Modem
-Boot
-System
Flashall.bat flashes your active slot and installs system_other.img to the inactive system partition and wipes data, unless you edit the flashall.bat and erase -w.
Thats it. Now, how people are handling the two slots is another story. I keep both slots identical. Having two different bootloaders is a recipe for bricks in my opinion.
FWIW, I endorse the post above this one. I would only add if you get in trouble flash all without the -w and then change the active slot and flash all without the-w again.
Golf c said:
Having two different bootloaders is a recipe for bricks in my opinion.
Click to expand...
Click to collapse
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
5.1 said:
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
Click to expand...
Click to collapse
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Golf c said:
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Click to expand...
Click to collapse
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
5.1 said:
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
Click to expand...
Click to collapse
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Golf c said:
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Click to expand...
Click to collapse
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
5.1 said:
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
Click to expand...
Click to collapse
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Golf c said:
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Click to expand...
Click to collapse
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
5.1 said:
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Click to expand...
Click to collapse
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Golf c said:
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Click to expand...
Click to collapse
Hey,
I did it just to show something to someone earlier. I don't need dual boot either...
One ROM is enough in my opinion.
Ok, time to hit the bed. See you later...
Cheers...
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
TonikJDK said:
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
Click to expand...
Click to collapse
And I don't even use it because I have never taken an OTA. lol!
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
canemaxx said:
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
Click to expand...
Click to collapse
No need since it ia working but you get into Fastboot mode then
Fastboot set_active a
Flash L, flash April bootloadee.
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
WyldOne91 said:
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
Click to expand...
Click to collapse
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Badger50 said:
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Click to expand...
Click to collapse
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
WyldOne91 said:
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
Click to expand...
Click to collapse
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Badger50 said:
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Click to expand...
Click to collapse
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Badger50 said:
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
Click to expand...
Click to collapse
Yeah for sure. I'm always willing to learn!
CyberpodS2 said:
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Click to expand...
Click to collapse
Yeah I actually already ran a backup with Titanium Backup and moved it to my PC last night just in case I did something stupid haha but I appreciate the tips!
I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Soooperstar said:
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes, I have done all of the typical things and I am having very, very bad luck. Out of the box, thinking is critical.
Fixed!
Scottay5150 said:
I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Click to expand...
Click to collapse
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Bryanx86 said:
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Click to expand...
Click to collapse
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Scottay5150 said:
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Click to expand...
Click to collapse
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
stebomurkn420 said:
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
Click to expand...
Click to collapse
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Scottay5150 said:
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Click to expand...
Click to collapse
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
borxnx said:
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
Click to expand...
Click to collapse
I wish I could say the wrong GAPPS, the version from the OP was used (others had issues as well), TWRP 3.2.0 again from the OP was installed per instructions. They were not. Not letting system boot up might have been the bigger issue. I shall never know.
Hey everyone, I'm currently trying to recover my 4G/LTE signal in my XT1672, here's the situation
*Phone was originally on stock ROM, May/2018 security patch
*Unlocked bootloader, installed TWRP 64-bit and Pixel Experience 8.1.0, IMEI/LTE still fine
*Restored older stock ROM, with January/2017, IMEI/LTE still working as they should
*Manually updated (fastboot mode) to latest security patch (July/2018), IMEI=0
I've read multiple guides over XDA, most of them say I gotta flash back the Pixel Experience ROM and it should be back on 3G, then run 'fastboot erase modemst1' and 'fastboot erase modemst2'. I've followed these instructions and this is what happened:
*Flashed back Pixel Experience, IMEI=0 on first boot
*Rebooted phone, IMEI back with 3G signal
*Booted into fastboot mode and ran the 'fastboot erase modemst1' and 'fastboot erase modemst2'
*Rebooted phone multiple times, instead of 4G/LTE i got IMEI=0 again
EFS backup is not even an available option for me in neither TWRP 64-bit nor 32-bit
Any help is appreciated, thanks for your time and greetings from Brazil! Let me know if you need something else in order to help me like logs, screenshots, etc. Cheers!
EDIT: Managed to get 3G in stock ROM by not running erase modemst1/2, still no 4G signal
https://forum.xda-developers.com/g5/how-to/how-to-recovery-4g-moto-g5-t3787208 this tutorial saved my 4G signal :good:
Just a little edit: for getting H+ signal in first step, I recommend installing PixelExperience ROM (based on Android 8.1.0) along with LATEST 64bit TWRP.
PixelExperience for G5: https://forum.xda-developers.com/g5/development/rom-pixelexperience-t3756673
TWRP x64 for G5: https://androidfilehost.com/?w=files&flid=236353
No verity opt (flashable TWRP zip, I recommend version 6.0, use in case if you are installing TWRP on stock ROM- without flashing this file on first run of TWRP, stock ROM won't boot): https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
EDIT2: It may take a little bit longer to establish network after boot with restored EFS (for me, it took almost 30 seconds). If phone logins into 3G network, just go to settings and make it search for all possible networks in range (there should be your 4G network also).
I AM NOT RESPONSIBLE FOR ANY DAMAGE, YOU ARE DOING THIS AT YOUR OWN RISK!
Thank you, I'm gonna try it tonight and see if it works. TWRP versions seem to be the same ones I'm using though. Do I need an external SD Card to backup the EFS partition?
patricksouza472 said:
Thank you, I'm gonna try it tonight and see if it works. TWRP versions seem to be the same ones I'm using though. Do I need an external SD Card to backup the EFS partition?
Click to expand...
Click to collapse
No, it will be saved into "TWRP" folder in internal memory.
Andrej_SK said:
No, it will be saved into "TWRP" folder in internal memory.
Click to expand...
Click to collapse
Dude I really can't thank you enough for your help! After following this tutorial my 4G signal came back but it would keep turning itself on/off all the time, a simple rebooting solved the issue and now I'm getting constant 4G signal! Thank you a million times!
patricksouza472 said:
Dude I really can't thank you enough for your help! After following this tutorial my 4G signal came back but it would keep turning itself on/off all the time, a simple rebooting solved the issue and now I'm getting constant 4G signal! Thank you a million times!
Click to expand...
Click to collapse
No problem, glad to help you.
Just to leave a note here: This old thread still helped me in 2023 to regain IMEI numbers and 4G-connectivity on my old Moto G5 XT1676. As I could not get hold of a working 8.1.0 PixelExperience ROM I tried with a 9.0 Pixel Experience. It worked.
Hi all,
I believe the original motherboard for my RN5 whyred went bad (spontaneous reboots) and so I found a replacement for it - but it is a RN5Pro whyred board. Since they are both whyred, I figured it would be ok to replace the RN5 with the RN5Pro board. The boards look identical and they're both whyred, so why not? Right?
I made a nandroid backup with OrangeFox (9.2.3 I think?), swapped the boards, everything booted great with the new board. I unlocked the bootloader, installed a slightly newer version of OrangeFox (10.0.3) and then restored the nandroid backup. It restored without any errors, but when I tried to boot it - then the problems started. Since there was no logo or anything to see on the screen, I thought I hard bricked it, but MiFlash saw it and I was able to reinstall a stock MIUI 11.0.3 image. Now it boots, but I have a few questions/issues:
1. It doesn't recognize the SIM any more. It did recognize it when I first booted the new board, so I know it's not an issue of the board not recognizing the SIM by nature. Maybe the nandroid restore bonked it? Not sure what I can do at this point besides asking for a replacement SIM. Any ideas?
2. Is it not possible to restore a nandroid backup from the RN5 to the RN5Pro? Or do you have to use the exact same version of recovery to restore that you used to backup? I would really like to not have to reinstall and reconfigure all my programs, which includes 2FA apps that will be a pain to refresh.
Any help is appreciated,
eisenbergw said:
1. It doesn't recognize the SIM any more. It did recognize it when I first booted the new board, so I know it's not an issue of the board not recognizing the SIM by nature. Maybe the nandroid restore bonked it? Not sure what I can do at this point besides asking for a replacement SIM. Any ideas?
Click to expand...
Click to collapse
OK, so I put the SIM in another phone and it works fine. So the problem is somewhere else. Can anyone point me in the right direction? The new board definitely recognized the SIM before I restored the nandroid backup and now after a stock ROM reflash, it doesn't recognize it. Driver?
eisenbergw said:
OK, so I put the SIM in another phone and it works fine. So the problem is somewhere else. Can anyone point me in the right direction? The new board definitely recognized the SIM before I restored the nandroid backup and now after a stock ROM reflash, it doesn't recognize it. Driver?
Click to expand...
Click to collapse
Persist partition and 1 more are corrupted... Search it on xda
drnightshadow said:
Persist partition and 1 more are corrupted... Search it on xda
Click to expand...
Click to collapse
Thanks for the reply. I found some resources for flashing the persist partition. Which is the other partition you suspect of being corrupted, or how can I discover that? Is it the modem partition/non-HLOS.bin? I've already done the regular stock ROM flash through fastboot, so the 'normal' partitions have already been rewritten. What other 'special' partitions are there besides persist?
eisenbergw said:
Thanks for the reply. I found some resources for flashing the persist partition. Which is the other partition you suspect of being corrupted, or how can I discover that? Is it the modem partition/non-HLOS.bin? I've already done the regular stock ROM flash through fastboot, so the 'normal' partitions have already been rewritten. What other 'special' partitions are there besides persist?
Click to expand...
Click to collapse
Ha, you have them CCA 28 partitions. You need to find out by your self. Start with persist, vendor,... Most common ones than less common. Maybe you should try flashing under EDL mode. I would advise you to check which partitions did restored and start there.
drnightshadow said:
Ha, you have them CCA 28 partitions. You need to find out by your self. Start with persist, vendor,... Most common ones than less common. Maybe you should try flashing under EDL mode. I would advise you to check which partitions did restored and start there.
Click to expand...
Click to collapse
Wow, no idea there were that many. I haven't been this deep into the phone before.
I see there is a file called partition.xml in the fastboot images directory, I assume that is the full list of partitions on the phone (but there are 64 entries there)? Do you actually check them all for corruption, or just try to reflash them all until it starts working? Some of them do not have a filename listed. Not sure what to do with those.
<partition label="apdp" size_in_kb="256" type="E6E98DA2-E22A-4D12-AB33-169E7DEAA507" bootable="false" readonly="false" filename=""/>
The 'flash_all.bat' file (that did the flash that got it working again) looks like it flashes 24 images by default, so I guess there aren't too many others to try.
Any links you can refer me to, to understand how to start poking at this? Thanks!
eisenbergw said:
Wow, no idea there were that many. I haven't been this deep into the phone before.
I see there is a file called partition.xml in the fastboot images directory, I assume that is the full list of partitions on the phone (but there are 64 entries there)? Do you actually check them all for corruption, or just try to reflash them all until it starts working? Some of them do not have a filename listed. Not sure what to do with those.
<partition label="apdp" size_in_kb="256" type="E6E98DA2-E22A-4D12-AB33-169E7DEAA507" bootable="false" readonly="false" filename=""/>
The 'flash_all.bat' file (that did the flash that got it working again) looks like it flashes 24 images by default, so I guess there aren't too many others to try.
Any links you can refer me to, to understand how to start poking at this? Thanks!
Click to expand...
Click to collapse
Start with EDL MODE and flash all.... Check and search 1st how EDL MODE works and how to get into it... Read a lot before you'll mess with your phone... for persist you need to patch file (like notepad++), very simple and for the rest like I said read a loooooot..
But if you use OrangeFox recovery than you should only look at those partitions + persist.. For everything else you need research by yourself, sorry no easy way out.
BE CAREFUL DON'T LOCK YOUR BOOTLOADER OR YOU'LL GET EVEN MORE TROUBLES !!!!!
Good luck.
You should be fine flashing 2 files, persist partition and modem file.
Extract the files from the fastboot rom installed in your device.
Please read and document yourself how to flash those files.
Modem file is called "NON-HLOS.bin" and is fastboot flashable.
Persist partition is recovery flashable by OrangeFox.
The best part is that you managed to hardware repair your device! The software part is easy.
Take care and good luck!
Follow @drnightshadow advice also.
MadK9 said:
You should be fine flashing 2 files, persist partition and modem file.
Extract the files from the fastboot rom installed in your device.
Please read and document yourself how to flash those files.
Modem file is called "NON-HLOS.bin" and is fastboot flashable.
Persist partition is recovery flashable by OrangeFox.
The best part is that you managed to hardware repair your device! The software part is easy.
Take care and good luck!
Follow @drnightshadow advice also.
Click to expand...
Click to collapse
Thanks for the info. I tried both items, flashing modem from fastboot and persist from OF, but it didn't change anything.
So I tried an EDL flash, but it won't flash persist.img. It recognizes that it is sparse, but still gives me a 'ERROR_BAD_FORMAT' error and that is the end of that. Reflashed persist.img from OF, no results. Tried a regular stock fastboot-based flash with no tweaks and now it won't flash the modem with the error:
error:FAILED (status read failed (Too many links))
There's really not much left in the images directory that isn't already flashed -
* ddi.elf
* misc.img
* lksecapp.mbn
* uefi.elf (but that looks like a bootsector kind of thing)
My Google-fu is not strong enough to find any mentions of the first three images or what they are used for.
I do note that rawprogram0.xml mentions a lot of partitions that have no files associated with them. I'm a bit wary of just dropping those images into there without a good reason to do so. But again, Google is not helping here.
Any ideas before I toss the phone and go buy a new one?
Oh, man... I'm no expert at all and really cannot help anymore... There are more android experts here then anywhere else on this web and still your issue found no fix. In my opinion you should try to flash the factory image, the rom which your device came. I did encounter the issue when flashing went wrong a few years ago. No other image was flashable! Had errors with more recent ones but when I went and flash the factory image, my RN5 came to life.
MadK9 said:
Oh, man... I'm no expert at all and really cannot help anymore... There are more android experts here then anywhere else on this web and still your issue found no fix. In my opinion you should try to flash the factory image, the rom which your device came. I did encounter the issue when flashing went wrong a few years ago. No other image was flashable! Had errors with more recent ones but when I went and flash the factory image, my RN5 came to life.
Click to expand...
Click to collapse
I did that and it did come back to life... except for not recognizing the SIM.
There is a lot of help here on xda, but I guess even that has its limits sometimes. If you or @drnightshadow don't have any other ideas, then I guess it's time to get a new phone. A shame really, this one lasted me about 3 years and I've had no reason to replace it until now.
No, you tried and accomplished a lot! You should not give up just because of us. We're no experts. Just try to look and search for similar issues but on other brands! Try this approach. And even if you buy a new phone, continue to look for solutions in order to have a RN5 functional again! I remember I even lost imei and all mac addresses for bth and wireless... Not quite like your issue but similar. Only flashing persisit partition brought my device back.
SIM not recognized after flashing at DuckDuckGo
DuckDuckGo. Privacy, Simplified.
duckduckgo.com
L.E.
You could also try to flash persist partition from other rom version, older or newer from stock images... an idea, something else to try...
MadK9 said:
No, you tried and accomplished a lot! You should not give up just because of us. We're no experts. Just try to look and search for similar issues but on other brands! Try this approach. And even if you buy a new phone, continue to look for solutions in order to have a RN5 functional again! I remember I even lost imei and all mac addresses for bth and wireless... Not quite like your issue but similar. Only flashing persisit partition brought my device back.
SIM not recognized after flashing at DuckDuckGo
DuckDuckGo. Privacy, Simplified.
duckduckgo.com
L.E.
You could also try to flash persist partition from other rom version, older or newer from stock images... an idea, something else to try...
Click to expand...
Click to collapse
I'm thinking - I got into this problem because I tried to restore a nandroid backup from the first board to the new board. I'm wondering if there is something like an IMEI or other 'burned in' identifier that got written in and now the phone has a mismatch so the OS won't recognize the SIM as being installed.
Fortunately, before I started doing anything with the new board I did a nandroid backup of what came shipped with it (I unlocked it and put OF on it first, obviously). A bunch of reading I did today made me think about the efs partition - I had restored persist and modem, but not that one. So I did a full nandroid restore of the clean backup, including efs. Rebooted and it went straight to fastboot, would not boot. No problem, used MiFlash to put MIUI 11.0.3 cleanly on it (no tweaks). When it booted after that - the SIM is back! Woo-hoo!
I'm guessing the EFS partition has something to do with it, but I'd have to do more reading to understand it more fully.
In any case, I have a usable board again. *finally*.
For the record (and for anyone else that might have this problem in the future):
* restore original clean nandroid backup (but probably only needed the *efs* partition)
* forced to do a stock rom install via fastboot (used MIUI 11.0.3)
** got use of the SIM again!
* flashed twrp in fastboot to be able to flash OrangeFox from inside twrp
* updated firmware to latest stable v12.0.2
* flash Lineage 18.1
* flash Magisk
* wipe caches and dalvik
* install gapps
* wipe caches and dalvik
* reboot to usable phone
Thanks for being part of the journey!
Sweet, that's nice to hear... Resurrection of whyred wuuuhuuu ..
good job... See, you just don't give up and success is here.. Remember that I told you persist and 1 more partition are corrupted... You find it, EFS
If it isn't hardware problem, whyred can be always unbricked.
Really, really happy for you man!!!
Well done!!!
Yesterday was about to do more research in order to find a way out for your issue but had something else at my job, only downloaded a fastboot rom and was trying to find that troubled partition, even to tell you about efs... And now, the good news from you is that you were busy and had success!!!
Enjoy your zombi phone! I mean resurrected!