Welcome to my nightmare part 3.
Everything started in this thread (https://forum.xda-developers.com/ga...-ui-update-causes-brick-t3938799#post79711614)
Then I moved to backup issues (https://forum.xda-developers.com/galaxy-s9-plus/help/google-drive-backup-backup-t3940831)
Today I tried to restore my backup on other device to see if it's Google issue or my device only.
Turns out that I was able to easily restore sgs9 backup on Xiaomi note 5.
So no matter what I tried to flash on my device it's impossible do restore trough Google drive backup directly.
I made a stupid thing since I'm hopeless and nobody answers my questions as they don't exist anywhere in internet.
I took the Xiaomi and made twrp data backup of restored apps in hope I can restore it through twrp on sgs9+
Well it ended with bootloop.
Next thing was factory reset through TWRP and it helped a bit.
Passing welcome screen on sgs9+ I used another Gmail account with different backup and it showed up. So I did factory reset again as it was faster than ending the initial setup.
Now it bootloops constantly, I made a clean flash of lineage vendor and gapps and it doesn't help at all.
Wtf I'm supposed to do?
Flash stock Oreo trough Odin and start again?
I'm losing my mind as there's no way to get my apps and data back.
As it looks that apps backup made with my device doesn't work for this device only. No matter the software stock or lineage
Related
Searched, but found nothing specifically related to this. I was on CM10 and flashed back to stock until they get the bugs worked out. Flashed back to stock via Odin with Samsung toolkit v. 2.1. I had backups for TB so I decided to restore missing apps with data and system data, however whenever I did, the device would get stuck at the samsung logo. I suppose this is due to conflicting system files, so the device doesnt know what to boot from, but how can i avoid this in the future? I thought TB was the ultimate answer when switching roms to transfer data, this is the first time I've had trouble with boot issues with TB.
emoandy said:
Searched, but found nothing specifically related to this. I was on CM10 and flashed back to stock until they get the bugs worked out. Flashed back to stock via Odin with Samsung toolkit v. 2.1. I had backups for TB so I decided to restore missing apps with data and system data, however whenever I did, the device would get stuck at the samsung logo. I suppose this is due to conflicting system files, so the device doesnt know what to boot from, but how can i avoid this in the future? I thought TB was the ultimate answer when switching roms to transfer data, this is the first time I've had trouble with boot issues with TB.
Click to expand...
Click to collapse
You're getting boot loops from restoring system data, thats a big no, no. Missing apps and data, I usually dont have any problems with that. The only "ultimate" is do a nandroid backup in CWM
True, but nandroid replaces system so it wouldn't be best when switching roms, correct?
I only recently got into the whole rooting deal, but i followed the instructions precisely double checking and everything went along well , after that i installed most of the apps from here, made a full backup with titianium backup, but then i decided to try and install a custom rom, which was where i made my first mistake, i made a backup of the current(stock) rom and then went straight on to downloading cyagenmod 7.2 to try it out on my phone.
When i started the install i obviously had the pre install options, i only left the one check there which was wipe delvik cache i think figuring that was all i needed to do. Phone rebooted and the loading logo started but didnt go past it and after it had reappeared for 3 times the screen just went in a white screen with differently colored horizontal stripes, i thought my phone was now bricked, but i managed to turn it off and turn it back on and get into recovery mode. I tried to do a recovery which didnt do anything, after that i just selected factory reset thinking it will get me back to the stock rom, but instead CM worked and finally got past the loading logo, i checked in the CWM if i had the backup i had made before trying to install CM and it was gone.
I want to know what i have done wrong(i obviously have), how can i reverse it and how to install roms properly(preferably in simple language). I already found this thread.
Phone: LG Optimus Hub (E-510)
P.S. I am missing the Play store app, is this normal for CM?
1. You got into bootloop because you didn't do factory reset/full wipe (the /data partition wasn't wiped, files on this partition were from stock ROM and weren't compatible with CM) -> this is the reason why it booted after full wipe. Full wipe only deletes data, it will not restore stock ROM.
2. '... i checked in the CWM if i had the backup i had made before trying to install CM and it was gone'
Are you sure you made a backup? Or didn't you delete it?
3. For the Play store - CM ROMs ussually don't have Google Apps in them, you have to flash them after CM installation (look in the ROMs thread for Google apps/ GApps)
1. Thanks for the explanation, im defineatly going to keep in mind to wipe the next time i attempt to install a custom rom. Is the stock rom still in my phone or do i have to look online for one?
2. I belive you are right, i do remember wanting to do a backup, but i might have forgotten about it, i did one now so i can have something to go back to just in case.
3. Dont really understand this, can you please direct me to a thread for this? I tried doing the flash CWM recovery which didnt do anything, could i try using my backups from titanium backup to get the apps back on the phone? It would be quite a mess to get all of it downloaded again.
Edit: i tried installing google play downloaded from other sites and whenever i go into it, it asks me to add an account, but when i press yes, it just closes.
|Madman| said:
1. Thanks for the explanation, im defineatly going to keep in mind to wipe the next time i attempt to install a custom rom. Is the stock rom still in my phone or do i have to look online for one?
2. I belive you are right, i do remember wanting to do a backup, but i might have forgotten about it, i did one now so i can have something to go back to just in case.
3. Dont really understand this, can you please direct me to a thread for this? I tried doing the flash CWM recovery which didnt do anything, could i try using my backups from titanium backup to get the apps back on the phone? It would be quite a mess to get all of it downloaded again.
Edit: i tried installing google play downloaded from other sites and whenever i go into it, it asks me to add an account, but when i press yes, it just closes.
Click to expand...
Click to collapse
First things first. Before you do anything else you need to do some reading in order to understand the Basics of Android. Otherwise your going to get yourself in a bind again. In my Signature your going to see some links if your on a PC. You should check them out, they will help with answers to a lot of your questions.
I cant thank you enough, i was looking for something like this! :good:
I will have something to read in my spare time, as little of it i have trough.
Your welcome . Glad I could help.
TEAM MiK
MikROMs Since 3/13/11
Not long ago I started a thread about how good this phone was and how I have never had a problem...….ironically....I just broke it
I hadn't installed a new rom in over a year, so I updated TWRP to the latest, took a full backup, and installed the firehound rom, after the install the phone booted to a pure black screen, like screen off black, so went back to recovery, wiped it and restored my backup, only now when it starts I get a screen of text in another language have no idea, but there is a button I have no choice but to press, when I do, it reboots to recovery and does something and I noticed it wiped data, then booted again back to the same screen of foreign writing....the first line says encriptacao sem exito.
in recovery it says something about krypt keeper I think it was
anyone have any ideas?
What version of twrp ?? Maybe your backup has become corrupted and you will have to do a clean installation, even having to format the internal memory. Once I backed up a rom along with the pin code and after installing a rom and did not like it, to return the backup my device simply did not unlock even though entering the password correctly.
Thanks for the reply, I fixed it this morning. I know about not making backups with passwords and stuff set so always take them off before a backup, not sure what TWRP version but it is the latest as of yesterday. and the backup was taken with and restored in the same version right before flashing. I think somehow my internal storage had been encrypted, as you said, I had to wipe everything internal and formatted data, then installed new rom and all is good now, luckily thanks to the google overlords, nothing of any importance was lost as it is all backed up to them, only thing is it takes a little longer to get all my apps back after losing my titanium backup flashable user apps zip. but oh well haha.
Device: Redmi Note 4X (mido), Android 7, MIUI 10
Hey! Pardon me if I've placed my thread in an inappropriate place.
So, what I did was remove the system's finddevice app.
Then on some forum I read that it will cause a bootloop (phone is still on, working at this point). So I backed almost everything up and, in a moment of brilliance, went and rebooted the phone, at this point I went in and made a TWRP backup of the whole thing too.
I've got an unlocked bootloader and I am here for ideas what I can do with that in order to somehow fix my broken system. I know that I can just do a factory wipe, but since I only made a MIUI local backup prior to turning the phone off, that would mean setting up a lot of things from scratch, and also I see it as sort of an experiment to try and revive the dead system.
What I've tried is doing a wipe and only restoring the data partition from the old system. This doesn't seem to change anything.
I also tried making a backup of a working system and then recovering only the system partition of that, onto the broken version.
My experimenting leads me to believe that the data partition is indeed the one broken.
I will be interested in reading what you guys think about this.
Hi guys!
I somehow messed up my system with LSPosed in Gravitybox. A conflict made my phone unworkable (screen just kept flashing). No worries since I kept a Nandroid. After just putting this back (I ticked literally ALL the boxes) my phone goes trhough the OnePlus-loader (dot turning into square) and then says only "turning off" in the screen. Nothing else works. So I can only re-access the device via PC-Terminal in TWRP.
Fact is... Nandroid was taken BEFORE LSPosed was installed, Nandroid gave no errors when taking and gave no errors when "putting back". But device just kind of softbricks AFTER boot. Very strange. Any ideas?
Could it have to do with DM-Verity?
Just wondering: did anyone actually MAKE a NANDroid (ticket all the boxes) and tried to put it back? Questions:
- when putting it back: do I need all the boxes ticked, or just a few?
- when making a NANDroid - do I need to disable PIN, fingerprints etc.? Or can it stay active?
- did anyone succeed so far? - I am wondering why mine doesn't work?
Please share your experiences!
Can confirm neither my Nandroid backups are working.
Dunno if any security pin or measure needs to be disabled first, but it shouldn't.
So far, the most safe way I've found to make a full device backup, is through adb:
While booted in TWRP use the adb commands:
Bash:
adb shell
ls -la $(find /dev/block/platform -type d -name by-name)
to list all partitions.Then you can use
Bash:
mkdir /sdcard/PartitionsBackup
dd if=/dev/block/sdc"partition number" of=/sdcard/PartitionsBackup/"partition name".img
to backup every partition in your internal storage.To flash them back you can use fastboot:
Bash:
fastboot flash "partition name" "partition name".img
# Example
fastboot flash boot boot.img
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Can anyone help me in overcoming that kind of a problem .?
I've tried recovering with TWRP, I suspect the problem there is encryption, because when I factory reset the data, I can start fresh.
If you just want to have a working phone, try doing a restore and factory reset (also try reformatting the data partition if a factory reset does not work).
Just let us know if this worked for you.
exis_tenz said:
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Click to expand...
Click to collapse
I've created a Tool that could help, if you're still able to backup the original working firmware.
Anyway, I personally suggest to go with multiple type of backups (TitaniumBackup + Nandroid + PartitionsBackupper) first.
And when it's time to restore, wipe everything with the stock recovery and start fresh. Restoring the userdata partition for last, checking if everything works before flashing it.
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Raygen said:
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Click to expand...
Click to collapse
As i always say: Dont flash around without backups
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
4th factory flash???? I think u shouldnt flash somerhing anymore
Well, when I started with this phone, I made a NANDroid of stock rom, just plain, rooted. During the adventure setting it up, I kept making NANDroids.
Then when I was done (phone in use for 2 days) I installed LSPosed and Gravitybox. WARNING: if you mod the clock position in Gravitybox to middle: your phone will not work anymore (some framework error I guess). Then I decides to put back a 2 hours before made NANDroid back... Which got no errors when making and none when putting back... But the phone bootlooped. Actually it started through the loader, started Android and then only showed "switching off" in the screen. Which it didn't.
Then I needed a factory flash. The first factory flash gave me a "serial nummer incorrect", the second one a battery drain (no sim, wifi and bluetooth off, lost 50 percent battery in 9 hours without finding out what caused it). The next factory flash worked without the serialnumber error but also gave the battery drain AND did not let me enter a pinlock neither a fingerprint.
So tomorrow we'll try again.
What I noticed that even when a factoryflash @oneplus servicepoint was done... Some data survived (!) in the phone (which shouldn't). I still had a TWRP-folder there so I guess it's like more junk just survices. That probably causes all the trouble.
It's time OnePlus releases the firmware!
I've been in the same situation (even twice ) For me just deleting the Gravitybox.apk from system folders did the job.