Hi folks,
I have a strange phenomen in my phone. I unlocked the phone yesterday, rooted it with the most current (I think) root tutorial for the Mi Note 4, installed TWRP; went fine, still does work. Installed those two zips named verity & supersu.
I then rebootet it, downloaded root checker and I saw it was root. Used some root file explorers to test it, works.
Phone gets rebooted sometimes. It works all the time. Now the ALL launchers don't work at all. They got some NUllPointerException in Java.
I downloaded Microsoft Launcher, Evie (don't know both) for the sake of testing and both didn't even start, theycrashed and ask me to send bugreports or cancel.
Every system launcher is crashing. I factory resetted. It worked, but the systemlauncher still crashes and it won't even boot properly. It's totally weird.
I did never erase the ROM or change it! The only things changed were recovery.
BUT there was one thing. I accidentally (because somebody was talking to me, damn) put the thing into boot.
I then sideloaded boot.img from the Stable ROM for the Red Mi Note 4 and it booted. It worked. Menus worked.
Now suddenly this.
My dumb guess is it has something do with rooting and replacing the boot.img. But WHY will it work for days and then suddenly stop? Doesn't make sense.
Has anybody any idea?
Related
phones been fine for 440 hours (uptime since last time this happened) - since i lost the virtual keys last time and had to use sonys software to reinstall everything.
now after a reboot this happened again. disabled all xposed mods and the menus returned but now with orbot and folder mount running i had endless reboots. only after uninstalling the other 2 apps did this stop.
anyone else had anything like this?
wish i had recovery - stupid win8 and locked bootloaders
sony update service with full wipe.
did that last time. 2 weeks later happened again. stopped when i made changes mentioned in OP
Looks like you've been using an incompatible Xposed module or possibly other mod(s). Install them one by one again and see what triggers the crash (if you feel like re-flashing your ROM again)
Btw, it's fully possible to unlock your bootloader using Win8. It's a little wonky, but it's possible (unless your bootloader is unlockable). Or you know, you can install Recovery for locked bootloaders, but you can't flash custom ROMs, but you can make NAND backups.
A little off topic: I installed uTorrent yesterday since i had to download a torrent, and after i was done with it and uninstalled it, my ZU crashed and rebooted. Once it booted up again it crashed again, and again and again. Luckily i had a NAND backup on my SD card, so that problem solved itself, but lesson learned; no uTorrent anymore.
"Fun" fact: This also happened with uTorrent on my Galaxy Note.
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
tommo123 said:
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
Click to expand...
Click to collapse
Recovery is not a problem once you're rooted. Go to this thread, download and run the file, press "Oui oui, mademoiselle" or something like that and voila, you got Recovery. Easy peasy. It'll take you five minutes. Just remember to make a NAND backup once it's up and running. It's a life saver, as you already know.
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
tommo123 said:
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
Click to expand...
Click to collapse
Yup! Good going mate! I see you made it without any issues
Hey all
So after a botched Cyanogenmod install on my AT&T GS3, I am having some issues with the stock ROM. Here's what happened: I tried to install CM using the windows installer, everything went well until the end and then I got a prompt on the phone prior to it rebooting "Root access lost, fix? Yes/No". Regardless of choice, phone would always boot back to stock ROM. Asked for some advice on the CM forum and was told KNOX was the issue. I then rooted the phone using Towelroot, and then installed Super SU. Super SU when opened for the first time said KNOX was installed, did I want to disable it, I chose YES. Re-tried CM installer, same issue, just boots back to stock ROM.
At this point I gave up and just re-installed all my apps and settings, synched my Google account etc. Since then I can no longer download anything from any Google app, it just says "Download failed". So Gmail attachments, links, Chrome etc. nothing downloads. Although stock Internet downloads are fine. Swiftkey now errors saying "Cannot save language pack" then crashes, Swype keyboard keeps on re-enabling itself after I turn it off, and apps that worked fine before are crashing like crazy.
Last night I performed a wipe/factory reset after starting in recovery mode. This did not help. I also noticed that recovery mode boot screen is Cyanogenmod boot screen still, so guessing factory reset is not exactly a full factory reset and it just wipes data/cache etc.
Seems to me like some kind of permissions issue. I downloaded Root Explorer and had a poke around. Permissions look fine (read/write etc.) on Downloads folder. Only thing that looked odd was there are 3 different file system areas so 3 different downloads folders (ie sdcard0/0/Downloads, storage/0/downloads and storage/legacy/downloads). Not sure if that is normal.
Just want to put it back to how it was. Any suggestions what to do next?
Cheers.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
I'm very new to the rooting community, and I'm well aware of all of the problems. I've messed around, and bricked my phone many times but always knew how to fix it by flashing the custom rom. I've did whole of April until I figured out the proper rooting my model's for 6.0.1 software, and the 7.1.1 software. I eventually got tired of repeating this process, so in May (after I properly rooted my device and everything worked perfectly) I backed up everything including my system in TWRP.
Now the problem is, after using the xui tuner from xposed installer a bit, my phone seemed working for a bit, and lockscreen worked, but it randomly kept restarting at the boot animation . I grew impatient and restarted my phone properly a couple times but it kept rebooting after I unlocked my phone or just waited at my lockscreen. I then started got scared that I damaged something in my system or software, so I went to use TWRP to restore my backup (which I also literally backed up on this Tuesday). It apparently was successful, until the bootlogo freezing and saying my kernal wasn't SEANDROID ENFORCING.
Then now, I kept reformatting my data and restarting but it wouldn't work, it kept failing. So I gave up, and flashed my stock rom. This worked, but I obviously lost all my data. So to possibly help someone, I want to list what I think could've been the problem. (Still new, so I may list alot of unlikely things. Also random order)
1. I didn't format my data before the first restore, thus it failing.
2. Improper backup, I either backed up unnecessary partions like radio, or TWRP just didn't backup properly.
3. My sd card, I had many problems with my sd card before doing this type of stuff, but it went away during may. During may however, I backed up my magisk modules to it too, but they didn't appear on TWRP. Meaning it may have stopped working again. It also deleted my root folder, where I held the magisk zip and uninstaller.
Now this could bring another problem, I was using Magisk and Xposed installer, while also having my stock framework, xposed framework, and sony framwork (this was to use remote play), and in result my phone couldn't handle it and the module from both Magisk and Xposed.
4. I backed up my system while using the ashyx encryption zip, meaning when TWRP restored encrypted files?
5? XUI Tuner, I modified too many things with the app and probably did something to to the root directory. (Most likely Unlikely)
6. I modified my build prop by adding more code like the android users function, and TWRP probably couldn't back that up so it restored wrong like in 2
7? I modified TWRP by using a custom theme in the recovery, making certain functions like backup and restore not work?
8. I was using an old version of TWRP, 3.0.2 instead of 3.2 because 3.2. However, this is because 3.2 didn't work with my phone, and neither did 3.1.
I now flashed the stock rom, and everything works again. I just have to re-root. I didn't lose much data really, and I backed up some stuff in samsung cloud anyway. I just wanted to make this thread so I can fix the problem properly in the future, in which someone else may need it too. This model of samsung phone really isn't popular in the community, so it really would be helpful to other people. The solution could also work for other J700 variants, especially J700T1 since it's the most similar.
P.S. This is also just a small thing to help people too. Rooting this model is actually pretty easy, there's just a catch for one version of it.
6.0.1 can easily be rooted, especially with autoroot. It's works well, and you don't have to lose anydata at ALL! However magisk is untested.
7.1.1 on the other hand does require to format it's data to work so you have to back up anything you want to keep.. Superuser for me made wifi and the flashlight inaccessible, so I had to use Magisk. Which worked fine. There are two different versions of this root though. (Tested Once) One is basically like how the stock rom and has the manual, mobile data quick setting, and battery settings. to get it, don't use ashyx encrptyion . The other is like how you got it your device and set it up normally, no manual or extra settings, and requires ashyx encryption for this. The one I used was the ashyx encrpytion, and I was fine using this method because I kinda already lost everything over and over so I didn't care (end of april).
Edit: Turns out the stock version happens when you flash the stock rom, then immediately flash a custom recovery, and formatting the data without launching the the phone. I think this happens because when you get your phone, and activate it with a carrier sim card it downloads the additional files for that carrier which allows and when you format the data it formats the carrier version instead of the default system on the phone.
I hope we can find a solution for the kernal problem, so other people can fix this properly.
I would also like to ask if someone can make a odin and TWRP flashable kernal file of both the 6.0.1 and 7.1.1 versions of the SM-J700 variants, but for now in this thread the J700T is fine, unless all variants have the same stock kernal. This could be a solution and very helpful.
I have a USA T-Mobile Samsung Galaxy J7 J700TUVU3BQK3 phone and Can someone give me links to where I need to download the firmware ROM for this phone & all the different software I would need to root this phone or modify-backup its operating system??? My computer operating system is windows and also does anyone know how to setup a multiple operating systems on a computer where u can choose to either boot to different versions of windows and lynux.?? Computer Lenovo Gaming Laptop & HP Pavilion Laptop.