Related
Hey guys,
i just started with falshing and those things. So i'm not so familiar with building and unlocking.
I bought a M2 with QUWERTY. I had and still has bootloop problems according to: http://forum.xda-developers.com/showthread.php?t=1457373
While analysing my bootproblem, i just realized, that i have a Fastboot Bootloader installed on this phone, what seems a little special.
Next step may be, to use the fastboot get this phone work, step after, use fastboot for improve this forum . But as i said, i'm new in this deep hardware near software-things, so need all your help for that .
greetz
how strange this in your bootloader, is similar as in the Atrix? So you installed it? I would like to know more about this topic
Looks like you have a dev phone. There are a couple of forum users with dev phones
Does rsdlite recognize it? I think you should try to have a look in Motorola Defy Android Development: there is a thread named ''experimental: trying to unlock the bootloader " (look at pages 60-75) .
I think someone wrote about some particular roms to be flashed in case of unlocked phones....
Does anyone know a way to extract this bootloader??
If so, I believe that lowering the fastboot and giving the command would be possible to unlock the MS2
Fastboot => http://www.mediafire.com/?2zdhukq3ha1qlrd
1) "fastboot oem unlock" to see the Station ID
2) "fastboot oem unlock ID" to unlock the bootloader
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
http://forum.xda-developers.com/showpost.php?p=21885753&postcount=735
Click to expand...
Click to collapse
djlooka said:
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
Click to expand...
Click to collapse
i think you can send PM to MKSilver.
Lutis said:
i think you can send PM to MKSilver.
Click to expand...
Click to collapse
I already did
Anyway I think the more dumps are posted, the better it is!
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
MKSilver said:
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
Click to expand...
Click to collapse
Did you tried simply wipe via moto recovery?
Or flash different sbf.
Have you tried the "fastboot oem unlock" command?
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
MKSilver said:
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
Click to expand...
Click to collapse
Well, I have bootloader 70.12. To get into BL I have 2 options:
1) arrow up
2) Camera + Volume down
Both ways leads to standard BL. Fastboot devices doesn't list my phone, just as before. I never tried to update my BL but I don't think it will do any difference.
I've tried it with bootloader 70.13.
Only option A works to get into Bootloader mode (not Fastboot).
Next "funny" fact.
While Flashing SBF with "normal" bootlaoder modus, everythings works with RSD lite.
While Flashing SBF with "fastboot" bootloader modus, I get an error after creating image files:
"Failed flashing process. Failed flashing process. Phone [0000]: Error getting subscriber unit information. Device API Error: 0xE0000042 Command: RQHW (0x0805041); phone connected"
Then is Result:"FAIL" and the phone stays in bootloader modus (fastboot).
May be I have wrong RSD lite calibration. Will investigate this, how it behaves in linux.
Ok, so googling "unsigned motorola milestone 2 SBF" turned up this as the first
Perhaps if that link is dead you could ask endless7 if he would be so kind as to re-upload it, or perhaps it is available elsewhere.
I say this because I remember reading somewhere that once it's unlocked you can only use unsigned SBF's.. pretty sure it was the bootloader unlock progress thread in the defy forums.. but I'm sure it's been said in our forums too
Just wrote a pm to Endless7. If thats true, it could help me get this device work (even in chinese) and than i can take a look forward, while using adb for example.
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
DreadPirateDan said:
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
Click to expand...
Click to collapse
Dan,
I'm not sure, but I don't think he is limited to flashing only unsigned stuff. The difference from developer phone to production phone, besides fastboot, is that the first one doesn't check signatures during boot chain. Theoretically speaking he is able to flash and boot any Milestone2 ROM he likes. I also suspect that he is able to downgrade from gingerbread to froyo, unlike us. There should be something else preventing him to boot the phone. That's just my opinion and it maybe wrong
Hey guys,
well enough is enough, bought today a second phone for the time the m2 is still dead.
I'm about to finish the defy thread today. Already learned a lot.
Well it is correct that i can flash signed SBFs. While booting into "normal" BL Mode.
But i can also boot into Fastboot and the RSD Lite Name starting with NS seems to show me something special.
So i risk something today and flash a froyo: It worked but still bootloops. The flash was successful and the M Logo turned gray.
At GB it is Red at my M2.
But now it would be great for an unsigned SBF, some more Ideas how to get it boot, or how to manipulate it over fastboot to get it work. Cause without get it into Android we can't go on analyse the bootloader.
PLZ help me. Will also ask a guy from the defy thread, who seems to know a lot about the milestone 1 and bootloaders/OMAP cpus. May he has a great idea what he wrote there was very clever and full of knowledge.
Greetz
As a preface, I keep my Nexus (16GB) stock/unrooted because having it down while flashing ROMs is not an option anymore. I need to the phone to work all the time, period. The irony is ridiculous.
Received the OTA from Sprint a couple of weeks ago, immediately noticed the (often-mentioned) dismal battery life and GPS hasn't been able to connect since that day. As I use GPS daily and need my phone to last for longer than 6 hours--these present full stop problems. This is in addition to the (often mentioned) stuttering/lag/freezing issues which are beyond frustrating as a heavy user. Really Google?!
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
-Been unable to send/receive SMS messages for two days
I'm beyond frustrated with this process and with Google for their lack of response in fixing widely-known 5.0 issues...on their own device. This phone is useless at the moment. What are my options? Root and roll back to KitKat? Throw this phone out of the window and go get a G3? I don't want to use a custom ROM/Recovery unless there are no other options.
Thanks for any advice-
993 said:
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
Click to expand...
Click to collapse
For the problems you're describing, you really haven't done much to solve it.
Unlock the bootloader, flash a factory image, relock the bootloader.
Why would you speak to Nexus support for 3 hours for? Waste of time
Frankly, I wanted to see if they would even acknowledge any of the issues that appear to be quite common recently with 5.0. They clearly did not, and it was relatively little effort wasted as it was through Hangouts (on a desktop though, phone forgot how to Hangout).
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.
993 said:
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.
Click to expand...
Click to collapse
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.
I agree, just flash the stock image from fastboot.
Sent from my Nexus 5 using Tapatalk
Wakamatsu said:
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.
Click to expand...
Click to collapse
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. You didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.
993 said:
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. It is telling you didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.
Click to expand...
Click to collapse
Flash the factory image. OTAs sometimes fail to implement properly. What you are describing is almost certainly that. You've already tried everything you can to fix the issues short of flashing. So flash.
You either have bad hardware, or the upgrade didn't install correctly. As others have mentioned, flashing the factory image should work.
993 said:
You didn't read my question. As I said, I would rather not flash if there are other viable options.
Click to expand...
Click to collapse
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.
If you wanted stablity you should of stayed on kitkat, hence why i never updated, you a os i can rely on and thats currently 4.4, as usual android builds at the start have minor issues and we wait for google to fix them.
I usually dont update till the devs can get a functioning build thats suitable for the community.
as above,
Fastboot oem unlock, flash 4.4 or 5.0 google image, relock bootloader
If he doesnt want to flash a custom rom then he should know how to flash a stock rom.
https://developers.google.com/android/nexus/images
I don't even speak to my own family for 3 hours, let alone a complete stranger lol wow
Wakamatsu said:
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.
Click to expand...
Click to collapse
Here's what's been done so far several times over:
Unlocked Bootloader
Installed SDK kit from Google using their walk though
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Multiple Full Wipes in both recoveries
Attempted ADB commands through terminal (W7 Pro - Admin)
Uninstalled, Reinstalled all recommended device driver packages, only recognizes in device manager as 'Google Nexus ADB Device' not Explorer Shell (read relevant FAQs) regardless of driver.
Used multiple USB ports/cables, rebooted PC each change in configuration
Root Toolkit 1.9.9 does not recognize through ADB
As of current, only Bootloader (unlocked) and Recovery mode work. I cannot access the SD card of the device through any means I've tried. The last that the OS booted I ensured that USB debugging was on in Settings. ADB mode in either recovery does not change device recognition on PC, nor does file system appear. System will not boot to ensure debugging setting has remained. Same issues with a laptop with no known prior driver issues.
993 said:
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Click to expand...
Click to collapse
You can't sideload a factory image. Fastboot commands are executed in bootloader, not recovery.
That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.
993 said:
That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.
Click to expand...
Click to collapse
Dude, you really need to read and understand the stickies before you do something bad to your phone. You are just flailing right now.
And really, all you needed to read was the install instructions on the Google factory image page.
1) Unlock bootloader
2) Unzip the factory image zip
3) Reboot in to bootloader
4) Run the flash-all script in the factory image folder.
This was the first method I tried. I have downloaded the factory image from Google several times and I get an 'unexpected end of data' message in 7zip when extracting my copies. Downloading from Google has been hit or miss with 'unknown network error' that halts the download, not sure what that could be.
I am trying to pinpoint the cause of these issues, as flashing back to factory without good images won't be possible. I understand how straightforward a factory flash should be especially with OEM tools but in my case I keep running into roadblocks.
Disable your antivirus and firewall during the download, that may help.
gee2012 said:
Disable your antivirus and firewall during the download, that may help.
Click to expand...
Click to collapse
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.
993 said:
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.
Click to expand...
Click to collapse
Try LG to see if they will help. Haha had to.
Can you not download on your phone? I'm not familiar with sending MMS but does it work forcing your phone to 1x? I'm trying to think of ideas. What all apps do you have installed?
Sent from my Nexus 5 using XDA Free mobile app
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers. Rebooted and opened msm tool and Is connecting and now showing 2 ports. Hope this works for anyone having trouble ; as earlier I had no Qualcomm driver's installed and no ports showing on msm tool after many attempts to install drivers. I'm now ready when something comes along to flash. After rebooting PC use cmd window adb reboot edl. Will then show up on msm tool as connected. When installing Qualcomm driver's choose first option Wwan is not used to get Ip address. If this works for you hit the like button "it's free". I've seen many people complaining they can't connect to msm tool. This fixed my issues. Tested on windows 10 pro
Driver's. https://drive.google.com/file/d/1AOeuMj6D5f6H4yhAC1QKGN437qV9YmJs/view?usp=drivesdk
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
XNine said:
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
Click to expand...
Click to collapse
No additional driver's need to make Qualcomm devices/one plus phones to connect to msm tool.
illusiveairforce said:
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Click to expand...
Click to collapse
You don't use the factory one use the one above or below. It's a tool that relocks bootloader and flashes device to original firmware that it was shipped with. It's an anti-brick tool so to speak.
I still cant get it to work. the driver looks to be working and MSM identifying it
but no matter what i do it wont progress. i cant adb reboot because adnb nor fastboot are responsive. the phone just disconnectes and reconnects USB over and over and thats it. no button combo of volume keys and power being held for along time seems to work either.
I finally got it functional and now at "Image does not match" tried on 3 other machines with 3 seperate MSm installs.
9 5G LE2115 is my phone I bought directly form OnePlus. Idk what to do from here.
Usually kicks up that warning if your trying to use the wrong msm tool.?
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
applyscience said:
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
Click to expand...
Click to collapse
What about that global fastboot rom I linked you to?
mattie_49 said:
What about that global fastboot rom I linked you to?
Click to expand...
Click to collapse
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
applyscience said:
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
Click to expand...
Click to collapse
You were able to get back from aospa though right? Via msm
mattie_49 said:
You were able to get back from aospa though right? Via msm
Click to expand...
Click to collapse
i always had fastboot access during that, i just was too stupid to extract my own img files form the paylod dumps (theres so many guides online, i just suck with it) anyhow, after you hooked me up with download i just ran the the imgs in a flash-all bat file to clean up both slots of the phone and it was wonderful. as soon as i went to the unofficial lineage my phone just gave up. 2 reboots later.
im not sure what im going to do. its been a long day and not too pleased with myself so im trying to just procrastinate it till tmw or sunday.
[17784][07-04 07:23:08.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[17784][07-04 07:23:11.061]<4> [3] [SP][195] Check cmd done status failed. 1
this is the 2 lines in the log that have ruined my weekend.
I'm investigating possible solutions to common MSM errors that prevent flashing.
See the following thread and feel free to try the steps outlined if you're brave enough.
Please report back your findings.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com
Can you re-up these? I'm getting a 404 on the google drive link.
Ethanadams642 said:
Can you re-up these? I'm getting a 404 on the google drive link.
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9
Flash by edl if you can't do it then pm I'll fix it by tv
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.
I had this problem because I flashed a custom kernel on a custom rom today
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.