I did a stupid thing. I got away with it. Pure Nexus running normally now. Questions remain that boil down to this: why wasn't this a much bigger ordeal than it turns out to have been? I'd like to at least learn something when I do a bone headed thing. Here's the sequence of events.
1) 6p, pure nexus 7.1.2, latest vendor etc with twrp 2.8, rooted and running like a champ.
2) fooling around with different apps and so forth, took a look at a couple of dialers that I didn't much like, took them back off. After one of these the stock pure nexus phone app (I think this is just google dialer) started crashing constantly. Restoring titanium backups didn't stop it. Restoring a month old nandroid backup didn't stop it.
3) getting super annoyed (a poor time to start ripping stuff out), I wiped every partition on the phone in twrp except the SD card where all my recovery images and things like SuperSU.zip and some ROMs are stored. Wiped system, data, cache, boot, & dalvik cache.
4) restored a backup image and rebooted. Twrp gave me the no OS warning but I was on automatic pilot, swiped to reboot, and then I was like "what?! No OS! Wtf?" But I had already done the deed. Nothing to do now but wait to see what would happen. I was expecting moderately bad news - like I would end up monkeying with fastboot or adb if I couldn't boot back to twrp and flash the pure nexus image I was pretty sure I still had in storage.
5) result: pretty quickly I was watching the Pure Nexus boot animation so I knew that I was booting Pure Nexus. And this was the case. It took an extra long time like it does on the first boot but then there is was. Welcome. Let's get started. I set the phone back up and replaced most apps from backups and no harm, no foul. Also, the phone app stopped crashing. Bonus.
Now, I have no idea why I got the no OS warning from twrp. I'm sure that if I'd read it before I swiped to reboot and not after, like a bonehead, I would have done something like trying to flash the backup again or even the ROM I have on the SD card. Anything but reboot with the no OS warning on the screen. But the result was the same as if I'd flashed the ROM without, as I think of it now, flashing gapps or SuperSU. I had to go back and flash SuperSU but I put the apps back with titanium backup.
If anyone would like to take a shot at telling me how I got this result I think it might light up a dark area in my just-enough-experience-to-be-dangerous brain. Thanks in advance.
Truechunks said:
I did a stupid thing. I got away with it. Pure Nexus running normally now. Questions remain that boil down to this: why wasn't this a much bigger ordeal than it turns out to have been? I'd like to at least learn something when I do a bone headed thing. Here's the sequence of events.
1) 6p, pure nexus 7.1.2, latest vendor etc with twrp 2.8, rooted and running like a champ.
2) fooling around with different apps and so forth, took a look at a couple of dialers that I didn't much like, took them back off. After one of these the stock pure nexus phone app (I think this is just google dialer) started crashing constantly. Restoring titanium backups didn't stop it. Restoring a month old nandroid backup didn't stop it.
3) getting super annoyed (a poor time to start ripping stuff out), I wiped every partition on the phone in twrp except the SD card where all my recovery images and things like SuperSU.zip and some ROMs are stored. Wiped system, data, cache, boot, & dalvik cache.
4) restored a backup image and rebooted. Twrp gave me the no OS warning but I was on automatic pilot, swiped to reboot, and then I was like "what?! No OS! Wtf?" But I had already done the deed. Nothing to do now but wait to see what would happen. I was expecting moderately bad news - like I would end up monkeying with fastboot or adb if I couldn't boot back to twrp and flash the pure nexus image I was pretty sure I still had in storage.
5) result: pretty quickly I was watching the Pure Nexus boot animation so I knew that I was booting Pure Nexus. And this was the case. It took an extra long time like it does on the first boot but then there is was. Welcome. Let's get started. I set the phone back up and replaced most apps from backups and no harm, no foul. Also, the phone app stopped crashing. Bonus.
Now, I have no idea why I got the no OS warning from twrp. I'm sure that if I'd read it before I swiped to reboot and not after, like a bonehead, I would have done something like trying to flash the backup again or even the ROM I have on the SD card. Anything but reboot with the no OS warning on the screen. But the result was the same as if I'd flashed the ROM without, as I think of it now, flashing gapps or SuperSU. I had to go back and flash SuperSU but I put the apps back with titanium backup.
If anyone would like to take a shot at telling me how I got this result I think it might light up a dark area in my just-enough-experience-to-be-dangerous brain. Thanks in advance.
Click to expand...
Click to collapse
Why are you still using TWRP 2.8? 3.11 is the latest version now. Not sure if it's related or not though.
My bad. That's the SuperSU version. TWRP is the latest. 3.1.1
Moderator Information,
Thread closed at OP's request.
Related
I think I might RUU back to stock tonight, re-root, reformat my SD Card and just start fresh.
I've done so much to this phone, and I'm starting to see some glitches that I think I can solve by restoring to stock and going form there.
Now, if I can just remember how to run UnrEVOked in Ubuntu....
It does fix a lotta problems
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
Sometimes when my phone used to act a little slow, I'd just wipe cache and dalvik cache and it would go back to normal. Now that I create NAND's every few days and delete the previous one (in case I have to restore my phone, this way my NAND will be as current as possible), I just wipe both caches during the NAND process and I haven't noticed my phone slow down one bit.
dont need to un-root. Just run the format-all.zip twice, flash a rom and reload apps.
One of the glitches is that none of my Nandroids will restore, which is part of why I want to start fresh, so I can have a fresh stock/rooted nandroid, and several of my apps aren't restoring data with Titanium Backup, for some reason.
Now for some reason, and this MAY be ROM related, my Swype stops Swyping, even though I just updated it via the Swype Installer, uhh, several timeas.
One other thing, I originally rooted with the one step root method, which kept freezing up, then UnrEVOked failed in Windows, which is why I did it on my Ubuntu, so right from the start things were a little messed up.
Besides, I can't remember what stock was even like anymore... lol
HipKat said:
Besides, I can't remember what stock was even like anymore... lol
Click to expand...
Click to collapse
I predict you won't like "stock" ... and even if it's tolerable, the urge to slip into that old dark rain coat will be lurking!
lol... 5 mins after Stock, I'll be reaching for a new ROM, I can see it already....
See that's the difference. On the Moment, you almost HAD to restore to stock before flashing a new ROM.
Just seemed like a lot less problems that way.
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
You have to install the rooted version first then install the deodexed zip because I believe the deodexed zip only changes some system files, I did the same thing by mistake. So unfortunately you will have to SBF but when you get back up and running just remember to flash the root only zip first then boot into recovery and you can then flash the deodexed zip, hope this helps
luigi90210 said:
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
Click to expand...
Click to collapse
This is what I did last night, just before going to sleep. Thankfully, it worked, so only thing I had to really do was re-apply the theme and 180 LCD Density. Cool that we had the same idea but I'm still concerned about the backup not working, because I definitely don't want to make a habit of SBF'ing any time I don't like a new ROM, though I'm probably going to wait for LibertyGB before I flash another, and I'm fairly certain I will like that one
Thanks for taking the time to read and comment, really appreciate it.
I tried to go back to my stock bg backup also. It went ok and started up but I got force close on all my blur apps. I couldn't get the fc's to stop so I also had to sbf and reload everything.
Here is my situation. I acidentally installed a custom rom over my stock JB 4.2.1 installation and I want to know if there is a way to restore my original JB rom without loosing my root and recovery. My current plan is to use TWRP recovery to wipe all caches and internal memory. I have a stock JB rom and after clearing everything I will reflash the stock rom.
I know I should have made proper backups, but I guess this is how I will learn. My goal is to make my nexus 7 the same as when I bought it, but I want it to still be rooted. Will my plan work?
Thanks in advance for any replies.
I'd say use mskip's Google Nexus 7 Toolkit (found here) or Wug's Nexus Root Toolkit (found here) and be done with it. I use mskip's toolkit (personally) and have no issues with it. Use it to restore the N7 to factory shape (4.2.1 is the JOP40D build, the latest, if that's your intention), then boot it up, enable the USB debugging, get back into fastboot mode then use the toolkit to root it, you're done.
If it takes more than a few minutes to do this (which I've done several times in the past week) then you're doing it wrong.
A clean wipe is going to kill the root which must be redone and only takes about a minute itself.
OR, another alternative:
1) Flash full factory ROM
2) Unlock bootloader if not already in that state
3) soft-boot any custom recovery you want to use with fastboot:
fastboot boot recovery-image-file.img
4) Overflash a minimal root package (Superuser.apk + su OR SupserSU + su)
Moral of the story is that even if you flash a completely stock ROM with no root, because you have an unlocked bootloader you can install whatever you want right over the top of it without ever having booted it once.
I suppose that a toolkit might also be able to assist you with such things, but doing things from the command line tends to be better for learning how things work under the hood.
Wug's toolkit will help you do just that. You can even put back a stock rom and root it again
Thank you. It worked perfectly and now I have a brand new clean installation.
I have one last question though. After I logged in with my g-mail, my device started to download all my applications automatically. I had a titanium backup that contained about 70% of my apps and so cancelled the downloads so that I could restore the backup. (I have capped internet so downloading apps that I had backed up seemed like a waste). So now I want to know if it is possibile to download the other 30% of my apps from the store automatically because would prefer to avoid pressing the install button multiple times. I've been looking for some kind of option but I was unable to find it.
Thank you for replying so quickly, it is great to have an operating nexus 7 again.
Fallen9900 said:
Thank you. It worked perfectly and now I have a brand new clean installation.
I have one last question though. After I logged in with my g-mail, my device started to download all my applications automatically. I had a titanium backup that contained about 70% of my apps and so cancelled the downloads so that I could restore the backup. (I have capped internet so downloading apps that I had backed up seemed like a waste). So now I want to know if it is possibile to download the other 30% of my apps from the store automatically because would prefer to avoid pressing the install button multiple times. I've been looking for some kind of option but I was unable to find it.
Thank you for replying so quickly, it is great to have an operating nexus 7 again.
Click to expand...
Click to collapse
I've had mixed results with the auto restore. Sometimes it works, sometimes not so much. Can't say that I blame it though, what with flashing different ROMs, restoring old backups of different ROMs, having the backup feature turned on sometimes & sometimes not...
At this point, the Play Store app on the N7 seems to show me (in the My Apps section, "ALL" listing) every app I have ever installed on any of my devices linked to the same account (including a Google TV device). Not quite what you are asking, but it's certainly better than a few generations ago where - if the auto-reinstall failed - you would have to try to do the same task from nothing but your memory. (Or restore an old backup and have a look-see what was in there)
good luck and enjoy your tab
So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?
shredder47 said:
So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?
Click to expand...
Click to collapse
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?
simms22 said:
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?
Click to expand...
Click to collapse
I wiped data, and I don't have a previous ROM or nandroid to go back to, because I (stupidly) wiped EVERYTHING last night, and I've been working on fixing it since then .... I'm currently booted to recovery though, and I may just push a new ROM to it and try again
says my SD card is read only? trying to remount it as rw
I ended up having to reflash all the stock images...
could be worse.
keep a copy of your latest running rom/kernel/gapps in your storage, for just in case. thats my normal procedure, if you dont want to keep a nandroid backup in your storage, because of its size. but a nandroid backup would be ideal
Having the same issue. Tried installing new Carbon nightly (with factory reset) and didn't boot past Google logo. After that I restored my nandroid, which lasted for about a day or two. Today I started getting force closes and phone won't boot. Now I'm backing up everything (ADB rules ) and will try stock image.
Dont feel bad. When twrp updated I didn't notice wipe internal as I usually wipe all but USB in bottom but it was too late. I had swiped my finger and lost everything. Worse? My computer crashed. So RMA backordered so I bought new s2 for backup. I have to fix before sending back. But its not broken. All asurion does is push files and make sure it boots. They wipe everything. So I did most of the job for them lol. I feel stupid as I've never had a problem in four years. Bam I got too far comfy and forgot the twrp updated and had no idea what was added. I will just find a computer and fix or they will get a wiped device with twrp lol not that I think they will do anything as I've heard far worse but I did it so I'll pay if they mention.
Sent from my Nexus 4 using xda premium
As the title says, could one of you fine people run through the process to flash twrp, swap slots, and backup, then the process to restore this backup when needed? All without getting stuck in bootloop and wiping?
I'd like to run LOS but want the option to restore my setup if I encounter jank, like the missing Gboard swipes I had on the first LOS install I tried. Ended up having to wipe and reflash because of that. Thx!
Sent from my PH-1 using Tapatalk
It's in the FAQ. Invisiblek recommends flashing TWRP to the other partition and then switching partitions again within TWRP to complete your backup. What I want to know is how to perform an adb backup properly on this device. When I do adb backup -all -apk, the file turns out to be only about 13 mb's. https://mata.readthedocs.io/en/latest/
Airwolf79 said:
It's in the FAQ. Invisiblek recommends flashing TWRP to the other partition and then switching partitions again within TWRP to complete your backup. What I want to know is how to perform an adb backup properly on this device. When I do adb backup -all -apk, the file turns out to be only about 13 mb's. https://mata.readthedocs.io/en/latest/
Click to expand...
Click to collapse
I've read the facts several times and I'm not feeling it. It seems you enter fastboot and immediately swap slots, then boot twrp and swap slots again, then backup? What about restore? And when I reboot out of twrp back to my stock rooted ROM must I flash the boot.img for my rom "F" or face bootloop again?
Sent from my PH-1 using Tapatalk
Eric_Sheill said:
I've read the facts several times and I'm not feeling it. It seems you enter fastboot and immediately swap slots, then boot twrp and swap slots again, then backup? What about restore? And when I reboot out of twrp back to my stock rooted ROM must I flash the boot.img for my rom "F" or face bootloop again?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Restore would be the same process, but not sure about the boot.img. This is why I want to perform an adb backup. The partition system on these phones is presenting a lot of obstacles for developers, and with sales so low, it's unlikely that we'll ever see a development community at the level of phones like OnePlus. I've been reading the Pixel forum a bit to try and learn more the partition system since the phones have been out longer and they have a stronger community. I have tried several times to perform a TWRP backup on both partitions, and it's never completed fully. Usually freezes around 90% and I have to force reboot and delete the backup. Haven't tried it without encrypting the backup yet though. Maybe that's the issue. If you are able to complete a backup, I would suggest deleting your fingerprints first and/or pin, as that can cause problems on restore.
Airwolf79 said:
Restore would be the same process, but not sure about the boot.img. This is why I want to perform an adb backup. The partition system on these phones is presenting a lot of obstacles for developers, and with sales so low, it's unlikely that we'll ever see a development community at the level of phones like OnePlus. I've been reading the Pixel forum a bit to try and learn more the partition system since the phones have been out longer and they have a stronger community. I have tried several times to perform a TWRP backup on both partitions, and it's never completed fully. Usually freezes around 90% and I have to force reboot and delete the backup. Haven't tried it without encrypting the backup yet though. Maybe that's the issue. If you are able to complete a backup, I would suggest deleting your fingerprints first and/or pin, as that can cause problems on restore.
Click to expand...
Click to collapse
Another issue I've run into is that I "allow modifications" upon booting twrp but it doesn't always allow writing to system, read only. If I could learn a reliable way to backup, restore, and boot every time I'd be a lot more comfortable!
I guess I have more time to tinker but every time I have to setup from wipe again I like the phone a little less and want to move to my OnePlus 5t. I really prefer the EP, most things being equal. Form factor is a huge plus for me.
Sent from my PH-1 using Tapatalk
Eric_Sheill said:
Another issue I've run into is that I "allow modifications" upon booting twrp but it doesn't always allow writing to system, read only. If I could learn a reliable way to backup, restore, and boot every time I'd be a lot more comfortable!
I guess I have more time to tinker but every time I have to setup from wipe again I like the phone a little less and want to move to my OnePlus 5t. I really prefer the EP, most things being equal. Form factor is a huge plus for me.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I agree. Not sure exactly what the benefit of swiping to allow mods is. At this point I've already had to wipe the entire device once, and I just don't want to mess with it anymore until we have some more reliable methods of flashing with TWRP, and until we get some more ROMs. This is why I'm just running the stock ROM for now with Magisk and Xposed. I absolutely hate the stuttering screen scrolling, and not crazy about the haptic feedback either, but the form factor of this phone is just so perfect, I just can't bring myself to get rid of it. How do u like the 5T? I love my OP3, and am strongly considering getting one.
This is something you'll eventually have to get used to as more phones launch with the A B partitioning scheme and system-as-root. The 5t didn't launch with Oreo in order to avoid having to implement all these things including Treble.
I suspect they'll eventually improve the tools to make it easier especially when Samsung finally ships Oreo. The OP6 would also likely drive more work to make it easier.
Airwolf79 said:
I agree. Not sure exactly what the benefit of swiping to allow mods is. At this point I've already had to wipe the entire device once, and I just don't want to mess with it anymore until we have some more reliable methods of flashing with TWRP, and until we get some more ROMs. This is why I'm just running the stock ROM for now with Magisk and Xposed. I absolutely hate the stuttering screen scrolling, and not crazy about the haptic feedback either, but the form factor of this phone is just so perfect, I just can't bring myself to get rid of it. How do u like the 5T? I love my OP3, and am strongly considering getting one.
Click to expand...
Click to collapse
I've wiped 4 times I think, it's cool 1-2 but after that it's a huge pain! I need magisk hide for gear S3 Samsung pay and my bank app so no xposed for me. I root for that reason and substratum Swift black theme.
I've got to tell you, I had my OnePlus 5 set up perfectly and sold it for the 5t, now slow dev and the white effing navbar I can't seem to reliably get rid of is hurting it vs the EP. Also it's a little bigger than the OP5 and it pushes it into "too big" territory, it's borderline. I thought the bigger screen vs the front capacitive buttons was a slam dunk but now not so sure. No more long press for last app and double tap for recents on the on screen buttons is another bummer for me. I used those on the back button on the right and never had to reach the recent button on the left, huge usability improvement now gone.
Sent from my PH-1 using Tapatalk
ChronoReverse said:
This is something you'll eventually have to get used to as more phones launch with the A B partitioning scheme and system-as-root. The 5t didn't launch with Oreo in order to avoid having to implement all these things including Treble.
Click to expand...
Click to collapse
Agreed, and once we start to get more of these phones on the market, we should get better dev support for the PH1.