Did something change within the framework?
I did not wipe date...I flashed new radio, bootloader, wiped and flashed cache, flashed boot, system, and vendor.
My phone booted up fine, but all exsisting apps all force close.
Did I do something wrong?
I was coming from a custom rom (pure nexus) and flashing the stock images...maybe thats where the hiccup is?
for now I am just restoring my backup.
Waiting for someone to come up with a flashable stock 6.0.1 ROM, hopefully, so I can keep my apps/settings and do a dirty flash.
joho5 said:
I was coming from a custom rom (pure nexus) and flashing the stock images...maybe thats where the hiccup is?
for now I am just restoring my backup.
Click to expand...
Click to collapse
That was definitely the problem. If you don't wipe data and flash the stock ROM over the top you'll encounter issues.
Related
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4
Hello,
I'm currently running CM11 and I flashed custom dialer in TWRP and I can not restore back to stock dialer. Each time I flash nightly dialer stays the same. I assume I need clean flash of CM11 to overwrite it. But how do I do that? Just flashing currently nightly just upgrades what is there already, so how do I start from scratch?
All the nightlies I've seen are full roms. Wipe system, data, and the caches.
I have the batman rom installed on my g95ff now since my stock rom got boot looped when i tried to flash a boot logo that was a size too big.When that happened i flashed the stock firmware with odin aswell as stock recovery and it let me clear my cache/factory reset my phone to fix it.Sadly i lost my bootlogo and boot animation collection i had stored but i had most of my important apps backed up with titanium,so to make up for the lost data i rerooted with twrp,installed the batman rom and restored my apps back.The rom is really neat since i can customize more ui things such as the status bar aswell as my nav bar color which couldnt be done on the stock rom.So now that im familiar with installing roms,would i be able to try other ones simply by reflashing the stock firmware over the batman rom and reinstalling twrp?
So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.
the_scotsman said:
So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.
Click to expand...
Click to collapse
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.
iostoandroidconvert said:
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.
Click to expand...
Click to collapse
Yep, the "System" partition is where the ROM is installed. When you wipe that, you're essentially wiping the ROM from your phone.
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
UPDATE: I did do something stupid after all. I forgot that my Oneplus was decrypted. So all I had to do was go into TWRP and go to Wipe and format data to re-encrypt it.
Z-Blade said:
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
Click to expand...
Click to collapse
When starting fresh, wiping of internal storage should be considered. I recommended 2 guides here https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post77205633
My main phone got damaged so i am using this Moto G4+ phone temporarily. Years ago i flashed Resurrection Remix Nougat on this and the phone is really slow and laggy right now so I am hoping flashing a stock ROM will fix it but i am not sure how to flash the stock ROM. I know about the fastboot method but i am worried about bricking the phone and i really do not want to risk bricking it at all since this is the only working phone i have right now. I am worried about all these different bootloader versions and the 32bit/64bit thing. My current bootloader version is 1.07. Should i fastboot flash the ROM given here https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 or do i have to do something else first?
Thanks
If you're worried about bricking your device, I would initially try flashing the TWRP flashable of the Nougat or Oreo stock ROM (from here https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 ) This TWRP flashable will update your system, boot(kernel) and modem and should not update your GPT/bootloader (so you'd still be on B1:07). The stock ROM is 32 bit - if you're flashing, I would recommend you wipe data, after flashing, before booting - so ensure you back up (e.g. backup system, boot, data in TWRP) and keep that back up off your device.
If anything does happen, restore your backup and reboot.
echo92 said:
If you're worried about bricking your device, I would initially try flashing the TWRP flashable of the Nougat or Oreo stock ROM (from here https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 ) This TWRP flashable will update your system, boot(kernel) and modem and should not update your GPT/bootloader (so you'd still be on B1:07). The stock ROM is 32 bit - if you're flashing, I would recommend you wipe data, after flashing, before booting - so ensure you back up (e.g. backup system, boot, data in TWRP) and keep that back up off your device.
If anything does happen, restore your backup and reboot.
Click to expand...
Click to collapse
Thanks a lot!
echo92 said:
If you're worried about bricking your device, I would initially try flashing the TWRP flashable of the Nougat or Oreo stock ROM (from here https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 ) This TWRP flashable will update your system, boot(kernel) and modem and should not update your GPT/bootloader (so you'd still be on B1:07). The stock ROM is 32 bit - if you're flashing, I would recommend you wipe data, after flashing, before booting - so ensure you back up (e.g. backup system, boot, data in TWRP) and keep that back up off your device.
If anything does happen, restore your backup and reboot.
Click to expand...
Click to collapse
I was able to successfully upgrade to stock Oreo through that TWRP zip but unfortunately the phone is still laggy, Do you think that fastboot flashing the stock ROM or upgrading to custom Pie ROM will help?