Related
hi,
my USB port on my phone is broken and I need to go back to stock ROM for warrenty. Currently I use the Paranoid ROM 4.2.2 JDQ39 (3.67) and TWPR recovery. I read a lot of posts but I didn´t find a complete guide. So I want to ask if I can do it this way?
1. Close Bootloader with "BootUnlocker for Nexus Devices" app from the playstore
2. Download Factory Image 4.2.2 from the google developers page
Extract everything. I need the files: System.IMG, Boot.IMG, Userdata.IMG, Recovery.IMG ? Or do I need other files?
3. Install Mobile Odin Pro on my phone
4. Load the IMG files in Mobile Odin Pro and start
Is this right? What is with the radio? I have XXLJ1 on my phone. I think it is the latest. Isn´t it?
It would be nice if someone can help me.
thanks
//Patrice// said:
hi,
my USB port on my phone is broken and I need to go back to stock ROM for warrenty. Currently I use the Paranoid ROM 4.2.2 JDQ39 (3.67) and TWPR recovery. I read a lot of posts but I didn´t find a complete guide. So I want to ask if I can do it this way?
1. Close Bootloader with "BootUnlocker for Nexus Devices" app from the playstore
2. Download Factory Image 4.2.2 from the google developers page
Extract everything. I need the files: System.IMG, Boot.IMG, Userdata.IMG, Recovery.IMG ? Or do I need other files?
3. Install Mobile Odin Pro on my phone
4. Load the IMG files in Mobile Odin Pro and start
Is this right? What is with the radio? I have XXLJ1 on my phone. I think it is the latest. Isn´t it?
It would be nice if someone can help me.
thanks
Click to expand...
Click to collapse
You'll have to close the bootloader last otherwise you won't be able to flash the imgs.
I don't know if you'll can, you'll have to keep root when you reset it because you'll have to lock the bootloader last, then you could factory reset.
Not sure though.
Beauenheim said:
You'll have to close the bootloader last otherwise you won't be able to flash the imgs.
I don't know if you'll can, you'll have to keep root when you reset it because you'll have to lock the bootloader last, then you could factory reset.
Not sure though.
Click to expand...
Click to collapse
I thought I don't need a open bootloader for Odin Mobile?
I just did this with the same problem about a month ago, and I relocked the bootloader first because you won't have root or a way to use fastboot to lock it afterward. Odin worked just fine with bootloader locked.
underwaterjr said:
I just did this with the same problem about a month ago, and I relocked the bootloader first because you won't have root or a way to use fastboot to lock it afterward. Odin worked just fine with bootloader locked.
Click to expand...
Click to collapse
You did it the same way as I described it in my first post?
Does nobody know if i can do it this way?
Sent from my Galaxy Nexus using xda app-developers app
i sent my gnex in for the same broken usb port issue, and all i did to the bad one was do a factory reset on cm10.whatever it was at the time, and locked the bootloader with that app, probably did that first i guess lol.
but they havent charged me for that, so i assume its all good, its been a few months so if they were going to charge me they would have i assume
un4givn85 said:
i sent my gnex in for the same broken usb port issue, and all i did to the bad one was do a factory reset on cm10.whatever it was at the time, and locked the bootloader with that app, probably did that first i guess lol.
but they havent charged me for that, so i assume its all good, its been a few months so if they were going to charge me they would have i assume
Click to expand...
Click to collapse
But I´m not sure if it works for me too, so I would like to try to go back to stock ROM. The problem is that I don´t know if it works with this guide and I don´t want to make a mistake.
can anyone tell me if it is possible to use the 4.2.2 factory image from the google developers site or do I have to use a special odin file?
If I have to use a odin file where can I find it? I only found old files with android 4.0.1
thanks in advance for any help.
Can anybody help me with my problem? I try to go back to stock to send it in.
Thanks
Sent from my Transformer TF101 using xda app-developers app
This may or may not be relevant but I used to have a T989 (TMO GSII) and the USB port when bad as well. Any connection that I attempted would last brief moments and in one of those, I took the chance and tried restoring. What ended up happening is the update did not complete and the phone remained in the ODIN screen even after reboots. I sent it in like so and they still honored the warranty. So what I'm trying to say, as a last resort you could intentionally brick your GN...
I have heard however, that warranty companies don't always check to see if you've messed with the software so there's another thought.
Just send it back as is. Your problem is hardware related, not software. They'll refurb the phone and re-image it anyway.
Thanks for your answers!
OK I understand. But is it that dangerous to go back to stock without USB, so I shouldn't do it or is it only that you think it is not necessary?
Sent from my Transformer TF101 using xda app-developers app
Hi,
I have still the same problem. Is nobody here who can help me?
I have the problem that I don´t know if I can use the guide from my first post, and which file I can use.
thanks for any help!
//Patrice// said:
Hi,
I have still the same problem. Is nobody here who can help me?
I have the problem that I don´t know if I can use the guide from my first post, and which file I can use.
thanks for any help!
Click to expand...
Click to collapse
Why dont you download this on your phone directly http://forum.xda-developers.com/showthread.php?t=1882248 and then flash it using Mobile Odin or Recovery. Dont flash SuperUser. Factory reset and then lock the bootloader.
Wouldnt that work?
rajuki said:
Why dont you download this on your phone directly http://forum.xda-developers.com/showthread.php?t=1882248 and then flash it using Mobile Odin or Recovery. Dont flash SuperUser. Factory reset and then lock the bootloader.
Wouldnt that work?
Click to expand...
Click to collapse
I think I could flash this with TWRP, if it´s no problem that I come from Paranoid 4.2.2 ? But it is not really stock. Is it? What happen than when I do the factory reset? Does it erase TWRP? And I think I need root to lock the bootloader...
//Patrice// said:
I think I could flash this with TWRP, if it´s no problem that I come from Paranoid 4.2.2 ? But it is not really stock. Is it? What happen than when I do the factory reset? Does it erase TWRP? And I think I need root to lock the bootloader...
Click to expand...
Click to collapse
So lets try this again, OK?
1. Download the stock rom from the link and copy to your phone
2. Boot into TWRP
3. Wipe data
4. Flash the stock 4.3 rom you downloaded
5. Reboot.
Now, you have stock 4.3 but you are still rooted. A factory reset from the OS doesnt unroot you or takes away your root.
6. Download this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en and lock yout bootloader. This will do a wipe again.Now reboot.
7. Remove /system/bin/su via adb shell or by using root explorer
8. Remove /system/app/Superuser.apk via adb shell on phone or by using root explorer
9. Factory reset.
Done. By now, you should be stock, unrooted and without any custom recoveries.
rajuki said:
So lets try this again, OK?
1. Download the stock rom from the link and copy to your phone
2. Boot into TWRP
3. Wipe data
4. Flash the stock 4.3 rom you downloaded
5. Reboot.
Now, you have stock 4.3 but you are still rooted. A factory reset from the OS doesnt unroot you or takes away your root.
6. Download this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en and lock yout bootloader. This will do a wipe again.Now reboot.
7. Remove /system/bin/su via adb shell or by using root explorer
8. Remove /system/app/Superuser.apk via adb shell on phone or by using root explorer
9. Factory reset.
Done. By now, you should be stock, unrooted and without any custom recoveries.
Click to expand...
Click to collapse
OK this sounds good. I will try it.
Thank you!!
rajuki said:
So lets try this again, OK?
1. Download the stock rom from the link and copy to your phone
2. Boot into TWRP
3. Wipe data
4. Flash the stock 4.3 rom you downloaded
5. Reboot.
Now, you have stock 4.3 but you are still rooted. A factory reset from the OS doesnt unroot you or takes away your root.
6. Download this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en and lock yout bootloader. This will do a wipe again.Now reboot.
7. Remove /system/bin/su via adb shell or by using root explorer
8. Remove /system/app/Superuser.apk via adb shell on phone or by using root explorer
9. Factory reset.
Done. By now, you should be stock, unrooted and without any custom recoveries.
Click to expand...
Click to collapse
I have one more question. In step 3 should I do a factory reset before I flash the rom? Because I usually do one when I install a new rom and I don't want to do a mistake because I can't use usb to fix it. And is it OK that I go from 4.2.2 Paranoid to this 4.3 stock rom?
//Patrice// said:
I have one more question. In step 3 should I do a factory reset before I flash the rom? Because I usually do one when I install a new rom and I don't want to do a mistake because I can't use usb to fix it. And is it OK that I go from 4.2.2 Paranoid to this 4.3 stock rom?
Click to expand...
Click to collapse
Before you flash the new ROM; you must wipe data.
And yes, its OK to come from 4.2.2 to 4.3 as long as you wipe data.
Got the update at 2am, posting it so maybe custom roms can get WiFi calling, feel free to mirror just asking you keep them in the thread.
https://docs.google.com/file/d/0B7lAMKoPVdWKU1VfSnRNZS10Zjg/edit?usp=docslist_api
would i be able to just flash this if i wanted to with twrp. just curious.
Android6190 said:
would i be able to just flash this if i wanted to with twrp. just curious.
Click to expand...
Click to collapse
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
dang. okay
T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
do we just flash in twrp? Thank you by the way
No it's a stock ota you have to use HTC recovery.
rubyman94 said:
do we just flash in twrp? Thank you by the way
Click to expand...
Click to collapse
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
Umm... your Firmware file is corrupted
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
I mean it could be my computer but it keeps saying its corrupted when I download it.
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
It's not, it's encrypted.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
gamer765 said:
It's not, it's encrypted.
Click to expand...
Click to collapse
Oh, well it won't let me put it on my device because the computer thinks it's corrupted
Fenny said:
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
Click to expand...
Click to collapse
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
cyclonesworld said:
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
Click to expand...
Click to collapse
If you're SOFF and supercid just flash the lollipop ruu T-Mobile just release. It doesn't matter what previous rom you're on. Then reflash custom recovery and rooted. I've done this alot of time already.
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
rickpref said:
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
Click to expand...
Click to collapse
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
bradley_e_smith said:
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
Click to expand...
Click to collapse
Wow, that sounds much simpler, thanks...gonna try that now.
Radio
Any chance someone can please post a flashable zip with the new t-mo radio?
Where would I get the stock recovery for this fw and update. I want to root but keep my ota
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)
Hey,
Quick question, I'm away on holiday and had to use an RUU to reset my phone completely back to stock. I don't have my PC with me but was wondering if there might be any other way to get TRWP installed so I can get back to custom ROM's before the end of my trip?
Regards,
Ravi
rav101 said:
Hey,
Quick question, I'm away on holiday and had to use an RUU to reset my phone completely back to stock. I don't have my PC with me but was wondering if there might be any other way to get TRWP installed so I can get back to custom ROM's before the end of my trip?
Regards,
Ravi
Click to expand...
Click to collapse
I've described how to do this for CM-based ROMS with Samsung devices. Unfortunately, I know of no way to do this for the HTC 10. The issue is getting it rooted. My understanding is that the Sunshine app can root some 10s, but not all. You could try that. When you run the app it will do a series of tests on your device. If it cannot be rooted by the app it will give the message, "Root is required first." Otherwise, the app can root your device and proceed from there. Once rooted you could then use Flashify to install TWRP.
2PS6IMG.zip
rav101 said:
Hey,
Quick question, I'm away on holiday and had to use an RUU to reset my phone completely back to stock. I don't have my PC with me but was wondering if there might be any other way to get TRWP installed so I can get back to custom ROM's before the end of my trip?
Regards,
Ravi
Click to expand...
Click to collapse
Like post 3 said. Just get the no wipe firmware that comes with twrp and change the name then reboot to download and flash it
Haldi4803 said:
2PS6IMG.zip
Click to expand...
Click to collapse
twinnfamous said:
Like post 3 said. Just get the no wipe firmware that comes with twrp and change the name then reboot to download and flash it
Click to expand...
Click to collapse
Thanks guys!!
I'm trying to figure out, if I want to flash just the recovery with the no wipe zip, can I delete all the other .img files within the zip or do I have to edit the Android-info.txt for the corresponding lines?
No issue in flashing the no wipe file as it is, just curious for future reference if I wanted to create easy 2PS6IMG.zip's in the future.
Sent from my HTC 10 using XDA Labs
I simply take the firmware.zip from OTA, delete all .img files, rename twrp.IMG to recovery.IMG and repack it to 2PS6IMG.zip
You don't need to change the android-info.txt as partitions without images won't get wiped, even if it says so.
You can flash Boot, Recovery and..... And.... Which was the third one? Without S-Off or signed firmware package.
My oneplus 3 has no OS installed. I am unable to install the stock os because my it states that my devices is "" and the one I am trying to install is for oneplus 3. PLEASE HELP.
Do you have unlocked bootloader?
Do you have custom recovery?
Can you boot the device to fastboot or recovery?
Did you try using flashing tools to flash a ROM?
Do you have root permission, adb or you have OEM unlock enabled?
Lastly, Is your phone in bootloop or is soft/hard bricked?
To ask for help you need to provide necessary information first.
No one can just look at this
My oneplus 3 has no OS installed. I am unable to install the stock os because my it states that my devices is "" and the one I am trying to install is for oneplus 3. PLEASE HELP.
Click to expand...
Click to collapse
And say, hmm I know exactly what he needs. Here I am the miracle maker the problem solver comiiing~~
We aren't in the powerpuff girls world here, get real please.
XDHx86 said:
Do you have unlocked bootloader?
Do you have custom recovery?
Can you boot the device to fastboot or recovery?
Did you try using flashing tools to flash a ROM?
Do you have root permission, adb or you have OEM unlock enabled?
Lastly, Is your phone in bootloop or is soft/hard bricked?
To ask for help you need to provide necessary information first.
No one can just look at this
And say, hmm I know exactly what he needs. Here I am the miracle maker the problem solver comiiing~~
We aren't in the powerpuff girls world here, please be realistic.
Click to expand...
Click to collapse
My phone is soft bricked. My bootloader is unlocked and there is a custom recovery which is blu spark. Also I do have root permission. Seems like my os is completely wiped, so my phone is stated as " " . When I try to install through recovery, it states that the zip file is for oneplus 3 and that my device is " ".
Have you tried solving your softbrick?
Try this:
Back up your data.
Flash the original TWRP.
Flash your desired ROM.
Make sure that the ROM you're trying to flash is meant for your device.
Don't forget the necessary drivers, fastboot tools, and cleaning dalvik cache once you're done.
Also flashing a ROM means losing root access, you may want to flash magisk again.
XDHx86 said:
Have you tried solving your softbrick?
Try this:
Back up your data.
Flash the original TWRP.
Flash your desired ROM.
Make sure that the ROM you're trying to flash is meant for your device.
Don't forget the necessary drivers, fastboot tools, and cleaning dalvik cache once you're done.
Also flashing a ROM means losing root access, you may want to flash magisk again.
Click to expand...
Click to collapse
Thanks for the help. I was able to fix the problem. Right now I am updating to the latest android version of oneplus 3.
Hitman00770 said:
Thanks for the help. I was able to fix the problem. Right now I am updating to the latest android version of oneplus 3.
Click to expand...
Click to collapse
Happy to help.