My phone is stuck on bootscreen. My bootloader is unlocked and I have root. I was trying to uninstall the preloaded Amazon apps and one ''Root Uninstaller' app rebooted my phone and ive been stuck on the bootscreen. The phone just tries rebooting over and over. I formatted data in stock recovery, but the issue still persists. Help please
Ebizza said:
My phone is stuck on bootscreen. My bootloader is unlocked and I have root. I was trying to uninstall the preloaded Amazon apps and one ''Root Uninstaller' app rebooted my phone and ive been stuck on the bootscreen. The phone just tries rebooting over and over. I formatted data in stock recovery, but the issue still persists. Help please
Click to expand...
Click to collapse
Restoring STock boot image fixed this.
Ebizza said:
Restoring STock boot image fixed this.
Click to expand...
Click to collapse
How did you restore stock? I flashed kernel but was on custom rom. Phone got stuck on bootloop. I can't enter recovery or fastboot. LGUP fails because i can't cross flash my Sprint to any other KDZ. Any suggestions on what i can try? thanks
Eljay227 said:
How did you restore stock? I flashed kernel but was on custom rom. Phone got stuck on bootloop. I can't enter recovery or fastboot. LGUP fails because i can't cross flash my Sprint to any other KDZ. Any suggestions on what i can try? thanks
Click to expand...
Click to collapse
Did you root your phone? If you did, you can use Qfil to restore your stock boot img (if you made a backup). If you didn't, you'd have to get someone to send you their boot image. I would have sent mine, but I cross flashed from Sprint to Open US. I doubt mine would work for you.
Why can't you cross flash?
Ebizza said:
Did you root your phone? If you did, you can use Qfil to restore your stock boot img (if you made a backup). If you didn't, you'd have to get someone to send you their boot image. I would have sent mine, but I cross flashed from Sprint to Open US. I doubt mine would work for you.
Why can't you cross flash?
Click to expand...
Click to collapse
Can you please guide me on how to cross flash? Because i am getting the error 0x5319, Not allow to change the device.(SPR_US->OPEN_CA). I am using LG UP CMD method. using LG UP and UPPERCUT, it crashes at 4%. Maybe i am missing something? how did you cross flash?
Eljay227 said:
Can you please guide me on how to cross flash? Because i am getting the error 0x5319, Not allow to change the device.(SPR_US->OPEN_CA). I am using LG UP CMD method. using LG UP and UPPERCUT, it crashes at 4%. Maybe i am missing something? how did you cross flash?
Click to expand...
Click to collapse
There's a post on the site. Did you follow all the steps?
Eljay227 said:
Can you please guide me on how to cross flash? Because i am getting the error 0x5319, Not allow to change the device.(SPR_US->OPEN_CA). I am using LG UP CMD method. using LG UP and UPPERCUT, it crashes at 4%. Maybe i am missing something? how did you cross flash?
Click to expand...
Click to collapse
[Tutorial] Crossflash, Bypass OPID Mismatched Error
Hi there ;) Thanks to all other guys here who have made helpful development to tame this beautiful =) To crossflash models other than LG G8 please read post 3. Before asking any question please read the troubleshooting section at the bottom of...
forum.xda-developers.com
Here.
Ebizza said:
There's a post on the site. Did you follow all the steps?
Click to expand...
Click to collapse
To cross flash? Yes i found one, but it's via TWRP. Right now all i get is logo, "your device software can not be checked for corruption.." and screen off. I can only enter Download mode. If i can at least restore recovery i can cross flash or install custom.
Eljay227 said:
To cross flash? Yes i found one, but it's via TWRP. Right now all i get is logo, "your device software can not be checked for corruption.." and screen off. I can only enter Download mode. If i can at least restore recovery i can cross flash or install custom.
Click to expand...
Click to collapse
No. You don't need TWRP. Just read that post and follow the steps
Ebizza said:
No. You don't need TWRP. Just read that post and follow the steps
Click to expand...
Click to collapse
thanks, i crossed flashed to open. but now i cant make calls. sim service blocked. maybe i have to flash a different modem file? did you come across such errors when flashing?
Eljay227 said:
thanks, i crossed flashed to open. but now i cant make calls. sim service blocked. maybe i have to flash a different modem file? did you come across such errors when flashing?
Click to expand...
Click to collapse
No I didn't. Did you clear stock modem file from QFIL?
You should clear modem and some other files stated in that post. Then you select all partitions in LGUP except one file also stated in the post. (I can't remember the name of the file)
Ebizza said:
No I didn't. Did you clear stock modem file from QFIL?
You should clear modem and some other files stated in that post. Then you select all partitions in LGUP except one file also stated in the post. (I can't remember the name of the file)
Click to expand...
Click to collapse
yea i cleared the files mentioned in that post. and also cleared modem. Any kdz i flash, the first message i get is: this phone is permanently locked. it can not be unlocked. before this i tried some guy's backup from TWRP of his lg g8 sprint. i got lots of errors popping up when it booted. i think that's where my sim whatever got messed up.
From my research, i think a file called fsg has something to do with sim working. Also my IMEI is 0. any suggestions would be highly appreciated.
Eljay227 said:
yea i cleared the files mentioned in that post. and also cleared modem. Any kdz i flash, the first message i get is: this phone is permanently locked. it can not be unlocked. before this i tried some guy's backup from TWRP of his lg g8 sprint. i got lots of errors popping up when it booted. i think that's where my sim whatever got messed up.
From my research, i think a file called fsg has something to do with sim working. Also my IMEI is 0. any suggestions would be highly appreciated.
Click to expand...
Click to collapse
Try to restore stock modem and stock fsg. Did you backup those partitions?
Ebizza said:
Try to restore stock modem and stock fsg. Did you backup those partitions?
Click to expand...
Click to collapse
No didn’t back up. If you have can you please send me? I’m out of ideas at this point. Thanks
Eljay227 said:
No didn’t back up. If you have can you please send me? I’m out of ideas at this point. Tha
Click to expand...
Click to collapse
You should have made a backup na.
Text me on Telegram +2347018132403. I'll send you my files.
Related
My Samsung note 2 won't move from the boot screen. It does boot into recovery when I press the buttons but it won't mount any files. Sideloading works through ADB but then that's just about it as it gives me errors. Tried to use Odin to unbrick it but it keeps giving me errors. What do I do? How do I unbrick my phone? I have posted a screenshot of the errors I am getting. Can someone please advise on what I should do?
boshez said:
My Samsung note 2 won't move from the boot screen. It does boot into recovery when I press the buttons but it won't mount any files. Sideloading works through ADB but then that's just about it as it gives me errors. Tried to use Odin to unbrick it but it keeps giving me errors. What do I do? How do I unbrick my phone? I have posted a screenshot of the errors I am getting. Can someone please advise on what I should do?
Click to expand...
Click to collapse
I have almost a same situation here with my brothers phone. I don't know why, but every time he manages to brick it like that. When booting into recovery from rom (power menu), it crashes the phone and it gets in a bootloop trying to get into the recovery.
What I did:
- Reflash recovery through odin (odin succes, phone fail)
- Reflash recovery through odin and erase nand (same...)
The only fix I found was to flash the stock rom and nand erase through odin, then flash the recovery (twrp 2.8.6.0), erase almost everything (sys, data, cache) and flash custom rom.
Looking at your pic, after nand write it fails, it could be that your nand chip is dead, and if it is like that, move to an other phone, it isn't worth to get a new mobo for your phone, those things cost more than 100 euro and a great new phone would get about 250 from you (like that asus zenfone, I think that is the one you should aim for if you want mid class to high class phones)
boshez said:
My Samsung note 2 won't move from the boot screen. It does boot into recovery when I press the buttons but it won't mount any files. Sideloading works through ADB but then that's just about it as it gives me errors. Tried to use Odin to unbrick it but it keeps giving me errors. What do I do? How do I unbrick my phone? I have posted a screenshot of the errors I am getting. Can someone please advise on what I should do?
Click to expand...
Click to collapse
The firmware you trying to flash xxalj3 (saw at screenshot) is very old 4.1.1 with sds bug also. Probably your phone has newer bootloader and 4 this you can't flash it, download latest firmware from Sammy and try again.
Sent from my GT-N7100
So I found out that my phone went through SDS. Had to get a new eMMC chip. the imei number got screwed up as well.
boshez said:
So I found out that my phone went through SDS. Had to get a new eMMC chip. the imei number got screwed up as well.
Click to expand...
Click to collapse
Sorry to hear this.
Sent from my GT-N7100
vagsvag said:
Sorry to hear this.
Sent from my GT-N7100
Click to expand...
Click to collapse
Got my phone to start working again after I installed a new eMMC. However when I updated it to a 4.4.2 Stock ROM, it won't register on to the network.
boshez said:
Got my phone to start working again after I installed a new eMMC. However when I updated it to a 4.4.2 Stock ROM, it won't register on to the network.
Click to expand...
Click to collapse
Your imei is normal or something 0004....? Corrupted general imei
Sent from my GT-N7100
vagsvag said:
Your imei is normal or something 0004....? Corrupted general imei
Sent from my GT-N7100
Click to expand...
Click to collapse
IMEI is the same as the one on the phone. I believe I must have installed the wrong ROM. I installed the N7100XXUFNL1 one which said Pakistan but then now that I checked it again, I found out it was for Nigeria, UAE, etc (which share the same CSC). Now I am downloading the N7100XXUFND4 one. Hope it makes a difference. I did backup my IMEI etc incase there is an issue.
boshez said:
IMEI is the same as the one on the phone. I believe I must have installed the wrong ROM. I installed the N7100XXUFNL1 one which said Pakistan but then now that I checked it again, I found out it was for Nigeria, UAE, etc (which share the same CSC). Now I am downloading the N7100XXUFND4 one. Hope it makes a difference. I did backup my IMEI etc incase there is an issue.
Click to expand...
Click to collapse
Samsung had made efs partition update when released 4.3 if I remember well. This update was making by the kernel when was flashing the fw was updating the efs too. If you haven't flash original firmware via odin 4.3 or later probably your efs is not updated. Try to flash original fw via odin, I think it will work.
Sent from my GT-N7100
Hi guys,
I've clicked Device Test on the Hidden Menu and the phone went into ATT mode. However, it wont boot, saying Secure Boot Error, Boot Certification Verify 680 or 670 sometimes.
I have a custom ROM installed, and through the recovery I've already tried to flash my ROM again, but it is still not booting. How can I fix this?
Please help me!
Thank you
WilsonML5 said:
Hi guys,
I've clicked Device Test on the Hidden Menu and the phone went into ATT mode. However, it wont boot, saying Secure Boot Error, Boot Certification Verify 680 or 670 sometimes.
I have a custom ROM installed, and through the recovery I've already tried to flash my ROM again, but it is still not booting. How can I fix this?
Please help me!
Thank you
Click to expand...
Click to collapse
Your Phone is bricked now - sounds not good ..
same issue. please dose anyone have an answer on how to fix this?
bybader said:
same issue. please dose anyone have an answer on how to fix this?
Click to expand...
Click to collapse
Wich model do you have ?
FrankySmith said:
Wich model do you have ?
Click to expand...
Click to collapse
D855 on rooted lolipop
FrankySmith said:
Wich model do you have ?
Click to expand...
Click to collapse
I have D855 rooted stock rom though!
I managed to fix mine using this guide: http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Just flash stock ROM using the .TOT method
WilsonML5 said:
I managed to fix mine using this guide: http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Just flash stock ROM using the .TOT method
Click to expand...
Click to collapse
thank you for the reply but this is not really a fix for me since i don't have a backup of my data, there are things on my phone that i can't afford to lose yet, if there are other ways to try that would be great.
things i have tried so far:
re-flashing boot.img and aboot.img
flashing stock Marshmallow rom
also i read somewhere here that dirty flashing the kernel might fix this but i have no idea on how to do that.
any ideas?
Guys here i am again, i was able to successfully flash the generic .224 firmware for my E6883 (z5p dual) on xperiablog it said there to "Tick Simlock.ta" if it appears on the flashtool. so i did so and now after flashing my phone boots but theres no signal on sim 1 and 2. Baseband shows on about phone even IMEI. how can i fix this? Please someone help me
Check APN
Sent from my E6853 using XDA-Developers mobile app
Technically this is considered to be a brick... Whatever tut told you to remove them should be revised or deleted. Did you make a backup before flashing anything? I also have a E6883, *IF* I can extract the keys to unlock... I will send them to you. Just need to figure that out, as I've only done this with a GS device... You can also try flashing the stock firmware, http://zonexservice.blogspot.com/2015/06/all-stock-rom-sony-xperia-firmware.html sometimes the FTF files are there.
Also curious when you type *#*#7378483#*#* do you have an IMEI?
dude9946 said:
Technically this is considered to be a brick... Whatever tut told you to remove them should be revised or deleted. Did you make a backup before flashing anything? I also have a E6883, *IF* I can extract the keys to unlock... I will send them to you. Just need to figure that out, as I've only done this with a GS device... You can also try flashing the stock firmware, http://zonexservice.blogspot.com/2015/06/all-stock-rom-sony-xperia-firmware.html sometimes the FTF files are there.
Also curious when you type *#*#7378483#*#* do you have an IMEI?
Click to expand...
Click to collapse
I actually saw the tut on xperiablog. They said there to tick on simlock.ta and never untick it. I've been flashing a lot of xperia devices and this is the only time i check to see what's changed on flashing firmware. About backup, yes i do have a backup using twrp for my 185 stock rom, should i try and restore that and see if it will fix the issue. And btw, my IMEI shows thats its ok, it doesnt show that its null
augie7107 said:
Check APN
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
Its not about mobile data, what i mean is there is no signal on the phone even if simcard is inserted
dyepnoodle said:
I actually saw the tut on xperiablog. They said there to tick on simlock.ta and never untick it. I've been flashing a lot of xperia devices and this is the only time i check to see what's changed on flashing firmware. About backup, yes i do have a backup using twrp for my 185 stock rom, should i try and restore that and see if it will fix the issue. And btw, my IMEI shows thats its ok, it doesnt show that its null
Click to expand...
Click to collapse
Oh perfect! I would restore from your backup/ I imagine you would have tried that by now...
dude9946 said:
Oh perfect! I would restore from your backup/ I imagine you would have tried that by now...
Click to expand...
Click to collapse
problem is even if my phone has unlocked bootloader now its not allowing me to fastboot a kernel and recovery. i get an error that says Failed. i tried relocking and unlocking via flashtool but no luck on flashing a recovery. it looks like its flashing it but gives an error
dyepnoodle said:
problem is even if my phone has unlocked bootloader now its not allowing me to fastboot a kernel and recovery. i get an error that says Failed. i tried relocking and unlocking via flashtool but no luck on flashing a recovery. it looks like its flashing it but gives an error
Click to expand...
Click to collapse
OH! okay I assumed you could flash... I'm not sure what your options would be if you cant get into recovery or flash.
dyepnoodle said:
problem is even if my phone has unlocked bootloader now its not allowing me to fastboot a kernel and recovery. i get an error that says Failed. i tried relocking and unlocking via flashtool but no luck on flashing a recovery. it looks like its flashing it but gives an error
Click to expand...
Click to collapse
I had the same issue in Xperia Z. I used unlock bootloader command many times but after that flashing recovery/boot always failed. Until i downgraded my phone to 4.3JB (in my case), fortunately successful.
You can try by downgrading to version on which you had successfully unlocked your bootloader, first time.
dyepnoodle said:
problem is even if my phone has unlocked bootloader now its not allowing me to fastboot a kernel and recovery. i get an error that says Failed. i tried relocking and unlocking via flashtool but no luck on flashing a recovery. it looks like its flashing it but gives an error
Click to expand...
Click to collapse
Did you allow OEM unlocking in the developer settings?
Sent from my Z5 Premium using XDA Labs
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
I have the LG G8 from Verizon. About a year ago I was trying to root it and got so frustrated with it that I ended up deleting all the partitions on. So bad that all it can do is go into edl mode. Well today I downloaded the chinese kdz tools and I've used it to extract I think dz to dz. I don't know what to do with the G82010g_00_VZW_US_0918_img file it made. Please somebody help me get my phone back to working.
johnnycm77 said:
I have the LG G8 from Verizon. About a year ago I was trying to root it and got so frustrated with it that I ended up deleting all the partitions on. So bad that all it can do is go into edl mode. Well today I downloaded the chinese kdz tools and I've used it to extract I think dz to dz. I don't know what to do with the G82010g_00_VZW_US_0918_img file it made. Please somebody help me get my phone back to working.
Click to expand...
Click to collapse
So, bad situation, as you know. Follow this link to a windows based kdz extractor tool.
Hopefully that will extract your vzw kdz. If so, flash abl, boot, laf and dtbo partitions to both slots using edl. That should give you download mode so you can use lgup to refurbish the vzw kdz.
I've never had to do this, so not sure what the result will be. Since you deleted all partitions, I don't know if they will be 'rebuilt' completely, with imei etc. But at this point, you've nothing to lose.
good luck
AsItLies said:
So, bad situation, as you know. Follow this link to a windows based kdz extractor tool.
Hopefully that will extract your vzw kdz. If so, flash abl, boot, laf and dtbo partitions to both slots using edl. That should give you download mode so you can use lgup to refurbish the vzw kdz.
I've never had to do this, so not sure what the result will be. Since you deleted all partitions, I don't know if they will be 'rebuilt' completely, with imei etc. But at this point, you've nothing to lose.
good luck
Click to expand...
Click to collapse
How do I flash them?
johnnycm77 said:
How do I flash them?
Click to expand...
Click to collapse
" partitions to both slots using edl."
AsItLies said:
" partitions to both slots using edl."
Click to expand...
Click to collapse
What do I use to do that. Im not too familiar with qualcomm
johnnycm77 said:
What do I use to do that. Im not too familiar with qualcomm
Click to expand...
Click to collapse
you said you deleted all partitions didn't you? How did you do that? It was edl mode and qfil wasn't it? As that's what's in guides section to root device.
that's what you use. Except this time, don't make the same mistake. This time, follow the guide to and flash partitions.
there are no other ways.
Yea but they were already there in the partition manager
johnnycm77 said:
Yea but they were already there in the partition manager
Click to expand...
Click to collapse
Check this guide. It addresses your situation exactly.