I was on stock rooted 5.1.1 and got the update notification, so i flashed the stock rom again to unroot, partition gpt.bin wouldnt flash, so i skipped it and it still worked, booted into 5.1..1 no trouble, hit the ota install, no trouble, booted up MM, no trouble, flashed twrp, booted into twrp, rooted using when twrp asked, and rebooted system- or tried to. it shows the bootloader is unlocked screen, and stays there indefinitely.
so i booted back into twrp and wiped cache, dalvivk, data, but it still didnt boot into system. i factory reset via twrp, no help, i flashed the supersu zip, thinking it was twrps root that was problematic, but still same problem.
Im going to try flashing cm13 via recovery to see if that works, but whats going on? is it that failed partition flash from earlier?
how can i get back to stock, mm or lp?
EDIT: CM13 works fine, no problems.
I'm having the same problem can u tell me how you solved this problem? Plzz ASAP
Sounds like dm-verity... Reflash your ROM and use systemless root from now on, don't ever touch /system!
Its been posted over and over, DON'T flash SuperSU when asked by TWRP, as Aquous said, use systemless root.
Sent from my SM-T530NU using Tapatalk
Related
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!
Okay. Saw that CM12.1 came out, downloaded it. Flashed it. Forgot Gapps. So I kept getting the error message the Gapps crashed. Decided to flash back to 12, but still didn't have any Gapps .zip on the phone so it gave me the same error. Loaded my recovery, phone worked even if it was stock android bloated bs. But whatever.
Then I got a notification of an OTA update, figured I'd do that, then make a new backup before trying to reflash CM12.1 with the new Gapps package. Phone reboots, gets stuck booting to TWRP. Got home and downloaded Gapps 5.1, won't load past TWRP. Reflashed it with GL_G3_Flash2FixStuckRecovery.zip from here on XDA. Still no dice. So I queued up that, CM12 and Gapps 5. Still boots to TWRP. Then queued up that fix .zip, CM12.1 and Gapps 5.1, same ****. TWRP.
I'm going on a trip tomorrow, I'd quite like my phone to be operational so I don't have to use my ****ty burner. Any suggestions?
edit:
I can still transfer files to TWRP from my PC and access all of my TWRP functions, but it won't boot past that.
If you have a backup I would just restore to the previously working backup until the trip is over. Then when you come back worry about it. That being said, you said you took the OTA to Lollipop. Did it update successfully because typically it won't go through successfully if your d850 has been rooted. Are you on 20f? I would try flashing a rooted version of stock lollipop there is a few of them on here some are even debloated for you. If it works and you get a succeful boot then redownload the cm12 and Gapps and do a fresh clean install.
adosin said:
If you have a backup I would just restore to the previously working backup until the trip is over. Then when you come back worry about it. That being said, you said you took the OTA to Lollipop. Did it update successfully because typically it won't go through successfully if your d850 has been rooted. Are you on 20f? I would try flashing a rooted version of stock lollipop there is a few of them on here some are even debloated for you. If it works and you get a succeful boot then redownload the cm12 and Gapps and do a fresh clean install.
Click to expand...
Click to collapse
The issue was before booting and my recovery didn't work either. But I found a solution and was on CM12.1 the whole trip, so we're good.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
thus I don't have OS anymore, so I can't boot into download mode.
I have TWRP, I think the only thing I can do is just get stock .zip ROM. But I can't find it for my G930F, I downloaded some but they are all prepared for odin, not for recovery.
Could please anyone give me a download link for a flashable stock rom?
Or any other ideas?
Thanks
You had TWRP but didn't make a backup?
Technically it doesn't have to be a stock ROM, you could just flash a custom ROM and once you've got system back then you can flash back to stock with Odin.
Beanvee7 said:
You had TWRP but didn't make a backup?
Technically it doesn't have to be a stock ROM, you could just flash a custom ROM and once you've got system back then you can flash back to stock with Odin.
Click to expand...
Click to collapse
So I do have LinkeageOS 16 installed now, but every restart, I can't mount /data in TWRP, I have to wipe it over and over. Why is that?
Another thing is that phone doesnt detect my SIM card (on stock recovery it did detect).
iirc that's something to do with encryption, but I've never experienced it so can't be sure.
Can you tried a stock Odin flash since installing Lineage?
Are you using the most recent TWRP?
Droiderat said:
Are you using the most recent TWRP?
Click to expand...
Click to collapse
I flashed newest stock ROM and updated twrp and everything seems to be working now
Weird, I didn't have to reflash LOS.
But yeah, I will write here if the problem still persists later.
So I was on tmobiles firmware rooted and something happened last night. It shut off and wouldn't boot up into system or recovery so after being frantic about it for about an hour and after some googling. I decided I was going to try a dirty flash (I think that's what I did)
I downloaded the latest ota zip from OnePlus 9.5.11 and used the all in 1 tool to boot to twrp and installed the ota zip there and installed twrp. Now the phone booted up to 9.5.11 on the international version and asked me to update to 9.5.13 which I let it. Then I rebooted back to twrp and installed magisk and reboot again. Bootloop happened so I went back to twrp and deleted my modules and rebooted again and it was fine and then reinstalled my modules....
Now for the actual question, should I be worried about corrupt data by doing what I did?
I really didn't want to lose my data, I have titanium backup but I can't get twrp to make any backups because I use OOS parallel apps
Bump
Anyone have an answer or any info to add?
If you didn't lose anything, then you didn't lose anything.