Hello everyone
Yesterday while restoring a backup of my rom, I also restored the firmware (didn't know I wasn't suppose to do that :/) and lost my IMEI etc.
I fixed that by flashing a stock rom suggested on another thread.
That fixed the IMEI and everything.
I restored my rom (correctly this time) and got everything back (I'm on Cardinal)
But now my gyroscope and accelerometer are acting weird.
I used an app to test and saw it was really erratic, jumping from side to side etc.
Now I have no idea where to go from here.
Any help would be great
Thanks
Danish78 said:
Hello everyone
Yesterday while restoring a backup of my rom, I also restored the firmware (didn't know I wasn't suppose to do that :/) and lost my IMEI etc.
I fixed that by flashing a stock rom suggested on another thread.
That fixed the IMEI and everything.
I restored my rom (correctly this time) and got everything back (I'm on Cardinal)
But now my gyroscope and accelerometer are acting weird.
I used an app to test and saw it was really erratic, jumping from side to side etc.
Now I have no idea where to go from here.
Any help would be great
Thanks
Click to expand...
Click to collapse
You can always flash the firmware file, if you want.
Do that, it should fix (most probably)
MyNameIsRage said:
You can always flash the firmware file, if you want.
Do that, it should fix (most probably)
Click to expand...
Click to collapse
The stock firmware? (the one with MIUI)
How do I go about doing that?
Through TWRP?
Danish78 said:
The stock firmware? (the one with MIUI)
How do I go about doing that?
Through TWRP?
Click to expand...
Click to collapse
If the rom you restored is aosp based then the firmware which you have for aosp roms, but if you have miui then installing miui again will fix it.
MyNameIsRage said:
If the rom you restored is aosp based then the firmware which you have for aosp roms, but if you have miui then installing miui again will fix it.
Click to expand...
Click to collapse
I restored a backup of a Lineage based rom, that's what cause the problem with the IMEI vanishing in the first place.
And I've read that the persist.img is what can fix the accelerometer... So confusing.
Danish78 said:
I restored a backup of a Lineage based rom, that's what cause the problem with the IMEI vanishing in the first place.
And I've read that the persist.img is what can fix the accelerometer... So confusing.
Click to expand...
Click to collapse
Try this,
I made this flashable zip, comtaining the persist backup of my phone, which i made using redwolf recovery. (Sorry i can't switch to regular twrp :crying
Ok so flash this and then try to restore.
https://drive.google.com/file/d/1aLwU_IuqzDrVwPC9SXsegTeZbUhfvREQ/view?usp=drivesdk
MyNameIsRage said:
Try this,
I made this flashable zip, comtaining the persist backup of my phone, which i made using redwolf recovery. (Sorry i can't switch to regular twrp :crying
Ok so flash this and then try to restore.
https://drive.google.com/file/d/1aLwU_IuqzDrVwPC9SXsegTeZbUhfvREQ/view?usp=drivesdk
Click to expand...
Click to collapse
Oh man this totally fixed the issue.
Thanks a lot.
I thought I'd have to flash an official firmware and start from scratch.
You saved me a lot of time.
Thank you very much
Related
Good evening, I'm having a problem with the backup.... (I am kinda new in this BUSINESS though...) After i make one i can't restore it, only the original android one, i do not know why. It is very annoying when i install another ROM and then, when i want to go back to the previous one, the boot screen freezes... Any ideas? Or a tutorial?
petrescu said:
Good evening, I'm having a problem with the backup.... (I am kinda new in this BUSINESS though...) After i make one i can't restore it, only the original android one, i do not know why. It is very annoying when i install another ROM and then, when i want to go back to the previous one, the boot screen freezes... Any ideas? Or a tutorial?
Click to expand...
Click to collapse
do mention the recovery version u are using ,wipe before restoring if the rom is not identical based as sometimes it might be an issue for screen freeze on bootscreen ,like cm7,cm9,gb are eg of diffrent rom but if u are flashing cm7 official and some modded cm7 by dev than it should not be an issue , use amonra3.0.6 http://forum.xda-developers.com/showthread.php?t=1523050 see if it solves
shhbz said:
do mention the recovery version u are using ,wipe before restoring if the rom is not identical based as sometimes it might be an issue for screen freeze on bootscreen ,like cm7,cm9,gb are eg of diffrent rom but if u are flashing cm7 official and some modded cm7 by dev than it should not be an issue , use amonra3.0.6 http://forum.xda-developers.com/showthread.php?t=1523050 see if it solves
Click to expand...
Click to collapse
thank you so much!
Hi everyone. This is my first post...anyways, been playing around with a gt-i9100 and have flashed many ROMs successfully. The latest (and best) being slim saber. I THOUGHT it was soooo easy! Haha! Wrong! Recently flashed the experimental cm11. Did the customary cwm backup, wiped cacheband partition, formatted, and wiped dalvik. Installed and Booted up fine. From reading that thread I'm experiencing the same common problems. The two worst are the battery level is out of whack and cwm can't read the SD card or micro SD. Smaller problems include can't adjust screen brightness and any apps on SD get deleted after reboot. Other smaller issues also. The overall speed is great and battery life is better than 4.3 ROMs.
Now, the real problem...because cwm can't read SD, I can't go reinstall my backup, which was my plan. Unable to flash new because downloads also go to sd, which is unreadable. Performed a backup of the current rom and its going to the phone memory. Is there anyway to move my nanadroid backup or new ROM there so cwm can see it and I can flash or any other suggestions? Any help would be greatly appreciated!!!
hawaiisteve said:
Hi everyone. This is my first post...anyways, been playing around with a gt-i9100 and have flashed many ROMs successfully. The latest (and best) being slim saber. I THOUGHT it was soooo easy! Haha! Wrong! Recently flashed the experimental cm11. Did the customary cwm backup, wiped cacheband partition, formatted, and wiped dalvik. Installed and Booted up fine. From reading that thread I'm experiencing the same common problems. The two worst are the battery level is out of whack and cwm can't read the SD card or micro SD. Smaller problems include can't adjust screen brightness and any apps on SD get deleted after reboot. Other smaller issues also. The overall speed is great and battery life is better than 4.3 ROMs.
Now, the real problem...because cwm can't read SD, I can't go reinstall my backup, which was my plan. Unable to flash new because downloads also go to sd, which is unreadable. Performed a backup of the current rom and its going to the phone memory. Is there anyway to move my nanadroid backup or new ROM there so cwm can see it and I can flash or any other suggestions? Any help would be greatly appreciated!!!
Click to expand...
Click to collapse
Flash apolo 6.1 tar from Odin, then you get cwm back.
full wipe n flash stock rom to aviod ny further problems n then install your backup after rooting again
Jimsilver73 said:
Flash apolo 6.1 tar from Odin, then you get cwm back.
Click to expand...
Click to collapse
thanks, Jim! can you direct me to a link to download apolo? been searching high and low...cant seem to find it...
hawaiisteve said:
thanks, Jim! can you direct me to a link to download apolo? been searching high and low...cant seem to find it...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2291756&page=314
First post ?
Not sure why you couldn't find it though, comes up straight away when I search for it?? Do you type in the search box for all forums xda?
Jimsilver73 said:
http://forum.xda-developers.com/showthread.php?t=2291756&page=314
First post ?
Not sure why you couldn't find it though, comes up straight away when I search for it?? Do you type in the search box for all forums xda?
Click to expand...
Click to collapse
Thanks again! Found it after all...I was using an ooolllllddd pc with really bad connection...everytime I clicked that link nothing happened. Went home and tried on mine and presto! It opened!
hawaiisteve said:
Thanks again! Found it after all...I was using an ooolllllddd pc with really bad connection...everytime I clicked that link nothing happened. Went home and tried on mine and presto! It opened!
Click to expand...
Click to collapse
OK, glad your sorted now. Have fun playing with new kk, think I'm gonna wait a couple of weeks till the devs iron out the teething problems ?
Jimsilver73 said:
OK, glad your sorted now. Have fun playing with new kk, think I'm gonna wait a couple of weeks till the devs iron out the teething problems ?
Click to expand...
Click to collapse
Man Jim, u gonna hate me lol. Unfortunately apolo 6.1 is a zip file, and as far as my research has gone, no way to convert it to tar for odin flash. any other suggestions? I think the only way might be to revert to stock and root again like bhavstech recommended. I'm not desperate, as it is still usable and I have another phone so I'll wait a while and hope someone can enlighten me...thanks!
hawaiisteve said:
Man Jim, u gonna hate me lol. Unfortunately apolo 6.1 is a zip file, and as far as my research has gone, no way to convert it to tar for odin flash. any other suggestions? I think the only way might be to revert to stock and root again like bhavstech recommended. I'm not desperate, as it is still usable and I have another phone so I'll wait a while and hope someone can enlighten me...thanks!
Click to expand...
Click to collapse
LOL - I forgot!! I think there is a tar file for 4.1 - use that, or use latest dori (either 8.43 or 9.43) it doesn't matter which because you will be re installing your back up which will have its own recovery img.
Hope this helps :cyclops:
Jimsilver73 said:
LOL - I forgot!! I think there is a tar file for 4.1 - use that, or use latest dori (either 8.43 or 9.43) it doesn't matter which because you will be re installing your back up which will have its own recovery img.
Hope this helps :cyclops:
Click to expand...
Click to collapse
Hey Jim I got it fixed using dori! Funny because the latest 4.4 addressed both of my major issues...stubborn me decided to try it out and I gotta say its pretty good! Stable but just a few broken apps and small issues. Gonna five it a try as a daily driver...thanks again!!!!
use odin to flash tar and then install and older rom which is functional with the sdcard. and then flash back your backups.
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
tried flashing another rom?
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
Delete some apps or unwanted ringtones from the rom zip then flash the rom..
try to use newest Milestone from SOKP, where is the file saved, on sd-card or internal memory ?
Make sure the ROM zip is completely downloaded/ copies to ur SD card .. An incomplete zip is a common cause of this error, also make sure u're on the latest version of whatever recovery u're using
Sent from my GT-I9300
Thank you guys for your help. yes jinayhvora I used the newer recovery and it worked like a charm.
However latest is not always better as last time while installing DN3 I couldnt get past the terms and condition. Then I downgraded to a previous version of philz recovery and it worked.
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
:good::good:
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
Yes I agree; can you help me with the below problem though?
anmolgoel said:
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
Click to expand...
Click to collapse
anmolgoel said:
I re-flashed the stock firmware and took its backup; same problem.
Click to expand...
Click to collapse
what do you mean by this?
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
kermage said:
what do you mean by this?
Click to expand...
Click to collapse
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
kermage said:
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Click to expand...
Click to collapse
maybe
anmolgoel said:
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
maybe
Click to expand...
Click to collapse
well, take a new backup now and try if it works..then we can conclude..
I'm curious as to why you aren't using TWRP.
kermage said:
well, take a new backup now and try if it works..then we can conclude..
Click to expand...
Click to collapse
I'm not able to make out whether you're messing with me
the current rom (SOKP) is able to be restored; only problem with the stock rom.
es0tericcha0s said:
I'm curious as to why you aren't using TWRP.
Click to expand...
Click to collapse
because the backup was made in philz. From what I know, CWM and TWRP have different kind of backup files which cant be restored by the other.. let me know if I'm wrong..
Should I use TWRP to backup now.. You think it'll work better than philz?
es0tericcha0s said:
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
Click to expand...
Click to collapse
sorry didnt see this post earlier.. I'm on philz, DN3 is ditto note 3 rom that I was using; it is stock based.
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
es0tericcha0s said:
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
Click to expand...
Click to collapse
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
anmolgoel said:
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
Click to expand...
Click to collapse
Ah. Never used the Online Nandroid one. Never saw the point and trust the actual recovery to be able to backup better. Less chance of issues.
I made a backup of my phone with LOS16 on twrp. I backed.up "boot, system and data", then when I go to restore I load it up and the phone restarts to the "pocophone" startup screen. After waiting the phone goes to fastboot mode.
How. Do I take a proper backup on POCO with twrp so I can switch rims easily?
Mooatreides said:
I made a backup of my phone with LOS16 on twrp. I backed.up "boot, system and data", then when I go to restore I load it up and the phone restarts to the "pocophone" startup screen. After waiting the phone goes to fastboot mode.
How. Do I take a proper backup on POCO with twrp so I can switch rims easily?
Click to expand...
Click to collapse
My solution: flash rom - Los16 (kernel,magisk if you used etc.) and restor only DATA
mikussj3 said:
My solution: flash rom - Los16 (kernel,magisk if you used etc.) and restor only DATA
Click to expand...
Click to collapse
I's there something I missed or it was just a fluke?
Mooatreides said:
I's there something I missed or it was just a fluke?
Click to expand...
Click to collapse
I had a problem with miui10 backup and this solution helped. someone on this forum advised me. works with you?
mikussj3 said:
I had a problem with miui10 backup and this solution helped. someone on this forum advised me. works with you?
Click to expand...
Click to collapse
It happened yesterday and I just reloaded the rom from scratch(all useful data is on SD anyway) , just wanted to know if I can avoid it in the future. Thanks man
Mooatreides said:
It happened yesterday and I just reloaded the rom from scratch(all useful data is on SD anyway) , just wanted to know if I can avoid it in the future. Thanks man
Click to expand...
Click to collapse
Go with the default settings for backup in TWRP. You will not have any issue. But one word of caution, use the same version of TWRP for backup and restore. Otherwise you MAY face issues.
tnsmani said:
Go with the default settings for backup in TWRP. You will not have any issue. But one word of caution, use the same version of TWRP for backup and restore. Otherwise you MAY face issues.
Click to expand...
Click to collapse
i did it was the three selected i mentioned but still it was wierd, my phone stayed on "pocophone" screen for a while then went to fastboot. I turned it off and relaunched into TWRP and reinstalled the rom.
Mooatreides said:
i did it was the three selecte
ed i mentioned but still it was wierd, my phone stayed on "pocophone" screen for a while then went to fastboot. I turned it off and relaunched into TWRP and reinstalled the rom.
Click to expand...
Click to collapse
When backing up, select system image Instead of system, and vendor image instead of vendor. It's the same, and no more problems when restoring.
hyborian said:
When backing up, select system image Instead of system, and vendor image instead of vendor. It's the same, and no more problems when restoring.
Click to expand...
Click to collapse
I'm using the official twrp. This has worked for you? On official
Yes, perfectly
Hi guys
My mido vibration stopped working a week back abruptly. I didn't flash anything new back then.
Tried diagnosing it with change of vibration motor (with a technician) as well but the new one didn't work either. He did attempt a temporary replacement of its underlying chip as well but again it didn't resolve the issue.
Attempted clean reflash RR. Then clean reflashed Havoc 2.9 build as well.
After reflash in both the builds, didn't install Magisk (just to be sure some version could have been conflicting with the motor may be)...No solution
Attempted firmware upgrade to notably stable versions 10.2.3 and then downgraded to 9.6.3 as well. No solution still....
Could anyone advise what I could attempt next..?
Current environment: Havoc 2.9
No magisk installed as of now.
Nothing works.
Magisk 20.1 was installed but removed now... Still doesn't work...
Please help.
@Walden0 brother could you help may be?
Naagraj said:
@Walden0 brother could you help may be?
Click to expand...
Click to collapse
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Walden0 said:
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Click to expand...
Click to collapse
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Naagraj said:
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Click to expand...
Click to collapse
First take a backup of EFS Am& modem partitions from recovery.
Wipe data, cache, dalvik & system. Flash miui rom, format data and flash orange fox recovery again. Boot into system.
That's it.
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Naagraj said:
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Click to expand...
Click to collapse
Should work, orangefox has aggressive stock recovery deactivation which isn't available in twrp I guess.
btw quote or mention me as I can't get any notification if you don't.
Naagraj said:
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Click to expand...
Click to collapse
Have already told you pal, try flashing miui and see if it works.
Modem partition should be in orangefox. I can't confirm as I don't have the device anymore.
Brother I am having same problem right now in 2020. did you find any solution to it? Any response will be greatly appreciated
I'm having this same problem in 2021. Any fix guys?