Database Users

Back to Stock Kernel, only Nexus start screen

Hi,
I had the Faux Kernel 16 mako and wanted to get back to Stock Kernel because I wanted to update to 4.3. So I downloaded a Stock Kernel and flashed it. I didn't work it's stuck at the nexus start screen. So then I wanted to get back to 16 mako faux kernel and it's still the same.. It keeps loading. Can someone help how to fix this? Please?
Thank you so much in advance...
Does maybe the Recovery Kernel Faux help? The link is dead

easygoingx said:
Hi,
I had the Faux Kernel 16 mako and wanted to get back to Stock Kernel. So I downloaded a Stock Kernel and flashed it. I didn't work.. it's stuck at the nexus start screen .. now I wanted to get back to 16 mako faux kernel and it's still the same.. can someone help pls?
Click to expand...
Click to collapse
What android version, what ROM, what did you wipe (if anything)?
Sent from my Nexus 4 using Tapatalk 4

szucsgf said:
What android version, what ROM, what did you wipe (if anything)?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I have 4.2.2 and I wiped dalvik cache..

easygoingx said:
I have 4.2.2 and I wiped dalvik cache..
Click to expand...
Click to collapse
Try wipe cache, dalvik, and system (assuming you're using twrp) (you won't lose any apps or data), then reflash your ROM and gapps without flashing a kernel.
Sent from my Nexus 4 using Tapatalk 4

szucsgf said:
Try wipe cache, dalvik, and system (assuming you're using twrp) (you won't lose any apps or data), then reflash your ROM and gapps without flashing a kernel.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yes I'm using TWRP. Do you mean in the menue 'WIPE' which says FACTORY RESET Wipes Data, Cache and Dalvik (not includiung internal storage)?
I don't lose any apps and data right?
Ok I did. But now it says I have no OS when trying to reboot. I always have used Stock Rom... where can I reflash it?

easygoingx said:
Yes I'm using TWRP. Do you mean in the menue 'WIPE' which says FACTORY RESET Wipes Data, Cache and Dalvik (not includiung internal storage)?
I don't lose any apps and data right?
Click to expand...
Click to collapse
No don't do that, you will lose data.
Click on "Advanced wipe", then select only cache, dalvik cache, and system. Make sure you have a ROM zip file available in your phone's storage. Wipe those 3 things, then flash your ROM and gapps. You will not lose any apps or data. It will remove any leftover files from past kernels and you'll be back on your ROM's default kernel. I often do this when switching kernels. Not needed most of the time but I hope it helps you now.
Sent from my Nexus 4 using Tapatalk 4

szucsgf said:
No don't do that, you will lose data.
Click on "Advanced wipe", then select only cache, dalvik cache, and system. Make sure you have a ROM zip file available in your phone's storage. Wipe those 3 things, then flash your ROM and gapps. You will not lose any apps or data. It will remove any leftover files from past kernels and you'll be back on your ROM's default kernel. I often do this when switching kernels. Not needed most of the time but I hope it helps you now.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Puh, I did the Advanced Wipe without DATA. The problem is that I don't have a ROM Zip on my phones storage. Can I somehow access to the storage to put the Stock Kernel on the phone and then install it? So confusing! I am so thankful for your help.

easygoingx said:
Puh, I did the Advanced Wipe without DATA. The problem is that I don't have a ROM Zip on my phones storage. Can I somehow access to the storage to put the Stock Kernel on the phone and then install it? So confusing! I am so thankful for your help.
Click to expand...
Click to collapse
Wiping System essentially wipes the Android OS off your phone (but keeps your user apps and data), so once you wipe system you need to flash a ROM to be able to boot your phone. That's why I told you to have a ROM zip available.
You can use TWRP's built in file manager (Advanced -> File manager) to see if you have one on your phone. If you don't have any, you can use a root toolkit (like mskip's) to push a ROM zip from your PC to your phone: http://forum.xda-developers.com/showthread.php?t=1995688 or use an adb push command.

How can I make it connected with adb? I always type in adb devices but my device is not listed. I have it connected via USB to my computer but it won't find it. How can I make it visible? Should I turn it off or have it on in the bootloader or recovery? Sorry
It didn't work... it said something with insecure boot blah? Jesus.. I'm getting crazy. I just want to put the stock rom on my phone..

easygoingx said:
How can I make it connected with adb? I always type in adb devices but my device is not listed. I have it connected via USB to my computer but it won't find it. How can I make it visible? Should I turn it off or have it on in the bootloader or recovery? Sorry
Click to expand...
Click to collapse
I'm sorry, I'm not skilled at ADB. I believe USB debugging needs to be enabled, which is something you enable in Android. You may need to do some Googling to figure out how to push a ROM to your phone. The command is "adb push" so try searching that.
In general I always recommend keeping a copy of a working ROM zip on your phone just in case.
The toolkit I linked you earlier has the functionality to flash the Google stock ROM. That's something you can try as well. However that may cause you to lose your apps and data.

I am very desperate. I tried so much to just push a file on my phone with toolkit or adb.. now nothing really works. Does anyone know what I can do? When I use adb and try to push it always says read-only file.. do i have to do something before? It won't push.. I just want to add the stock rom on my phone. Is there any other way?
Ok, I somehow managed to push.. but I can't find it when I want to Select Zip Install the Stock Rom.. the file was TGZ. Is there the Stock rom as ZIP too? Or why is it not there where I pushed it?

Nexus 7 Bootloop, tried switching to F2SF...

So i downloaded TWRP 2.8.2.0 on my Nexus 7 4.3.3, i was rooted and everything. Then wiped my system in recovery.
After that i went to Advanced wipe and changed all the partitions to f2sf except internal storage, i was then going to flash my Slimkat rom, but then i couldnt access any folder! Tried a reboot but now it wont start... Can acces fastboot and so, but what do i do??
EDIT: So now i wiped them back to ext4, but when i pressed reboot twrp sais i had no OS installed? What to do?
Thanks for any help

You can still go back to the bootloader I assume so when you're on it connect your Nexus to your computer and run the Nexus Toolkit to flash Google Factory Image. Then you'll have to do the same steps as before, reflash a recovery, root and then flash the rom you want to use.

TWRP hangs on booting to recovery

Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.

kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684

kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.

Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?

kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.

Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.

the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.

kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.

Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.

kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.

is it possible to sideload supersu somehow?

kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.

I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.

i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.

supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?

kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.

kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(

kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726

kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.

Can't get back to Stock ROM (what am I doing wrong?)

History of what I did:
I first installed the first small OTA Update to 4.5.1 then unlocked the Bootloader and flashed TWRP v46 from xdvs23. And made a full TWRP Backup and flashed Magisk afterwards.
Everything worked fine until I debloated the System and wanted to make the OTA Update to 4.5.2 (1,5 GB), which didn't work. After I flashed it, the phone didnt boot anymore. So I restored the TWRP Backup, which doesn't work either.
Current status:
TWRP v58 is flashed and works. I can flash ExcperienceOS from Jamal, which works fine, too. But flashing the OTA file doesn't work and restoring my backup wont work either -_-
I would really appreciate help to get back to an OTA updatable version of OxygenOS!

If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.

djsubterrain said:
If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.
Click to expand...
Click to collapse
I did that several times. It doesn't work sadly... I get into a bootloop

You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway

djsubterrain said:
You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway
Click to expand...
Click to collapse
I might have, I will try that, thanks

Or just wipe everything, flash stock recovery, and flash Full OxygenOS zip.
https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2

I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...

How about trying to wipe everything from wipe menu except internal storage and then flash the oos zip followed by lazy flasher zip from here - bit.ly/lazyflasher
If this doesn't work then try changing to a different version of TWRP!

Casual_Max said:
I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...
Click to expand...
Click to collapse
You didn't do these steps wrong by any chance?
Steps To Disable Forced Encryption i.e, Decrypt Data
1. At first time when you open twrp, it will ask you to allow system modification.
2. Allow it and then flash the no-verity-opt-encrypt.zip file .
3. Then Go to Wipe-->Format Data.
4. Type Yes to confirm wiping of Internal Storage.
5. Now you have decrypted the data sucessfully.
Note: Dont try to restore the nanodroid backup which you have taken before. It may end in bootloop.
Click to expand...
Click to collapse
From here:
https://forum.xda-developers.com/on...der-intall-t3626122/post72777899#post72777899

ok, there I see what caused my first bootloop. Thanks
But why doesn't flashing the Stock ROM .ZIP work on an wiped (fastboot format userdata) phone? What else do I have to do?
EDIT:
*** solved ***
I failed hard. Luckily the OnePlus Support is excellent and was able to fix my issue with a remote session using their official tools. The Phone and I are both happy again.
Thanks for all the help, though. I learned quite a lot while dealing with this issue. It's a very kind and nice community here

[HELP!] TWRP createTarFork() error 255 when backing up data

I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left

I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.

Pro4TLZZ said:
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Click to expand...
Click to collapse
What was corrupt? How did you fix it?

keeganjk said:
What was corrupt? How did you fix it?
Click to expand...
Click to collapse
Something in the partition, so I didn't restore that

Pro4TLZZ said:
Something in the partition, so I didn't restore that
Click to expand...
Click to collapse
Which partition? I just wiped my device and reinstalled FreedomOS.

keeganjk said:
Which partition? I just wiped my device and reinstalled FreedomOS.
Click to expand...
Click to collapse
Userdata partition

Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
OK.

Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.

keeganjk said:
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
Click to expand...
Click to collapse
I'm sorry I can't help you more

Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom

I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.

dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
What's the difference between TWRP and bluspark TWRP?

dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
I can't restore; I deleted all my backups in an attempt to free up space.

I think I found the solution!
1. Go to Wipe in TWRP, swipe to factory reset
2. Download:
OnePlus Recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
OxygenOS: http://oxygenos.oneplus.net.s3.amaz...3_OTA_015_all_1708252353_e6d7756780064352.zip
3. Rename recovery image as recovery.img, boot phone into fastboot, plug into computer, run these commands on the computer:
fastboot devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
4. Open recovery on phone
5. Select Forgot Password, will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select Install over ADB or Install Over USB or something similar and plug phone into computer.
7. Run 'adb sideload oxygen-os-filename' without quotes on computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probobaly isn't, so don't shut it off or unplus USB.
9. Download Bluspark TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=26601&task=get
9. Reboot into fastboot, plug into computer and run these commands on the computer:
fastboot devices
fastboot flash recovery bluspark-twrp-filename-location.img
fastboot boot bluspark-twrp-filename-location.img
10. Success (hopefully)

Oh. Wait. Now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?

the solution to this was to boot to your previous rom that u have made nandroid backup with and then setting up the same password/pin in settings > security. When you then boot into twrp it will ask you for the pin/password to decrypt your data partition and then you can flash the nandroid backup(you have to have the same password there). here it is obvious that you are trying to flash data partition that uses different encryption password (in case of stock rom there is non) and this obviously wont happen.
maybe another solution would be to connect externally usb and unmounting data partition and then restoring from usb...

I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?

Need4Sneed said:
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Click to expand...
Click to collapse
For me flashing normal oxygenos with magisk 16 and formatting data and trying to make it boot with the new flash and then rebooting into recovery and restoring made it work. I guess it has to do with the right filesystem having to be made first.

hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.