Related
For starters if I have this in the wrong place or missed whet I need in search please forgive me as this is my first post.
Droid Incredible rooted with no problems. I am still on the stock kernal. I downloaded setcpu and flashed the associated perflock disable (again, due to stock kernal). Now it appears the phone is bricked as I can only get to the white "htc incredible" screen. I have tried booting into recovery with no luck.
I've read a few ways on how to get out of this situation and frankly I'm scared to try anything else. I just don;t know what could have gone wrong with flashing the perflock_disable zip?
Any suggestions would greatly be appreciated.
I can get into Clockwork mod Recovery however it appears my nandroid backup files are gone....most likely due my having to reformat my SD card due to music file issues awhiel back. I must have forgot to do a backup after that.
This definately will be a learning experience.
Nevermind I got it up and running again. Thanks for your time if you read any of this.
how did u fix it i have the same problem please help
Hello:
I'm having a frustrating experience attempting my first root of my G2X.
I've had a previous thread from yesterday, attempting to do things from the Mac side:
http://forum.xda-developers.com/showthread.php?t=1172487&highlight=velanche
As of now, I've decided to revert to Windows 7 on my Mac to try and rectify things. I'm able to use One-Click Recovery Flasher, following the instructions, to flash the phone. I then downloaded an earlier nightly version of CM7, installed it on my flash drive, and did the install via ClockworkMod.
I had no errors from CWM, from the wipe to the install. I then choose the reboot open, and it powers off my phone.
Upon attempting to turn on my phone, I would get the LG screen, followed by a quick flash, followed by another LG screen with some horizontal blue background behind it. I'm taking it that it means that it's stuck, because I've waited 10 minutes before having to do a battery pull.
I did at one time attempted to flash back to the stock T-Mobile, but when the LG screen came it, it would just remain there without any progress.
At this stage, I don't know where else to go. I'm not sure if there's something amiss, because my phone, as far as I know, as been erased. If there's a way to progress to CM7, I'm game. But one thing I really need to do is to get my phone back.
I didn't backup my phone's contents initially because I was going to recreate everything anyway. Now I'm in a not-so-good place, save having to get a phone exchange.
Any assistance would be appreciated; thanks so much.
V.
Download one of the "Stock Rooted Nandroid Backups" from the development section, stick it on your SD card and do a Nandroid restore from CWM. That should get your phone working again...
On the CM7 installation problem, I have no idea what that could be. I've been flashing ROMs on Android devices since the G1 first came out a few years ago and the only reasons I had bootloops were from me trying to flash without wiping or flashing an unstable build.
Sorry to digress for a second here, but you DO have the T-Mobile branded G2x and NOT the Optimus2x, right?
Working on It
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
Sent from my Nexus 5g using XDA Ultimate App
velanche said:
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
Click to expand...
Click to collapse
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
Sent from my LG-P999 using XDA Premium App
LordButtersI said:
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
I don't know if this might have anything to do with why I've had problems getting CM7 to work, but I've noticed that when I plug the phone either into Windows or OS X, I've somehow lost the internal drive. I know that it's there because I've found a whole bunch of files on it while in CWN, but I'm suspecting that there's some link between neither computer seeing the internal drive and the issue with getting the phone to boot.
Yes, I can mount the external drive, either from CWM's mount on both platforms or when I press both volumes on my phone and plug in to Windows 7 via USB.
Do you have any insight on this? I was watching a few of The Unlockr vids, and I noticed that even though the guy's phone was rooted and flashed, he still could boot into his phone until he was ready to put on the new ROM (CM7, in this case).
Thanks!
Click to expand...
Click to collapse
scooter247 said:
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
I tried on the OS X side to do this, having to download an RAR app. I found the LG file, and told the app to extract it to the backup directory on my phone. I tried the restore again in CWM, but still a mismatch.
I will try it in Windows 7 tomorrow, and will let you know the outcome.
I'm beat; spent the whole weekend on this phone modding biz. I suspect I'll be really good by the time I finally am able to get things working.
V.
Click to expand...
Click to collapse
Is this an old SD card? Perhaps some bad sectors on it? Without holding the phone in my hands I can't think of anything else. Other than double check your steps, re-copy the files and try, try again.
The SD card is not old; about 2 months old. I tried formatting the card via Windows 7, but did it in FAT32. I take it that it's supposed to be formatted differently? The card is 16GB, but when I looked into CWM it's limit is 4GB.
I tried the steps again, and still get the same md5 mismatch. Is my guess correct that the card is supposed to be formatted a certain way? Unfortunately, I can access the previous OS via my phone, nor will the internal memory appear when the phone is plugged into the computer. However, I am able to mount the SD card within the computer's OS.
I almost feel like walking away from it for a week, but that means I'll be stuck without phone access for awhile. Tips or suggestions are most welcome.
BTW, there's apparently alternate instructions to deal with the md5 mismatch error. Though in Windows the NDIVIA driver is loaded for the phone, I tried the adb shell command but my device isn't detected by the software.
Thanks again,
V.
Hello all,
I'm a bit confused here as to how to perform a full back. My phone is rooted. I believe I used SuperOneClick or something like that and it did succesfully root the phone and all is fine. However, I see some guides that have many other options on the recovery menu. Mine only shows the option to Wipe Data. ??
I use ROM Toolbox and boot into recovery but don't see all other other options. I have researched a little and it looks like I have to have ClockWorkMod and ROM Manager installed. I installed ROM Manager and now it tells me I need to flash ClockWorkMod. ??
Everything I find on installing this is a guide to ROOT your phone and that's part of the process. I'm confused because my phone is already rooted. I just don't have all this other options and wondering if someone can please help me figure this out?
Thank you much,
--mike
You are rooted, but don't have CWM Recovery loaded. Two different things.
Open ROM Manager and click on Flash ClockworkMod Recovery and choose the TMo SGSII option (can't remember the exact name). Let it flash and reboot, and then try rebooting into recovery again.
Thank you for the quick response. Yes, was a bit confused because "Guides" I read online go through the root process as part of it. OK, I will try this...was a bit hissitant because my Skyrocket was not listed. I will pick that option.
Before I do this, can you please confirm it will not affect anything or change everything I have done on the phone? I take it this will basically allow the option to backup my existing ROM without modifications?
Finally, if I backup using this method, will this contain ALL information? For example, if something happens and I would like to get my phone working the same again, will the restore do this for me without any major issues?
Thanks again,
--mike
This will not reset your phone. Everything will stay intact. Yes, you will be able to make a nandroid backup, which will be a backup of your entire phone as it currently sits, including all apps, settings and data. Yes, you will be able to restore this at a later time to return to the exact state that it was in when you made the backup.
Thank you very much! I appreciate it!
In time backup bootmenu there was here a such:
"No /emmc/. android_secure found. Skip ping backup of applications on external storage."
That it?
How to correct?
Forgive for my English=)
I from Ukraine.
all the user applications get stored on the phone memory in /data.. so that does get backed up in both Full and Fast backup
you dont really need to backup your sdcard
Edit: yeah the applications from sdcard dont get backedup.. just did a backup :S
anikadam said:
all the user applications get stored on the phone memory in /data.. so that does get backed up in both Full and Fast backup
you dont really need to backup your sdcard
Click to expand...
Click to collapse
Means and has to be? You too have such message?
yeah i got that message, /emmc/ could not/skipped backup or something like that.. :?
We have no /emmc on this phone, so ignore that. The bionic and the razr and a few other phones have /emmc, but the A2 does not, so you can ignore this "error".
jimbridgman said:
We have no /emmc on this phone, so ignore that. The bionic and the razr and a few other phones have /emmc, but the A2 does not, so you can ignore this "error".
Click to expand...
Click to collapse
Thanks a lot!
You calmed me.
I have one more question to you.
Instead of BootMenu I delivered to atrix 2 bootstrap recovery
Also there was a new message
Log:
ClockworkMod Recovery v5.0.2.5
SD Card spase free: 7618mbMB
Backing up system...
Backing up data...
Backing up .andoid_secure...
Backing up cache...
No sd_ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete!
What you can tell? it norm?
At me costs 123 build.
+modification russian language
Chester103 said:
Thanks a lot!
You calmed me.
I have one more question to you.
Instead of BootMenu I delivered to atrix 2 bootstrap recovery
Also there was a new message
Log:
ClockworkMod Recovery v5.0.2.5
SD Card spase free: 7618mbMB
Backing up system...
Backing up data...
Backing up .andoid_secure...
Backing up cache...
No sd_ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete!
What you can tell? it norm?
At me costs 123 build.
+modification russian language
Click to expand...
Click to collapse
Yep perfectly normal, and a successful backup. Again since we do not have an internal /sdcard (like the samsung phones do), there is no /sd_ext, so it will skip that. You can use bootmenu or bootstrap to get a successful backup, your previous errors, were not really errors, and you most likely got a good backup.
I will be 100% honest here, and that the backups from CWM are really worthless. We have the fxz, and since we can not really get into CWM on boot easily (like they can on say samsung phones, which they can flash a custom CWM to thier recovery partition), the fxz is really your ONLY savior here. You might be able to restore a backup of stock ICS, ONLY if you do not bork your current rom, and can still get into CWM on boot somehow. If backing up with CWM gives you a warm and fuzzy, then it does it's job, but since we have an ICS fxz now, it is really not needed. And even more so, if you want to move over to things like CM10 or MM, and then want to go back to stock. Yes you can technically restore your backup, but I and others have seen some odd things that get left over from doing that, so the fxz is really the best thing to do.
jimbridgman said:
Yep perfectly normal, and a successful backup. Again since we do not have an internal /sdcard (like the samsung phones do), there is no /sd_ext, so it will skip that. You can use bootmenu or bootstrap to get a successful backup, your previous errors, were not really errors, and you most likely got a good backup.
I will be 100% honest here, and that the backups from CWM are really worthless. We have the fxz, and since we can not really get into CWM on boot easily (like they can on say samsung phones, which they can flash a custom CWM to thier recovery partition), the fxz is really your ONLY savior here. You might be able to restore a backup of stock ICS, ONLY if you do not bork your current rom, and can still get into CWM on boot somehow. If backing up with CWM gives you a warm and fuzzy, then it does it's job, but since we have an ICS fxz now, it is really not needed. And even more so, if you want to move over to things like CM10 or MM, and then want to go back to stock. Yes you can technically restore your backup, but I and others have seen some odd things that get left over from doing that, so the fxz is really the best thing to do.
Click to expand...
Click to collapse
Thanks a lot! Everything is very simple and clearly written.
But I didn't understand that such FXZ?
Chester103 said:
Thanks a lot! Everything is very simple and clearly written.
But I didn't understand that such FXZ?
Click to expand...
Click to collapse
An FXZ is the factory install provided by Motorola. Now Motorola does not provide this to normal users, they give it to AT&T and Motorola repair sites, and it gets leaked to us, from the incredible Motorola Firmware team.
The FXZ needs to be flashed with a program called RSD lite (only works on windows machines), it will fully restore your phone back to the factory install of ICS.
Take a read at this thread it explains a lot of great things for the A2:
http://forum.xda-developers.com/showthread.php?t=1396650
Now that has not been updated in a while, but it will give you enough information.
You can get the proper FXZ file for your phone or region from here:
http://sbf.droid-developers.org/edison/list.php
You can also get the files from here, for the international phones:
http://forum.xda-developers.com/showthread.php?t=1934874
Or here for the AT&T phones:
http://forum.xda-developers.com/showthread.php?t=1961310
RSD lite version 6.0 is needed to flash ICS, and you can get that from here:
https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
You will also need to get the motorola atrix2 drivers for windows from the motorola website, I will not link those as I am sure you can find them from going to the motrola home page and look under mobile device drivers.
By using the FXZ, it will be like your phone came brand new out of the box.
jimbridgman said:
An FXZ is the factory install provided by Motorola. Now Motorola does not provide this to normal users, they give it to AT&T and Motorola repair sites, and it gets leaked to us, from the incredible Motorola Firmware team.
The FXZ needs to be flashed with a program called RSD lite (only works on windows machines), it will fully restore your phone back to the factory install of ICS.
Take a read at this thread it explains a lot of great things for the A2:
http://forum.xda-developers.com/showthread.php?t=1396650
Now that has not been updated in a while, but it will give you enough information.
You can get the proper FXZ file for your phone or region from here:
http://sbf.droid-developers.org/edison/list.php
You can also get the files from here, for the international phones:
http://forum.xda-developers.com/showthread.php?t=1934874
Or here for the AT&T phones:
http://forum.xda-developers.com/showthread.php?t=1961310
RSD lite version 6.0 is needed to flash ICS, and you can get that from here:
https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
You will also need to get the motorola atrix2 drivers for windows from the motorola website, I will not link those as I am sure you can find them from going to the motrola home page and look under mobile device drivers.
By using the FXZ, it will be like your phone came brand new out of the box.
Click to expand...
Click to collapse
I am very grateful. Thanks for the information.
Good luck to you.
Chester103 said:
I am very grateful. Thanks for the information.
Good luck to you.
Click to expand...
Click to collapse
That is a wealth of knowledge to ensure you get no sleep at night messing with your phone.
Please click the thanks button at the bottom right of the posts from Jim.
Not a requirement but a courtesy. He went beyond the call of duty.
Thank you, I learned new knowledge
Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.
Juwapa said:
Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.
Click to expand...
Click to collapse
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video --> https://www.youtube.com/watch?v=jtc7EhNsfPA&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!
Mr.FREE_Bird said:
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video -->
&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!
Click to expand...
Click to collapse
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?
Juwapa said:
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?
Click to expand...
Click to collapse
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?
Mr.FREE_Bird said:
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?
Click to expand...
Click to collapse
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.
Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.
Juwapa said:
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.
Click to expand...
Click to collapse
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:
Mr.FREE_Bird said:
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:
Click to expand...
Click to collapse
So I finally had time to sit down and make backups of my device. I made a backup of just the EFS and Modem Partition only and I made another complete backup of everything. This should be all I need right?
And yes, I will keep the backups on my PC and on the flash drive I keep my current rom, recovery, kernel, and magisk on.
Shyciii said:
Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.
Click to expand...
Click to collapse
I could be wrong, but I don't think I had KernelTweaks on to begin with. I keep reading people are having problems with it, so I think I'll just stop using it. And it wasn't reboots that were the problem, I only had the one reboot. The problem was my phone wasn't recognizing my sim card nor did it give me my IMEI number, which is why I thought I might of messed up the EFS Partition. But thank you for the reply.
I'm about out of options anyone tried using smt download mode on msm tool.? Then restoring efs partitions.? And had any success. I'm getting a sha 256 does not match error on msm tool when trying to download super partition. Op8 verizon bricked.