[Q] Failed upgrade of LG P-350 phone - Upgrading, Modifying and Unlocking

I tried to upgrade an old LG P-350 and - well, things went spectacularly wrong. Suffice it to say that when I turn it on, this is what I get on the screen:
Fastboot mode started
udc_start()
The phone does not seem to be utterly bricked, for when I connect it via USB to my Linux box here is the extra output I get on the screen of the P-350:
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
STALL GET _DESCRIPTOR 128 6 38400 0 5
STALL GET _DESCRIPTOR 128 6 38400 0 5
STALL GET _DESCRIPTOR 128 6 38400 0 5
fastboot: processing commands
A Google search reveals that people have encountered similar issues, and solutions have been proposed. However, so far those solutions just plain don't work, due to incomplete and/or incorrect instructions, or simply because the symptoms are not quite the same as I am describing here.
Anybody got suggestions on how to get this handset out of this situation? I am not an XDA developer so please be specific.

I found out how to fix the problem. Thanks everybody for your feedback.

Related

LG G3:D855; Subsystem Crash! = Blue Screen and Unhappiness :(

Pretty much what the title says. My phone blue screens. This is the third time that it's happened in the past week...and I first installed it last week...lol
Got an LG G3 D855
Latest version of Paranoid Android
Did a completely clean install: using TWRP, wiped all available partitions, then flashed PA zip.
The first time it happened was the day I installed. I just kinda shrugged it off and went ahead with making it mine. And it happened earlier today and I went ahead and ignored that too. It just happened a third time (few hours after the second time; exact time after is shown below by uptime).
When it blue screened it gave me the following message on screen (without the astrisks)
*****************************
---------------------------------------------------------------------------------------
Subsystem Crash! : modem (susbsys-restart Resetting the SoC)
---------------------------------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash ! : modem (subsys-restart: Resetting the SoC)
Press key to choose Dload Mode or Reboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration
---------------------------------------------------------------------------------------
Board Info
rev.:1.0 speed,pvs: 3,7 serial : muhSerial
---------------------------------------------------------------------------------------
ERR crash log report. Version 3
Error in file wl1trm.c, line 404
Error message: WL1TRM: wl1_trm_grant_callback: Invalid Parameter(%d %d %d)
Time of crash(m-d-y h:m:s): 8-14-2015 21:32:46
Uptime (h:m:s): 5:12:38
Build ID: MPSS.DI.2.0.1.c1.13-0046-M8974AAAAANPZM-1
param: (0x5, 0x0, 0x0)
aux_msg:
qsdm_dbg_msg:
*****************************
Also, from what I've been able to find out, I think that that file might have something to do with radio functions, but I can't be sure because I just did a quick search.
Help would be greatly appreciated!
You should look in your device forum for help on this. I don't think it's a ROM specific issue. I'm pretty sure its a device specific issue
Try to Flash official stock Rom via KDZ or TOT&DLL method.

LG leon LTE - I can't get it into stock

I have rooted my lg using this instruction, but i have not had polish language and my SIM card has got locked (so i can't call or sent SMS, or use mobile data). I thought that i can get it into stock using ubricking manual, but when i did my phone got bootloop, he was stucked on LG logo all the time and restarting itself. When I follow rooting instructions again it comes back to first problem with calling etc.:crying:
So to sum up i cannot call or use my SIM card otherwise.
I also tried to unlock my device following LG tutorials, but i always get stuck on 'fastboot ode device-id [waiting for device]' without any results of this command, just servelar minutes of waitnig.
news - Now on the stock version I can't even get my phone into dwonload mode, it says then:
[470] fastboot_init()
[470] Loading keystore failed status 5 [580] USB init ept @ 0x8f1df000
[590] udc_start()
[700] -- reset --
[700] -- portchange --
[740] -- reset --
[740] -- portchange --
[830] fastboot: processing commands
download mode works fin on laptop

How to find original build version when soft bricked?

Ok, I have searched the internet and these forums for hours and have not seen an answer to this anywhere.
I can't believe I'm the only person who has ever wanted to know how to determine this information!
I repair Nexus 7 2013 as a hobby - usually with broken screens, but now and then buy a soft bricked one.
I have the same issue every time - trying to find what is the original build number when it is soft bricked and you can't access Recovery either. I have even tried to see if Asus has a cross reference of serial number to original build number - no they don't.
I use the Wug tool and so far the score is 3 saved, one that even has Wug stumped, and the one I'm working on tonight that I simply can't get to work.
I always have to guess and try versions. tonight I've tried the single version of 4.4.4 and 3 other version of 5 to 6. Each time the best that I can get is a sluggish boot that usually eventually freezes while trying to run setup. That is BEST CASE. Worst case would take pages to describe. It sort of works on lmy47v a little and not at all on any other build. Manufacture date is March 2015.
If I didn't know better, if this was a PC, I would say there is a bad RAM chip.
Regardless, I would feel a lot happier if I knew I was installing the right build which leads back to the original question - how do you find the original build if it's soft bricked?
Thanks to anybody who can answer this!
Do this:
PC: download TWRP image, e.g. twrp-2.8.6.0-flo.img
N7: boot in fastboot mode
PC run: fastboot boot twrp-2.8.6.0-flo.img
N7: in TWRP UI mount system
PC run: adb shell cat /system/build.prop > build.prop.txt
View build.prop.txt on PC:
Code:
ro.build.id=LMY48Y
ro.build.display.id=cm_flo-userdebug 5.1.1 LMY48Y ceb9c142ee test-keys
ro.build.version.incremental=ceb9c142ee
But why do you bother to restore "original build number"?
Most of them are locked and will lose all data in the process of unlocking.
Then why not flash the latest OS image?
k23m said:
Do this:
PC: download TWRP image, e.g. twrp-2.8.6.0-flo.img
N7: boot in fastboot mode
PC run: fastboot boot twrp-2.8.6.0-flo.img
N7: in TWRP UI mount system
PC run: adb shell cat /system/build.prop > build.prop.txt
View build.prop.txt on PC:
Code:
ro.build.id=LMY48Y
ro.build.display.id=cm_flo-userdebug 5.1.1 LMY48Y ceb9c142ee test-keys
ro.build.version.incremental=ceb9c142ee
But why do you bother to restore "original build number"?
Most of them are locked and will lose all data in the process of unlocking.
Then why not flash the latest OS image?
Click to expand...
Click to collapse
Thanks for your reply. No less complicated way to find that out eh? I'm afraid that's a bit over my head (or perhaps its just the way its worded - no offense intended). If it was PC, and particularly DOS, I would be laughing.
When nothing else was working on this particular tablet, I did try for the heck of it to use the Wug toolkit to root and install TWRP, and it would just lock up and never install - no error messages or anything.
As far as why not use the most recent image, there are lots of opinions, and the majority I have ever read says if you don't use the original build you will get all kinds of problems right up to completely bricking the device. Since you have to take every opinion with a grain of salt, it just seems to make sense to use what it came with. 2 out of 3 tablets I have been able to do that with I have be able to save. Only 1 where I used a random build worked.
consumer61 said:
No less complicated way to find that out eh?
Click to expand...
Click to collapse
The simplest way is to check it in stock recovery but you say it is not an option...
consumer61 said:
the majority I have ever read says if you don't use the original build you will get all kinds of problems right up to completely bricking the device
Click to expand...
Click to collapse
Please post a link to one of them.
k23m said:
Please post a link to one of them.
Click to expand...
Click to collapse
I wish I could. Just random things read from hundreds of pages over a couple of years, and of course when you look for them you can't find them. I have on and off been trying to find an answer to this question for over a year.
Even the wug toolkit encourages you to make a backup of your own system rather than re-flash a random stock image. Since as soon as you unlock you lose everything anyway, there hardly seems any purpose to a backup as opposed to just re-flashing with the newest version - ergo that also leads you to believe you need to use the exact version that was there before.
I don't discount the possibility that even though not said, what was actually meant was that each device model has a version specific to it. Again, that was never clearly said, I am just using logic based on your concept that you can install any image at all, with absolutely no issue.
consumer61 said:
I wish I could... when you look for them you can't find them.
...rather than re-flash a random stock image.
Click to expand...
Click to collapse
That's it, all those horror stories are from "random stock" flashers. If you choose wisely the very latest stock image then there is no danger whatsoever.
Let's talk about the latest case - is it unlocked already?
I was able to unlock, but could not access recovery - when booting to recovery it would still just sit at the Google logo.
In order, I tried from the list that comes up on the Wug tool, a 6.01 version, then lmy47v, then lmy48g, then finally thought I would try going back quite far since there was only one version for 4.4.4 - ktu84p, then finally lmy48t.
With tiny variations, all had the exact same result - no errors when wiping or reloading. The circling balls would just around as normal, then eventually grind to halt - moving a tiny bit every 5-30 seconds. After maybe an hour, sometimes you would finally get the normal "pick your language" screen, although most times, after about 30 min I would just shut it down and power it back on.
That would result in sometimes getting the "pick a language". Sometimes able to get as far as entering a gmail address, but the system would always lag - registering a touch many seconds after doing it. Once single time, I got a full boot up. Then it came up with the OTA as it should. ran it, and back to soft bricked.
Also a couple of the times I was able to get it to boot, as soon as you would reboot, it would be back to soft bricked.
Motherboard got exceptionally hot, and battery was down to 18% once, and 27% another time from full charge - so it was working abnormally hard
I have been playing with and building pc' etc since the Vic 20, C 64 and so on, and it behaves just like a bad RAM chip. I did find a post on here saying the Kingston/Toshiba chip can get corrupted and must be replaced, with a link to the same guy selling MB on ebay - can't remember his id on here, but here is the ebay sale:
http://www.ebay.ca/itm/121637666631?_trksid=p2055119.m1438.l2649&ssPageName=STRK:MEBIDX:IT
Overall this is similar behaviour although not quite as bad, as the other motherboard that stumped Wug. He finally said it must be hardware in that case, and I certainly tend to think the same thing here.
consumer61 said:
He finally said it must be hardware in that case, and I certainly tend to think the same thing here.
Click to expand...
Click to collapse
Let's find out exactly. As you are comfortable with DOS then the following should be piece of cake:
download twrp-2.8.6.0-flo.img from https://dl.twrp.me/flo/
go to Wug(NRT)\data folder - can you see fastboot.exe and adb.exe there?
boot the Nexus in fastboot mode (when off press power+vol.down), connect it to your PC
in Wug's data folder open a DOS command window and copy/paste: fastboot boot twrp-2.8.6.0-flo.img [Enter]
when TWRP is up and running, copy/paste in the DOS: adb shell dmesg > dmesg.txt [Enter]
you will find dmesg.txt in Wug's data folder
zip up the file and attach it to your next post
This is THE hardware log and another chance to play with DOS-like stuff :laugh:
Ok excellent instructions. (did tech support for years).
I had pulled the MB and replaced it, so I just switched it back.
Install TWRP worked fine. TWRP screen came up.
Typed command for the msg file, and dos error was "error: device '<null>' not found
I know of TWRP, but have never used it. I hit the centre button on the screen which brought up what appears may be an install log, and its full of errors.
Goes down over a full screen, but the common statement is:
"unable to find partition size for /boot" /recovery /misc and about 15 more lines.
Also other errors like unable to mount cache, data, system
I just took a photo of the screen but it seems you can't post actual images, only links to images stored on the internet, not something off your hard drive.
Just to let you know, I did try various spacing around the dmesg > dmesg.txt command just to be sure, same error every time.
Now that is from the TWRP screen with all the buttons on it. If you meant for me to open a certain function of TWRP, I didn't.
Regards,
UPDATE: had a brainwave and loaded up Wugfresh and device manger. Showed exclamation mark beside the device so re-installed adb driver. Now the log worked. It is only 64k, and both the twrp photo and the log file should be attached now.
I looked through the log, and even not knowing the internals of the system that well, only one part stood out as appearing bad:
<3>[ 0.277130] msm_gpiomux_install: write failure: -22
<3>[ 0.277221] msm_gpiomux_install: write failure: -22
<3>[ 0.277404] msm_gpiomux_install: write failure: -22
<3>[ 0.277496] msm_gpiomux_install: write failure: -22
<3>[ 0.277648] msm_gpiomux_install: write failure: -22
<3>[ 0.277740] msm_gpiomux_install: write failure: -22
<6>[ 0.278656] Registering gpio keys
<6>[ 0.278778] Reconfigure VOL_UP(GPIO155) and VOL_DOWN(GPIO189) with PMIC
<4>[ 0.278991] 8921_l17: Failed to create debugfs directory
<4>[ 0.280609] ------------[ cut here ]------------
<4>[ 0.280700] WARNING: at arch/arm/mach-msm/subsystem_restart.c:573 subsys_restart_init+0xd8/0x104()
<4>[ 0.280883] Modules linked in:
<4>[ 0.281066] [<c0015f44>] (unwind_backtrace+0x0/0x11c) from [<c007ae88>] (warn_slowpath_common+0x4c/0x64)
<4>[ 0.281250] [<c007ae88>] (warn_slowpath_common+0x4c/0x64) from [<c007aeb8>] (warn_slowpath_null+0x18/0x1c)
<4>[ 0.281433] [<c007aeb8>] (warn_slowpath_null+0x18/0x1c) from [<c0c0c600>] (subsys_restart_init+0xd8/0x104)
<4>[ 0.281616] [<c0c0c600>] (subsys_restart_init+0xd8/0x104) from [<c0008718>] (do_one_initcall+0x8c/0x15c)
<4>[ 0.281799] [<c0008718>] (do_one_initcall+0x8c/0x15c) from [<c0c00a24>] (kernel_init+0xe8/0x1a4)
<4>[ 0.281982] [<c0c00a24>] (kernel_init+0xe8/0x1a4) from [<c000fdf8>] (kernel_thread_exit+0x0/0x8)
<4>[ 0.282104] ---[ end trace ff63e6c2cba9c001 ]---
consumer61 said:
Typed command for the msg file, and dos error was "error: device '<null>' not found
Click to expand...
Click to collapse
When TWRP is running please type adb devices and it should respond like:
Code:
List of devices attached
087777e8 recovery
If not, re-plug USB cable, check Windows device manager for new hardware. You may need ADB driver but Wug would install it before.
Please upload the picture(s) to http://imgur.com/?noFlash
We don't need to interact with TWRP for this task at all.
Btw, TWRP was not flashed, but only temporarily booted so you may need to repeat it all over again.
Cheers
I suspect you were writing your reply above, as I updated the info. Please see the end of page 1 - the photo and the log file are attached.
simply put is was my mess up - adb had to be re-installed every time you plug a device in when running XP Pro. (Yes I know XP. Hate 7 and 8 and 10, but this is the last version where you had SOME semblance of control over your own computer lol)
Thanks!
consumer61 said:
I suspect you were writing your reply above, as I updated the info. Please see the end of page 1 - the photo and the log file are attached.
simply put is was my mess up - adb had to be re-installed every time you plug a device in when running XP Pro. (Yes I know XP. Hate 7 and 8 and 10, but this is the last version where you had SOME semblance of control over your own computer lol)
Thanks!
Click to expand...
Click to collapse
Yes.
I use Linux and ...XP too :highfive:
Please check my last post here.

Nexus 6 with Android N stops booting after entering start pin - bricked?

Scenario:
- I have a Nexus 6 (shamu) with Android preview: the version of the OTA is NPD90G. (Android beta)
- Yesterday it crashed right after it lost radio signal (this used to be a common problem for me but when it crashed it came back again fine for me)
- Now when it boots it asked for my personal pin, then the animation makes its first round and at the end of the second round it stops and it reboots.
-- This is what it looks like for a moment: www andreaundstefanhoehn de / nexusboothang.jpg (cannot post urls at the moment)
-- Removing the simcard has no effect
-- I wiped the cache partion
- Of course I do not have a backup of my data
- Of course the device is locked
- The last message in the log_kmsg is "SELinux: initialized...
What I did:
- I tried the famous "Fix Dead Android in Recovery Mode" but it doesn't help
- After many tries I understood I can update my device with "adb sideload"
-- after searching around a lot I even found the firmware NPD90G and I was successfully to reinstall the firmware.
-- For those who are desperately looking for that version as it seems not to be listed anywhere, here is the still working link: storage.googleapis.com /androiddevelopers/shareables/preview/ota/ shamu-ota-npd90g-06f5d23d.zip (cannot post urls at the moment)
-- Unfortunately even after reinstalling the firmware, it still stops at the same point
-- I tried to unlock the device with "fastboot oem unlock" but it tells me to check "allow oem unlock" in Dev Options which 100% likelyhood is not checked
- Run graphics test results quickly "error", then in a dead android image, then saying "erasing" and then saying "installing system update" but it doesn't fix the problem
Questions
- Does anyone know what the actual issue is that the device stops?
- Is there any newer OTA for shamu I could use? Is there maybe a final Android N for shamu somewhere available?
- Given the above situation, is there any chance I can access files on my device?
- Any other option I have, except factory reset (and wiping my data)?
I really put a lot of effort in it (and learned a lot) but I only got that far. I wished there are other options?
Thanks in advance for helping,
Stefan
I "reposted" the question to the forum here. Not sure how to move delete it in the the other forum. Sorry.
Mod Edit
Duplicate post
Thread Closed.
jackeagle
Forum Moderator

Locked bootloader, cannot OEM Unlock or access USB Debugging

Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.
deleted
***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.

Categories

Resources