is my phone bricked it only boots into fastboot and if I go on recovery or start the phone just shows a black screen this is after a twrp restore
You are clearly not bricked if you get to Fastboot. You can try writing the boot.img to both slots, and if that doesn't recover you install the factory image using flash-all (get rid of the -w in the batch file to retain your data). Read up a bit before posting. There are a lot of guides and good info here.
sliding_billy said:
You are clearly not bricked if you get to Fastboot. You can try writing the boot.img to both slots, and if that doesn't recover you install the factory image using flash-all (get rid of the -w in the batch file to retain your data). Read up a bit before posting. There are a lot of guides and good info here.
Click to expand...
Click to collapse
i took it to a shop they said they flashed it but it was doing the same thing
atari260 said:
i took it to a shop they said they flashed it but it was doing the same thing
Click to expand...
Click to collapse
What did you restore in twrp?
jd1639 said:
What did you restore in twrp?
Click to expand...
Click to collapse
i think it was system can't remember i did a backup then restore
jd1639 said:
What did you restore in twrp?
Click to expand...
Click to collapse
all i know is it said restored failed then started doing this
atari260 said:
all i know is it said restored failed then started doing this
Click to expand...
Click to collapse
Ok, I assume you made a backup of boot, system, and data in twrp and then restored that? You backed up system and not system image? Have you flashed a factory image before using fastboot commands or have you been using a tool kit of some sort to do your flashing? I'm trying to gauge your proficiency and how your PC is set up to determine the next steps.
jd1639 said:
Ok, I assume you made a backup of boot, system, and data in twrp and then restored that? You backed up system and not system image? Have you flashed a factory image before using fastboot commands or have you been using a tool kit of some sort to do your flashing? I'm trying to gauge your proficiency and how your PC is set up to determine the next steps.
Click to expand...
Click to collapse
I have never flashed a factory img before took me while to grasp how to root not a software person what i got told by a friend who's tried fixing it for me is that he has flashed the stock rom on to it and it is still doing the same thing
atari260 said:
I have never flashed a factory img before took me while to grasp how to root not a software person what i got told by a friend who's tried fixing it for me is that he has flashed the stock rom on to it and it is still doing the same thing
Click to expand...
Click to collapse
When you tried to restore in twrp, was it a backup you made on your device or was it backup from some other device? Is your friend pretty proficient at flashing google devices? It may be that there's nothing you can do at this point. To walk you through flashing a factory image is going to be a time consuming process.
jd1639 said:
When you tried to restore in twrp, was it a backup you made on your device or was it backup from some other device? Is your friend pretty proficient at flashing google devices? It may be that there's nothing you can do at this point. To walk you through flashing a factory image is going to be a time consuming process.
Click to expand...
Click to collapse
backup I made on the device and you got any idea what has actually happened?
and he owns a repair shop so presume he does
jd1639 said:
When you tried to restore in twrp, was it a backup you made on your device or was it backup from some other device? Is your friend pretty proficient at flashing google devices? It may be that there's nothing you can do at this point. To walk you through flashing a factory image is going to be a time consuming process.
Click to expand...
Click to collapse
sad times ah i broke the lcd 2 weeks after i got it the phones been in a repair shop longer then I have had it
atari260 said:
backup I made on the device and you got any idea what has actually happened?
and he owns a repair shop so presume he does
Click to expand...
Click to collapse
I don't have an idea of what happened. Google devices are pretty hard to brick. And if they turn on and boot to anything they technically aren't bricked. But with that said, these dual slot devices are a bit finicky. It could be just a coincidence that something failed while you where restoring.
jd1639 said:
I don't have an idea of what happened. Google devices are pretty hard to brick. And if they turn on and boot to anything they technically aren't bricked. But with that said, these dual slot devices are a bit finicky. It could be just a coincidence that something failed while you where restoring.
Click to expand...
Click to collapse
a dumb question would a rma work if I relocked the bootloader?
atari260 said:
backup I made on the device and you got any idea what has actually happened?
and he owns a repair shop so presume he does
Click to expand...
Click to collapse
It is not a certainty that he does. He could have sideloaded the OTA or even used the wrong factory image. Here is the guide for the 3XL. #4 has the information on a factory image.
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
atari260 said:
a dumb question would a rma work if I relocked the bootloader?
Click to expand...
Click to collapse
Your biggest problem with a RMA is that you had the screen replaced. Something could have been damaged when doing that. Whether the bootloader is locked or not usually isn't an issue with Google. But it's worth a try. If you don't ask you definitely won't get a RMA. But I don't condone you fib on anything they ask you.
If it were my device I'd flash the factory image. Then change the active slot and flash it again. Then if that didn't work I'd flash each partition separately to both slots. That's a real pita as there's 20 to 30 different partitions, maybe more I haven't looked for awhile. That probably wouldn't do me any good but it might tell what partition is failing, not that I could do anything about it if one did.
I would probably even take it a step farther and fastboot erase the system on both partitions, the data, and the vendor on both. Then install the factory image.
If u can get to fastboot you are far from bricked
jd1639 said:
I don't have an idea of what happened. Google devices are pretty hard to brick. And if they turn on and boot to anything they technically aren't bricked. But with that said, these dual slot devices are a bit finicky. It could be just a coincidence that something failed while you where restoring.
Click to expand...
Click to collapse
well i got told by the shop/dads friend who owns it that I've apparently messed around with the system files and that it's ****ed tbh i think he is bs but idk as i did a system twrp backup and restore which the restore then failed
atari260 said:
well i got told by the shop/dads friend who owns it that I've apparently messed around with the system files and that it's ****ed tbh i think he is bs but idk as i did a system twrp backup and restore which the restore then failed
Click to expand...
Click to collapse
None of the suggestions here have involved using TWRP. The days of just restoring a TWRP backup on your phone do not apply for this device. Even the most skilled have issues with TWRP and the Pixel series. I have been on it since the OG Pixel and Pixel XL, and to be honest I haven't bothered restoring a TWRP backup. I can reinstall the factory image (with or without a wipe) and be back to normal sooner and with less headaches.
I ran into a similar situation after restoring a backup a little while ago. I ended up fixing it by flashing the stock build to both slots using the flash all bat. At this point I wouldn't be concerned about removing the -w. Just let it wipe everything and start from scratch.
Related
Hi, Yes you're probably right I shouldn't have messed around without knowing exactly what I'm doing, but any help would be greatly appreciated, I have tried to search for answers on here, but the forum is running so slowly for me at the moment that searches just time out for me.
Anyway, heres what I did - I rooted via ODIN, (CF-Root) and installed CM12.1 - First though, having read about the EFS risks I thought I was covering my ass by downloading EFS Backup from the Play Store - I then backed up my EFS Partition, there were three options, and I assumed the safest option was to leave as default (tar.gz)
So when I saw I'd lost my IMEI after flashing CM, I reinstalled the app, tried to restore - which directed me to an app "Partition back up", which turned its nose up at my tar.gz files! (thanks for that EFS Back up!)
Can anyone tell me what I need to do with the tar.gz files? and do I need all of them?
Thanks in advance.
Partition backup?
Just use the restore options in EFS PRO. What's inside the archive, images or files?
I've just got a file of tar.gz's Radio, CDMA Radio, EFS, and three named M9kefs1 ,2, & 3
I copied them onto my Mac and managed to open them, which gave me .img files too, Which I've tried restoring on the tablet (using Partitions backup app) It reported success but didn't work.
I'll try this EFS Pro, I had seen it mentioned wasn't sure if thats the way to go, thanks!
I've got to ask, why through all of this you didn't use the one tool that would have solved your problem in minutes. TWRP?
ashyx said:
I've got to ask, why through all of this you didn't use the one tool that would have solved your problem in minutes. TWRP?
Click to expand...
Click to collapse
To back up EFS you mean? Quite simply I didn't think I needed to, I thought I'd done it with the EFS Back up app
zoidster said:
To back up EFS you mean? Quite simply I didn't think I needed to, I thought I'd done it with the EFS Back up app
Click to expand...
Click to collapse
There's nothing better than making a full backup in recovery.
It's your one and all get out clause if your device ever doesn't boot or something goes wrong.
Backup apps rely on a Bootable system.
In fact I would suggest you do it before going any further.
I suppose I wasn't too bothered, as coming from an "empty" tablet with no data loss to worry about, I had in my mind that if all went tits up I could simply flash the stock firmware with Odin. (Which I've now done anyway as EFS Pro wouldn't play ball)
Thanks for you help! Lesson learned on Backups.
zoidster said:
I suppose I wasn't too bothered, as coming from an "empty" tablet with no data loss to worry about, I had in my mind that if all went tits up I could simply flash the stock firmware with Odin. (Which I've now done anyway as EFS Pro wouldn't play ball)
Thanks for you help! Lesson learned on Backups.
Click to expand...
Click to collapse
Stock Firmware does not flash the EFS partition.
If it gets wiped or corrupted it's gone and not recoverable.
You have been lucky.
Well flashing the stock firmware back cured the problem, Must be a CM12.1 issue. That would explain why restoring the EFS .imgs didn't work either then.
Hi, I have a similiar issue with my SM-T705. I have the stock rom installed. My IMEI number seems to be broken. It's a generic imei 00499 number. However, I still have my box laying around which it came in. Is there any way to restore it from that?
haimann95 said:
Hi, I have a similiar issue with my SM-T705. I have the stock rom installed. My IMEI number seems to be broken. It's a generic imei 00499 number. However, I still have my box laying around which it came in. Is there any way to restore it from that?
Click to expand...
Click to collapse
Have you been able to resolve it? I am in the same boat as you
einsteino said:
Have you been able to resolve it? I am in the same boat as you
Click to expand...
Click to collapse
There are dozens of us, DOZENS! Seriously though, if you get a method please share.
Hey all,
I searched and couldn't find anyone else with this issue, so I thought I'd ask. My phone was stock and unrooted, and I had encrypted it. When the conversion to Developer Edition came out, I converted and wiped the phone. I installed CM 13 and it works well. Whenever I install a 5.1.1 ROM, though, it asks for a password on boot and says it's encrypted. I tried my previous password and it says it is incorrect. I tried doing all options on Advanced Wipe in TWRP, as well as Factory Reset and Format. Reinstalled 5.1.1 ROM and still encrypted. Not sure what else to try.
Any advice would be helpful. Thanks!
Nobody? I'm tearing my hair out here.
What I'm going to suggest is fraught with peril, but...
Try returning to an unrooted, 5.1.1 condition. Use this and flash in Odin. http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224 Wipe everything first including the system.
The peril? This will return your phone to its unrooted condition. Your recovery options will be fewer. But this should return your phone to its out of the box condition.
douger1957 said:
What I'm going to suggest is fraught with peril, but...
Try returning to an unrooted, 5.1.1 condition. Use this and flash in Odin. http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224 Wipe everything first including the system.
The peril? This will return your phone to its unrooted condition. Your recovery options will be fewer. But this should return your phone to its out of the box condition.
Click to expand...
Click to collapse
I really did not want to try this and lose root, so I been holding out. Today I took the plunge - full restore, bootloader locked, root lost, everything wipes. Still encrypted! How is this possible?
Vagabondage80 said:
I really did not want to try this and lose root, so I been holding out. Today I took the plunge - full restore, bootloader locked, root lost, everything wipes. Still encrypted! How is this possible?
Click to expand...
Click to collapse
Dude, I'm sorry.
douger1957 said:
Dude, I'm sorry.
Click to expand...
Click to collapse
Thanks. I may have it now. I just hammered wrong passwords until it did a factory reset. This time it appears to have actually reset it. Won't be sure until I get root again, but it booted.
Vagabondage80 said:
Thanks. I may have it now. I just hammered wrong passwords until it did a factory reset. This time it appears to have actually reset it. Won't be sure until I get root again, but it booted.
Click to expand...
Click to collapse
That was an unique solution. I would have bet anything that doing an ODIN flash would have put the phone in an out of the box condition. Live and learn, I guess. I'm glad it worked out for you.
douger1957 said:
That was an unique solution. I would have bet anything that doing an ODIN flash would have put the phone in an out of the box condition. Live and learn, I guess. I'm glad it worked out for you.
Click to expand...
Click to collapse
Yeah, no idea what could have still been encrypted after that many wipes. Oh well, it seems to be working now.
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!
Ok so I wasnt paying attention and I restored by pixel 2 xl data partition to my 3 xl and now my phone is stuck at the G screen with the status bar moving. Wont go any further. I am unlocked and have TWRP installed. I have tried flashing a factory image but no luck. Anyone got something I am missing?
Does someone have a Unlocked stock nandroid of a XL 3?
lol...
boot into fastboot and run the flash-all batch file.
use nandroid manager to browse the TWRP backup if rrestoring doesnt work, you probably restored with a format, try restoring with RM-F in TWRP settings.
virtyx said:
lol...
boot into fastboot and run the flash-all batch file.
use nandroid manager to browse the TWRP backup if rrestoring doesnt work, you probably restored with a format, try restoring with RM-F in TWRP settings.
Click to expand...
Click to collapse
I have reflashed a couple of times to no avail. It did reformat to ext4 so i formated back to f2fs.
I will try restore with RM-F next.
Brakiss said:
I have reflashed a couple of times to no avail. It did reformat to ext4 so i formated back to f2fs.
I will try restore with RM-F next.
Click to expand...
Click to collapse
Now it say I am corrupt and will not boot. I need a deuces script LOL. This sucks
Brakiss said:
Now it say I am corrupt and will not boot. I need a deuces script LOL. This sucks
Click to expand...
Click to collapse
factory reset from recovery and itll work
So figured out my problem, factory image wasnt installing right because my SDK was out of date. My bad. Thanks for the pointers.
Brakiss said:
So figured out my problem, factory image wasnt installing right because my SDK was out of date. My bad. Thanks for the pointers.
Click to expand...
Click to collapse
So glad you figured it out. I did something similar a couple of years ago when I accidentally installed the Pixel TWRP (my wife's phone) to my PIxel XL. Bit of a PITA to fix, but it was of course my fault. Your post got me to thinking though. I have been checking the SDK tools version (the one they post with the OTA images) every month for a couple of years. For all the time we all spend on our phones, why folks continue to use an obviously deprecated minimal version or an out of date version of the regular SDK is hard to understand. So many of the problems reported on XDA are a result of this issue. DL, unzip and compare file dates is about a 1 minute operation with another one minute to replace the old files if there is a new version.
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!