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.
Related
Hello guys! Any ROM i try to install fails. I can`t mount system partition. Please help!
Recovery TWRP
Calanderia said:
Hello guys! Any ROM i try to install fails. I can`t mount system partition. Please help!
Recovery TWRP
Click to expand...
Click to collapse
Which ROM are you trying to install and which version of TWRP are you using?
Are you s off? Rooted?
stovie_steve said:
Which ROM are you trying to install and which version of TWRP are you using?
Are you s off? Rooted?
Click to expand...
Click to collapse
slim, maximus, one plus... everything fails... TWRP 2.8.0.2, s-on, rooted
Right we need a bit more info than that...
Please post a fastboot getvar all leaving out your serial number and IMEI
stovie_steve said:
Right we need a bit more info than that...
Please post a fastboot getvar all leaving out your serial number and IMEI
Click to expand...
Click to collapse
i managed to resolve the isssue... formating system to ext4 format, mounted it but still can`t flash roms, phone freezing... after another hour of struggling it simply work with slimkat
P.S.: Thx for trying to help
TWRP 2.7.1.1
Calanderia said:
i managed to resolve the isssue... formating system to ext4 format, mounted it but still can`t flash roms, phone freezing... after another hour of struggling it simply work with slimkat
P.S.: Thx for trying to help
Click to expand...
Click to collapse
Flash TWRP 2.7.x.x version. All the roms you are trying to install are incompatible with TWRP 2.8.x.x. I had the same issue. Copy all the files on the phone storage using twrp. Now reboot to bootloader. I hope you have fastboot files that you used to unlocked bootloader. now rename twrp .img file to "recovery.img." Connect you phone to laptop/computer and run this command line. fastboot flash recovery recovery.img" That's it. Once the process is done reboot to recovery and install rom.
Hi guys!
So i unlocked my m7 and though i could flash a twrp custom recovery.
But somehow the phone stuck on fastboot usb when i boot to recovery via cmd command promp...
I got :
C:\xxxxxxxxx\mini-sdk>fastboot boot twrp-3.0.0-2-m7.img
downloading 'boot.img'... OKAY
booting... OKAY
But the phone won t boot to recovery.
The vol up/down doesn t work either so i had to use power button to shut down my phone..
Tried many times but it didn t work.
Somebody knows why is that ?
nARDOs said:
Hi guys!
So i unlocked my m7 and though i could flash a twrp custom recovery.
But somehow the phone stuck on fastboot usb when i boot to recovery via cmd command promp...
I got :
C:\xxxxxxxxx\mini-sdk>fastboot boot twrp-3.0.0-2-m7.img
downloading 'boot.img'... OKAY
booting... OKAY
But the phone won t boot to recovery.
The vol up/down doesn t work either so i had to use power button to shut down my phone..
Tried many times but it didn t work.
Somebody knows why is that ?
Click to expand...
Click to collapse
The "fastboot boot recovery.img" is not supported in hboot 1.54 to 1.61 (was only supported in 1.44). So you can't boot a recovery you must flash it over your stock recovery using "fastboot flash recovery twrp-3.0.0-2-m7.img":
Code:
fastboot flash recovery twrp-3.0.0-2-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then reboot in recovery mode.
alray said:
The "fastboot boot recovery.img" is not supported in hboot 1.54 to 1.61 (was only supported in 1.44). So you can't boot a recovery you must flash it over your stock recovery using "fastboot flash recovery twrp-3.0.0-2-m7.img":
Code:
fastboot flash recovery twrp-3.0.0-2-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then reboot in recovery mode.
Click to expand...
Click to collapse
Thanks
Got custom recovery.
Just need to find a stock recovery next time :good:
Another question: is the nandroid backup size that big ? it said 6504 MB and i have only about 2700MB available..
Need to free some space...........
nARDOs said:
Thanks
Got custom recovery.
Just need to find a stock recovery next time :good:
Another question: is the nandroid backup size that big ? it said 6504 MB and i have only about 2700MB available..
Need to free some space...........
Click to expand...
Click to collapse
Nandroid backup of? It depends what is included in the backup.... if the data partition is included and there were a lot of things saved on the phone then yes it can be really big.... Normally id say around 1.5 gb is normal when its a stock backup without any user data.
alray said:
Nandroid backup of? It depends what is included in the backup.... if the data partition is included and there were a lot of things saved on the phone then yes it can be really big.... Normally id say around 1.5 gb is normal when its a stock backup without any user data.
Click to expand...
Click to collapse
Was actually thinking of stock backup without user data.
Do i have to backup "Boot" also ? or only the "system".
nARDOs said:
Was actually thinking of stock backup without user data.
Do i have to backup "Boot" also ? or only the "system".
Click to expand...
Click to collapse
Boot is the kernel and system is the OS. I would recommend to backup both of them. Boot isn't very big so it worth being backed up.
Sent from my HTC One using XDA Labs
alray said:
Boot is the kernel and system is the OS. I would recommend to backup both of them. Boot isn't very big so it worth being backed up.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
OK.
Is the Root feature on TWRP stable ? Can i use it to root ?
alray said:
Boot is the kernel and system is the OS. I would recommend to backup both of them. Boot isn't very big so it worth being backed up.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Hi again,
Can I find stock recovery.img on the nandroid file ?
Didn t find it t there.
nARDOs said:
OK.
Is the Root feature on TWRP stable ? Can i use it to root ?
Click to expand...
Click to collapse
If you are going to use twrp's root make sure you have a recent twrp version otherwise it will flash an outdated SU version and cause a Bootloop. But yes it's a reliable method, if you prefer you can flash the latest supersu.zip file from twrp.
nARDOs said:
Hi again,
Can I find stock recovery.img on the nandroid file ?
Didn t find it t there.
Click to expand...
Click to collapse
Stock recovery isn't included in a nandroid. What is your version-main number? Will try to find it for you.
Sent from my HTC One using XDA Labs
alray said:
If you are going to use twrp's root make sure you have a recent twrp version otherwise it will flash an outdated SU version and cause a Bootloop. But yes it's a reliable method, if you prefer you can flash the latest supersu.zip file from twrp.
Stock recovery isn't included in a nandroid. What is your version-main number? Will try to find it for you.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Thanks mate.
Mine is 7.19.401.51.
nARDOs said:
Thanks mate.
Mine is 7.19.401.51.
Click to expand...
Click to collapse
yep make sure to use SuperSu 2.65
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
alray said:
yep make sure to use SuperSu 2.65
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Click to expand...
Click to collapse
Thanks :good:
Do u know a better custom ROM which is not based on sense ?
I m thinking about miui v6 (don t know if there is stable miui v7 for m7) or cm12 (or stable cm13)
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!
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)
I recently dusted off my Nexus 6 to test a few projects on and wanted to update everything. But no matter what I try within TWRP, every zip/img fails. Any guidance on how to repair the filesystem would be helpful. The attached images is the error. For now it seems shamu has been beached:crying:
Running TWP 3.1.1.0
ROM: LineageOS, not sure which version
Android version: 7.1.1
Bootloader is unlocked
Update to the latest TWRP and see if that helps. You want version 3.2.1-0.
https://dl.twrp.me/shamu/
Thanks, I just tried that. I was able to flash the recovery img through adb, but any attempt to flash a zip through fails with the same errors
format data on twrp you will lose everything so do backup
belive ihave the same problen but when i formated data with twrp the problem is gone so got to twrp - wipe -format data Type yes
ctrl1122 said:
Thanks, I just tried that. I was able to flash the recovery img through adb, but any attempt to flash a zip through fails with the same errors
Click to expand...
Click to collapse
Your safest bet would be going for a factory image, and then reflash twrp and then try again to see if everything is allright.
Or try formatting data from TWRP, like person above me mentioned. USB Drive+otg adapter might come in handy to keep stuff you want to flash there
VarDes said:
Your safest bet would be going for a factory image, and then reflash twrp and then try again to see if everything is allright.
Or try formatting data from TWRP, like person above me mentioned. USB Drive+otg adapter might come in handy to keep stuff you want to flash there
Click to expand...
Click to collapse
I'll give this a shot, seems likely it will rebuild the corrupted bits.
MiroALG said:
format data on twrp you will lose everything so do backup
belive ihave the same problen but when i formated data with twrp the problem is gone so got to twrp - wipe -format data Type yes
Click to expand...
Click to collapse
After doing this, data fails mount in TWRP. I will tryflashing a factory image. Thanks!
ctrl1122 said:
I'll give this a shot, seems likely it will rebuild the corrupted bits.
After doing this, data fails mount in TWRP. I will tryflashing a factory image. Thanks!
Click to expand...
Click to collapse
no problem back to stock with NRT then root and flash twrp and try it will fix all your problem
---------- Post added at 02:13 AM ---------- Previous post was at 02:12 AM ----------
MiroALG said:
no problem back to stock with NRT then root and flash twrp and try it will fix all your problem
Click to expand...
Click to collapse
but when you format your data you need to reboot to recovery again the copy your rom zip and gapps to your phone with pc or otg and flash
ctrl1122 said:
I'll give this a shot, seems likely it will rebuild the corrupted bits.
After doing this, data fails mount in TWRP. I will tryflashing a factory image. Thanks!
Click to expand...
Click to collapse
Success! Running the latest build now. Thanks everyone, I appreciate your time.