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.
Related
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.
Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric
Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric
Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric
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.
Hi,
A few days ago I unlocked my bootloader and tried to install a ROM on my phone, more specifically the latest version of Bootleggers, to my surprise it didn't work and now I have a serious problem, because of my lack of patience(I didn't wait for health to get better to buy a bigger memory card, mine is only 2gbs sad life), I didn't back up my phone (nooby and stupid, sry guys), and now my phone doesn't want to boot into any OS I put on it (even the original one), I've tried pretty much everything (I know off), do mind that i only have 2 days of experience so I don't know that much. If anybody knows anything that might change my phone for the better I would appreciate the help.
Stuff that happened
I think I might have deleted something I should't have when trying to install Bootleggers for the first time.
I have successfully installed a OS ones, Havoc OS 2.9 (through ADB though), but I didn't like the interface so I deleted it and tried others, Resurrection Remix and ASOP, none of them worked so I tried flashing Havoc through ADB again, but this time it failed, it stopped in the middle of booting like all the other ones.
I can get into Recovery, eRecovery and Fastboot mode.
I don't have ROOT (Magisk) on it (at least I think), I installed it ones, but my OS didn't load so I tried deleting it afterwards and I got a error in the terminal probably because I didn't have it installed.
I still don't have a bigger SD card, I'm gone buy it tomorrow tho.
Info
Phone - Huawei P10 Lite
Model - LX1A
Firmware - WAS-LX1 8.0.0.368(C432)
Software (Mentioned in the quick start guide that came in the box) - WAS-LX1AC900B049
TWRP - 3.3.1 (also 3.2.1 but only for the MTP function(sometimes it gives me a black screen after opening it))
Problem - Phones starts booting the OS I put on it, but then stops and returns or to Recovery or eRecovery.
I dont know what more info to put here, like I said earlier nooby (and pls dont hack me if ive put the wrong info online, thx).
AlphaReigN said:
Hi,
A few days ago I unlocked my bootloader and tried to install a ROM on my phone, more specifically the latest version of Bootleggers, to my surprise it didn't work and now I have a serious problem, because of my lack of patience(I didn't wait for health to get better to buy a bigger memory card, mine is only 2gbs sad life), I didn't back up my phone (nooby and stupid, sry guys), and now my phone doesn't want to boot into any OS I put on it (even the original one), I've tried pretty much everything (I know off), do mind that i only have 2 days of experience so I don't know that much. If anybody knows anything that might change my phone for the better I would appreciate the help.
Stuff that happened
I think I might have deleted something I should't have when trying to install Bootleggers for the first time.
I have successfully installed a OS ones, Havoc OS 2.9 (through ADB though), but I didn't like the interface so I deleted it and tried others, Resurrection Remix and ASOP, none of them worked so I tried flashing Havoc through ADB again, but this time it failed, it stopped in the middle of booting like all the other ones.
I can get into Recovery, eRecovery and Fastboot mode.
I don't have ROOT (Magisk) on it (at least I think), I installed it ones, but my OS didn't load so I tried deleting it afterwards and I got a error in the terminal probably because I didn't have it installed.
I still don't have a bigger SD card, I'm gone buy it tomorrow tho.
Info
Phone - Huawei P10 Lite
Model - LX1A
Firmware - WAS-LX1 8.0.0.368(C432)
Software (Mentioned in the quick start guide that came in the box) - WAS-LX1AC900B049
TWRP - 3.3.1 (also 3.2.1 but only for the MTP function(sometimes it gives me a black screen after opening it))
Problem - Phones starts booting the OS I put on it, but then stops and returns or to Recovery or eRecovery.
I dont know what more info to put here, like I said earlier nooby (and pls dont hack me if ive put the wrong info online, thx).
Click to expand...
Click to collapse
Hi,
have you tried to enter into eRecovery and click download and flash and then tried it?
for one thing i know most of some of you might be happy to see me here so whats up i am fine but stressed
so i was helping someone to get lineage OS running on their phone and i managed to get that part successful but lineage sucks for me unless theres alot i missed on how bad everything went, crashes, cant access my screen during a call etc.
so now i want to get another OS but i ran into this issue, i couldent access twrp, i tried to ADB the boot command no go so i reinstalled twrp (same verson i had 3.3.0-1) and now nothing boots just sits at the LG screen, so i said %^&* it i redo the whole phone from scratch but that one is a fail to, i cant get factory reset to even come up, when i do the button command it will show the circal with eraseing and reboot and just sits on the verizon screen. im guessing i messed up my recovery and no way to figure this one out or what to ask google to find an exciting post about my issue,
well i managed to got it figured out saw a post similer to mine and did the steps, well in that post i had to get LGup but i managed to get a patched verson of LGUP, on there it said to do a partiotion DL option and select all, well that did not work for me so i said lets see if refurbish will work altho it ALWAYS FAILS well with the patched LGUP refurbish is an option, that got my stock OS going, i tried my recovery and still no go, but i did a soft restore and phone is back to normal, if anyone has any issues i be glad to help, this was new to me to getting it going
www.facebook.com/laser452