Related
A day or two ago I unlocked my ChaCha using the HTCDev.com instructions. I then used DooMLoRD_v4_ROOT-zergRush-busybox-su to root it. Everything was going fine until I apparently deleted one too many system apps and now my phone is in extremis.
The problem: As the phone boots up and reaches the HTC logo screen, just when the main interface should appear, an error pops up. It says:
Code:
Sorry!
The process com.htc.bg has stopped unexpectedly. Please try again.
[Force close]
When I close it, the HTC logo appears again as the main GUI is reinitialised, which leads to the same error popping up again, thus entering into an infinite loop.
I can just about manage to connect the phone to my PC as a disk drive, but it's not connected in such a way that RUU or unrooting applications can "find" it from within Windows, so if I'm to fix this it's gotta be from the SD card/Hboot.
Details:
* HTC ChaCha with the latest Android firmware.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
* Factory resets and recovery boots don't seem to have any effect.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Is there any hope of fixing this issue given my obvious lack of critical faculties?
Thank you for reading this.
You can always install clockworkmod recovery and from there a custom rom. Check the relevant thread, it is pinned.
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
Click to expand...
Click to collapse
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
Click to expand...
Click to collapse
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
Click to expand...
Click to collapse
You can't restore a system app if there is a conflict. Try and identify the conflict.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
Click to expand...
Click to collapse
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
* Factory resets and recovery boots don't seem to have any effect.
Click to expand...
Click to collapse
See above about freezing.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
Click to expand...
Click to collapse
Doesn't matter, you'll fix it, guarantee it.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
Click to expand...
Click to collapse
See what I said above.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Click to expand...
Click to collapse
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
For a safe to remove list, check the Themes and Apps section.
skezza said:
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Click to expand...
Click to collapse
Music to my ears!
skezza said:
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
Click to expand...
Click to collapse
In Titanium Backup I tried restoring the backups I made; the "Recovering Backup" notice would just hang indefinitely until I forced TB to close. This only happened with system apps. The backed up files are still on my PC hard drive from when I copied them from my SD card, but I'm not sure they're of any use at this stage.
skezza said:
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
Click to expand...
Click to collapse
Ahhh, this is probably my problem then. I ignored most of the fixes and workarounds listed as [S-OFF] because I didn't think they'd work for my device haha.
skezza said:
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
Click to expand...
Click to collapse
I'm disappointed in myself for being so haphazard in my deleting, I'm usually not that stupid but I think I was a little overexcited to have finally gotten rid of some of the bloatware that'd irritated me for so long haha. I was like "oh boy, I can save even more battery power and internal space if I just remove a little more!". Lesson learnt
skezza said:
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
...
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
Click to expand...
Click to collapse
As I said above I didn't realise I could make use of [S-OFF] materials so I didn't even attempt them for fear of making matters worse. I just now attempted to flash CWM and it hung on "parsing" which is what happened with previous flash attempts. If a flash attempt doesn't hang on "parsing" it parses for a second and then goes back to the main menu, apparently having no effect.
I'd be lying if I said I'm not overwhelmed by all of this; the tutorials I've read seem to assume a fair degree of prior knowledge that I definitely don't have haha. I hope I don't stretch anyone's patience here, but if you could explain it to me like a 6-year-old whose mother drank heavily during pregnancy I think it will help move things along!
Thank you for the thorough reply, much appreciated
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
dapaua said:
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
Click to expand...
Click to collapse
Unfortunately I can't do anything via my computer; my phone isn't "discovered" by the command line, unrooting tools or anything else. It does allow me to access the SD card as a hard drive but that's all it does. Obviously this wasn't the case before my problems started, because I used my PC to root and unlock the phone originally, but now the phone's boot process can't reach a point where it becomes receptive to the PC's commands. I don't know why it lets me access the SD card though.
Is there any way to do this without my PC being involved beyond transferring files to the SD card? If not, am I screwed? haha
Thanks mate!
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
The fastboot binary is here C:\Program Files (x86)\Android\android-sdk\tools , if you installed the android SDK, which I asume you did.
Good luck, I hope this works!
dapaua said:
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
Click to expand...
Click to collapse
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
dapaua said:
Good luck, I hope this works!
Click to expand...
Click to collapse
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
PaddyM said:
Dear CHRIST thank you for that - I didn't...
Click to expand...
Click to collapse
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
PaddyM said:
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
Click to expand...
Click to collapse
I'm happy it worked. Let's hope WiFi technology improves in the future
skezza said:
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
Click to expand...
Click to collapse
I knew about the recovery menu (the stock one, at least) but I didn't realise I could go into the Fastboot option and for the phone to then be recognisable to the PC, thus making it possible to flash via the command line. If I had known that I probably wouldn't have needed to post this thread at all haha.
skezza said:
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
Click to expand...
Click to collapse
Yeah... I think if it happened to one of you guys you probably would have had it sorted in about 6 minutes. 3 days isn't bad for my first attempt though! hahaha
skezza said:
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
Click to expand...
Click to collapse
Thanks for the advice man, I'll definitely be looking into the Nandroid backup option, although I hope I've learnt enough from this experience to have no need for it
Thanks to everyone who posted here, I appreciate the patience and the tolerance of my noobery.
Funnily enough, I tried TitaniumBackup today and the original poster is correct. While you can freeze, remove apps etc, you can't return them. especially system. I've not tried any of the alternative install methods that TB uses, but it's quite interesting.
TB is a bit quirky, I think. The system apps won't restore at all, but sometimes apps that I've downloaded myself will restore and other times they won't (the "Restoring App" notice just hangs there indefinitely). I usually find that forcing TB to close and then trying again does the trick, but I can't figure out why it happens in the first place.
Im wondering if anyone else has worked out a good configuration that will allow it to work every time?
This is probably a silly question, but I hope some more experienced Android experimenters can help ease my mind. I'm an Android noob, but I do know enough to follow instructions and I've successfully installed aorth's CWM Recovery and made a backup. (If I understand correctly, this is called a Nandroid backup and represents a complete backup of the system. Please correct me if I'm wrong.)
Now my Tab boots into CWM Recovery when I hold the volume-up key. It sees my backup when I select the "restore" option. All that looks as I would expect it to.
My question is: How safe is it to play around with flashing other firmwares, for example CyanogenMod 10? Will I always be able to get back to where I am now simply by booting into recovery and restoring? Or is it still possible for something to go so horribly wrong that that won't work? On a scale of 1 - 100, how high are the chances of being able to recover no matter what?
(BTW, I do have a copy of the backup on my PC, so if it got wiped from the Tab I would still be able to get it onto the external sd card.)
I am not a developer by any means. But I love to tinker. My rules are. Read everything. I have never been unable to restore a backup if somthing seems to have gone wrong. These guys are not out to mess up your device. Once you understand the terminology and flash a few it will bring new enjoyment to device. Go for it.
Sent from my GT-P6210 using xda premium
On July 20th 2013, I bought a new Verizon Galaxy S3 i535 (no contract due to I need unlimited data). As a 50 year old guy, I admit that I never rooted before. I decided to do some research on the web which also included this XDA site. By the way, this is the best site!!
As someone who never rooted, I found multiple different ways of rooting which caused great confusion. Some told me to download Odin, while some did not. Some told me to download a superSU or something like that, while other directions did not, and so on and on......
But what really concerns me is that most of the directions were written back in 2012. Should this be a concern?
I don't want to seem like a retard or impose, but would someone do a video skype with me and walk me thru rooting my phone for the very first time? Perhaps during that skype session I could ask a few questions? I would pre download all files so that the session would not take too long.
Any volunteers?
Respectfully,
Bryan
All you need to Do is visit this link:
http://forum.xda-developers.com/showthread.php?p=42791826
Those are the most straight forward directions you can find. And it will Root, unlock your bootloader, and install a custom recovery.
thank you for the reply. this is yet another way off rooting. why does this not use Odin? will this method allow me to undo or fix something if something goes bad?
BKSinAZ said:
thank you for the reply. this is yet another way off rooting. why does this not use Odin? will this method allow me to undo or fix something if something goes bad?
Click to expand...
Click to collapse
It doesn't use Odin because it doesn't need to. The one click solution includes all the tools needed to make the necessary changes to your phone.
If something goes wrong, then you would use Odin to go back to stock no matter what root /unlock method you used. This is because Odin has the lowest level access to your phone, and can rescue it as long as you can boot into download mode.
As long as you don't flash files intended for other phones (including s3s from other carriers) your phone should be safe.
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
funnyperson1 said:
It doesn't use Odin because it doesn't need to. The one click solution includes all the tools needed to make the necessary changes to your phone.
If something goes wrong, then you would use Odin to go back to stock no matter what root /unlock method you used. This is because Odin has the lowest level access to your phone, and can rescue it as long as you can boot into download mode.
As long as you don't flash files intended for other phones (including s3s from other carriers) your phone should be safe.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
BKSinAZ said:
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
Click to expand...
Click to collapse
I'm going to pop in here and help out. Once you do the casual root process, it will also install a recovery for you. You can make a nandroid backup with your recovery and just keep that somewhere safe. There are also directions on how to recover and return your phone to Verizon here. Hope that answers your question.
BKSinAZ said:
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
Click to expand...
Click to collapse
No, as I said above, as long as you can reach download mode on your phone you can always Odin back to stock. If you somehow break download mode, then your phone is pretty much bricked without sending it out to someone with a JTAG programmer. The risk of that happenning though is minimal unless you flash a ROM intended for a different device (such as the international i9300 S3).
funnyperson1 said:
No, as I said above, as long as you can reach download mode on your phone you can always Odin back to stock. If you somehow break download mode, then your phone is pretty much bricked without sending it out to someone with a JTAG programmer. The risk of that happenning though is minimal unless you flash a ROM intended for a different device (such as the international i9300 S3).
Click to expand...
Click to collapse
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
BKSinAZ said:
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
Click to expand...
Click to collapse
It sounds like you were successful in rooting and unlocking your phone's bootloader. The program you are seeing (TWRP recovery) allows you to flash roms/mods (install), backup your phone, wipe and restore your phone. However, this shouldn't be what you see on bootup unless you pressed volume up while booting. Your stock ROM may have been wiped during the root process.
I suggest you dive into the world of Custom ROMs with CleanROM which is basically a de-bloated and tweaked version of the stock ROM.
Download the file from here:
http://forum.xda-developers.com/showthread.php?t=1832070
Use your PC to put it on a microSD card. In TWRP recovery, perform a Factory Reset (from the Wipe Menu), then navigate to the external_sdcard and install CleanROM (from install menu). Wipe caches and reboot once installation is finished. You should boot straight into CleanROM.
funnyperson1 said:
It sounds like you were successful in rooting and unlocking your phone's bootloader. The program you are seeing (TWRP recovery) allows you to flash roms/mods (install), backup your phone, wipe and restore your phone. However, this shouldn't be what you see on bootup unless you pressed volume up while booting. Your stock ROM may have been wiped during the root process.
I suggest you dive into the world of Custom ROMs with CleanROM which is basically a de-bloated and tweaked version of the stock ROM.
Download the file from here:
http://forum.xda-developers.com/showthread.php?t=1832070
Use your PC to put it on a microSD card. In TWRP recovery, perform a Factory Reset (from the Wipe Menu), then navigate to the external_sdcard and install CleanROM (from install menu). Wipe caches and reboot once installation is finished. You should boot straight into CleanROM.
Click to expand...
Click to collapse
It seems that when I went into the backup area and made a backup (a backup of what, I do not know because I am totally new to this) and after the backup the phone rebooted to the normal home screen with all the normal icons. I even just received a phone call so I guess all is good.
I don't know what to do now that my phone is rooted. My goal was just to uninstall unwanted programs etc, So when I get the courage, I will use the CLEANROM.
Question.... do I now have to constantly update my existing root or Cleanrom once installed? Do I now avoid Verizon or Samsung updates?
BKSinAZ said:
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
Click to expand...
Click to collapse
If you're not ready to flash roms just touch reboot and you'll be back to your stock jellybean. In regards to the padlock, I also got that after using CASUAL and underneath the padlock it says custom. I haven't gotten a definitive answer about that but the general consensus is that it's nothing to worry about. I suppose it's just Verizon letting you know that they detected changes to your phone.
Do yourself a favor and read for days and days before you start flashing roms. You'll find the answers here and YouTube.
BKSinAZ said:
It seems that when I went into the backup area and made a backup (a backup of what, I do not know because I am totally new to this) and after the backup the phone rebooted to the normal home screen with all the normal icons. I even just received a phone call so I guess all is good.
I don't know what to do now that my phone is rooted. My goal was just to uninstall unwanted programs etc, So when I get the courage, I will use the CLEANROM.
Question.... do I now have to constantly update my existing root or Cleanrom once installed? Do I now avoid Verizon or Samsung updates?
Click to expand...
Click to collapse
Great. The backup you made is what is called a "nandroid" backup. By default it includes the Android System, your apps, and associated application data and settings. This is great because it basically includes everything you need to restore your phone to it's previous state. So if you were to flash a custom ROM and ended up not liking it you could always restore this backup and it would restore your phone to how it is now.
Being rooted allows you to install and use applications from the Play store that require root. There are tons of them. The one I use most often is called Titanium Backup. It's primary purpose it to backup and restore your data and applications on an individual basis. I use it mostly to save my text messages and game save data between ROM flashes. It also allows you to uninstall, wipe data, and freeze (disable) any application on your phone.
Right now since you are still running stock rooted, you want to avoid installing any official updates, otherwise you may have to re-root. Beanstown may have disabled system updates through the rooting method, but I am not sure. If a new update is released, keep your eyes on the forums here, someone will create a flashable zip of the new firmware that maintains root/unlocked bootloader, you can then flash that in TWRP. Also once you flash a custom ROM like CleanROM, they removed the Samsung Firmware updater most likely so you don't have to worry about it.
Hi,
I just want to know what the most powerful backup solution is.
I explain myself: I would like to do dangerous operations on my phone and I would like to have a much more powerful backup solution than a TWRP backup if one of these operations fails and my phone is hard bricked.
So I'm looking for a very powerful backup method that works even if tools like fastboot are broken.
If such methods do not exists, what is the nearest solution?
Thank you in advance for all the information you will be able to give me
Translated with www.DeepL.com/Translator
Except a nandroid backup with everything that it's in the phone (and so not a normal TWRP backup, but a full one with every partition available to be backed up in TWRP menu), i didn't understand exactly what kind of backup you're referring to. I suggest apps like Titanium Backup, MyBackup, Super Backup and similar ones to backup apps data also, but i think the TWRP backup is the strongest one.
RedSkull23 said:
Except a nandroid backup with everything that it's in the phone (and so not a normal TWRP backup, but a full one with every partition available to be backed up in TWRP menu), i didn't understand exactly what kind of backup you're referring to. I suggest apps like Titanium Backup, MyBackup, Super Backup and similar ones to backup apps data also, but i think the TWRP backup is the strongest one.
Click to expand...
Click to collapse
Thanks for your answer
I don't want to backup my apps and data, I want to backup every single partition of my phone.
Sometimes you can break you're phone very badly and even Fastboot can't recover it (recovery: dead, fastboot: dead, your phone: hard bricked). My request is There is a solution in this case to get back to live the phone with some kind of super-mega-backup software ?
siffrein said:
Thanks for your answer
I don't want to backup my apps and data, I want to backup every single partition of my phone.
Sometimes you can break you're phone very badly and even Fastboot can't recover it (recovery: dead, fastboot: dead, your phone: hard bricked). My request is There is a solution in this case to get back to live the phone with some kind of super-mega-backup software ?
Click to expand...
Click to collapse
TWRP can do just that, backup EVERY SINGLE PARTITION there is on your phone, and then restore them all.
But honestly if you brick your device that bad, I don't know if you will be able to boot TWRP to restore the backups...
Sent from my BLN-L21 using XDA Labs
Exactly, as i said. TWRP backup everything and you'll have the best phone image you can have. Just don't let your device explode
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.