No folders after coming back from a ROM - OnePlus 6T Questions & Answers

Hello,
I am quite new to ROMs and I came back to OxygenOS from Pixel Experience. I downloaded the OxygenOS from Oneplus support website and successfully installed it via the TWRP recovery. Now the system works quite much as it should, but there is one big issue.
I can't download files, take pictures or save screenshots.
I then went and looked at my files from the Files app, and there were no folders at all. I don't remember what should they be, but like pictures or downloads folder, you know... I am not exactly sure how did this happen, but it seems that I fully emptied my phone.
I am quite lost and unaware of how could I fix this. Do you think I could make those folders myself, or is there any possibility to download ~everyting~ again? Is there a file like that which would have all those folders too?
I am just assuming it would be related to those folders, but please do correct me if you think it is something else.
Thank you very much for any possible help

Jack826278 said:
Hello,
I am quite new to ROMs and I came back to OxygenOS from Pixel Experience. I downloaded the OxygenOS from Oneplus support website and successfully installed it via the TWRP recovery. Now the system works quite much as it should, but there is one big issue.
I can't download files, take pictures or save screenshots.
I then went and looked at my files from the Files app, and there were no folders at all. I don't remember what should they be, but like pictures or downloads folder, you know... I am not exactly sure how did this happen, but it seems that I fully emptied my phone.
I am quite lost and unaware of how could I fix this. Do you think I could make those folders myself, or is there any possibility to download ~everyting~ again? Is there a file like that which would have all those folders too?
I am just assuming it would be related to those folders, but please do correct me if you think it is something else.
Thank you very much for any possible help
Click to expand...
Click to collapse
Do a Factory Reset in stock recovery or Format Data in TWRP. That should fix it.

DarthVader said:
Do a Factory Reset in stock recovery or Format Data in TWRP. That should fix it.
Click to expand...
Click to collapse
Thank you so much sir, I have been desperately fighting with my phone for the past 23 hours without success!
I already had tried factory resetting BUT in the phone settings, not recovery. Now I just opened the recovery and it did it automatically. Everything is working just as it should.

Related

I need your Galaxy On5 (USA) ROM

Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?

P9 Lite booting lock

Hi all, i'm new to Android Phones, so i started a few days with this phone. But now i think i've done a big mistake, i tried to erase everything from the phone, in a hope to "restore" to the factory state. Instead, i think i've deleted everything from the phone, and now, it only says "Your device is booting now..." and it doesn't boot. It's unlocked and rooted, i've deleted it from the TWRP menu.
So, is there anything that i can do, to restore it back? The model i think it's the VNS-L31, i'm downloading a firmware from the L21, can it be replaced or something like that? Thankx in advance.
*Edit* I found stock rom for my phone here in the fórum, but it says i need to have stock recovery but i have the TWRP recovery. Is there any way that i can do it, with that recovery?
*Edit 2* In Erecovery, when i try to download it says "Getting package info failed"
First of all... Why don't you have a backup in TWRP? ALWAYS back up your stuff before doing ANYTHING in TWRP.
Second: there is an option for factory reset within the EMUI system itself. Absolutely no need to mess around in TWRP for something like that. Of course you can "factory reset" in TWRP but this can also wipe your system which then requires you to flash something.
To your problem:
Since I luckily was not forced to flash a stock firmware yet, some more information would be nice.
In which format does the firmware come (link to where you downloaded it)? TWRP can handle .zip files. So if it comes as a .zip file, you can try flashing it through TWRP (really depends on what you downloaded!)
If you only need stock recovery, try accessing TWRP with your phone plugged into a PC.
This way it normally fires up the stock eRecovery.
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
iDeadSmack said:
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
Click to expand...
Click to collapse
Hmm maybe best way is to send the user that made it work a PM and maybe he can provide you a guide on how to do it.
And maybe he or you can then provide a guide here on how to do it.
This device is rather new and the forum is building up so there is a lot of work to do and a lot of things have to be worked around.
Hope you can fix it, like I said, I cannot really help you properly since I never had the problem and therefore do not really understand what's happening on your device.
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
iDeadSmack said:
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
Click to expand...
Click to collapse
Could you help me with this problem i have the same problem on Huawei l-21 ??
Always have a backup of your fresh system on TWRP. Then whatever happen just restore it whenever you think you messed up your device and you should be fine ALWAYS.

New update available for KIW-L24

Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.

Help! My LG k20 plus is boot looping, I don't know how to fix it

My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
bump:fingers-crossed:
megamind994 said:
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
Click to expand...
Click to collapse
did u ever get it figured out? i am in the same boat grr
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
megamind994 said:
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
Click to expand...
Click to collapse
thanks
Yeah. Sorry for the late reply given you guys found the fix by now, but yes, generally with the sort of severe mishaps from editing or accidental deletion of certain system files or directories, sometimes a dirty flash or even a totally clean flash after performing data ave system partition wipes, will just not fix or restore the device.
You would then need to do a complete stock image reflash either using LGUP or the official LG software recovery tool. If you know what you're doing, you could skip over reflashing stock in its entirety, if say you know the problem has only to do with a particular protected partition like modem, EFS, etc. But generally good practice to just recover all the stock partitions, refresh the device software to factory conditions, reflash your bootloader and recovery images, root STOCK or install custom ROM, so on and so forth.
If you're a frequently curious tinkerer, making backups will be crucial to your sanity.

Mi A1 persist.img - Custom Roms & Mac Change?

So it seems, some custom roms floating around out there can cause the WiFi Mac address to get changed, my understanding it has to do with the persist getting messed up.
There are a few tools floating around on XDA, one is the Persist_Resurrector.
But it's my understanding, if you have not messed with flashing another persist.img, then you are safe, and flashing back at Stock ROM will correct this.
I had one or two custom roms change my wifi mac, not sure which ones now, but I just flashed stock oreo back, and my original mac address is back, so I'm assuming I am all good, and this problem isn't bad, as long as you don't mess with another persist.img, flash stock back and you're golden?
How can I check if my persist partition is ok?
Thanks
Remove
cherryb8844 said:
Remove
Click to expand...
Click to collapse
@cherryb8844
Sorry remove what?
DoR3M3 said:
@cherryb8844
Sorry remove what?
Click to expand...
Click to collapse
I think he post on the wrong thread and ask mod to remove post
For your question I still don't know I'm really happy with stock experience and those persist partition froze me on moving to a custom ROM
But all MiA1 are not the same and yours seems to have survive also they have probably fix this problem on newer custom ROM build
Dead-neM said:
I think he post on the wrong thread and ask mod to remove post
For your question I still don't know I'm really happy with stock experience and those persist partition froze me on moving to a custom ROM
But all MiA1 are not the same and yours seems to have survive also they have probably fix this problem on newer custom ROM build
Click to expand...
Click to collapse
Ok on removed message...
I like the Stock too, I just wish Xiaomi could of put out a ROM, that doesn't have Gapps, and allow the users to pick their own...
I personally don't want anything google on my phone, or as little as can be possibly had...
DoR3M3 said:
Ok on removed message...
I like the Stock too, I just wish Xiaomi could of put out a ROM, that doesn't have Gapps, and allow the users to pick their own...
I personally don't want anything google on my phone, or as little as can be possibly had...
Click to expand...
Click to collapse
That would be bizzare if it happened for a AndroidOne phone not to have 'google anything' on the phone.
DoR3M3 said:
So it seems, some custom roms floating around out there can cause the WiFi Mac address to get changed, my understanding it has to do with the persist getting messed up.
There are a few tools floating around on XDA, one is the Persist_Resurrector.
But it's my understanding, if you have not messed with flashing another persist.img, then you are safe, and flashing back at Stock ROM will correct this.
I had one or two custom roms change my wifi mac, not sure which ones now, but I just flashed stock oreo back, and my original mac address is back, so I'm assuming I am all good, and this problem isn't bad, as long as you don't mess with another persist.img, flash stock back and you're golden?
How can I check if my persist partition is ok?
Thanks
Click to expand...
Click to collapse
As long as you have the original Xiaomi WiFi and BT Mac addresses, your persist partition is untouched.
DoR3M3 said:
Ok on removed message...
I like the Stock too, I just wish Xiaomi could of put out a ROM, that doesn't have Gapps, and allow the users to pick their own...
I personally don't want anything google on my phone, or as little as can be possibly had...
Click to expand...
Click to collapse
Why not just disable the Gapps you don't want.
I have these apps I don't use frozen (updates removed first):
Google play games
Google play books
Google play movies
Google play music
korean input
indic input
pinyin input
and zhuyin input all disabled.
I don't disable them because I object to Google, I freeze them because I don't want them to update, once updated you have two copies on your device, the outdated original stays in system, the new uses your storage (for an app you don't want).
I have also removed the Xiaomi installed user apps I don't use, feedback, mi store etc
joeyhuab said:
As long as you have the original Xiaomi WiFi and BT Mac addresses, your persist partition is untouched.
Click to expand...
Click to collapse
Hey joeyhuab, the persist got messed up, but I had the original WiFi Mac address from my router, LOL...
As far as the BT Mac, well, if the persist is messed up, is it going to change it too?
I figured out how to flash stock rom, using the persist.img with MiFlash tool and got it all working, I guess for now, not sure the BT Mac address was changed or not...
@kudos1uk, yeah titanium is good to freeze apps, I was doing that before in Stock...
DoR3M3 said:
@kudos1uk, yeah titanium is good to freeze apps, I was doing that before in Stock...
Click to expand...
Click to collapse
You don't need titanium, just disable then in the app manager.
kudos1uk said:
You don't need titanium, just disable then in the app manager.
Click to expand...
Click to collapse
Yes of course the app manager, I just mentioned titanium, I just find it easier to scroll through it, either way works...
DoR3M3 said:
Yes of course the app manager, I just mentioned titanium, I just find it easier to scroll through it, either way works...
Click to expand...
Click to collapse
Titanium is great but it needs root and I don't know if you can use it without changing the system partition and stopping OTA, app manager is safer as you can't disable important apps by mistake, Google only allow you to disable non critical apps.
I only mention it as you can keep your phone 100% stock without root and disable most Google apps which can be easily turned back on in the future, of course things like Play Store can't be disabled.
Back to the original topic...
So my persist was messed up, and I restored it, but the only way I could figure this is with the image on xiaomifirmware.
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
Hopefully this wasn't such a bad move, wifi works, and I see a mac address, but I'm not sure if they are the original, also I can make calls, so not sure if the imei is the original, or the network, just updated the phone to a new iemi.
How can I tell, or is there a way, if I have everything back to original?
Thanks
DoR3M3 said:
Back to the original topic...
So my persist was messed up, and I restored it, but the only way I could figure this is with the image on xiaomifirmware.
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
Hopefully this wasn't such a bad move, wifi works, and I see a mac address, but I'm not sure if they are the original, also I can make calls, so not sure if the imei is the original, or the network, just updated the phone to a new iemi.
How can I tell, or is there a way, if I have everything back to original?
Thanks
Click to expand...
Click to collapse
Is that way considered as flashing another phones persist file that not belong to our phone? Its just because we don't know where that persist (that available there) come from. I don't know for sure so CMIIW. Because i restored my persist by persist resurrector to get my original mac back. I don't wanna wreck my device by flashing another persist file that I don't know where it come from. One more time, correct me if I wrong.
upilguebu said:
Is that way considered as flashing another phones persist file that not belong to our phone? Its just because we don't know where that persist (that available there) come from. I don't know for sure so CMIIW. Because i restored my persist by persist resurrector to get my original mac back. I don't wanna wreck my device by flashing another persist file that I don't know where it come from. One more time, correct me if I wrong.
Click to expand...
Click to collapse
I don't think by flashing with this persist.img we call the phone damaged, just that the mac addresses are changed, maybe the imei too, but I made calls and text ok, so if it changed my imei, the carrier picked it up no problem...
For now, I'm trying to get the phone booted into edl mode, and oh what a PAIN in the, you know what! LOL...
Just a few simple cmds and the hours it seems to take to do things, heck, running Linux is simpler then this, I could of installed several Unix/Linux systems, by the time I have figured this out! LOL
Last go, I installed the 15 Seconds ADB installer by Snoop, and adb devices wouldn't show anything, then I tried the minimal adb setup/installer and same problem. Now I'm going to try the android sdk and install and the platform tools and see if it works this way, mind you, all this time, to make sure everything is clean, I have been constantly wiping out my box, reformatting it, and putting back a clonezilla image I have for Win8.... OH BOY, so much bloody work...
The WHOLE goal here is, that supposedly, you place phone in; fastboot oem edl, have the oreo rawprogram0.xml edited, so it has 'persist.img' in it, then flash with MiFlash and this is suppose to flash the original stock persist.img
BUT, I see that a lot of people are saying the only way to get edl is to open phone, and short out a few connectors on the board, which put's it into edl...
http://en.miui.com/thread-1680467-1-1.html
Also I read, you hold both up/dn vol and power and wait for phone to vibrate twice and this makes edl...
So I've been going to all this trouble to try and run; adb reboot-edl because fastboot oem edl always gives me some failed...
Hmm
kudos1uk said:
Titanium is great but it needs root and I don't know if you can use it without changing the system partition and stopping OTA, app manager is safer as you can't disable important apps by mistake, Google only allow you to disable non critical apps.
I only mention it as you can keep your phone 100% stock without root and disable most Google apps which can be easily turned back on in the future, of course things like Play Store can't be disabled.
Click to expand...
Click to collapse
if you want to remove the apps,you can use the bat script,no root needed,put in the adb folder and give the necessary permission,run the bat script..mi launcher is disable by default
View attachment 4526190
upilguebu said:
Is that way considered as flashing another phones persist file that not belong to our phone? Its just because we don't know where that persist (that available there) come from. I don't know for sure so CMIIW. Because i restored my persist by persist resurrector to get my original mac back. I don't wanna wreck my device by flashing another persist file that I don't know where it come from. One more time, correct me if I wrong.
Click to expand...
Click to collapse
roshan2989 said:
if you want to remove the apps,you can use the bat script,no root needed,put in the adb folder and give the necessary permission,run the bat script..mi launcher is disable by default
View attachment 4526190
Click to expand...
Click to collapse
Ahh interesting...
Thanks
P.S. Post all good, issue resolved, no need to reply...

Categories

Resources