Hi
I upgraded my LOS exactly as it was at wiki page described. With one exception. Instead of stock ROM as a base system I used LOS19. Wiki page does not described what kind of ROM should it be. Now I know that as base system have to be always STOCK ROM.
Well, lesson learned, but problem still presists. My LOS 20 works with few issues here and there, but main issue is USB problem.
Any cord which previously worked for me flawlessly, now does not work. under win I see an icon with ! in device manager. It is marked as device driver failure or something like that. This make me sick so badly. Because of that even MSM/EDL mode does NOT works...
Under linux no communication via USB at all. I did not check any logs but commands such as fastboot devices and adb devices returns empty lines.
only one thing which I managed to work is ADB over the wifi. This works.
My question is: can it be fixed? Can I get back to stock? does adb over wifi help with anything? I think that siedloading over wifi does not even exists, so I'm screwd pretty much.
My bootloader is one provided with LOS 20.
Well, new thing learned. When any custom ROM is used, then MSM tool might make thing worse. So I have to stay away this tool until I will have live stock ROM on my phone.
Figured out another thing. I can flash my phone without adb, fastboot either but I have to root the phone 1st. May I do it without USB access now?
Related
Hello
First of all, let me explain the situation:
My phone is the Oneplus One, currently with no OS, the reason being - because i wanted to re-root my phone after the Oneplus updated (this update was a while ago) either way many problems occurred and i figured the easiest way to re-root my device is to simply wipe it, and try again on a clean slate.
I attempted to wipe my phone, but did it the complete wrong way. Instead of using the OS's wiping strategy, i may of used the recovery's one instead, doing so i clean swooped the OS right off my phone.
At the moment, the phone has no OS installed - nor is the phone rooted. The phone isn't capable of passing files over through usb debugging because the computer doesn't recognise it no more. (It did have usb debugging turn't on). Of course i need to reinstall an OS on the phone. The TWRP recovery is working fine. But i do not know how to do it. I looked up things such as mounting, didn't really understand the vague explanations given by the helpers of this forum (i am slow haha ). If someone is able to point me in the right direction in how to simply put an OS back into the phone some how i would be grateful.
I did read up on one post that suggested making a system.img placing the OS inside and flashing it over using fastboot mode. Which brings me to the question. Is it possible to use command to install an OS on my Oneplus whilst in fastboot mode?
RazorCJ123 said:
Hello
First of all, let me explain the situation:
My phone is the Oneplus One, currently with no OS, the reason being - because i wanted to re-root my phone after the Oneplus updated (this update was a while ago) either way many problems occurred and i figured the easiest way to re-root my device is to simply wipe it, and try again on a clean slate.
I attempted to wipe my phone, but did it the complete wrong way. Instead of using the OS's wiping strategy, i may of used the recovery's one instead, doing so i clean swooped the OS right off my phone.
At the moment, the phone has no OS installed - nor is the phone rooted. The phone isn't capable of passing files over through usb debugging because the computer doesn't recognise it no more. (It did have usb debugging turn't on). Of course i need to reinstall an OS on the phone. The TWRP recovery is working fine. But i do not know how to do it. I looked up things such as mounting, didn't really understand the vague explanations given by the helpers of this forum (i am slow haha ). If someone is able to point me in the right direction in how to simply put an OS back into the phone some how i would be grateful.
I did read up on one post that suggested making a system.img placing the OS inside and flashing it over using fastboot mode. Which brings me to the question. Is it possible to use command to install an OS on my Oneplus whilst in fastboot mode?
Click to expand...
Click to collapse
See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
victor-zorro said:
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
Click to expand...
Click to collapse
Try reflashing it with the factory original firmware using their own flashing tool.
Once you got it working with that, then you can try flashing it with whatever you want.
Till then, there just too many variables with custom ROM.
Why is it suddenly impossible to update or log into miflash or miflashpro?
Tried all the usual issue fixs? Type c cable good. Drivers installed. Windows command prompt can see my Poco X3 NFC an can change recovery.
It just refuses to allow a log in page an will not work without log in?
Has anyone else had issues like mine?
Ive been trying to get it working for an hour now
Edit: I have a suspected culprit. Bloody timewasting windows 10 updates messing with drivers.
Grrrr. Will see it installing updates allows Miflash to work?
Bryceicle1971 said:
Why is it suddenly impossible to update or log into miflash or miflashpro?
Tried all the usual issue fixs? Type c cable good. Drivers installed. Windows command prompt can see my Poco X3 NFC an can change recovery.
It just refuses to allow a log in page an will not work without log in?
Has anyone else had issues like mine?
Ive been trying to get it working for an hour now
Edit: I have a suspected culprit. Bloody timewasting windows 10 updates messing with drivers.
Grrrr. Will see it installing updates allows Miflash to work?
Click to expand...
Click to collapse
No difference. I am just going to assume Miflash no longer works. Any other flash tools I can use? Without miflash to restore my device its no longer safe experimenting with custom roms. Fact.
Bryceicle1971 said:
No difference. I am just going to assume Miflash no longer works. Any other flash tools I can use? Without miflash to restore my device its no longer safe experimenting with custom roms. Fact.
Click to expand...
Click to collapse
Why? You can still use recovery versions of MIUI, or fastboot versions of MIUI, no?
I reflashed many many times MIUI or custom ROMs, and never used Miflash, got into various curious situations and always was custom recovery enough to restore my phone to a working state, only when I destroyed Ofox or Twrp in the process I had to use fastboot to reflash either recovery or MIUI...
So honestly, I don't understand this Miflash obsession which people sometimes here present, as Miflash is the only way to restore your phone...
jeryll said:
Why? You can still use recovery versions of MIUI, or fastboot versions of MIUI, no?
I reflashed many many times MIUI or custom ROMs, and never used Miflash, got into various curious situations and always was custom recovery enough to restore my phone to a working state, only when I destroyed Ofox or Twrp in the process I had to use fastboot to reflash either recovery or MIUI...
So honestly, I don't understand this Miflash obsession which people sometimes here present, as Miflash is the only way to restore your phone...
Click to expand...
Click to collapse
because its the best way out there to fix driver issues with correct firmware an unbrick softbricks when things go wrong with custom roms.
Have never found anything as good as its made for Xiaomi/Poco devices.
What do you use when things go wrong?
Bryceicle1971 said:
because its the best way out there to fix driver issues with correct firmware an unbrick softbricks when things go wrong with custom roms.
Have never found anything as good as its made for Xiaomi/Poco devices.
What do you use when things go wrong?
Click to expand...
Click to collapse
OFOX or TWRP, and when things go wrong fastboot - along with external sdcard with recovery or fastboot versions of MIUI, but as I said, I'm only using fastboot if I destroyed custom recovery while experimenting
Good for you.
I suspect most people are like me.
For the rest of us who might not all be super tech savvy when things go wrong or there is corruption of things or more commonly android bugs.
The forced flash of miflash provides a safe back up.
We're not obsessed with miflash. It's just good as a way to reflash firmware an start again.
Without it I am seriously considering going back to stock as it's no longer safe to experiment without it.
It's really that simple.
I am not an electronic genius so miflash provides the best way to avoid hard bricks of which I have had many
Hi
I use a Realme X, while I assume the model might be not relevant to this case.
I tried several methods to flash both stock Rom`s and alternative ones, I did use both adb commands and adb sideloading and the official Realme tool.
To me, as a computer expert but phone noob, it seems like something fundamental might be broken in some protocol or even hardware.
Whatever I do, the firmware flashes to a certain extend and cancels then.
In most cases, there is not even a error message, it just fails to flash completely and pretents everything is good.
The phone is unlocked, has 3.4 TWRP installed and I can access it via my computer.
I used two different Windows computer, in order to exclude the host OS as the source of the failure.
Also used around 3 different cables.
Moving data around also works, I already did try to move the ROM to the device and install it there, same.
The device ran perfectly fine before I decided to try another ROM.
Is there any log that I can provide?
Twrp log would tell what happens. Also mitool would make logs on the pc.
MiTool for a Realme device?
ShalokShalom said:
MiTool for a Realme device?
Click to expand...
Click to collapse
I miss read that.