I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!
Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta
Youngunn2008 said:
Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.
penser said:
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.
Click to expand...
Click to collapse
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock
Dude oh my god I had this same issue on a different device, I forgot what the fix was. If I come up with something I'll let you know.
Sent from my MB886 using xda app-developers app
I think he has to get the motorola factory programming cable to fix it, since it acts like a os for you to load a new os to your phone. Sorry I don't know a link on where to buy.
penser said:
I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!
Click to expand...
Click to collapse
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
fastboot flash modem NON-HLOS.bin
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot erase cache
fastboot reboot-bootloader
fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img
fastboot reboot
Click to expand...
Click to collapse
if everything is done right, your device is now ok.
Silentwidow said:
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock
Click to expand...
Click to collapse
Flashed stock with Myth about 3 times, didn't work.
Aingaran said:
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
if everything is done right, your device is now ok.
Click to expand...
Click to collapse
I'll try that. Thanks!
EDIT: It worked!
penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
Click to expand...
Click to collapse
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there
penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
EDIT: It worked!
Click to expand...
Click to collapse
nice to hear it worked :highfive:
Aingaran said:
nice to hear it worked :highfive:
Click to expand...
Click to collapse
I thanked ya cause he didn't
skeevydude said:
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there
Click to expand...
Click to collapse
I always flash all partitions. Its just good practice
Sent from my MB886 using Tapatalk 4 Beta
Related
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
pplude said:
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
Click to expand...
Click to collapse
The harder this phone is to mod, the more it seems worth it Thanks for trying!
@pplude
Can you give any more detail on the root file you flashed to your droid 3?
Is it really from an Atrix? Are there any downsides to running this root partition?
The reason I ask is - the Atrix has been rooted, so perhaps this would be a good way to attack the droid 3.
Here's the Atrix root hack. Care to give it a try if you're still feeling brave?
http://www.motorolaatrixforum.com/m...s-f15/how-to-root-motorola-atrix-4g-t318.html
It's the preinstall partition from the atrix. There's no integrity check there so it flashes A-OK. I suppose the preinstall from any phone would work though.
You're the second one to do that successfully. I think it was discussed at length as a potential source for root, but we couldn't get the permissions we wanted out of it for some reason. I think it came down to nosuid, but I'm not positive. The root thread talks more about it.
thingonaspring said:
@pplude
Can you give any more detail on the root file you flashed to your droid 3?
Is it really from an Atrix? Are there any downsides to running this root partition?
The reason I ask is - the Atrix has been rooted, so perhaps this would be a good way to attack the droid 3.
Here's the Atrix root hack. Care to give it a try if you're still feeling brave?
http://www.motorolaatrixforum.com/m...s-f15/how-to-root-motorola-atrix-4g-t318.html
Click to expand...
Click to collapse
I used that on my Atrix way back (a month ago , to enable sideloading, I believe.
You want me to give it a try on the D3 (i.e., flash the /preinstall partition?)
That's what I used to break out of fastboot. Can't help us because of nosuid and noxec built in at the kernel level.
pplude said:
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
Click to expand...
Click to collapse
I see you said you've reflashed a half-bricked D3 with an image from Atrix? You said it was root.img?? Did you mean boot.img? I have an Atrix too, and don't see this partition anywhere. Did you or someone pull it with dd? If you have it, could you send it to me and tell me what command you used to flash in moto-fastboot or fastboot?
I tried flashing from the OTA and I'm **** out of luck at the moment, after borking /system trying to make the OTA update in recovery. It's been one headache after another with this fine device
rynosaur said:
I see you said you've reflashed a half-bricked D3 with an image from Atrix? You said it was root.img?? Did you mean boot.img? I have an Atrix too, and don't see this partition anywhere. Did you or someone pull it with dd? If you have it, could you send it to me and tell me what command you used to flash in moto-fastboot or fastboot?
I tried flashing from the OTA and I'm **** out of luck at the moment, after borking /system trying to make the OTA update in recovery. It's been one headache after another with this fine device
Click to expand...
Click to collapse
What the OP is describing only works with fastboot. It sounds like you're able to get into recovery, a completely different system. Start a new thread if this is the case and I'll try to help you out.
psouza4 said:
What the OP is describing only works with fastboot. It sounds like you're able to get into recovery, a completely different system. Start a new thread if this is the case and I'll try to help you out.
Click to expand...
Click to collapse
I have flashed a partition that failed the verification check and now I can't do anything but boot into BP menu. Really, my problem and his are/were pretty similar, I think.
rynosaur said:
I have flashed a partition that failed the verification check and now I can't do anything but boot into BP menu. Really, my problem and his are/were pretty similar, I think.
Click to expand...
Click to collapse
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
pplude said:
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
Click to expand...
Click to collapse
Thanks. I haven't located the /preinstall you're talking about yet, but I believe you're talking about the the /preinstall that was used to unlock the bootloader, or are you talking about the initial power cord-recovery hack? Anywho, I've been able to successfully flash /system and /boot, but I'm looping into BP menu. The fight continues . . .
EDIT: There are some partitions that the phone will not let me flash in Fastboot, and I think least one of those is my problem (like BP, for example). I keep getting a permissions error, and I am using moto-fastboot in linux or windows.
rynosaur said:
Thanks. I haven't located the /preinstall you're talking about yet, but I believe you're talking about the the /preinstall that was used to unlock the bootloader, or are you talking about the initial power cord-recovery hack? Anywho, I've been able to successfully flash /system and /boot, but I'm looping into BP menu. The fight continues . . .
EDIT: There are some partitions that the phone will not let me flash in Fastboot, and I think least one of those is my problem (like BP, for example). I keep getting a permissions error, and I am using moto-fastboot in linux or windows.
Click to expand...
Click to collapse
My success was using the Android SDK fastboot binary on Windows using PowerShell. And yes, it was the preinstall used to unlock the bootloader. I don't have a copy of it anymore, I seem to remember Ben64 on the IRC Freenode Channel #KrazyK giving it to me.
Huh -- so, despite the fact that Atrix4g won't do squat with regular fastboot, you're recommending it for this problem on the Droid3? Interesting. I did find the preinstall you're speaking of -- I actually found two, just in case. Thanks for your help so far, I will report back.
That's why I recommend using PowerShell (free download from Microsoft.com), it's a fully POSIX compliant shell and ADB/Fastboot is a lot more useful with it!
pplude said:
That's why I recommend using PowerShell (free download from Microsoft.com), it's a fully POSIX compliant shell and ADB/Fastboot is a lot more useful with it!
Click to expand...
Click to collapse
Roger that -- I've been using it since I installed Win7 two years ago. The only thing that's better is bash, in my opinion, and I have already seen where flashing a failed phone/bootloader only works with powershell, for some reason.
pplude said:
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
Click to expand...
Click to collapse
Can you help me out with a step-to-step instruction?
I cannot boot into recovery mode, it switch to AP Fastboot mode and says "BOOT FAILURE".
jchenny said:
Can you help me out with a step-to-step instruction?
I cannot boot into recovery mode, it switch to AP Fastboot mode and says "BOOT FAILURE".
Click to expand...
Click to collapse
Did you already do a factory reset? If you haven't do not!
rynosaur said:
Did you already do a factory reset? If you haven't do not!
Click to expand...
Click to collapse
I did try to factory reset...but again it reboots to the AP Fastbook screen again, and wouldn't let me reset it...
The phone still works, just somehow the camera does not work, I have tried 3 or 4 different camera Apps, and none works...
jchenny said:
I did try to factory reset...but again it reboots to the AP Fastbook screen again, and wouldn't let me reset it...
The phone still works, just somehow the camera does not work, I have tried 3 or 4 different camera Apps, and none works...
Click to expand...
Click to collapse
I'm guessing your drivers are messed up. Did you already flash the OTA or copy parts of the OTA into your /system directory?
I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx
devastatorx said:
I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx
Click to expand...
Click to collapse
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.
giveen said:
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.
Click to expand...
Click to collapse
I've now got it on Honeycomb, and booting into fastboot to flash recovery presents an identical error
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas?
Update: I figured I'd try booting from the image file rather than try to flash just to see, oddly enough this works using: fastboot boot recoveryname.img. Now if I could get it to flash...
Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2
giveen said:
Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm don't intend to be condescending, but I clearly state in my last post that I had since successfully flashed Honeycomb and was no longer working with 2.2. Since then I have attempted to flash both cwm and twrp with no success. I am able to boot either of them from fastboot and have flashed ics-b5 cm9 which is what I am currently running. So I'm working around by booting the image from fastboot rather than flashing. I'm curious as to why it is throwing the error and what the error means exactly.
Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2
giveen said:
Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using fastboot from the android sdk
devastatorx said:
I'm using fastboot from the android sdk
Click to expand...
Click to collapse
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.
giveen said:
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.
Click to expand...
Click to collapse
I'll give that a go, thanks giveen.
error getvarartition-type:userdata user(0x2)
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!
santi1928 said:
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!
Click to expand...
Click to collapse
1. Start your own thread, don't hijack others
2. Need more info , as in logs, more description on what happens when you press power, charge status, did you install the drivers after downloading them, did you put the device in fastboot mode, what color of underwear are you wearing etc etc etc
****deleted*****
My phone is f'd up.
I tried installing Liquid Smooth 6/10 version, and I got nothing but system UI FC's over and over. So, I held power and volume up until the screen rebooted, and then volume down to get to bootloader.
Then, I selected recovery from there. When I got into recovery, there was nothing in the internal memory, so I did the "fix" where you type in adb on your computer. Every thing went well, I suppose, but when I tried to reboot, it went to the splash screen and did nothing else.
Well, I went back into recovery to restore a backup, a stock Sense back up, and TWRP rebooted. It has been doing this every time I try to get into recovery. I can't do anything. I even installed a previous TWRP by going into bootloader and using an SD converter card with my PC, because ADB doesn't even recognize the device anymore.
I was using Cpt Throwbacks recovery, the newest one, and then I tried reverting to an older one.
Any help....PLEASE!?
Have you tried formatting data and internal storage?
Do you have a recovery log?
Captain_Throwback said:
Have you tried formatting data and internal storage?
Do you have a recovery log?
Click to expand...
Click to collapse
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
mcwups1 said:
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
Click to expand...
Click to collapse
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Captain_Throwback said:
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Click to expand...
Click to collapse
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
mcwups1 said:
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
Click to expand...
Click to collapse
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Captain_Throwback said:
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Click to expand...
Click to collapse
I will try partition repair, but is that on the newest version only?
I can still get into bootloader, and when I plug it in to my computer, it still makes the connection sound, but recovery will not stay active. After about 10 seconds, it reboots to splash screen, but goes no further because I don't believe there is anything installed now.
Well, it won't stay in TWRP long enough to do anything. My internal is there now at least. I just don't get it.
Running RUU as we speak. I hope that since I have the .13 firmware installed, that it won't mess up.
Wow. Again.
I made a mistake by doing a backup, then trying to install another ROM, but forgot to wipe data. Went through the process (splash screen, boot animation, updating apps) and it booted for a second and rebooted. I figured it would happen, since I didn't wipe correctly.
Try to go into TWRP, and the damn thing reboots out of TWRP! I can't stay in TWRP for more than 5-7 seconds, before it reboots on its' own. Went to flashboot to reinstall TWRP, no change. I can't even do a restore.
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
I searched for an answer, and this is all I got! My phone must be borked. Guess I'll have to RUU again.
I had this issue last night and I got it to restore a backup by unplugging it from the wall first. I think the voltage is too high or something during a flash or something.
mcwups1 said:
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
Click to expand...
Click to collapse
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Captain_Throwback said:
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Click to expand...
Click to collapse
I already RUU'd, so I should have had the appropriate firmware.
mcwups1 said:
I already RUU'd, so I should have had the appropriate firmware.
Click to expand...
Click to collapse
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Captain_Throwback said:
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Click to expand...
Click to collapse
I ended up RUU'ing again.
If it happens again, I will take your advice and report back.
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)