I have reverted to stock. I am on official 5.0.1 OxygenOS. I installed Stock recovery Locked bootloader still safety net is failing.
Any help please ....
Attached screenshot
This problem is on Oneplus3 screenshot is from internet of same app on redmi. But the error is same. first 2 are success rest two fails.
vjendra said:
I have reverted to stock. I am on official 5.0.1 OxygenOS. I installed Stock recovery Locked bootloader still safety net is failing.
Any help please ....
Attached screenshot
This problem is on Oneplus3 screenshot is from internet of same app on redmi. But the error is same. first 2 are success rest two fails.
Click to expand...
Click to collapse
How you reverted to stock matters. Did you wipe the phone completely before flashing stock?
tnsmani said:
How you reverted to stock matters. Did you wipe the phone completely before flashing stock?
Click to expand...
Click to collapse
1st I formatted system, data, cache, dalvik, internal
then I did factory reset from twrp
then I installed 5.0.1
then flashed Oneplus stock recovery
then booted the phone and did factory reset again
then locked the bootloader which did factory reset. Thats it.
vjendra said:
1st I formatted system, data, cache, dalvik, internal
then I did factory reset from twrp
then I installed 5.0.1
then flashed Oneplus stock recovery
then booted the phone and did factory reset again
then locked the bootloader which did factory reset. Thats it.
Click to expand...
Click to collapse
Why did you flash stock recovery? It is built in in the stock ROM.
Too many factory resets. If you wipe all including internal storage, no need for any factory reset. These might have influenced the outcome.
Do the wipes from ADB and flash ROM also through ADB, wipe Dalvik and cache and reboot.
Why does the screenshot say Redmi Note 3?
skymera said:
Why does the screenshot say Redmi Note 3?
Click to expand...
Click to collapse
When reading, read fully. In this instance, read the last two lines above the screenshot.
tnsmani said:
When reading, read fully. In this instance, read the last two lines above the screenshot.
Click to expand...
Click to collapse
When posting logs post the proper logs and screen shots. People will not read everything you type. So if you use a Screenshot from the internet (why would you even do that) instead of using a shot from the device.
zelendel said:
When posting logs post the proper logs and screen shots. People will not read everything you type. So if you use a Screenshot from the internet (why would you even do that) instead of using a shot from the device.
Click to expand...
Click to collapse
Not sure whether you are addressing me or why ..........
vjendra said:
I have reverted to stock. I am on official 5.0.1 OxygenOS. I installed Stock recovery Locked bootloader still safety net is failing.
Any help please ....
Attached screenshot
This problem is on Oneplus3 screenshot is from internet of same app on redmi. But the error is same. first 2 are success rest two fails.
Click to expand...
Click to collapse
Did you fix that . i have same problem :crying::crying::crying:
7afith said:
Did you fix that . i have same problem :crying::crying::crying:
Click to expand...
Click to collapse
Sometimes the su binary can be left behind , I believe there is an app called unsu me which will completely get rid of any binary left behind but you'll have to google it because I've forgot where I saw it...
Related
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3
buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore
buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)
buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh:
I can't take it ever since i updated my t210r to 4.4.2 problems galore. i flashed several roms still i get random reboots and app stopps. i wiped everything and flashed odin over and over and still i get random reboots and app stops its driving me crazy that update was the worst mistake i ever made surely there is someone out there experiencing the same thing or know of a way to fix
kgalv419 said:
I can't take it ever since i updated my t210r to 4.4.2 problems galore. i flashed several roms still i get random reboots and app stopps. i wiped everything and flashed odin over and over and still i get random reboots and app stops its driving me crazy that update was the worst mistake i ever made surely there is someone out there experiencing the same thing or know of a way to fix
Click to expand...
Click to collapse
Sounds like a dirty flash try another rom using transche myself which is fine.
i have tried that rom even nolekat and experience the exact same problems
kgalv419 said:
i have tried that rom even nolekat and experience the exact same problems[/
I would suggest disabling the tablet of the apps you are not using and install greenify which will hibernate the apps until you are using them.
Click to expand...
Click to collapse
kgalv419 said:
I can't take it ever since i updated my t210r to 4.4.2 problems galore. i flashed several roms still i get random reboots and app stopps. i wiped everything and flashed odin over and over and still i get random reboots and app stops its driving me crazy that update was the worst mistake i ever made surely there is someone out there experiencing the same thing or know of a way to fix
Click to expand...
Click to collapse
Try flashing the full stock firmware from sammobile; then boot into the stock recovery and do a full factory reset. If that doesn't work, then you may want to install a custom recovery and re-format (not wipe, but actually format) the data partition.
Ok will try that. After wiping the data partition what should i do?
kgalv419 said:
Ok will try that. After wiping the data partition what should i do?
Click to expand...
Click to collapse
I would boot into the complete stock system and see if you have any problems. If everything works fine when completely stock, then you can install a custom recovery and try some other roms.
Ok cool i really hope this works bud because I've tried everything even used twerp recovery to advance format system, data, cache and internal storage
gr8nole said:
I would boot into the complete stock system and see if you have any problems. If everything works fine when completely stock, then you can install a custom recovery and try some other roms.
Click to expand...
Click to collapse
still no luck gr8 i tried booting into stock still i get random app stops, like "unfortunately playstore has stopped"., "unfortunately systemui has stopped", "unfortunately touchwizhome has stopped", and all other apps depending on which one i'm using. they still come on back but its really annoying also i get random reboots. i feel like i have tried everything.
Did you ever get this fixed?
Did you ever figure out a fix? I'm having the exact same problem.
gr8nole said:
Try flashing the full stock firmware from sammobile; then boot into the stock recovery and do a full factory reset. If that doesn't work, then you may want to install a custom recovery and re-format (not wipe, but actually format) the data partition.
Click to expand...
Click to collapse
I've flashed back to the stock fimware from sammobile and I still have errors and random rebooting. So I rooted with CWM ad did a full factory reset, still the same problems. I've re-formatted the data and the data/media (/sdcard) partition,still the same problem.
gr8nole said:
I would boot into the complete stock system and see if you have any problems. If everything works fine when completely stock, then you can install a custom recovery and try some other roms.
Click to expand...
Click to collapse
Even a completely stock system, I'm having problems. I've tried wiping everything (cache, dalvik ,data/factory reset ) then flashing back to the stock firmware using Odin3 v3.09, and I'm still getting errors and random rebooting.
Has my t210 bit the dust?
Seems like a lot of people are having trouble with the new updates. I would try to find an older version of the stock rom and load it thru Odin 3.7 and see if you still have the same problems.
Same thing I'm thinking but I still have hope
Did any of you all clear your cache and dalvik-cache as part of the flashing process?
The 4.4 ROM is an update to the stock 4.2. If you use a custom ROM, you will probably need to reflash stock 4.2 in order to flash 4.4.
But this tab never had 4.2 only 4.1 and I did a complete wipe before flashing anything
kgalv419 said:
But this tab never had 4.2 only 4.1 and I did a complete wipe before flashing anything
Click to expand...
Click to collapse
Here's what I would do then:
Reflash 4.1, then try 4.4. If that doesn't work, flash all three consecutively. Gotta test around to find out what works.
Greaper88 said:
Here's what I would do then:
Reflash 4.1, then try 4.4. If that doesn't work, flash all three consecutively. Gotta test around to find out what works.
Click to expand...
Click to collapse
We have got a V4.2.2 Version, but this was ported from the Tab 3 sm-t110 lite.
Format and wipe all folders using none stock recovery like CWM this will empty all junk left behind
Should I erase all this everything I've included in the screenshot?
andynroid said:
Format and wipe all folders using none stock recovery like CWM this will empty all junk left behind
Click to expand...
Click to collapse
U there bro?
...What recovery you r using ? Cause the wipe n format is under in recovery mode (not stock recovery)
Yes everything must be deleted
I don't know what's going on here. I have the SM-T800, and I've tried flashing two different T800 ROMs but each just results in being stuck on the boot screen. I'm on 5.0.2 rooted with the latest TWRP installed. Am I missing some key step that's specific to this device?
ktimque said:
I don't know what's going on here. I have the SM-T800, and I've tried flashing two different T800 ROMs but each just results in being stuck on the boot screen. I'm on 5.0.2 rooted with the latest TWRP installed. Am I missing some key step that's specific to this device?
Click to expand...
Click to collapse
If you are already on lollipop you need to flash another lollipop Rom. If you flash a kitkat Rom you will need to wipe cache and data in recovery.
ktimque said:
I don't know what's going on here. I have the SM-T800, and I've tried flashing two different T800 ROMs but each just results in being stuck on the boot screen. I'm on 5.0.2 rooted with the latest TWRP installed. Am I missing some key step that's specific to this device?
Click to expand...
Click to collapse
Sometimes you need to update your base firmware so ROM, kernel, bootloader & modem etc all work together. After that, go through the process needed to flash the ROM. Best to search the ROM thread first of pre-installation requirements and if no luck, post in the relevant ROM thread with your entire firmware details and exact steps used to reproduce issue
Both were 5.0.2 ROMs (Iron, yTab). I wiped cache, dalvik, and data before flashing, maybe wiping data is what was hurting?
Thanks guys.
ktimque said:
Both were 5.0.2 ROMs (Iron, yTab). I wiped cache, dalvik, and data before flashing, maybe wiping data is what was hurting?
Thanks guys.
Click to expand...
Click to collapse
If you wiped data then it will take at least ten minutes to boot.
mine took fooooooooooooooooooooooooooorever. I actually thought something was wrong. But it eventually came on. weird.
I finally got PN on my PixelXL and just looked at storage and it says the system uses 19.9 GB and I'm wondering if I can clean the alternate slot to free up this space
My 128gb XL on latest update only use 6.79gb system
Sent from my Pixel XL using XDA-Developers Legacy app
You need to flash a factory image which will wipe all data as I had the same issue I believe its the only fix as you need a full wipe to fix and if your going to full wipe your better off to just flash a full factory image and be 100% factory fresh.
M9guy said:
You need to flash a factory image which will wipe all data as I had the same issue I believe its the only fix as you need a full wipe to fix and if your going to full wipe your better off to just flash a full factory image and be 100% factory fresh.
Click to expand...
Click to collapse
I had the same issue. This ^^^ was the only fix.
toknitup420 said:
I had the same issue. This ^^^ was the only fix.
Click to expand...
Click to collapse
Did you try > fastboot format userdata
cam30era said:
Did you try > fastboot format userdata
Click to expand...
Click to collapse
Formatting didn't work for me. I needed fresh system image too
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Yamalito said:
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Click to expand...
Click to collapse
If you are on Verizon, DO NOT LOCK BOOTLOADER! Just a friendly reminder.
Yamalito said:
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Click to expand...
Click to collapse
That's a silly way of wiping data. Factory reset from os or fastboot erase userdata will accomplish the same thing.
tiny4579 said:
That's a silly way of wiping data. Factory reset from os or fastboot erase userdata will accomplish the same thing.
Click to expand...
Click to collapse
If someone is going to format user data they might as well flash the newest factory image. It just makes sense its also preventative maintenance and can keep your phone running at top performance.
M9guy said:
If someone is going to format user data they might as well flash the newest factory image. It just makes sense its also preventative maintenance and can keep your phone running at top performance.
Click to expand...
Click to collapse
Flashing the image is fine. Locking and unlocking the bootloader is unnecessary and should not be done if you're just trying to format. Locking th bootloader while playing around with a messed up system is the perfect storm for a bricked device.
toknitup420 said:
Flashing the image is fine. Locking and unlocking the bootloader is unnecessary and should not be done if you're just trying to format. Locking th bootloader while playing around with a messed up system is the perfect storm for a bricked device.
Click to expand...
Click to collapse
Oh definitely, I never would recommend to relock the bootloader that would be just asking for trouble. I replied to the guy saying to just wipe user data, which if your going to do that it just makes sense to flash the newest factory image and make good use of wiping user data and get back to factory fresh in the process that is just a no brainer.
I agree that locking and unlocking bootloader is silly, it can cause trouble, I'm aware of that, however that was the ONLY thing that worked for me in this case. I tried everything and the storage was still at 19 GB. I'm sorry if the method that worked for me is silly and unorthodox but for me that is all that worked. It's happened to me three times.
Hey,
So im currently on holiday and dont get back home until the 13th aug.
I was on my phone last night until i ran out of battery and the phone inevitably died. I charge it this morning and the phone is stuck on the boot animation and has a slowly flashing blue led. I do get past the lg bootloader unlocked screen too and the android boot animation runs fine, just never completes. My phone is running bootloader unlocked, twrp recovery and the imperium rom. My model is h815 and s/n is 512 prefix. The battery was running pretty bad so it might be that. Either way it is stuck in bootloop and i am not sure how to approach it. I also have some internal storage that would need backing up if possible.
Cheers for any help
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
Thats interesting, never thought of that. I should be able to backup any files etc from the internal storage using adb right?
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
MattheewHun said:
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
Click to expand...
Click to collapse
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
jet399 said:
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
Click to expand...
Click to collapse
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
htr5 said:
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
Click to expand...
Click to collapse
Yeah i saw that post and was reluctant to do so as im on my holiday. Dont want to lose my pics either, even when im very sure twrp is installed correctly as i use the quick boot app to go into recovery quite often.