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.
Related
Hi, all! I'm sorry if this is in the wrong section, but I'm having a hard time trying to understand the different forums.
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
Thanks in advance, and I apologise if this is in the wrong forum!
You might want to ask to the rom thread for some help or ask in this section,
Galaxy Ace S5830 Q&A, Help & Troubleshooting
Anyway, I will try to help. If your custom recovery is support backup and restore (and advanced restore) your rom (check your custom recovery thread), try to backup your phone rom for now, so you could restore it back when solution not working.
Try to reflash the rom again without wipe data and reboot. If still in bootloop try to wipe data and reboot, see if that phone still bootloop.
If phone is successfully boot, go back to recovery and go to advanced restore, restore only data and then reboot. If still not working, then just full restore back to the phone to state before since I have no idea anymore.
That is the option I only know for now. However, try to ask help on section I link above or the rom thread before try this one, since I only familiar with Galaxy Gio (really similar to Ace) in the past.
I tried what you suggested but no positive results, really. I managed to boot after a full wipe, but restoring data locked it back into a bootloop. I'll try posting it in the other section.
Thanks.
Hello,
Today, I came back home and put my phone on my desk.
I went outside the room for a couple minutes, and when I came back, the phone was turned off.
I thought the battery got emptied, so I plugged the phone to the charger. The phone turned on, but instead of my custom start screen, the default Cyanogenmod screen was up.
Then, I got the "Encryption Unsuccessful" message, saying the only way to recover my phone is to wipe it and hope google backed enough stuff.
Now, I still haven't used the button on the bottom of the screen. I went to the recovery mode, thinking maybe I could back up stuff before I wipe everything.
My question is: Is there a way to restore back my phone without wiping everything? I tried to back everything up to the SD card, but the backup stopped once it reached the /data folder, which I assume, is the source of the problem. Can the problem be solved by formatting the /data folder from the recovery mode? I also currently don't have any clockwork backups, thus I cannot use recovery to restore everything to the way it was.
Please help, I have very important information on my phone and I'd hate to lose it.
The data folder is where all your information is stored. There are many threads where people have tried to recover data from a brick, I've not heard a single success.
You could just try flashing the exact same rom you already had, without a wipe. That might cure any system issues but won't help corrupt data.
It sounds like your phone has suffered a partition corruption or failure.
boomboomer said:
The data folder is where all your information is stored. There are many threads where people have tried to recover data from a brick, I've not heard a single success.
You could just try flashing the exact same rom you already had, without a wipe. That might cure any system issues but won't help corrupt data.
It sounds like your phone has suffered a partition corruption or failure.
Click to expand...
Click to collapse
And what could possibly cause that?
As I said, I didn't do anything special or risky to the phone. The Cyanogenmod has been installed on it for a year and a half, so I don't think that's the problem.
Is there a way to extract some folders from the phone? I tried to plug it with a USB to the computer, but aside from the name, all information is unknown.
Also, will flashing the exact same rom will work? And what do you mean by "won't help corrupt data"? How do I know which data is corrupted?
And as I asked, will formatting the /data folder through the recovery mode will work? Can it cause damage?
I'm sorry for asking so many questions, I'm trying to be really careful with that and I need to fully know what I'm doing.
Thank you for replying.
Try ADB pull or aroma file manager in recovery, but if data partition is corrupt then your data is already lost.
boomboomer said:
Try ADB pull or aroma file manager in recovery, but if data partition is corrupt then your data is already lost.
Click to expand...
Click to collapse
It says "device not found". does that mean my data is lost?
And can you please answer my other questions?
Thank you for your help.
Edit: In case I do have to reset my phone, can someone guide me how to do it step by step?
I don't want something to mess up and get no help or wait hours for an answer.
FlyingPotato said:
or wait hours for an answer.
Click to expand...
Click to collapse
Take it to a service centre and pay them to help you.
okay nvm, I used the button on the bottom and it did the trick.
I should probably start backing up things more often because right now I use a backup from a year ago.
Thank you for your help.
Hi, guys
my phone is Huawei p10 Lite (WAS-LX2)
Note: if you have a bricked huawei p10 lite of any kind (incl WAS-LX2) (or a NZ model)
and you want to know how i finally fixed mine, jump down to the end where it says
GOOD NEWS
quick synopsis: unlocked bootloader, flashed twrp, now i get an error (255) when trying to create backup using twrp..
you can read the rest if you want but the above basically covers it please help
so i have unlocked my bootloader and flashed twrp, before i did this i did a factory reset through androids settings, the phone is also only two months old.. but i cannot create a backup using twrp, it always fails in the same place when backing up data, does this mean my stock rom that has never been altered in anyway ect is somehow corrupt? wtf? i havnt even rooted it yet, i was going to make a backup first (of a known good rom.. lol)
i am assuming the data files are part of the rom? not something you can ignore.. they were one of the few things selected by default.. i have tried rebooting phone a few times, formatting sd card etc (64gb) so there is plenty of space...
any help would be much appreciated
the tutorial i was following is here: https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
my phones full build (or do i mean firmware number?..) number: WAS-LX2C706B170
android version 7.0
emui 5.1
any more info, just ask..
also, ive heard that once you have installed twrp/ unlocked bootloader you cannot use system update or androids factory reset without bricking your phone? is that true? otherwise i want to try that, i just want to root my damn phone already... or... its been a long time since i last rooted a phone... you dont need root to make a twrp rom backup do you? nah, surely not..?
or could my twrp install be corrupt? the tutorial said to drag and drop the downloaded file into cmd, but that wasnt working so i entered the location manually, it still appeared to install fine that way though so surely thats not it. i dont know
ok, i just bricked my phone... i did a factory reset in twrp, thinking it was... a factory reset... i googled whether it was safe first and everything came up clean... but it is not it wiped the os or something and now i just get a boot loop... what the hell? how could i be so stupid?! and how could twrp not warn me.. it was just a factory reset? and i havnt even rooted it yet, at this point i would probably prefer it was rooted in the hope their would be more options available to me to un brick it.. ok now i really need someones help.. why am i drinking and trying to watch tv while doing this, i am so stupid, this is the best and most expensive phone ive ever owned, what have i done?! sorry sorry ill calm down...
so if my firmware number is: WAS-LX2C706B170 then can i use one of these (also for huawei p10 lite) and if so what would be the difference? why are the numbers slightly different? same phone model, different firmware/ slightly...
here they are:
WAS-LX2C706B120
WAS-LX2C185B121
and they each had a OTA and a full firmware version too.
here is the link: https://romfirmware.com/2017/08/04/huawei-p10-lite-was-lx2/
but before i try these things, is there any saving my current stock rom? i dont understand how a factory reset could prevent it from booting properly..? its not actually bootlooping, it either gets stuck on logo, or goes to black screen but you can still see the volume slider when pressing volume buttons, see the home and back buttons (which do nothing) and hear the lock sound when you press the power button... still always a black screen though.. i guess its possible i knocked the format data button in twrp but im 95% sure i didnt. if i remove twrp and install stock recovery would i be able to get the stock rom working that way? or is there any way to do an OTA update/ fix as i havnt rooted it yet so it should be capable (except i cant boot to rom..) if i hold down all buttons it seems to try to do something... it says emui then goes to 4% then says software install failed: the update package does not exsist. please download the package again... reboot system now..? whats that all about?
ok, so i have found a possible solution but would like confirmation from someone who knows these things first...
i found this tool: Huawei Firmware Finder (Team MT)
link: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
and using this i have found my exact firmware, apparently straight from the official huawei update servers. the firmware number matches exactly, but there is no mention of it being for a huawei p10 lite so not 100% sure its a good idea, but if the whole firmware number matches perfectly and its the only one of its kind it must be the right one surely? and the size is the same as other huawei p10 lite firmwares..
here is the direct link:http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1514/g104/v89953/f2/full/update.zip
please someone else chime in to give me some advice...
is there any risk with flashing roms, or can i always still access twrp recovery to flash a new rom if i brick the phone?
cheers all
ok UPDATE:
i tried the repair file system option in twrp on the data partition just for fun (wrong word, im not having fun..) because i thought this rom was a lost cause..
upon reboot a huawei warning pops up saying the data partition has some serious damage and offers to try a low level format, it finishes successfully then restarts.
no change, still broken, but it offers to do a full format of data due to serious damage.
after restart phone boots fine, and enters setup wizard for first boot etc... perfect.
problem is, i still cant backup the data partition in twrp, still get same error:
createTarFork() process ended with ERROR: 255
bacjup failed..??
did i somehow get a brand new phone with a bad flash of a stock rom straight from the manuafacturer? with a slightly corrupted data partition... is there anyway to fix this? or can i assume the rom i downloaded from huaweis servers for my exact firmware is correct and i can use that as a backup in case i need it?
or in case my data is corrupt should i try to install that rom now?
or should i try to reflash twrp first and see if i can get a successful backup?
or should i just forget all this crap now my phone works and go straight to rooting it?
i really need some professional advice here.. lol
clearly i aint no expert
ok, so i noticed the frp was still locked for some reason so using adb, i relocked and unlocked bootloader, now frp is unlocked too, reflashed twrp, wiped dalvik cach/ cache, tried backup again...
no change, still fails on data partition, same error 255...?!
im lost,
close to trying to flash that rom i found...
or at least just rooting already..
OK UPDATE: first the bad news, then the good news:
so i gave up on backing up my data partition, as it was clearly somehow corrupt?...
so i went ahead and rooted my phone, everything was more or less working untill i used apps2sd...
that required several reboots and partitioning my sd card etc, then it said something about needing systemless root and a reboot, i went ahead with that and then my phone started bootlooping again, this time there was no fixing it, i of course tried removing sd card too.. nothing..
so i tried restoring to the rom i found using huawei firmware finder tool, that didnt work, using twrp to install zip, i got error -9? (couldnt find that one on the net..)
tried unzipping and putting update.app in dload folder on root of sd card, then booting to erecovery pressing vol- vol+ and power button, that also failed. now i was stressed near tears, this was the third day of research and trying to fix this... so i searche dhigh and wide, and gave up on stock roms, i figured that a custom rom designed for my chipset (hi6250)
and said to work on a huawei p10 lite then it should at least semi work on my phone, i did more research and the rom creator said to only use his version of TWRP to flash their ROM, so i reflashed to theirs... BIG mistake, if the custom recovery is the only thing you can boot into and the only way to access boot loader, do NOT risk losing it.. i did.. i lost my recovery..
so there for i lost my bootloader, so therefore i lost my ability to use ADB, or connect to pc in any way. i wanted to step in front of a bus at this point... but then there was:
GOOD news:
so i resorted to trying the official recovery roms on XDA for p10 lites, only i had been avoiding them as none of the build/ firmware numbers matched mine at all.. but i went ahead and clicked on the first download, (here is the link to post: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097) - you might find a few comments from me near the end there, lol..
anyway , once downloaded i unzipped and just pasted the dload folder straight to sd card and rebooted phone with all three buttons depressed. to my amazement when the huaei erecovery came up it started installing!!!? wow, i tried not to get my hopes up though..
first boot restarted after blue huawei splash logo, second boot went back to erecovery, offered factory reset and wipe cache(so i did), now it boots up perfectly every time like new, everything works! even gave me NZ language options etc, even though my build number didnt match any of those above, its still worked and even better it still shows all the correct information under about phone.
my build number was: WAS-LX2C706B170
so i can confirm it works for nz huawei p10 lites with 4gb ram and dual sim and WAS-LX2 builds
hope this helps someone else out there like me
tags: all official huawei rom,stock rom,twrp.stock,backup,official,rom finder,nandroid,back up, save,solution,fix,help,stuck,advice,simple,easy,guide,tutorial,root,huawei,p10,p10 lite,huawei p10 lite,was-lx1,was-lx2,firmware,iso,image,zip,file,download,error 255,255,error,createTarFork(),
Hey, just wanted to say thank you for posting this!
I'm from New Zealand, and have the exact same phone and the exact same issue.
Your "good news" section was exactly what I was looking for, and helped me fix my phone.
Cheers, George
update copy
Hi was wondering if you have a copy of the update you used as it is near impossible to get from the link on the other thread. Another Kiwi with a bricked phone.
All good, after 4 hours it finally downloaded. I will keep a copy in case anyone needs it. WAS-LX2
I apologize for the lengthy back-story -
I had, but have since returned, an Asus Zenfone Max M1 ZB555KL. I thought it was a decent phone, but after spending the better part of the week setting it up (rooting, etc...) I inserted my sim and that sent the phone into a non-stop cyclic boot loop. Took the sim out & it worked fine. Research on the Asus forums proved that this is a widespread problem with the phone. Hence, I unrooted, factory reset it, and returned it.
Anyway, while playing with this phone for the week, I managed to root it with Magisk, and port a mostly functional TWRP. I never flashed TWRP...just booted to it. So that may, or may not, be the cause of my issues. I was able to select/browse the external sd card & flash zips as well. I had even performed a backed up to the external sd card. I was not, however, able to select/browse the internal storage. Also, each time I booted to TWRP, I was asked for a decrypt password. Simply cancelling it got me into TWRP. After some research, I determined that I needed to flash no-verity to disable encryption on the phone.
I followed instructions by wiping/formatting data then flashing no-verity. Rebooting to TWRP did not ask for a decrypt password anymore and I was then able to select/browse internal storage as well as external. Unfortunately, rebooting to the system caused a bootloop. Flashing Magisk and rebooting did not help either. I "restored" the backup I had made, and it appeared to work. But rather than booting to my original configuration, it rebooted as if it had been factory reset and I had to go through the whole setup process again.
Knowing I could get back to a factory reset at least, I tried a couple other versions of no-verity along with flashing magisk...all to no avail. At that point I decided that having root, along with the ability to flash some zips here and there, along with Titanium Backup was good enough. But then I found out about the reboot issue when inserting my sim and that was the final straw. So...my questions are:
1. Does the version of no-verity flashed matter? When downloading no-verity, there are about 6 versions but no change log, and no mention about if it is device specific. My understanding is that no-verity is universal. Is that correct?
2. Does TWRP need to be permanently flashed to the phone for no-verity to work? Is that why I ran into problems...because I was booting to TWRP but it was not the permanent recovery?
3. Did my backup not restore properly since the phone was not decrypted and was not able to write to the internal system? Why would it have restored to factory reset? (Thank goodness it did or I likely would not have been able to return it).
Thanks for helping clear up any misunderstandings I have about the whole process!
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