Related
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Seleren said:
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Click to expand...
Click to collapse
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Lucky Thirteen said:
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
Click to expand...
Click to collapse
I have the International model.
jbharbin said:
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Click to expand...
Click to collapse
Tried that already, nothing changed at all, TWRP logo shows up and then the phone reboots to ROM. CWM works partially as I said, it reboots when I tell it do do anything (backup/wipe/flash) and the phone is unaffected.
Bump. Help please, I tried flashing another kernel but that didn't help. I can't even wipe or flash another ROM in CWM.
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Try redownloading the recovery and rewriting it. It may be a bad download.
Sent from my One X+ using xda premium
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Flash the kernel and then the recovery with fastboot and see what happens.
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
@Seleren I would be interested to know if the above worked for you? Also useful if anyone else gets this problem
Lucky Thirteen said:
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
Click to expand...
Click to collapse
I've already tried that numerous times, I can get to erasing cache etc but once I try to boot into the recovery ... I'm done. TWRP won't boot even after erasing cache. CWM fails at wiping/backuping/flashing and just reboots without any notice at all. I'm really out of ideas now.
Sorry for a bit late answer.
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
Seleren said:
Hello there,
... A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery....
Click to expand...
Click to collapse
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Lucky Thirteen said:
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Click to expand...
Click to collapse
Yes, I am correctly rooted, I've rooted numerous phones, I unlocked using the official HTC method. I could say I'm not a complete noob to Android. I wouldn't even post here if I didn't try all the standard procedures.
I flashed the Non-touch CWM yesterday and nothing changed (not that I expected it to). I decided I'll try flashing the bootloader in the end but I have to back up my whole SDCard before that ...
Bump.
SALVATION
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
hukel56 said:
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
Click to expand...
Click to collapse
wut?! TWRP = Recovery
boot.img = KERNEL
Seleren said:
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Click to expand...
Click to collapse
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Lloir said:
wut?! TWRP = Recovery
boot.img = KERNEL
Click to expand...
Click to collapse
Yea idk. But this happens
Lloir said:
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Click to expand...
Click to collapse
I wish that was the problem, I tried quite a few versions, including the one from ALL IN ONE toolkit, an older version that previously worked, the latest version and the ViperX version. Trust me, that was not the problem.
hukel56 said:
Yea idk. But this happens
Click to expand...
Click to collapse
What Lloir meant to say was that the boot.img has nothing to do with the recovery, so flashing a boot.img will NOT change your recovery to so-said TWRP.
TWRP is being flashed by a different command namely 'flash recovery' instead of 'flash boot' like previously mentioned boot.img
As I was using CM 4.4.2, everything was going fine, I had 3 bars of LTE, and then I tried to make a call and it said mobile networks not available, I checked my signal in the status bar and it still said LTE and data still worked fine. I went to my phone settings and checked it and it said my mobile network was unknown, and my phone number was 000-000-0000. I wiped, and flashed CM10.2(4.3) and it did the exact same thing, only this time it said my phone number, but still, I couldn't make any calls or text, I've tried flashing two sense 5 roms and none of them display my phone number or let me call or text, but upon changing the subscription type from global to LTE/CDMA, it gives me LTE data, but that's it...Can anyone please help me?
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
rejectedjs said:
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
santod040 said:
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
rejectedjs said:
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
Click to expand...
Click to collapse
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
rejectedjs said:
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
Click to expand...
Click to collapse
No problem bud.
Glad that worked out for you.
Same process always fixes 3g/4g issues after flashing many roms for me, on all of my devices.
:good:
This exact thing happened to me a few weeks ago. Busted my ass trying to fix it, after a few days of no service i finally got it.
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
The way you fixed it seems a lot easier than what I did. I returned to s-on, 1.15 hboot and the oldest firmware. Now my phone's bootloader will always say tampered too, since i had to HTC dev unlock it to get root.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
:good: Can't thank you enough.
I have a second DNA that I have not been able to use.
Since Moonshine S-off I have not had any data connection. It has been very frustrating.
Followed your steps and now it's back up and running.
Awesome my friend, just awesome. Thank you.
quick question
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
LuckyPuppy said:
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
Click to expand...
Click to collapse
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
how to
sdamark said:
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
Click to expand...
Click to collapse
Awesome! Thank you so much!
Where is there a stock rom
thayl0 said:
Where is there a stock rom
Click to expand...
Click to collapse
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
sdamark said:
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
Click to expand...
Click to collapse
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
thayl0 said:
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
Click to expand...
Click to collapse
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
sdamark said:
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
Click to expand...
Click to collapse
why would i do a dirty install?
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
uNdea said:
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
Click to expand...
Click to collapse
You do know flashing 3.06 ruu makes it stock recovery. Not sure of you flashed a Rom or a ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk
Hi all,
The story is that I had Linage flashed, but it said it was time to update the firmware, so I tried to do that.
I booted in twrp and flashed the most recent firmware. I had plenty of power on the battery. But after it finished it booted into a classic miui interface. From here it only got worse. It asked for my password which I entered several times, but it was incorrect.
What I tried was to clear the storage. But I get the same error when it boots - it boots into miui, then shortly after a google load screen and then it reboots.
I tried downloading the mi flash tool. But when I connect the phone and locate the file, the screen has just one line in the corner saying something like "press any key to reboot".
With the adb command it doesn't seem like there is actually made a connection.
I do not really care which OS you suggest I install, as long as it at least can get it up and running again.
------------------
I just got it into fastboot and it goes fine with fastboot devices where I can see that it is connected, but when I enter fastboot flash recovery twrp.img then the phone reboots with an error code in the cmd window saying:
"FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed"
Any suggestions to what I can do? Can it be the twrp image that is causing the issue?
twrp-3.3.0-0-beryllium.img 30.3mb
kitkat87 said:
Hi all,
The story is that I had Linage flashed, but it said it was time to update the firmware, so I tried to do that.
I booted in twrp and flashed the most recent firmware. I had plenty of power on the battery. But after it finished it booted into a classic miui interface. From here it only got worse. It asked for my password which I entered several times, but it was incorrect.
What I tried was to clear the storage. But I get the same error when it boots - it boots into miui, then shortly after a google load screen and then it reboots.
I tried downloading the mi flash tool. But when I connect the phone and locate the file, the screen has just one line in the corner saying something like "press any key to reboot".
With the adb command it doesn't seem like there is actually made a connection.
Any suggestions to what I can do?
I do not really care wchich OS you suggest I install, as long as it at least can get it up and running again.
Click to expand...
Click to collapse
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:https://xiaomifirmwareupdater.com/firmware/beryllium/
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
sotosgolf said:
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:https://xiaomifirmwareupdater.com/firmware/beryllium/
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
Click to expand...
Click to collapse
is it fastboot flash file link which you have provided above?
hondraopranav said:
is it fastboot flash file link which you have provided above?
Click to expand...
Click to collapse
Twrp!
You flash firmware as a normal zip.
I understand that twrp works for you.
If it doesn't, flash twrp through fastboot and then proceed as i mention above
Thanks for your replies.
The problem I have is that fastboot does not really seem to work.
When I try to do a fastboot command I get the error that goes:
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
Also, I just tried the Mi unlock tool and it seems that it cannot create a connection with the usb cable - so could that be the reason that I cannot flash it?
kitkat87 said:
Thanks for your replies.
The problem I have is that fastboot does not really seem to work.
When I try to do a fastboot command I get the error that goes:
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
Also, I just tried the Mi unlock tool and it seems that it cannot create a connection with the usb cable - so could that be the reason that I cannot flash it?
Click to expand...
Click to collapse
Download twrp for poco f1 from the official twrp site.
When everything is ready and you have pressed flash, THEN boot into fastboot and connect the cable
Edit: you also might have relocked your bootloader. If what I mention above doesn't work, unlock your bootloader again with the unlock file Xiaomi originally sent you.
sotosgolf said:
Download twrp for poco f1 from the official twrp site.
When everything is ready and you have pressed flash, THEN boot into fastboot and connect the cable
Edit: you also might have relocked your bootloader. If what I mention above doesn't work, unlock your bootloader again with the unlock file Xiaomi originally sent you.
Click to expand...
Click to collapse
The phone doesn't boot into a system, and currently as I load fastboot whenever the connection to the computer is made it goes to a screen saying 'press any key to turn off'.
I did notice, though, that after I from recovery wipe all data, then in the first boot it encrypts the phone. But it never manages to get the OS up and running.
------
Just downloaded the latest twrp from the official site. And when I tried to flash it I got the same error
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
kitkat87 said:
I did notice, though, that after I from recovery wipe all data, then in the first boot it encrypts the phone. But it never manages to get the OS up and running.
Click to expand...
Click to collapse
Let's get this straight m8,
Can you boot into recovery ("up"+"power")?
Yes or No?
Thanks for your replies.
sotosgolf said:
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
Click to expand...
Click to collapse
HI mate,
I wanna check how long did it take to install Android 10 on your poco?
Cuz I installed the rom for more than 30 minutes after reboot and it is not over by follow your steps.
Idk what's the problem with my poco.
------------------------------------------------------------
New update:
Finally, I completed flash the rom, and Idk what's the problem, lol
I can boot into both fastboot and recovery. The recovery is Mi-recovery 3.0. Though, in recovery it doesn't seem that I can get any connection with it.
-----------
update
Currently, when I do anything beyond fastboot devices I get the screen reading "press any key to shutdown"
sotosgolf said:
Let's get this straight m8,
Can you boot into recovery ("up"+"power")?
Yes or No?
Click to expand...
Click to collapse
I can boot into mi-recovery 3.0 but no twrp or other custom recovery.
kitkat87 said:
I can boot into mi-recovery 3.0 but no twrp or other custom recovery.
Click to expand...
Click to collapse
You most likely had your bootloader re-locked. You have to unlock it again
sorry for the late reply.
I downloaded MiFlashPro, and apparently I could flash miui 11. So far, so good. But as I tried to flash or even boot into twrp I got the same command as I used to.
Can the issue be because I maybe don't have the latest drivers installed?
kitkat87 said:
I can boot into both fastboot and recovery. The recovery is Mi-recovery 3.0. Though, in recovery it doesn't seem that I can get any connection with it.
-----------
update
Currently, when I do anything beyond fastboot devices I get the screen reading "press any key to shutdown"
Click to expand...
Click to collapse
Do you have all the drivers installed on your pc ?
ADB and Fasboot drivers. And try using usb 2.0 ports. Mi tools have issues with usb 3.0 ports. And You should be on an Intel processor. You can also try twrp 3.3.1 beta by @Reignz.
Hello. I've tried many different ways to install the customs ROMs on here for Moto G8 Power (XT2041-3) but nothing has worked. When I try to flash using fastbootd every ROM except the Lineage one fails at the stage where I try to load the system.img. Even when I think I've correctly installed Lineage that way, when I go to reboot my phone it won't boot properly. I keep getting the screen alternating between the Motorola icon and the unlocked bootloader warning screen. It does that repeatedly for a while and then eventually boots as if I am powering on my phone for the first time out of the box after buying it.
So I've also tried TWRP. Again, I can seemingly install some of the flashable zips (Lineage and Omnirom), but when I reboot the same thing happens. Motorola screen, unlocked bootloader warning screen, etc, repeately for a couple of minutes, and then it boots to the Android system that came with the phone. As if there's been a total factory reset and I am turning on the phone for the first time. ADB sideload doesn't work either because even though it can detect ADB devices at first, as soon as I go to sideload on TWRP and then try "adb sideload .....zip" on the terminal of my computer (Linux) it doesn't seem to recognise any ADB devices any more.
I know it says to reboot to recovery after installing a custom ROM, but the same thing happens if I try that. Some sort of bootloop I think, and then basically a factory reset start.
TWRP doesn't seem to permanently install on my phone. If I try going into bootloader and then recovery after I have just used TWRP then all I get is the 'No Command' screen. Could this be part of the reason? I recently found out about DM-Verity. Could something on my phone be preventing changes to the system? It's really frustrating. Previously when I've installed custom ROMs on other Motorola phones I haven't had any problems. Any suggestions would be much appreciated. Thanks
Check out my post here.
Thanks tinbilly but I'm still unsure what to do. I hadn't tried CrDroid before so before anything I tried flashing those image files via fastbootd. Same problem - it failed at system.img. Which leaves me unable to boot into custom ROM or stock ROM. Before when that has happened I have always been able to just reflash stock using the commands on the XML file. Now even the first command fails (fastboot getvar max-sparse-size) so I don't seem to be able to get back to stock at the moment. I'll keep trying.
I didn't know how you flashed stock ROM to partition b. The only way I can think to change to partition b is to go into fastbootd and use the "fastboot set_active b" command. Or to flash TWRP (which doesn't work at the moment) and change slots that way. I think changing it on fastbootd might have messed me up a bit because it just went into a bootloop when I tried to do anything after that. For some reason I seem to be back in partition a now though (I typed "fastboot getvar all" while I was in fastbootd and it came back showing slot a).
Here is my suggestions:
1. Hard reset your device following this or this. They are basically the same instruction. Hopefully this will get your phone back to the stock rom. If not, then just try step 2 below.
2. Install the xt2041-3 stock rom on your device by following the instructions in the download link. Or you could try this method.
3. Once you are back to stock rom, you can install any custom rom via fastboot mode.
Hope that will help.
Thanks for that. I'm going to work on it over the weekend and see how I get on. I feel like I've spent too many valuable hours of my life trying to figure this out. If only this custom ROM thing could just be straightforward for everyone all the time.
tinbilly said:
Here is my suggestions:
1. Hard reset your device following this or this. They are basically the same instruction. Hopefully this will get your phone back to the stock rom. If not, then just try step 2 below.
2. Install the xt2041-3 stock rom on your device by following the instructions in the download link. Or you could try this method.
3. Once you are back to stock rom, you can install any custom rom via fastboot mode.
Hope that will help.
Click to expand...
Click to collapse
Cheers for your suggestions but nothing has worked. The phone wasn't taking any commands to reinstall stock ROM so I went to fastbootd (via recovery - no command - hold power button and up) and did a factory reset from there. Then I was able to flash the commands on the stock ROM xml file via the bootloader. So I got back to stock fine. But after trying to flash Lineage OS it seems to have worked fine but when I go to reboot I keep booting to bootloader. I tried fastboot oem fb_mode_clear but that didn't change anything. I'll keep trying different things and let people know if I find a solution.
lazzr said:
Cheers for your suggestions but nothing has worked. The phone wasn't taking any commands to reinstall stock ROM so I went to fastbootd (via recovery - no command - hold power button and up) and did a factory reset from there. Then I was able to flash the commands on the stock ROM xml file via the bootloader. So I got back to stock fine. But after trying to flash Lineage OS it seems to have worked fine but when I go to reboot I keep booting to bootloader. I tried fastboot oem fb_mode_clear but that didn't change anything. I'll keep trying different things and let people know if I find a solution.
Click to expand...
Click to collapse
Did you format data before or after installing lineage os? As in, where you have to type yes, not just wiping data.
Beetle84 said:
Did you format data before or after installing lineage os? As in, where you have to type yes, not just wiping data.
Click to expand...
Click to collapse
Hi Beetle. I always swipe to the right to wipe the cache etc. And after flashing I swipe to wipe the dalvik. But I'm never given the option to type yes. I'm not sure what you mean.
I've spent a lot of time wondering why TWRP never reboots when I try to reboot into recovery after flashing a zip. I just realised (after reading the instructions for flashing ArrowOS on this forum) that I can flash TWRP to partition b as well by using the commands:
fastboot flash recovery twrp.img
fastboot flash recovery_b twrp.img
By doing that I was able to (or so I thought) install the zip to the inactive slot b, and then reboot to recovery using TWRP, and it comes back as having the active slot b. I got excited but when I went to reboot system the same thing happened. Just some sort of bootloop thing. Nothing seems to work. I've tried OmniROM and Stag zips as well.
lazzr said:
Hi Beetle. I always swipe to the right to wipe the cache etc. And after flashing I swipe to wipe the dalvik. But I'm never given the option to type yes. I'm not sure what you mean.
I've spent a lot of time wondering why TWRP never reboots when I try to reboot into recovery after flashing a zip. I just realised (after reading the instructions for flashing ArrowOS on this forum) that I can flash TWRP to partition b as well by using the commands:
fastboot flash recovery twrp.img
fastboot flash recovery_b twrp.img
By doing that I was able to (or so I thought) install the zip to the inactive slot b, and then reboot to recovery using TWRP, and it comes back as having the active slot b. I got excited but when I went to reboot system the same thing happened. Just some sort of bootloop thing. Nothing seems to work. I've tried OmniROM and Stag zips as well.
Click to expand...
Click to collapse
When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.
Then reboot.
Beetle84 said:
When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.
Then reboot.
Click to expand...
Click to collapse
Thanks. I tried it but then I end up with no zip file in my internal storage so have nothing for twrp to install. I tried copying and pasting the file from my PC to my Android folder but it was going to take about a week to copy over. I also can't use ADB sideload for some reason. I get this:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
and
E:Unable to get child ID
on my phone when I cancel the sideload. I can't figure it out at all.
I also just tried flashing my stock recovery to replace twrp. After I had already used twrp to format everything. Then went to fastbootd and tried flashing the image files. They looked like they had installed but now when I reboot it automatically takes me to bootloader instead of into system.
In twrp, there's no option to wipe system. So in my case, I replaced twrp with stock recovery, then did a Factory Reset [Advanced > Reset options > Erase all data (factory reset)].
Before "tried flashing the image files" in fastbootd, did you "fastboot set_active a"?
tinbilly said:
In twrp, there's no option to wipe system. So in my case, I replaced twrp with stock recovery, then did a Factory Reset [Advanced > Reset options > Erase all data (factory reset)].
Before "tried flashing the image files" in fastbootd, did you "fastboot set_active a"?
Click to expand...
Click to collapse
I've tried the "fastboot set_active a" but it still doesn't work. I've factory reset through stock recovery too, and seem to have tried everything I can think of. I miss my old original Moto G which was easy to install on. I've been trying for weeks and keep running into the same issues. I'll keep trying over the next few days and report back if I solve it in case anyone else has the same problem.
Mine is a XT2041-1. What I did:
1. flashed back to stock ROM 10_QPE30.69-16
2. rebooted the phone, then set it up (I did not upgrade to Android 11 as notified by the system)
3. wiped the phone using System > Advanced > Reset (just to be safe)
4. flashed to crDroid 7.4 (Android11-based)
You said you failed to load the custom ROM's system.img. What is the exact error message? Please attach some screenshots as well.
tinbilly said:
Mine is a XT2041-1. What I did:
1. flashed back to stock ROM 10_QPE30.69-16
2. rebooted the phone, then set it up (I did not upgrade to Android 11 as notified by the system)
3. wiped the phone using System > Advanced > Reset (just to be safe)
4. flashed to crDroid 7.4 (Android11-based)
You said you failed to load the custom ROM's system.img. What is the exact error message? Please attach some screenshots as well.
Click to expand...
Click to collapse
I thought I'd try some more possible ways to fix it before replying but I've just wasted another few hours to no avail. I have the flashable zips for OmniROM 11 and Lineage, but I can't even get TWRP to ask for a password anymore so all my files show up as gobbledegook. Not that I think they would work either because they haven't so far.
The one that I thought had been successful was installing Lineage images using fastbootd, but whenever I go to reboot I end up in bootloader. The bootloader log says "Reboot mode set to fastboot". I have no idea how to get out of that. Fastboot fb_mode_clear doesn't work.
I thought I would try to root the phone (I know people say you don't need to do that first but I'm sure in the past I have done) but I can't get Magisk to install.
I installed Lineage images again, and then after it rebooted into bootloader I installed TWRP and tried entering the dd commands on this page in the terminal (I didn't know how to do the backup in section 2 of the instructions):
Troubleshooting: TWRP Boot Loop after OTA update in MOTO G4 (XT1621 Athene)
Hi. This is my first post in this forum. I had this problem, the phone always started in TWRP Mode after updating by OTA update, I should NOT have updated it this way, but I have done it still. :cyclops: XD To fix it, try this: TWRP Method: 1-...
forum.xda-developers.com
All I got back was "no such file or directory".
The error message from installing images (the one below was CrDroid 7.4 but it happens with most of them) seems to be quite common from what I can tell from reading other people's posts. I have also I tried "sudo" before flashing the system image because I've seen that recommended, but it didn't work either:
writing 'system_a' 5/6 (usually 3/3 on other ROMs)...
FAILED (remote: Operation not permitted)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wiping my data and formatting has caused me some issues too. I've done that many different things that I can't remember what exactly, but I do know that when I tried to install ZIP files using TWRP the Failed to mount '/system_root' error message came up a few times.
I've attached an images below to give an example of the types of other red screen messages I've had:
Forgive the long message. If any of this gives you any ideas or you've seen it before then please let me know. To be honest I just want a phone without all the google stuff on it and the amount of time I've spent on this I'm feeling like I should just get myself a different phone it would be easier to install on.
By the way, the image at the bottom there was the error message I got while trying to wipe in TWRP
A final attempt for now. I factory reset through fastbootd. Then "installed" Lineage image files. Rebooted and ended up in bootloader. Flashed TWRP, which this time could recognise my folders. ADB pushed Omnirom zip to my data folder. Tried a wipe, got lots of error messages, then tried installing the zip, and got the below:
This whole experience has been brutal.
From my experience with TWRP on my XT2041-1, I won't go with TWRP to flash a custom ROM. So just forget TWRP for now.
One important question, I think: Can you flash and boot your device to stock Android 10? [Note: I find this is a reliable method to go back to stock ROM. Just make sure you get the correct one matching your device.]
If yes, let take it as a starting point. From there, I suggest you wipe the phone using System > Advanced > Reset then flash to a Custom ROM using fastbootd. Btw, which custom ROM you prefer and intend to flash on your phone?
lazzr said:
A final attempt for now. I factory reset through fastbootd. Then "installed" Lineage image files. Rebooted and ended up in bootloader. Flashed TWRP, which this time could recognise my folders. ADB pushed Omnirom zip to my data folder. Tried a wipe, got lots of error messages, then tried installing the zip, and got the below:View attachment 5309925
This whole experience has been brutal.
Click to expand...
Click to collapse
What did you do after factory reset? How did you install Lineage image files? Please briefly describe what you did step-by-step. Just briefly.
tinbilly said:
From my experience with TWRP on my XT2041-1, I won't go with TWRP to flash a custom ROM. So just forget TWRP for now.
One important question, I think: Can you flash and boot your device to stock Android 10? [Note: I find this is a reliable method to go back to stock ROM. Just make sure you get the correct one matching your device.]
If yes, let take it as a starting point. From there, I suggest you wipe the phone using System > Advanced > Reset then flash to a Custom ROM using fastbootd. Btw, which custom ROM you prefer and intend to flash on your phone?
Click to expand...
Click to collapse
I can boot to stock using the same list of commands in that link. Starting with fastboot getvar max-sparse-size. Then I set up my phone to enable USB debugging and "file transfer" under default USB configuration. Then "ADB reboot bootloader", and click to enter recovery. I get the "No command" screen so I hold the power button and press up. Then "enter fastboot" to enter fastbootd. I've followed the next few instructions exactly as everyone says. Set active a, flash boot then system etc, then erase userdata.
This time I enabled "PTP" instead of "File Transfer" under default USB configuration to see if it made any difference. It still won't load system and I get this message:
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 20.736s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
I don't understand how it helps to install stock ROM and then wipe the phone using System > Advanced > Reset. That just puts me back to the same place as after I installed stock and I have to go in Developer Options etc again.
I'll try any ROM. I'm trying CrDroid now but it doesn't work. Lineage is the only one that seems to install system but I can't reboot to system.