Database Info

[Completed] Is it possible to flash over a ROM to Android?

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 :silly. 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 :silly. 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
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the OnePlus One at http://forum.xda-developers.com/oneplus-one . I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/oneplus-one/help where the experts familiar with your device will be best able to guide you.
Good Luck!

Need Guru to Discuss Rooting in general with me

I'm fed up with people on this forum. I keep trying to engage people in a discussion, a conversation to explain some things to me and No one seems willing. It's like there are No Rooting gurus that can answer my simple questions. On a forum full of Android developers, I'm very disappointed, I thought i'd get tons of help. If you read this, Please consider staying to have a discussion/conversation with me.
Preface to The Discussion:
I have used both Android and Linux in the past, I know what Super User is, I use it in Zorin 12 Linux and own a rooted (kingroot) android tablet. I am trying to get information on rooting my Figo Atrium phone by trying to understand Rooting better in general. perhaps this discussion will make since to you and together you can help me find a way to root my phone - But I Must have a back and forth or I'll never understand this. - I know there are many exploits to root a phone used by tools like kingroot. I know these exploits are many and varied depending on your phone's CPU architecture, and software and not all root tools with work with my device. . I know the bootloader has to be unlocked and one must have USB Debugging enabled in Developer Options. I know some phone manufacturers make tools that help you root your phone (MTK Droid Tools) So far, none of these tools can root my phone.
Let's Start The Discussion Here:
I was able to not root but my Upgrade my phone from Lollipop to Marshmallow. I did this using SP Flash Tool and these instructions (which were badly translated and which as you can see by the comments in the video, I had to correct due to bad translation) See this video and comments by me to understand. https://www.youtube.com/watch?v=EEIJM2YjNzE - I used SP Flash Tool and a Rom Figo provided. After I figured out the botched instructions, I was able to upgrade my device with no problems.
Question 1: Isn't this essentially the same process that is used for Rooting? It proves my bootloader is unlocked and the phone does have the ability to flash a new Rom. <- Based on That, doesn't it seem to you that my phone would be in fact Rootable?
If you think so, tell me why, if you think Not, tell me why.
Question 2: If you think So, then: Someone suggested to me that using a tool like Magisk or SuperSU may be able to root my device. Does this seem likely to you based on what I've told you so far? No one in the SuperSU sub forum can answer this question.
If you think No, then we'll discuss this more. I'll wait for your replies. Thank you.

Rooting is, simply said, placing a 'su' binary in the system folder. SU means switch user, when you give that command you're instructing Android to give you root user privileage. OEM's don't want that to happen so they won't include it in their ROMs. Tools like supersu are made to copy that 'su' file to the system partition. There are a lot of ways to explain this, I'm just giving you something quick and easy to understand.
Now regarding your questions;
1) Flashing anything requires the bootloader to be unlocked on most phones. BUT MTK phones don't. (Except some HTC phones). SP Flash Tool can flash any partition without needing to unlock. It's dangerous security wise, but this means its also easier to root.
Infact all MTK phones are rootable. So don't worry about that.
2) How to root? The best way to root is with supersu. (You can also try magisk if you want to use Android Pay).
You need a custom recovery like TWRP first.
I found one here which is for your same CPU. https://www.needrom.com/download/twrp-recovery-13/
^I am just giving you a link to recovery which uses the same CPU so It may or may not work. PLEASE take a backup of your original recovery before doing anything.
Now download SuperSU zip file from here https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Don't open it, just keep it in your sd card.
Flash the recovery using SP Flash Tool (check only the recovery box and select this file). Now unplug the phone and press Volume Up+Power Button to boot into recovery.
Then if it says swipe to allow modifications, swipe.
Now goto Install->Select the Supersu.zip file you downloaded->Swipe and reboot.
That's it! You're rooted!

Thanks.. again, you've answered things others couldn't. Much appreciated.
You say, " You need a custom recovery like TWRP first.
I found one here which is for your same CPU. https://www.needrom.com/download/twrp-recovery-13/
^I am just giving you a link to recovery which uses the same CPU so It may or may not work. PLEASE take a backup of your original recovery before doing anything."
Lets say Twrp doesn't work. What is this for, just to re-flash your original rom in case twrp fails at making a backup? ( I assume the tool makes your installed rom flashable in case the root doesn't work and you need to revert back to your original system) I have the SP Tool and the Rom for Marshmallow that works with my device from Figo. Can I use that if Twrp fails - or am I not understanding what twrp is used for? Just checking before I start this. Otherwise, I'll try to follow your instructions to the letter and see what happens.

Still Looking ?
STILL Looking? IF so, a few thoughts .... It is a nice phone for the price. The newer version eventually coming out looks even nicer, and for now, it is still my backup phone to my Figo Gravity. Discovered Figos when I got totally fed up with BLU phones.
ONE - If you have upgraded your Atrium to Marshmallow, as I did, none of the rooting methods that worked on Lollipop will work, so forget about them.
TWO - Down in Developer Settings you need to make sure OEM unlocking is allowed.
THREE - ASSUMING you have a TWRP build that will work, it is pretty simple. Take the ROM image that FIGO sent you and replace the "recovery.img" file with the TWRP (re-name it recovery.img and save the old one as recovery.old JUST IN CASE) file. It will be much larger than the factory ROM recovery image and that's fine. The scatter table, if you read hex addresses, provides for enough space to do this. Flash ONLY the recovery (TWRP) image, and be sure to DOWNLOAD ONLY with the SP FLASH tool. If uncertain, DO NOT PROCEED. It can be a real pain in the arse to re-do things if you accidentally format or upgrade things you didn't mean to. ASSUMING that worked, you can boot into TWRP by holding down the power / volume buttons (I assume you are familiar with this sequence).
FOUR - it is entirely possible that the next time you boot the thing normally, TWRP will be blown away. Happened to me a few times. There is some setting down in the boot image that causes this and I will have to dig up my notes to see exactly what the heck it was. It required taking apart the boot image - I used Carliv - fixing the one setting, and then re-packing and re-flashing it, BUT, you can ALWAYS keep replacing the TWRP image as needed. Inconvenient, but better than a sharp stick in the eye.
FIVE - when booted into TWRP, you should be able to flash SU, which will give you root, and it should STAY rooted after that unless and until you uninstall SU. FLASHIFY is STRONGLY recommended as a VERY useful app for rooted devices. TWRP, if you are unfamiliar with it, is SO MUCH MORE than just a recovery replacement. Handiest whole device backup there is. Has saved my bacon on several devices through numerous acts of personal stupidity. :crying:
SIX - IF ALL ELSE FAILS, you can ALWAYS revert to the factory image ROM. Just DOWNLOAD ONLY rather than Upgrade and DO NOT Format.

Fairphone Brick Fastboot / ADB

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.

Brick. Stuck at "Qualcomm Crashdump"

Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.

Ganapatya said:
Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.
Click to expand...
Click to collapse
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.

lm089 said:
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.
Click to expand...
Click to collapse
Thank you for your reply.
is your phone running stock OOS or some custom ROM?
Click to expand...
Click to collapse
Stock OOS, android 10, last release.
Then: how much do you know about flashing recoveries, ROMs etc.
Click to expand...
Click to collapse
I have basic experience installing customs roms, rooting, twrp, unlock fastboot...following tutorials, of course.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
Click to expand...
Click to collapse
here someone says that in theory it would be possible if you have the usb debugging enable, but silly me I had it open but I deactivated it I think, so I'm not sure if I have access or not.
OnePlus 6 Stuck At "Qualcomm Crashdump" Screen All A Sudden | Data Retrieval Critical
Hi good people at XDA. This is my first post on this website and I am absolutely hoping to receive help from you all to find a way out of the depressing and extremely anxious situation I'm in. I was using my OP6 normally today and while I was...
forum.xda-developers.com
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
and then finally try to recover anything that is in you backups.
Click to expand...
Click to collapse
but if I do all that flashing process any backups that are in the internal memory will be erased, right?
I had photos, files, whatsapp chat history, documents...etc and they were all in the internal memory. It is not a great loss but it is important for me to be able to recover it.
in your current situation it may be extremely difficult if not impossible to secure any personal data now
Click to expand...
Click to collapse
for me it is more important to recover the files than to recover the phone. your words are discouraging
I have read other posts and maybe being able to install on top (dirty install) the same rom I have, would leave the system as it, is being able to access my files. Not even installing the whole rom but extracting the boot image from the rom and then installing it. but I don't know if I can install a rom or boot image from fastboot, or if I need to have a working TWRP first.
It is said here:
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82257413
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82261087

Ganapatya said:
your words are discouraging
Click to expand...
Click to collapse
of course that is not my intention. I just try to be realistic
As I wrote in my post, my knowledge is quite basic. I know what I read , and what I experienced with my different devices. So again: you may find instructions and real-life stories showing you ways out of there.
My experience is that you cannot connect your OP6 phone to your PC via ADB while in bootloader / fastboot mode.
a) It's either one or the other: bootloader <=> fastboot or recovery / system <=> adb. Other devices may have different options but we're not talking about Samsung but about OP.
b) I did some additional research last night but I couldn't find a single source talking about *read* access to user data from fastboot. All you can do there is flash i.e. overwrite partitions
c) keep in mind that most probably your personal data are encrypted. So even if you find a way to access your personal data from bootloader / fastboot you may not be able to read it
d) I never used MSMtool, never had to. But I did some more research about it. It looks as if you could re-flash stock ROM using that tool but to the cost of wiping everything. At least that is what the tutorials I found are saying
That said I'd say you don't have much to lose and can go trying out some things.
From my experience the qualcomm crashdump error can have it's source in a malfunctioning recovery solution; I had that when flashing a wrong TWRP version that would not be in harmony with the previously flashed OOS firmware.
From what I read our devices don't have a separate recovery partition, instead it somehow lives somewhere/somehow in the boot partition (experts: please don't crucify me if that is wrong ). So if that is the case one idea would be to extract the boot image from the stock ROM image then flash that to /boot/ from fastboot. Don't know whether that really works and helps, but in theory you would have a default boot partition and kernel *without* a conflicting recovery solution.
In case you're successful you may be able to boot into system and make backups of everything that's valuable to you.
Again: this is extremely wild guessing here, and you'll have to read in a bit on how to properly extract parts of the ROM image.
I also would *strongly* recommend that you continue asking for help in a more technical thread like the LOS19.1 one or Funk Wizard's thread about unlocking and flashing our OP6.
I wish you all luck you need!

I think your best bet it a HW solution, get someone to:
1. replace the modem IC, it's the possible cause of the qualcomm crash
2. solder a direct connection to the internal memory so you can recover your data

[Oneplus 7 pro] semi brick after inappropriate LOS20 upgrade

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?