Everytime I restore my stock back up (167-35-5) I can't seem to mount system, magisk and SuperSU seem to flash fine and it appears to be rooted but no other zips will work (except rom zips) because the system isn't mounted (and won't)......anybody know why this is? It seems to only happen on my stock back up which I like to go back to sometimes. I just want to be stock rooted with a couple of modifications but this is stopping me. Anybody have any clues?
Related
Hello
I already saw 2 similar posts/questions but nothing seemed really to help, people just somehow managed to make it work. miraculous
I have a backup so i restored after having this issue without any problems. But still I want to use my custom ROM
Coming from Rayglobe 3.2 I updated to the latest TWRP x.x.3.3. (i think), however. When wanting to flash the ROM, it says in the console that it was unable to mount /system. In the mount setting I can't click on /system neither.
It stays in a loop, saying it is flashing the ROM, but nothing happens.
I know how TWRP on G2 can take forever, especially when wiping. But this is a real loop as far as I can tell. Since I updated TWRP, wiping doesn't take much time neither.
Did anyone have a similar issue and/or a solution?
Thank You
Hello,
today I managed to brick my device and restore it to working state, and I wonder at what point I made an error.
So here's what I did:
Had stock lollipop 30b
Rooted using oneclick root+recovery
Installed twrp using autorec
Xposed etc. and used it for a while without problem
Decided to flash something new
AOSPA 5.1.1 seemed like a good choice
Flashed bootstack, that was mentioned in aospa thread, system and gapps
Wow, that was smooth, but I needed my apps next day so I decided to restore my stock backup
Restored backup and ended up with phone in 9006 mode
Later I did some stupid moves that made whole situation worse, but that's not the point.
I backed up and restored everything that twrp allowed me to, so not only system and data, but also boot, efs, modem, recovery, sns etc. Could this be the cause? I didn't change bootstack, because I thought, that I had the needed one (autorec puts kk bootstack, right? and aosp roms also require this).
What should I do to avoid such problems in the future? I'll probably flash a lot, trying to find best possible rom for me, so it's neccesary to now whatto avoid.
And tip for future newbies like I was: if you can enter download mode, then use it, flash tool won't wipe your device data when you're using normal flash. When you've got normal working system to begin with then you can tinker further.
(Also there seems to be no way to recover from demigod critical error, even though it says it enters recovery. Then it's only this method with shorting capacitors on motherboard (fix real hardbrick)).
Cheers,
Marmelada
You can flash the patch (go back to LP from Sombons), flash, reboot recovery, restore stock rom and reboot.
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:
One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.
I've had this happen before on other phones, usually fixed by just installing a different rom or restoring a backup. Not here.
I finally unlocked my bootloader on the XT1607 (the Motorola site just randomly worked one day), installed TWRP & the 7.1.1 Soak Test (from here). I forgot to backup 6.0.1, so I backed up the soak test which was booting and working flawlessly. I was using it for a while, but I did a factory reset inside TWRP and it randomly said "cannot mount storage" and when I rebooted, it was into TWRP. It wasn't working at all, so I got LineageOS 15.1 and flashed that. Same error, "cannot mount storage" and back to TWRP. I went into Wipe>Format Data and then reinstalled Lineage. The "cannot mount storage" error was gone, but still booting into TWRP. I tried AOSP Extended, CyanogenMod, Paranoid Android. roms with gapps, roms without, with & without supersu or magisk. Nothing worked. So then I thought that restoring my backup (of all partitions) would fix the issue. It didn't, still booting back into TWRP. I'd also like to mention that plugging the phone in still worked, I can view the files in file manager, sd card works, etc.
So, no clue what to do here. What's wrong? It all started with that simple factory reset from twrp.
edit: I found that if I boot into bootloader and press start it will go into android, but hardly a permanent solution.
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
sumit1327 said:
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
Click to expand...
Click to collapse
Heyyy, thanks man. Worked like a charm.
My phone was rooted for the longest time without any problems, but some time ago (I'm assuming after the Treble update) apps would not detect root, although any app that was already using root could continue doing so.
I checked Magisk, which said root was not installed. I booted my phone into recovery, and somehow my phone had the stock recovery flashed on it. I tried flashing TWRP on it again, and it worked. Except, when I rebooted my phone into recovery later again, it went back to stock recovery.
I have no idea what's going on, and would really appreciate some help.
(PS: I do know how to update my phone without the phone reverting to stock recovery, I've done it many times before, so that can't be the problem)
update: I tried flashing TWRP again (through bootloader), and this time I jumped straight to recovery. It showed all the directories as if my phone had just been completely wiped. Internal memory 0M. No files anywhere. Didn't even have a downloads folder.
In a panic, I rebooted my phone, but my phone was actually untouched, no data wipe whatsoever. I'm even more confused about what the hell is happening now.
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
It's the version. If I use 3.2.3.0 or 3.2.2.0 I get no files. But 3.2.1.1 works for some reason. You can also install pie now. There is a link in the one plus 5 forums here to hydrogen os. It's Chinese version but that doesn't matter. It is in English. You will need to uninstall a few Chinese bloatware apps and flash gapps. But besides that I don't see much difference. If anything the hydrogen os looks nicer. I'll add some screenshots . Developer options was enabled from first boot, with the advanced reboot menu I noticed.
Also, if you have root the TWRP app can flash recovery from in the OS.
Fif_ said:
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
Click to expand...
Click to collapse
It's frustrating for sure. Lol