G'day all,
Hoping someone can help. (firstly I've searched on here over and over and some things have really helped, but can't find this issues on here)
Samsung Galaxy S4 GT-i9505 (originally with Vodafone rom)
Back story, I managed to put google rom via WINTEAM at some point in time (I don't recall how I did this now) this file - crdroid-6.0.0-20151208-jfltexx.zip (I still have this but not a md5 file)
Anyway, I wiped it under settings and basically stuffed it right up. Loops on WINTEAM (this part I had found in search and downloaded Odin3 v3.13) and Samsung Rom and a couple of others.
I9505XXUHOJ3_I9505VAUHOJ1_I9505XXUHOJ3_HOME.tar.md5
I9505XXUHQK1_I9505MAXHQK1_I9505XXUHQK1_HOME.tar.md5
I9505XXUHOL3_I9505TELHOL2_I9505XXUHOL3_HOME.tar.md5
CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
The last one actually fixed up the google install but was hoping to place the original Samsung ROM back on and now it doesn't help at all when I run again.
The top 3 are Vodafone, Telstra and Max a forum had suggested (from a page on here somewhere). All of these say pass in Odin3 when installing onto phone. But once it gets to the Samsung with what looks like dots shooting out from the word it never gets past this at all.
When I power up the S4 phone, to get to download screen. I have volume up to download or volume down to restart phone. Some places I've read say to select wipe, I don' t have this option at all.
I saw an option to install s8 rom to s4 which I would like to do, but the how to do that requires working software first and install TWRN or something like that.
I'm not sure if this will run fast or ok on this phone, but it isn't a MD5 file either.
I would like Samsung ROM back on as it (for me cleaner than google or maybe just what I've been used to). I'd like to give to my youngest child as their first phone.
I also had tried to place zip files and also unzipped files on the SD card on the phone, nothing worked for me as it looks like it is expected ODIN3 to work.
At this stage of the day, I would just like to have it functioning again with anything that works.
Any advice on what to do now would be greatly appreciated, also I'm truly sorry if this problem has been documented, I really did try to do my research first before putting this up here. I've been on this for weeks now
So quick update. through more research, I have managed to install TWRP and now have access to additional utilities through WINTEAM. I've now tried to install ROM through the Micro SD card.
I think it comes up with a mount error, but has rebooted and still stuck so can confirm just yet.
I've managed to go through the entire process of installing the PurifieD+ROM+v3.5.zip through the micro SD card in the phone. Asked me about all the options etc during the install. There didn't appear to be any errors at all. Asked to reboot. etc....
I even had sound on the bootup, Now I have the Samsung word on the main screen with a blue backlight just flashing. Been like that for nearly 10 minutes. Not looking good.
Have I got bad memory or am I doing something wrong?
I managed to do a wipe after I did an install and it booted up find. I had no WiFi but than installed the vodafone install that should be the original and all works now.
The amount of time I had been working on this, I really didn't think I was going to get it going. I honestly thought I had some hardware error going on.
In the end it runs now, I can setup and had to my child
so I've managed to now use several different ROMs but now I can't root the phone (it should be able to, has been before)
When I run Motochopper I get this error
error: only position independent executables (PIE) are supported.
Seems to happen no matter what rom I've installed. I can't seem to find an older rom running android version 5.01 now
Any help on how to root this. Would be great
Now says it has been rooted, but I do not get the teamwin boot menu option at all. more like just a text style menu for wiping and loading other roms.
Related
Hi All,
Please HELP.
I was a complete noob to rooting until I started this but spurred on by successfully rooting and overclocking / undervolting my defy I thought I would try to install Gingerbread so I can use the stupid stupid sky+ app which no longer supports 2.2.2.
Its all gone horribly wrong and I still dont know why as I checked and rechecked the prep but S..t happens so they say.
I have pretty much given up on this and will buy a new phone tomorrow if I cant sort today but would like to ask everyone that has more knowledge than myself on this subject (which doesn't narrow the field much!) if they have any ideas.
Well where do I start, I bricked my defy.
Apart from when I flash shadows rom (see below) I have only black screen, white led on usb connection, no recovery boot. phone is visible to rsd lite but nothing else. This happened after I lost sd card availability after reset / wipe trying to install a fixed gingerbread rom using RSD lite.
I could not flash back to froyo and every other recovery sbf i tried wouldn't work until I found an old sbf from shadow which actually booted up! YESS!! but then Nooo!. phone screen looks very nice - not sure what version it is but assume ICS (its got spareparts folder which I`ve not seen before) - and works as alarm clock and web browser but no phone function at all - no signal, no call or end call buttons - just not there! this (http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143) is the link where I found shadows version, couldn't wipe in between each step so just flashed 3 files in turn using rsd lite and it seemed to work - phone booted up after 3rd sbf was flashed. The rom is set up for developers and has some developing tools included acr, api demo,dev tools, hstcmd & redlinecap
Main problems:-
The rom is a tmobile version and I`m on vodaphone so maybe this is why there's no phone service but I wasn't prompted for an unlock code so assume its not locked.
The 2nd boot recovery no longer works even after reroot and reinstall (see below). I can surf the web very well via wifi - much quicker than before but downloads dont seem to work but only tried shortfuse.org and that site is apparently down atm and anything that requires google wont work as Gapps got deleted. I cant install GAPPS without boot menu.
recovery from main boot menu is unavailable and zip from sd just reboots.
I also cant connect my phone to my pc via usb and have the sd card available at the same time, as soon as the USB is connected the sd card is not available to the phone, I can see it on the pc and can read / write / delete from the pc - (usb debugging is disabled). when I access the sd card via file manager on phone (with usb disconnected) I can install some programmes that I have transferred from my pc; 2ndinit installed and said 2nd init installed ok again (after re-rooting) but still no blue led on reboot.
I've since tried everything I can think of or search for - After loosing the sd card availability I copied card contents to pc and reformatted sd card on pc. copied back the files immediately before flash attempt to sd as well as the rooted froyo backup I had and nothing changes. I have a titanium backup on the card but have so far been unable to install titanium again to try and restore it. no play acces as no gapps and when I try to access via pc and send it to phone it says installed but its not on the phone. every other file on the sd card results in error parsing file or file type not supported.
BTW when I say originally that I lost sd card availability I have now realised that it was the problem with having the usb installed at the same time which caused it and if I had unplugged it may have worked but still dont understand where this problem came from but I did have usb debugging turned on at the time.
I have scoured these holy pages for 2 whole days and tried several fixes which have probably really messed up everything even more but nothing has changed with the usability (or not) of the phone. A lot of the old links found were dead or taken over by a fake install of filemanager that my antivirus caught was a trojan. Due to this I may have missed an avenue or 2 but think I`ve tried everything I can.
At this stage I do not know exactly what I`ve tried as the list is endless but it includes reflashing the green lense kernel, attempting to reflash the original rom and any other recovery, fixed or stock roms I have found which don't specifically say only for defy+ and the only rom that allows the phone to boot is shadows above and that has no functionality.
I would love to install the latest cm10 build but cant get into the 2ndinit menue so unless someone knows away to flash it using RSD lite I`m stuck.
I do not even know if the cm10 would work as I`ve probably messed up the kernel and the original rom so the 2nd init may not get a look in.
Any help would be greatly appreciated. You'll find me under the stairs mumbling to myself and probably dribbling a bit - my wife thinks I`ve gone mad and is not talking to me until I get another phone or fix this one but I hate admitting defeat on technical problems.:crying:
PS I dont mind if I fix the issues with shadows rom, go back to any stable build or get cm10 working I just need the phone.
Thanks in advance, Tim
update
Hi All,
Just a quick update on this thread as I`ve had a bit more of a play and think I`m getting somewhere possibly.
I have now eliminated the problem of not being able to see the sd card files in file manager when the usb is connected.
How? - i haven't got a clue, i just unsuccessfully tried flashing a few more roms and when I reinstalled shadows rom i could view files whilst connected.
Also the 2ndinit now gives me the green led when it installed the 2nd boot but unfortunately I still dont get the blue led on reboot.
Another strange thing is I dont get the round M logo on boot but motorola written in white??
If I could just get to the CW recovery on boot I could install cm10.
Any suggestions?
Thanks
Tim
fixed by flashing with JDGC_U6_2.13.0
YESS FIXED BY FLASHING JDGC_U6_2.13.0 SBF using RSD lite.
Many thanks to everyone that helped via another thread http://forum.xda-developers.com/showthread.php?t=1217016&page=2, I thought they were far too many issues with this phone to repair but the latest froyo rom and kernal in the above sbf worked fabulously.
As has been said on several posts flashing this SBF will not allow you to return to the uk stock rom after (to return a phone under warranty etc) but if you're stuck with a brick then this should clean up your phone to original settings to allow the install of cm10 or another rom of your choosing (as long as its build 6 or later)
Hi Guys!
Sorry, I couldnt find any problem similar to mine regarding note 3.
Device: N900W8 Canadian (Rogers)
TLDR: After flashing a rom a second time (First time was perfect) phone says its in factory mode and now stock lockscreen doesnt work at all no matter what settings. In factory mode wifi is one of the settings it says isnt suppose to work but it does work, and Im extra confused.
Steps leading to the problem:
- Rooted using cf auto root
- twrp to backup entire stock rooted rom
- flashed Darthstalker v6
- phone works flawlessly, except with gps issues which I suspected was not a rom issue
- decided to test it out anyways, tried to restore my stock rooted backup but for some reason failed (Honestly have no idea why)
- flashed Darthstalker v6 again, complete clean install to see if GPS fixes itself
Phone now boots up normally, but on first boot up it showed a short popup that disappears shortly saying something like this
"Factory mode is ON, in this mode some settings such as wifi may not work blah blah blah"
Thing is, it does work, so far the only difference that I see from this mode is that I cant have a lock screen no matter what setting I put on it. Right now forced to use an alternative lockscreen (Go locker).
Just flashed Jedi Elite v5 yesterday, same issue as above, but everything else is working fine...
Thanks for the help guys!
I suspect it is and EFS thing, but I dont know what that is.
I used root explorer to look in the folder and nothing seems to be inside (Even when selecting to view hidden files and folders)
Unfortunately since my original stock root backup did not work I have no way of restoring the original. If you think this is the issue can someone point me in the right direction to get my EFS folder proper? Currently I only see Backup/restore options. Not the full EFS folder that I think I might need.
Two more things I noticed
- 4 way reboot doesnt work, it just turns off the phone
- when playing youtube "An error occurred" appears for maybe 10 seconds and disappears. Video is playing in the background so its pretty annoying.
Download this file by firasusman and flash thru recovery. Don't know if the lockscreen will come back but if it doesn't reinstall whichever rom you have right now to fix the broken file.
Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.
Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Ghujii said:
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Click to expand...
Click to collapse
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Ghujii said:
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Click to expand...
Click to collapse
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
I will attempt to do this, since nothing since has work. I am about to get a new logic board for the system in the next 2 weeks. Towel root DOES typically work on this system, however the last time I attmpted it it failed to work outright. Im not sure what has changed with the device, but i believe reflashing stock is the best method. The phone now, will boot up, then skip the lock screen and go straight to the home screen, which is black with no pull down bar, or with no signal and there is no way to rectify it. Even if there were, it boots back down and launches back up and becomes locked at the ATT logo.
After a fair bit of messing with it, and recovery mode it will sometimes boot normally where it tells me that processes has failed and askes me to cancel the ''app''. This is the best option to update the phone and attempt root, but getting it here is so difficult because it reboots itself and the mode is rare to acquire. This problem either is due to the kernel, or the rom i believe. I also am to believe the powercell may have some issue, as i replaced the battery a few weeks back and it worked fine for about 1 week.
Booting into safemode doesnt work either as it skips over the lock screen straight to the home screen. Outsidce of replacing the logic board, or attempting another flash im at the end of the short rope i was already on in terms of options.
sway8966 said:
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
Click to expand...
Click to collapse
UPDATE: I found therein two methods to flashback to stock. I did so, then proceeded to attempt to flash from nb1 to nj4. Progress stopped there when it flung an error 7 at me. So this means either something in my phone is corrupted or the file i downloaded from the above mentioned forum is corrupted. I also attempted flashfire, but seen as it STILL crashes at random due to process errors thats almost impossible to attempt.
Original thread "https://forums.oneplus.net/threads/root-op5-twrp-dissaster.742632/"
Video of current STATUS "https://youtu.be/GBWbid59f1E"
Current state of my problem -- STUCK in a screen at Drive Screen "an empty modal opens" Also looking for -- OnePlus 5 OxygenOS 4.5.15 rom --
OP5 EUROPE (if this helps to know what kind of phone I got, I know there are some differences in countries, dont know if it happens with OP specifically)
Currently trying to fix this using:
twrp-3.2.1-0
OnePlus5 Oxygen 4.5.15
-----------------------------------------------------------------------------------------------------------------
After reading plenty of other Threads with similar problems, I am clueless of whatelse to do but to exhibit how I disgraced my phone in hopes for somebody to help me.
I know I am 100% guilty of all that happened but I still somehow hope to get help.
Now the proper what happened.
After the purchase of some apps that seemed to encourage me to root my phone from Android Store, to get more features, I decided to give it a go.
So I got myself:
twrp-3.1.1-0
The Rom from Cyanogen
SuperSu v2.79-20
Granted myself access to booting and usb debugging after becoming a developer (granted by the university of tap your phone screen like a monkey smashing buttons, I figure this is even an inside joke from actual Devs)
I followed a tutorial that said next thing was installing twrp and stuffing my rom and my super su in my phone after rooting it, here is when things turn dark after installing the rom.
I saw my data was wiped and thought I had erased its memory, and instead of just putting back the things that I had to install I clicked on another tutorial of a had that had a similar problem (I can provide links later if requested).
In this tutorial the person, said that I should go to Advanced Settings -- WIPE and try and reformat my SYSTEM and my DATA, (heres when I wish my future-self would have come and stopped me because after this it all spiraled into madness)
After this happened my phone said I had no OS, so I didnt know what to do, I had no idea, I tried recovery mode but there was nothing to recover.. , I tried plenty of things really. reformating, downloading more ROMS , when I tried to install any of this Roms a new surprise awaited for me, my phone didnt know it was a OnePlus5 anymore it decided asume a misterious identity now he was " " instead.
I googled this, and a guy had a work around in wich I had to go into the rom and into the META-INF --COM -- google -- android -- updater-script
and inside this very archive delete the script that validated wich phone I had, this solution wouldnt work with any rom I had because they all said "updating the img was unsuccesful" at this point I was asking myself only one thing "WHAT IMAGE?!?!" a second ago there was no OS at all and now there was an image to update?.
I kept trying roms until one worked the stable official version, now I managed to install the rom rebooted, to find that the OS seems to have been installed, but.. when I introduce my pin things begin guetting funny again...
My SIM doesnt seem to be recognized its called "Slot 2" and when I enter the pin it and "SWIPE UP" as the phone suggests it gets stuck at a panel called "Drive".
I am guessing I am having an issue with the drivers but this is only a guess, I really have no Idea how to fix this, I tried to look up if somebody else was strugging with a FREEZE at DRIVE.
but it seems that nobody else fell into the spiral of foolishness I did, please help me find a way into a solution.
When I try to recover from the phone and install from "internal storage" doesnt allows me as there was no such thing.
use codeworkx twrp
Use a Keurig and just breathe
try flashing a twrp recovery. then boot to recovery. then push via adb a recent oneplus rom. then install the rom. then reboot to system and see if it is working.