Database Develop

Boot loop after update

Hi. Last night I've updated to las OTA. After reboot and installation it make a reboot and never start again, it stopped in gear live initial logo and stay there until batteries end.
Now, when I plug the watch it show battery logo forever and if I press the bottom enough time it goes to startup infinite loop.
Some help?
Thanks!
Sent from my SM-N910F using XDA Free mobile app

Things that I've try:
Go into bootloader Ok.
Go into recovery fail: Do nothing and start to warmup.
Download twrp version 2.7.1.2-sp.img and twrp 2.8.6.0 and fastboot boot twrp.img: Nothing fastboot say ok and after that just nothing, watch start to warm
Download SamsungGearLive-sprat-ddPull-AdamOutlerDevice-24July2014.tar.gz ... inside lots of img's files, I've try to boot with recovery.img and.... nothing.
I'm soooo lost.

Mquinteiro said:
Things that I've try:
Go into bootloader Ok.
Go into recovery fail: Do nothing and start to warmup.
Download twrp version 2.7.1.2-sp.img and twrp 2.8.6.0 and fastboot boot twrp.img: Nothing fastboot say ok and after that just nothing, watch start to warm
Download SamsungGearLive-sprat-ddPull-AdamOutlerDevice-24July2014.tar.gz ... inside lots of img's files, I've try to boot with recovery.img and.... nothing.
I'm soooo lost.
Click to expand...
Click to collapse
Ok first things first: is your bootloader unlocked? if not then you can't flash/boot anything that is not signed by the Samsung/Google for our specific watch. So you can't boot into TWRP unless you unlock it. fastboot oem unlock will unlock it, but for security purposes, it will also reset your watch to factory.

Thanks Aligatror, it is not unlocked, i wish to restore to stock and I've tried to boot from external google//samsung recovery with out look.
Regarding the stock firmware i can't find anywhere instructions about how to flash everything and were to find factory images.
Thanks!
Sent from my SM-N910F using XDA Free mobile app

Did you try the Gear Live restore tool? It's in the gear live android development forum

Brendo said:
Did you try the Gear Live restore tool? It's in the gear live android development forum
Click to expand...
Click to collapse
Yes, it is a great tool, but there appears to be a broken bluetooth file in the v3 image which makes it impossible to pair watch to a phone. So, use V2 instead.

Brendo said:
Did you try the Gear Live restore tool? It's in the gear live android development forum
Click to expand...
Click to collapse
I do it and .... worst! now it still in boot loop but everithime show de lable "Recovery booting" Even in batery charge!
The only thing that works is bootloader.
Note I've unlocked and locked

Mquinteiro said:
I do it and .... worst! now it still in boot loop but everithime show de lable "Recovery booting" Even in batery charge!
The only thing that works is bootloader.
Note I've unlocked and locked
Click to expand...
Click to collapse
Which version did you download and what option did you select? Recovery boot message is normal when you do unlock since it erases the user partition. Select option to restore to stock or something like that in that program you downloaded. Just make you that you have version 2 and not 3.

I did with version 2 and 3 I do it by hand because linux script does not work.
I've flash boot recovery and system partitions included in the tool zip file.
And. ... nothing
Sent from my SM-N910F using XDA Free mobile app

Mquinteiro said:
I did with version 2 and 3 I do it by hand because linux script does not work.
I've flash boot recovery and system partitions included in the tool zip file.
And. ... nothing
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Is it still stuck in bootloop? Can you boot into recovery from bootloader?

I can't boot into recovery. Only bootloader works.
Every time that I press recovery from bootloader I get an "recovering boot " forever
Sent from my SM-N910F using XDA Free mobile app

Mquinteiro said:
I can't boot into recovery. Only bootloader works.
Every time that I press recovery from bootloader I get an "recovering boot " forever
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Lets try something more radical.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
And then flash boot, recovery and system.

No, I can't go into recovery, just Bootloader. recovery hangs and normal boot hangs too.
I have take a look to update script and it have a new img for partitions associated with it.. I have flashed all of them and.... nothing.

Mquinteiro said:
No, I can't go into recovery, just Bootloader. recovery hangs and normal boot hangs too.
I have take a look to update script and it have a new img for partitions associated with it.. I have flashed all of them and.... nothing.
Click to expand...
Click to collapse
Try reflashing the bootloader itself. Download latest OTA update
sprat-LDZ22J-from-LWX49K.1e8de7cf.zip
Extract it and you'll see bunch of files "bootloader.xxxx.img". Flash all of the .img files.
fastboot flash apnhlos bootloader.apnhlos.img
fastboot flash aboot bootloader.aboot.img
.... and so on with all bootloader files.
Reboot bootloader and try booting into recovery or system.

aligatro2010 said:
Try reflashing the bootloader itself. Download latest OTA update
sprat-LDZ22J-from-LWX49K.1e8de7cf.zip
Extract it and you'll see bunch of files "bootloader.xxxx.img". Flash all of the .img files.
fastboot flash apnhlos bootloader.apnhlos.img
fastboot flash aboot bootloader.aboot.img
.... and so on with all bootloader files.
Reboot bootloader and try booting into recovery or system.
Click to expand...
Click to collapse
It is exactly what I did yesterday and no luck!
The only thing that I coulden't did was flash 5.1.1 recovery, and other partitions because it come like .p files (dif images)
But thanks

Mquinteiro said:
It is exactly what I did yesterday and no luck!
The only thing that I coulden't did was flash 5.1.1 recovery, and other partitions because it come like .p files (dif images)
But thanks
Click to expand...
Click to collapse
Well I guess your only option is to flash to 4.4, flash older bootloader and request repair service from Samsung.

aligatro2010 said:
Yes, it is a great tool, but there appears to be a broken bluetooth file in the v3 image which makes it impossible to pair watch to a phone. So, use V2 instead.
Click to expand...
Click to collapse
Is the watch effectively bricked once that image is flashed? I've come across your post too late after reading about the tool. Used v3, told the tool to restore to stock, the watch boots its image fine but the bluetooth is definitely broken now (phone won't connect to it). I can get to settings to enable ADB on wear but I can't authorize my PC it seems, never get the notification on the watch screen to allow the PC. It's just stuck at the initialization telling me to Install Android Wear on my phone.

naaaaail said:
Is the watch effectively bricked once that image is flashed? I've come across your post too late after reading about the tool. Used v3, told the tool to restore to stock, the watch boots its image fine but the bluetooth is definitely broken now (phone won't connect to it). I can get to settings to enable ADB on wear but I can't authorize my PC it seems, never get the notification on the watch screen to allow the PC. It's just stuck at the initialization telling me to Install Android Wear on my phone.
Click to expand...
Click to collapse
Its not bricked, but the bluetooth is not working due to corrupted file. You can flash v2 no problem. Just make sure to do reset after flashing.

[MoFo IMG] 5.1 Rooted AT&T XT1097 with Tether

Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.

Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?

Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.

Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!

Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.

Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!

The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.

Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?

What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!

bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.

Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!

bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?

bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.

Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.

bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.

bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.

bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.

Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?

bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?

bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.

XT 890 Stuck on Warning Bootloader Unlocked / Fastboot and Recovery Access possible

Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras

rassle said:
Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras
Click to expand...
Click to collapse
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?

Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
im actually trying with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml which has the title of XT890_emara-user 4.1.2 9.8.2I-50_SMI-26 1358465787 release-keysSUNRISE_SMB_REV30_V2_R3_1251.B
i do have problems of finding stock roms as most links are pointing to sbf droid developers (cant post link due to beeing new) which is dead for me.
ive used shadows mirror list, but its only showing non-4.1.2 versions for me. however, im not quite sure which firmware was one the phone before *sorry*
by commands of the xml file u mean the xml file which is contained in the "firmware" downloads for the XT890?

Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/

rassle said:
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/
Click to expand...
Click to collapse
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root

Hazou said:
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root
Click to expand...
Click to collapse
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?

rassle said:
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?
Click to expand...
Click to collapse
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support

rassle said:
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support
Click to expand...
Click to collapse
Good that it worked. The message will remain there. I don't know how to fix that issue. But I don't think it is a huge issue, but its annoying.

Oneplus 3 decryption Ultimate guide

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!

TWRP stuck on splash screen?

I just got my 3T, flashed TWRP, flashed the new OOS Beta 2 build, and changed my 3T's splash image. Now out of nowhere, TWRP will get stuck in its logo. I didn't flash anything the last time it worked, it just randomly stopped working after a backup. I've gave it a few minutes, tried older/newer versions, and deleting the .twrps file on the internal storage. Does anyone know what's going on and how to fix it, preferably without wiping data?
Edit: I can boot into OOS just fine and everything but TWRP works.

Just fastboot flash the lastest twrp https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308

I had the same problem a few hours ago...
I flashed the latest TWRP and then booted it via fastboot (fastboot boot twrp-3.0.3-1-oneplus3t.img.).
I waited 1-2 minutes, rebooted it into TWRP again (this time not via fastboot but with the buttons of the phone). After a few minutes I finally saw the usual TWRP UI.
I don't know why or how, but it worked.

It also takes a long time for me here..

mximer said:
I had the same problem a few hours ago...
I flashed the latest TWRP and then booted it via fastboot (fastboot boot twrp-3.0.3-1-oneplus3t.img.).
I waited 1-2 minutes, rebooted it into TWRP again (this time not via fastboot but with the buttons of the phone). After a few minutes I finally saw the usual TWRP UI.
I don't know why or how, but it worked.
Click to expand...
Click to collapse
Thanks. I had to wait about 6 minutes, but it worked.

I have similar problem but for me just get black screen with only notification led on... I have tried everything (reflash, dm verity zip, swap zip, f2fs version etc.) but nothing work. Im using RR rom, EXT4, decrypted. Only way to boot recovery is "fastboot boot twrp.img"

zige said:
I have similar problem but for me just get black screen with only notification led on... I have tried everything (reflash, dm verity zip, swap zip, f2fs version etc.) but nothing work. Im using RR rom, EXT4, decrypted. Only way to boot recovery is "fastboot boot twrp.img"
Click to expand...
Click to collapse
Me to
Trimis de pe al meu ONEPLUS A3003 folosind Tapatalk

Same thing happened with me. Followed the usual "flash recovery" and "boot" approach. Got stuck at splash forever.
Removed the USB cable, turned off the phone. Started the phone with "Volume Down+Power" combination and it booted in recovery after a few minutes of the splash screen.

Remember that it takes a while to boot up TWRP if you're using f2fs, the more files on the data partitions the longer it takes.

pitrus- said:
Remember that it takes a while to boot up TWRP if you're using f2fs, the more files on the data partitions the longer it takes.
Click to expand...
Click to collapse
true ! kernel source been released hopefully some one makes an advance stock kernel.

I had the same problem recently, I found a solution on a reddit post somewhere;
Basically in terminal/CMD in fastboot mode wipe cache and userdata then reboot to recovery.
Code:
fastboot format cache
fastboot format userdata
Worked for me.
Disclaimer; Data will be lost!
Edit: found OP https://www.reddit.com/r/Nexus6P/comments/4agvpc/help_android_n_twrp_hangs_at_splash_screen/

This a late addition to the thread but it will hopefully avoid continued confusion or new threads on the same subject. It seems that Nougat defaults to ext4 for the SYSTEM (and boot?) partitions but f2s2 for the DATA partition. TWRP will open within seconds with an EXT based partition but will take several minutes (eg 5-10) to open if your DATA is f2s2. You can live with it for now, or you can reformat your DATA partition to EXT4. Note that this will wipe out all of your data!

bowlandspoon said:
I had the same problem recently, I found a solution on a reddit post somewhere;
Basically in terminal/CMD in fastboot mode wipe cache and userdata then reboot to recovery.
Code:
fastboot format cache
fastboot format userdata
Worked for me.
Disclaimer; Data will be lost!
Edit: found OP https://www.reddit.com/r/Nexus6P/comments/4agvpc/help_android_n_twrp_hangs_at_splash_screen/
Click to expand...
Click to collapse
Just replying to say this worked on my Redmi Note 3 even though this isn't the correct forum. Formatting cache only doesn't work, you must format both cache and userdata, so I hope you have a backup. I wonder what causes this...

You sir are a saint. This command worked for me I was able to boot into TWRP
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
I was able to boot into TWRP after formatting
Osga21 said:
Just replying to say this worked on my Redmi Note 3 even though this isn't the correct forum. Formatting cache only doesn't work, you must format both cache and userdata, so I hope you have a backup. I wonder what causes this...
Click to expand...
Click to collapse