Related
Hi guys, since the development is started i think that we also need a way to restore the watch to the stock FW.
HOWTO:
- download from the following links the boot, recovery and system image;
- reboot to fastboot and:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and then go to recovery and do a wipe data / factory reset.
LINK:
Boot
Recovery
System
UPDATE: MarshMallow
system
boot
recovery
When I boot to recovery, all I get is the Android on it's back with the Red ! triangle.
Also, will I be able to re-lock the bootloader?
pTeronaut said:
When I boot to recovery, all I get is the Android on it's back with the Red ! triangle.
Also, will I be able to re-lock the bootloader?
Click to expand...
Click to collapse
Did u try to touch the screen?
Skin1980 said:
Did u try to touch the screen?
Click to expand...
Click to collapse
Yes. no response.
Skin1980 said:
Hi guys, since the development is started i think that we also need a way to restore the watch to the stock FW.
HOWTO:
- download from the following links the boot, recovery and system image;
- reboot to fastboot and:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and then go to recovery and do a wipe data / factory reset.
LINK:
Boot
Recovery
System
Click to expand...
Click to collapse
can you please help me with the step by step guide of flashing LG Watch urbane. I have downloaded from all the links you have given.
I am new to flashing anything to Wear.
@pTeronaut From what I've read elsewhere on this forum, it seems that if the recovery is doing that after a flash, you should boot into the bootloader and you should be able to get into recovery through there.
Do you think that is possible to return to Android 5 from Android 6?
Do you known a site (official if possible) to download the Android 5 ROM?
Thanks
bartito said:
Do you think that is possible to return to Android 5 from Android 6?
Do you known a site (official if possible) to download the Android 5 ROM?
Thanks
Click to expand...
Click to collapse
The links i posted are for the Lollipop Rom
Is there any possibilites to lock bootloader? I tryed fastboot oem lock but i`ve got: FAILED (command write failed (unknown error))
Got it to work. Just installed latest adb and rebooted the computer.
Do we have md5sum's for these?
So if I have v6 on my watch can I downgrade back to V5 so I can have root? for some reason I unlocked the bootloader, but I can't get TWRP or root on the watch since the last update. I'm familer with android but this is my first smartwatch.
Anyone still on these forums? I bought this watch off swappa and the guy had AW 2.0 installed on it. I wanted to unlock the bootloader and stuff so I did. Once the watch rebooted it is now stuck on the bootanimation. It's not bootlooping because it's not going back to the LG logo. It's just staying on the Android bootanimation. Any help is greatly appreciated.
spc_hicks09 said:
Anyone still on these forums? I bought this watch off swappa and the guy had AW 2.0 installed on it. I wanted to unlock the bootloader and stuff so I did. Once the watch rebooted it is now stuck on the bootanimation. It's not bootlooping because it's not going back to the LG logo. It's just staying on the Android bootanimation. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. Go to bootloader
https://www.youtube.com/watch?v=-BshOHvAKUw
2. Install this recovery: https://dl.twrp.me/bass/twrp-3.1.0-0-bass.img.html
3. format system and data partition to ext4 and go to sideload
4. Do only step 1 and 6 from this https://forum.xda-developers.com/showpost.php?p=71751597&postcount=5
I installed AsteroidOS and need the stock userdata partition, however I cannot find it. Do you know where can I get the img?
majekqwert said:
1. Go to bootloader
2. Install this recovery: https://dl.twrp.me/bass/twrp-3.1.0-0-bass.img.html
3. format system and data partition to ext4 and go to sideload
4. Do only step 1 and 6 from this https://forum.xda-developers.com/showpost.php?p=71751597&postcount=5
Click to expand...
Click to collapse
Same problem, how do I install the recovery I am very new to this
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
How do we go about to install this
jemmini said:
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
Click to expand...
Click to collapse
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
ItGuyJax8430 said:
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
Click to expand...
Click to collapse
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
jemmini said:
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
Click to expand...
Click to collapse
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
ItGuyJax8430 said:
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
Click to expand...
Click to collapse
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
During the loop, I get this message.
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
jemmini said:
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
Click to expand...
Click to collapse
Can you provide step by step instructions?
I imagine it would be something like this.
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit?
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
xdadev_user11 said:
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
Click to expand...
Click to collapse
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
emowing said:
Can you provide step by step instructions?
Click to expand...
Click to collapse
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
jemmini said:
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
Click to expand...
Click to collapse
I'm planning on trying out TWRP later today. Before I do that, what files should I grab (as a backup) and from where should I grab them? I'm happy to upload them for others, too.
So I will be able to root the phone with this? After unlocking bootloader and flashing twrp I flash supersu?
jemmini said:
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
Click to expand...
Click to collapse
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
emowing said:
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
Click to expand...
Click to collapse
The confirmation he means is after you execute the unlock command, on the phone screen asks you to confirm by press volume up. That all.
[del]
xdadev_user11 said:
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
Click to expand...
Click to collapse
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
acotto said:
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
Click to expand...
Click to collapse
Nice find :good:. I'll try it when I get my phone.. it will be delivered today.
emowing said:
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
Click to expand...
Click to collapse
So I unlocked bootloader and also got the bootloop. I flashed this firmware to fix it, but I found out the radio included is not the same as the US version, so now the sim cards don't work.
The firmware image have a file called "MT6753_Android_scatter.txt" which determine what partition to flash. Base on this guide http://www.mtkroms.com/2015/03/how-to-restore-lost-imei-on-any.html, the "secro" partition being replaced may be what caused the issue, so looked like that's what I have unchecked before flashing.
jemmini said:
..
Click to expand...
Click to collapse
I just discovered that you can back the secro and many other partition within TWRP. I don't know if that alone will fix the sim problem. WRONG
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?
ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:
ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)