Related
* Your warranty is now void.
I am not responsible if this causes your device to be bricked, for the planets to align, monkeys take over the earth, nuclear war, missed sexual favors or whatever nonsense ensues due to your device not working. Please do some research if you have any concerns before flashing.
By using this recovery you agree to these terms!
Click to expand...
Click to collapse
Clockworkmod Advanced 5
http://d-h.st/BNT
Bugs
-cwm runs in background while charging(Fixed)
-tell me?
Install
(requires unlocked bootloader)
Code:
fastboot flash recovery recovery.img
To enter CWM(or stock recovery) turn off and then hold vol up+power
https://github.com/KainXS/android_device_huawei_y301a2/tree/cwm
Credits
ShabbyPenguin - Phandroid
KINGbabasula
CNexus
Would you be able to port CWM to a Huawei G526-L22?
Specs are similar to this Vitria(Y301-A2).
Tried this .img but can't mount /cache/recovery etc
extendcommand threw up failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache
(no such file or directory)Yet that path/directory is present in file explorer.Any assistance would be much appreciated.
The device has been discounted to AU$99 so a lot of geeks have grabbed them and are looking for mods
As is the norm for android heads ;|}Regards from Down Under
Gomax
gomax said:
Would you be able to port CWM to a Huawei G526-L22?
Specs are similar to this Vitria(Y301-A2).
Tried this .img but can't mount /cache/recovery etc
extendcommand threw up failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache
(no such file or directory)Yet that path/directory is present in file explorer.Any assistance would be much appreciated.
The device has been discounted to AU$99 so a lot of geeks have grabbed them and are looking for mods
As is the norm for android heads ;|}Regards from Down Under
Gomax
Click to expand...
Click to collapse
do you have the original recovery backed up
and can you run these commands while its booted in android with adb
cat /proc/partitions (info on partition sizes)
run ls too
and did you just take the image and flash it without modifying it.
Was sent the image by a developer, who has sent a revised version which works.
Thanks for your interest.
good to hear:good:
but did you really flash the recovery without modifying anything and it booted on the 526
KainXSS said:
good to hear:good:
but did you really flash the recovery without modifying anything and it booted on the 526
Click to expand...
Click to collapse
Both versions booted OK.
The first didn't mount external card.
gomax said:
Both versions booted OK.
The first didn't mount external card.
Click to expand...
Click to collapse
wow if it booted unmodified at all, these devices must be extremely similar minus the screen, hopefully kernel source pops up for one of them, guess the recovery fstabs were different though
edit
the link is gone?
I requested the source code for the vitria a month ago and huawei just released it
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=17935
I had time to play around with it and build it, did not boot though, wanted to clean it up some but yesterday I broke my hand so there might not be updates for a while.
how did you get the unlock password for this device? im on their website but it doesn't list this device....
mattlowry said:
how did you get the unlock password for this device? im on their website but it doesn't list this device....
Click to expand...
Click to collapse
sorry it took so long to answer but I got the unlock password from huawei by emailing them, I haven't worked on this device solidly in a while.
you might be able to also flash recovery with adb also, if you wanna try it let me know because I unlocked my bootloader before using adb but when I try it works.
remembered to upload cwm advanced 5
also have cwm 6.0.4.7 and advanced 6 but I need to fix a nasty bug with it.
forgot to add if someone were to upload the recovery.img's and a partition layout for the g526 or G740 I can more than likely try to get cwm and cwm advanced running on them.
had to change the vitria recovery to mount by name instead of block number, changed font also.
added source
KainXSS said:
sorry it took so long to answer but I got the unlock password from huawei by emailing them, I haven't worked on this device solidly in a while.
you might be able to also flash recovery with adb also, if you wanna try it let me know because I unlocked my bootloader before using adb but when I try it works.
Click to expand...
Click to collapse
Yes, it takes a few email exchanges with [email protected], but I got my unlock password in couple of days from them.
Great job, OP, works like a charm.
Finally got my unlock from Huawei after a week, and just in time! I lost my old HTC G2 (its somewhere in the kitchen, i swear!) and needed a replacement phone fast.
Enter the Vitria. installed CWM and did a full backup, then installed titanium backup and started ripping out bloatware and live wallpapers and other crap.
I have to say, i REALLY hope development of Cyanogen continues for this device, its hard enough leaving CM7 to go to jelly bean. If there's anything i can assist with with a backed up/bootloader unlocked device, let me know. Or buy you enough beer to last a weekend so you can get this compiled
Flashify
I did something different, I flashed with flashify but I realize now I shouldn't have, it reboots but has a signature error before rebooting, I sure hope there will be cynogen mod or something because this phone has a data connection problem, once data goes off it won't come back on until restart and sometimes all bars without data goes off too and then have reboot too, good phone but needs work, glad to see someone out there doing something, thanks.
OK, I think I know how to fix, but I don't have the correct IMG to fix since I have already corrupted it by flashing with flashify.
Does anybody have the recovery.img and the boot.img from a working stock for this phone?
by having a good recovery.img, I can flash with flashify and get it back to working correctly, this is what I did to fix a similar problem from flashing CWM to my LG G2 and worked.
Update, downloaded stock ROM and the recovery and boot img where there so I flashed recovery.img with flashify and everything good.
Just wondering, anybody has a recovery of their Vitria that already has CWM working properly on it, I wonder if that recovery.img contains proper CWM to be flashed to another Vitria?
this is not for the h882l, it might work on that one but I don't know.
if you try to flash without having the bootloader unlocked, it won't work, you will get a crc signature failure error every boot even if you use adb or a flashing app, after unlocking you can use adb, not sure about flashify(never tried it).
CRC Signiture Error
KainXSS said:
this is not for the h882l, it might work on that one but I don't know.
if you try to flash without having the bootloader unlocked, it won't work, you will get a crc signature failure error every boot even if you use adb or a flashing app, after unlocking you can use adb, not sure about flashify(never tried it).
Click to expand...
Click to collapse
Yes CRC Signiture Error, but the bootloader is unlocked, I use T-Mobile with phone, but only problems I see with this phone is connecting to Data all the time, I end up having to turn data off then back on then it is usually fine sometimes it has problems still, I did pay a service to get the bootloader unlocked with a code so it is unlocked.
Would like to see a nice ROM built for this phone, I haven't the slightest clue to do so, Cyanogen mod would be fine.
Did try to install CWM but could not do so, is this the touch or regular version of CWM you have listed?
Keep up the good work, thanks.
Arctic Prodigy said:
Yes CRC Signiture Error, but the bootloader is unlocked, I use T-Mobile with phone, but only problems I see with this phone is connecting to Data all the time, I end up having to turn data off then back on then it is usually fine sometimes it has problems still, I did pay a service to get the bootloader unlocked with a code so it is unlocked.
Would like to see a nice ROM built for this phone, I haven't the slightest clue to do so, Cyanogen mod would be fine.
Did try to install CWM but could not do so, is this the touch or regular version of CWM you have listed?
Keep up the good work, thanks.
Click to expand...
Click to collapse
I also use tmobile on mine and I have data problems too but haven't tried to fix it yet, don't have the time but your bootloader is unlocked right, your not confusing sim unlock with bootloader unlock right, also your using fastboot to install right.
I am not working on cyanogenmod for the vitria though, it needs a device tree and the kernel needs to be updated for it too, on mine I just run with a custom rom based on stock and a custom kernel for overclocking and stuff, thats enough for me.
Maybe sim unlocked, but thought was bootloader unlocked, I paid to get phone unlocked, they sent a code and I am able to use t-mobile sim card on MetroPCS phone, as for bootloader, it is rooted and says unlocked if that is what you mean, I have SuperSu installed, I used Framaroot as suggested.
Yes I can get into fastboot mode.
Hmm, to verify if bootloader is truly unlocked, how would I go about getting to that to verify for certainty?
I was literally flashing something ten minutes before and then I tried going back to recovery and there were no directory so I then rebooted it says I need a password... But I never one made a password, I didn't even know there was passwords for recovery
Sent from my Nexus 5 using xda app-developers app
Never mind... Just kept rebooting then eventually the problem was gone... How can I set a password for bootloader and recovery... Just wondering if it's even possible
Sent from my Nexus 5 using xda app-developers app
You can't set a password for either (well, not to my knowledge!)
Even with a password we can fastboot flash new images.
Team Win explains this on their website.
Primokorn said:
Even with a password we can fastboot flash new images.
Team Win explains this on their website.
Click to expand...
Click to collapse
Yes and no.. Actually we can lock the bootloader so fastboot flash wont work.... All we need is for the recovery password to block the following to secure your data (on the nexus 5):
Mount of external (OTG) media
adb access
file manager capabilities
This would mean you can still boot into recovery and flash / backup (although not to removable media) until you went into a security menu to "unlock recovery". This would even mean that your automated jobs can still occur without having to face a "boot password". The password could be stored on /sdcard in clear test and there could be an option to delete the password incase you forgot it in this same recovery menu, which also wipes the device.
recovery is the only weak point of my device.
Sure, Samsung's Odin will get round this password on their devices as the BL is not locked but any device with a locked bootloader (locakbale bootloader) will benefit.
Another caveat is that this is not to prevent the device being wiped.... unlocking the bootloader will wipe the device, and this is what I want. I don't care about getting the phone back as much as I would care about securing my data. Its all backed up. Nothing is lost. I just might not want someone else getting access to it.
Although this is beyond the extent of my knowledge to achieve, I don't think it would be hard for anyone who knows what they're doing with code.
rootSU said:
Yes and no.. Actually we can lock the bootloader so fastboot flash wont work.... All we need is for the recovery password to block the following to secure your data (on the nexus 5):
Mount of external (OTG) media
adb access
file manager capabilities
This would mean you can still boot into recovery and flash / backup (although not to removable media) until you went into a security menu to "unlock recovery". This would even mean that your automated jobs can still occur without having to face a "boot password". The password could be stored on /sdcard in clear test and there could be an option to delete the password incase you forgot it in this same recovery menu, which also wipes the device.
recovery is the only weak point of my device.
Sure, Samsung's Odin will get round this password on their devices as the BL is not locked but any device with a locked bootloader (locakbale bootloader) will benefit.
Another caveat is that this is not to prevent the device being wiped.... unlocking the bootloader will wipe the device, and this is what I want. I don't care about getting the phone back as much as I would care about securing my data. Its all backed up. Nothing is lost. I just might not want someone else getting access to it.
Although this is beyond the extent of my knowledge to achieve, I don't think it would be hard for anyone who knows what they're doing with code.
Click to expand...
Click to collapse
Do u mean that you always have a locked BL?
Thanks for your feedback but one thing remains the same IMHO. Of course we can lock the BL but a thief can unlock it then flash factory images. No more custom recovery, passwords...
I'm not talking about the user data but to be able for a thieft to use a device even with locked stuff.
Primokorn said:
Do u mean that you always have a locked BL?
Thanks for your feedback but one thing remains the same IMHO. Of course we can lock the BL but a thief can unlock it then flash factory images. No more custom recovery, passwords...
I'm not talking about the user data but to be able for a thieft to use a device even with locked stuff.
Click to expand...
Click to collapse
I'm just talking about data security. That is my only concern. Devices are replaceable. Unlock bootloader, data wiped. fine!
Oh thanks everyone, I just wouldn't want a theif to use a phone they don't deserve, pretty much the only security on my phone to not go to bootloader is for no power menu on my lockscreen but you could probably use adb to get through
Sent from my Nexus 5 using xda app-developers app
That's what imei blocking is for
Sent from my Nexus 5 using Tapatalk
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:
Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...
Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.
No worries
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood
rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?
Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.
Yup. RMA
Sent from my Nexus 5 using Tapatalk
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
D0UBLEJUMP said:
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions: https://developers.google.com/android/nexus/images
krs360 said:
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions
Click to expand...
Click to collapse
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
D0UBLEJUMP said:
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
Click to expand...
Click to collapse
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
theesotericone said:
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
Click to expand...
Click to collapse
Bootloader always relocks when the phone restarts :/
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
BirchBarlow said:
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
Click to expand...
Click to collapse
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
D0UBLEJUMP said:
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
Click to expand...
Click to collapse
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
nexus.freak said:
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
Click to expand...
Click to collapse
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Niflheimer said:
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Click to expand...
Click to collapse
Woohoo! Flag reset!
Judging by what I found when I was looking around it doesn't seem like bad emmc is too common, couldn't find many suffering the same issues as me.
As for triggers, my brother's Nexus worked completely fine just like mine, then powered off, powered on, and broken. So...I guess the message of the story is to never turn them off (or try reflash) and they'll be fine?
If you bought phone of play store you can send it to google, there was a tread here some time ago and it said that google accept to replace phones with temper flag and unlocked bootloader.
Good luck
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 typing something on Telegram the phone suddenly froze and after I re-booted it, it took me to the Qualcomm Crashdump screen.
My OP6 isn't tampered in any way (no bootloader unlocked, no TWRP recovery installed, nothing rooted).
At the moment, I can enter the fastboot mode while pressing volume up and power button.
The crucial thing is the data which I MUST RETRIEVE, can't afford to lose it.
Could y'all please suggest a way where the data can be retrieved or the phone can be revived without data loss?
I did read the forums on MSMDownload Tool but I believe it wipes off the phone, right?
PLEASE HELP!
If ADB ( read: USB Debugging ) got enabled on phone - what is the door to Android OS - then try this to pull out user-data stored on phone
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
jwoegerbauer said:
If ADB ( read: USB Debugging ) got enabled on phone - what is the door to Android OS - then try this to pull out user-data stored on phone
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
Click to expand...
Click to collapse
Thanks @jwoegerbauer for the prompt response. I can surely try that. Considering that I'm fairly a noob, could you please share in a bit detail, the steps I need to take before executing those commands?
Also, since there's a tiny chance that USB Debugging may not have been enabled, what's the alternative that I consider?
Thanks!
Since I must retrieve the data in internal SD, can this help me enter the OS?:
1. Extracting the boot.img of the latest version that's currency installed on my OP6, from payload.bin
2. Testing if this boot.img can revive me into the OS by fastboot boot boot.img.
Also, one pressing doubt: does a fastboot flash boot boot.img command erase internal SD contents??
Please help!
Any help, anyone?
pagan_1 said:
Any help, anyone?
Click to expand...
Click to collapse
My friend has the same problems. Did you find any ways to retrive data? I found a way to use msm tool but it surely erases all data and its his college memories so I'm trying to find alternate ways. Does the msm tool work on bootloader locked phones?Sorry that I am of no help to you. I too am a novice
KannanSathyanarayanan said:
My friend has the same problems. Did you find any ways to retrive data? I found a way to use msm tool but it surely erases all data and its his college memories so I'm trying to find alternate ways. Does the msm tool work on bootloader locked phones?Sorry that I am of no help to you. I too am a novice
Click to expand...
Click to collapse
No man. Still looking for some solutions. Read umpteen threads only to see that MSMDownload Tool erases data because it first unlocks bootloader (which mandatorily wipes data), flashes system files and then relocks it.
But I'm pretty sure, there exists some way out to flash a OP 6 with locked bootloader but retaining userdata partition intact.
Hoping to receive some solution here from this community of Android geeks.
pagan_1 said:
No man. Still looking for some solutions. Read umpteen threads only to see that MSMDownload Tool erases data because it first unlocks bootloader (which mandatorily wipes data), flashes system files and then relocks it.
But I'm pretty sure, there exists some way out to flash a OP 6 with locked bootloader but retaining userdata partition intact.
Hoping to receive some solution here from this community of Android geeks.
Click to expand...
Click to collapse
Hey man, were you able to do anything abut it? I'm in the exact same situation. Don't mind losing the phone if I'm able to save the data.
Smohi said:
Hey man, were you able to do anything abut it? I'm in the exact same situation. Don't mind losing the phone if I'm able to save the data.
Click to expand...
Click to collapse
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
Oh, that's awesome. I have some hope then. Do you mind telling me what your location is. I'm based out of bangalore and wondering I'll have to take it to your specialist incase I don't find any solution locally. All others have been saying they were asked to replace motherboard by Oneplus service centres. Please let me know of your repair centre as well. I'll try to atleast speak to them. Thank you so much
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
How much did it cost? They changed IC and since then your phone is working properly?
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
Bro can i have your number please i m stuck with the same problem since last year but not got the solution to boot up my phone normally its always showing crash dump mode. I tried everything but nothing worked for me.
like many even i too ugraged my op6 to oo11.1.1.1, rooted was running well for a week till i encountred face crash dump mode error
Stupid thing i did was instead of flashing fastboot oos 10.3.8 i tried to flash msm 10.3.8 which didnt solve crash dum and also locked my BL.
now nonof the msm could solve crash dump nor we can unlock BL bz we cant toggle OEM in Dev option,
i discussed with @L0ND0NB0Y regarding this, his suggestion would be to take a backup of oos10.3.8 config partation of a working rom, then use edl to flash it on affected op6, by that way we can unlock bootloader and flash fastboot rom.
we need to fide a working op6 and back config which @L0ND0NB0Y can guide us. if it works he ll creat a post to solve crashbump and BL locked issue.
if this wont work, we may need to wait for msm oos11 file.
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.