Develop Bugs

***need help please***

two days ago, i rooted my phone using simple root, nand unclocked and flashed clockwordmod and everything. i was using fresh rom, and i wanted to use the vanilla lockscreen. but in order to do that, i needed to flash amons ra. i tried doing that, and somehow i got rid of my clockword recovery mod (and amons ra didnt work) so whenever i went into recovery mode, it just stayed at the screen with the phone and triange and red exclamation mark. i tried running the recovery windows .bat file, but it didnt work. and i tried running the ruu .exe file to unroot my phone, but everytime it said it couldnt find my device, even though it was connected via a usb chord. i tried it in charge only mode, disk drive mode, and htc sync mode and none of them worked. i tried using rom manager, but everytime i tried doing something it said error attempting to run privilidged scrips or something. i tried downloading the superuser .apk file and installing it onto my phone, but that didnt work either. the terminal emulator didnt work when i tried to flash something, it just said it couldnt find the file on my sd card, even though i put it on there. help?

Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.

any suggestions?

Yeah, answer my questions or provide more info so you can get better direction.

you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.

SilverZero said:
Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.
Click to expand...
Click to collapse
ill try your first suggestion. and i cant boot any rom right now, because rom manager isnt working. and im pretty sure my phone is rooted, because i still have dev tools and CIQ settings and all those rooted apps.
update: your first suggestion worked, except once i entered AR recovery, the only options i had were: reboot system now, apply sdcard:update.zip, wipe data/factory reset, and wipe cache partition. at the bottom, it said "E: can't open /cache/recovery/command,

t3project said:
you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.
Click to expand...
Click to collapse
i tried reflashing with simple root but it didnt work. can you give me a link for toasts method?

i had a similar problem, i used the OTA simple root, get that and plug ur phone back in with debugging on , one of the drop down menus will let you flash a recovery so flash clockworkmod

okay so somehow i managed to unroot it by wiping my data/cache..but now whenever i try using simpleroot or OTA simpleroot it doesnt work, because it says device is not found. i have it plugged in via usb, usb debugging is on, and ive tried it in charge mode and disk drive mode. anyone know what the problem is?

I'm sure there is a way to fix this, but I would suggest using the full root method by toastcfh.

okay i'll just reroot using that method, thanks. also, whenever im on my computer and im using command prompt, none of the adb commands ever work. do i need to download something for it to work?

Yes, you need the ADB framework. Read the guide (or the one by TheBiles, which is basically a rewrite). The ADB framework is a part of the Android SDK. You have to run ADB commands from the ADB directory (which is actually the "tools" folder inside of the SDK directory, wherever you extract that). Just cd to the tools folder, then run your commands from there.

Boot Loop stuck in Animation help.

Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,

Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4

Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351

Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.

I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk

Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!

?
Any other ideas?
Thanks!

Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!

Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.

Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*

"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results

Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!

Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work

[Q] Can't mount USB Mass Storage onto my PC as ICS has crashed on my Kindle Fire

I rooted my Kindle Fire using KFU 0.9.5 and flashed a custom ROM. It worked fine for a few days and then just crashed -- The options bar located on the bottom disappeared and the error message was: System UI has crashed. (I have attached two pictures for better clarity)
Also, whenever I boot up, there is no yellow flame that appears, it goes to the moving colourful discs straight on.
I tried using terminal emulator and entered many codes in some hope of mounting USB Mass Storage so that I can use KFU and restore my Kindle, but in vain.
I have tried EVERYTHING. I've been at this for 6 days now and am at wits end. :crying: I have read up close to a 100 articles; this was my last resort.
I just want to get the Kindle's stock OS back - no root, nothing.
And the only was is, I suppose, if I am able to mount my Kindle as USB Mass Storage onto my computer.
ANY help is appreciated!
AndroBoss.

I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app

jr71x said:
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
As it now runs on ICS, there is no Gingerbread for Kindle anymore on it. I can't wipe it clean from the device or atleast I don't know how to, please help?

All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.

Thepooch said:
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Click to expand...
Click to collapse
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless

Androboss1994 said:
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Click to expand...
Click to collapse
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452

kinfauns said:
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
WOW! Okay, thank you so much; I'll keep you updated. I'll do all this tonight! Cheers :good:

[Q] Terrible Kindle Fire (2nd gen) issue that can't be resolved

Hi guys I'm new here but not to rooting Android devices and such. I had a XDA account back in the Windows Mobile 6.5 days but I have no clue what happened to it so I just made a totally new account. I have searched for this issue top to bottom and I cannot find a solution.
So for about 3 weeks now I've been having this problem with the Kindle Fire I got for christmas. It's not bricked, but I tried to switch to the AOSP stock JellyBean 4.2.2_r1 ROM from CM10.1/SGT7 version9. When I did this the kindle seemed to booted up fine, and when the setup process was done I had no Navigation Bar or a Status Bar, also causing the installer to malfunction and give an infinite installing screen (forcing me to reboot due to there being no Navigation Bar.). I thought to myself "OK I'll just reinstall CM10 and everything will be normal." Nah. The same problem was experienced when I finished the setup after reinstalling CM10. So I tried flashing an earlier version of CM10. No dice.
When I switched ROMs I made sure I wiped everything from System to Devlik. Still having the same problem. I have twrp 2.3.3.0 atm and I noticed that when I boot into twrp, off deck it says "E:Unknown File System: 'datamedia' " in the log. I also noticed that when ever I format something it says "Using rm -rf on......" So I decided to go and disable this as it might be why I'm having such issues. I went to settings and tried to disable this option but it wont let me disable it (as in it wont let me deselect the "Use rm- rf instead of formating?" option.).
When this happened I decided to look for an update for twrp to fix this issue. When I found the update to 2.4.4.0, it's only apparently able to be installed via fastboot. I as of now do not have a fastboot cable, nor can I make one. I would buy one, but money is a bit short. This also brings me to my next issue that I have searched to no end for.
No matter what drivers I install for my kindle Fire, my computer asks to install new hardware when I plug my kindle in. This is just for USB mounting. I haven't even tried ADB drivers yet. I can't mount USB storage in android or twrp. Twrp says "E:Unable to locate volume information for USB storage mode." When I am able to finally get some good drivers installed and working, only 30 seconds pass before they stop working and I'm not able to do anything. This forces me to transfer all files in ES file explorer over Wifi (which has to be installed manually by downloading the apk and copying it to the system/app folder and rebooting.).
After all this occurred I decided to go back to the stock Amazon OS and unroot to start from dirt. I went to Amazon's website and downloaded the 10.3.1 update for Kindle Fire second gen. It downloaded in .bin format so I just renamed the file update.zip and copied it to the root of the SDcard. After all that I booted into twrp and tried to install the ROM and it gave me this:
Installing '/sdcard/update.zip'
Checking for MD5 file......
Skipping MD5 check: no MD5 file found.
assert failed: is_substring("Otter2", file_getstring("/proc.product_name"))
E:Error in /sdcard/update.zip
(Status 7)
Error flashing zip 'sdcard/update.zip'
Udating partition details...
Once this happened I promptly searched the error on google. There was nothing exactly pertaining to this issue, so I searched the error in general and found that it happens a lot with ICS roms. They were all however errors that dealt with the system name being wrong but that's not exactly my problem is it? I even tried modifying the Update-script but that only gave me an infinite blue kindle logo screen.
If anyone can help me it would be greatly appreciated. This is my first run with any kind of tablet. I would like know how I can restore it back to the stock Amazon OS. If so how, I feel like I have tried everything.

Do you have a fastboot cable? First, I recommend that you get one.
Then, your best bet is to completely restore from stock and start over using the kindle fire restore utility in the development section.
Read my last post especially
http://forum.xda-developers.com/showthread.php?t=2035047
The update.zip isn't going to flash for you because of the asserts set in the updater script. Basically, once you flashed cyanogen your device no longer identified itself the same way.
The problem you have with formatting isn't a bug. You would be screwed if TWRP let you uncheck the box.
The E: thing is normal and not an issue..
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mindmajick said:
Do you have a fastboot cable? First, I recommend that you get one.
Then, your best bet is to completely restore from stock and start over using the kindle fire restore utility in the development section.
Read my last post especially
http://forum.xda-developers.com/showthread.php?t=2035047
The update.zip isn't going to flash for you because of the asserts set in the updater script. Basically, once you flashed cyanogen your device no longer identified itself the same way.
The problem you have with formatting isn't a bug. You would be screwed if TWRP let you uncheck the box.
The E: thing is normal and not an issue..
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Alright so I need a fastboot cable, and to restore to factory settings. I'm guessing TWRP would be gone when I do this right? Also Thank you. I think I'm going to stick to Amazon's OS for a while untill I can figure out the drivers.

Yes. Twrp will be gone.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I think the fact that CM10 changes the device name is the reason why I have so many driver problems. So I'm going to stick to Stock Amazon untill CM10 is on it's final release. Is there any way to change the device name back to the original? The only difference is a space between the names is Amazon Kindle Fire 2 and Amazon Kindle Fire2(on CM10).

The device name change doesn't effect the drivers. That only effects the update script. Once you are stock the device name will revert back
Make sure you have uninstalled all previous drivers for the kf.
Then make sure you used the drivers I suggest at the end of that thread.
99% of all the issues I see for this device are just driver problems.
--
Sent from my mind to your screen.

Are you sure that it doesn't? Because as soon as I installed CM10 all my drivers were suddenly incompatible.

Dwarphkin said:
Are you sure that it doesn't? Because as soon as I installed CM10 all my drivers were suddenly incompatible.
Click to expand...
Click to collapse
So you are probably using the Google device drivers from another phone or windows update or such. Cm10 drivers seem to work out of the box, but of you want both to work use my method.
The name change isn't what effects the drivers, it's the operating system that effects the drivers needed
When I first set up my system I couldn't access the devices USB Mount on stock but cm was OK. I went back and followed my own instructions... Now adb, fast boot and USB mounting works from both oses
--
Sent from my mind to your screen.

Oneplus 3 do not boot after installing OxygenOS 4.0.2

Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin

Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.

dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.

Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.