I had TWRP and and 1xx KangVip installed.
I wanted to flash an 1xx, then 321 stock rom in order to update to a newer KangVip, but neither fastboot nor adb sideload was working.
I stupidly blindly followed step by step instructions from a random internet user and the first step was to wipe everything.
When rebooting into the bootloader, it would say "connect to the computer and start HiSuite"
When running adb sideload update.zip i got "cannot read update.zip".
I checked everything but couldn't find the problem so I tried pushing the file but when trying to install it with TWRP it failed.
The next thing I did bricked my phone completely, I ran fastboot flash recovery RECOVERY.img while in the fastboot menu where it displayed "connect your phone to the computer and start HiSuite"
That removed TWRP and now when I boot into recovery I get a loading circle that goes to 5% and then stops.
In the circle is a USB logo with an arrow and under the circle are chinese characters commenting the progress.
Is there anything I can do to save my phone?
Edit: Sorry this always happens to me, I tried fixing this for 5 hours and 5 minutes after I post this the problem fixes itself...
I just tried fastboot flash again and now it works.
OK you're saying you can still flash files while it's on "Connect to the computer and start HiSuite" Yes?
If so you should be able to reflash Cust.img, boot. img, system.img and recovery.img form a
1xx Update.app file. Use Huawei Firmware Extractor to get these files.
---------- Post added at 11:07 PM ---------- Previous post was at 10:56 PM ----------
That's good to hear
Related
i attempted to put the clockwork mod reovery and the matrix ROM on my nexus and now my phone will turn on show the google name and the root lock for 1/2 sec then go to my boot loader and at the top it says "NO BOOT OR RECOVERY IMG" PLEASE HELP!
You need to flash a rom. Once you root your phone you have to have a image to boot into.
http://www.youtube.com/watch?v=GSD92Qjt5Og&feature=youtube_gdata_player
†††
........................................
my nexus is already rooted but on startup it says NO BOOT OR RECOVERY IMG.
Try flashing the recovery image again via adb. Watch that video it will show you how to do that. If you are rooted and you are not able to boot into recovery the image didn't take, was installed incorrectly, or maybe is the wrong or a bad dl. If all else fails start from scratch., step by step.
†††
kcook2369 said:
my nexus is already rooted but on startup it says NO BOOT OR RECOVERY IMG.
Click to expand...
Click to collapse
I hope this helps http://dodgerturf.com/forum/showthread.php?tid=2830&pid=5556#pid5556
---------- Post added at 09:25 PM ---------- Previous post was at 09:21 PM ----------
also try flashing your custom recovery once again using the adb command "fastboot flash recovery FILE PATH" without quotes.
So i bought a htc one xl on craigslist a few months ago. I downloaded an app to check if its rooted and it said it was. Long story short i think i downloaded the wrong rom and i cleared everything from TWRP. I really have no business doing anything like this.. Now im stuck. I can get to the bootloader mode screen but when i got to recovery it takes me to twrp. I hope i didn't screw it up too bad. TWRP says "no os" also.
Any help would be appreciated! Im done with messing with rooting and such i don't want to mess up my phone anymore.
ps: I didn't do a backup.
Download the right Rom to your computer lets make it viper xl to make things easy once done downloaded mount usb storage in twrp drag the Rom over... Factory reset and flash the Rom and you're good
It installed fine and everything but its been at the viper xl loading screen for 10 minutes. Any reason why its doing this?
Do you have hboot 1.14? And did you factory reset
Yes and Yes
You still have the zip on your computer right? So I guess we're going to have to fastboot the boot.img which is very simple I'll give you a quick tutorial in a sec
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"
I extract the fastboot folder right? I did that and its "saying waiting for device".
Install the drivers
Sorry but where do i find those?
Alright i think i did it right it said finish in the command prop. Now what do i do?
1991birdofprey said:
Alright i think i did it right it said finish in the command prop. Now what do i do?
Click to expand...
Click to collapse
If you have adb/fastboot installed, have a copy if the rom on your phone and also the computer for less confusion. On your computer, extract to rom and copy the boot.img INSIDE your adb/fastboot folder.
Enter boot loader on your phone, (white screen 3 skating droids). Make sure it says fast boot usb. Run a simple command like "fastboot devices" and see if something shows up. If so, proceed. If not, restart computer or make sure drivers are installed.
On your computer, right click on the adb folder and choose "open command prompt here" in the cmd window type->
Fastboot flash boot boot.img
Upon success, immediately boot into recovery (twrp) and flash (install) the entire rom.
Profit
Sent from my HTC One XL using Tapatalk 2
Thanks a bunch guys! I thought i lost my phone! Everything worked!
I have a Razr Maxx HD. I am stuck in a bootloop and cannot recovery with factory firmware. The phone was rooted but the bootloader not unlocked. I could use some help. I have tried many of the things that I have seen on online forums but have not had success.
Here is what led to the problem:
1) I rooted my phone. It rebooted fine.
2) I downloaded a modified framework-res.apk and Root Explorer (File Manager) to my phone.
3) Mounted Root Explorer in r/w mode.
4) Copied and overwrote original /system/framework-res.apk with modified file.
5) Phone rebooted and got stuck in loop.
*USB debug mode was on at time of failure.
Here is what I have tried on a Mac:
1) In Android System Recovery <3e>, I tried "Wipe cache partition" and "Wipe data/factory reset." That did not work.
2) I downloaded the Mac Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can run ADB in my terminal. However, it only shows the device when in "Recovery/Apply update from ADB " mode. When I perform "adb devices" it shows a serial number and "sideload." I use the "adb sideload" command to transfer the firmware .zip file. It reads the following after it is uploaded:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/framework-res.apk", "bunch of numbers")
Installation aborted.
This was after sideloading the package "Blur_Version.9.1.41.XT926.Verizon.en.US.zip." This was the same file I was modifying earlier. I have tried it with the fireware xml.zip files from sbf.droid-developers.org/vanquish/list.php and only got to line 3 before it aborted.
3) Tried to update from microSD card and got same result.
4) I have the original framework-res.apk file; however I don't know how to push it. I cannot get it to recognize the device in ADB outside of the Recovery from ADB sideload option. All other ADB commands return an "error : closed" reply.
5) As far as Fastboot, it reads AP Flastboot Flash Mode (S), Device is LOCKED. Status Code: 0, Battery OK, USB Connected. I got the device ID and tried the online unlock key generator on Motorola.com but it stated my device was not eligible for unlocking at this time, so it remains locked.
Here is what I have tried on a Windows 7 PC:
1) I downloaded the Windows Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can open ADB in cmd line. However, when I perform "adb devices," it does not show a serial number, even in Recovery ADB sideload.
2) I downloaded RSD Lite 5.3.1. Selected one of the extracted sbf.droid-developers.org/vanquish/list.php .xml files. Hit start and nothing happened. "Show Device" did not bring anything up. I am guessing the PC is not detecting the device, but I uploaded the latest Motorola Drivers Package. I even tried the Google USB Driver install in Android SDK.
Can you recommend another course of action or a means of getting one of these methods to work? Please help me unbrick my phone. Thank you in advance for any advice.
..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.
mentose457 said:
..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.
Click to expand...
Click to collapse
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?
rmp2737 said:
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?
Click to expand...
Click to collapse
Is this the case in both windowz and osx?
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 06:00 PM ---------- Previous post was at 05:31 PM ----------
I cant find the article bout using a stock update zip. Though you could flash the latest ota update. It would eliminate any chance of you unlocking the bootloader and possibly obtaining root.
mentose457 said:
Is this the case in both windowz and osx?
Click to expand...
Click to collapse
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
mentose457 said:
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Click to expand...
Click to collapse
Thanks. Let me know if you find it.
If you could get your phone to be recognized in adb all of your problems could be solved. You could even unlock your bootloader without being able to get into the os. If I were you id continue to try to get my computer to communicate with my phone.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
rmp2737 said:
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
Thanks. Let me know if you find it.
Click to expand...
Click to collapse
is the "apply update from adb" part of the stock recovery? Ive never encountered it.
---------- Post added at 06:09 PM ---------- Previous post was at 06:08 PM ----------
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.
mentose457 said:
Is the "apply update from adb" part of the stock recovery? Ive never encountered it.
Click to expand...
Click to collapse
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.
rmp2737 said:
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.
Click to expand...
Click to collapse
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
mentose457 said:
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.
Click to expand...
Click to collapse
Have you tried this ^^^
---------- Post added at 07:34 AM ---------- Previous post was at 07:17 AM ----------
What method did you use to fastboot?
mentose457 said:
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
Click to expand...
Click to collapse
I tried it a few times with RSD Lite different file versions. They did not work. Perhaps the permissions for the folder were not reverted and this is a problem?
I have tried to connect to with ADB during the bootloop and in the recovery mode menu. It did not work.
As for fast boot, I am using the AP Flastboot Flash Mode as part of stock recovery.
Thank you for your help so far. I am lost at this point, since it seems all the typical methods are not working.
I am suspect that performing the factory reset disabled USB Debugging Mode and that is why ADB won't work. If so, I think I am stuck because it's Catch 22. I can't push the files with ADB, I cannot flash the system.img file because it is too big, I cannot flash the system.img file with RSD Lite (for what I can only assume is a permission error), I cannot erase the system.img to clear it before I flash over it because the bootloader is locked, and I can't unlock the bootloader because the exploit requires you to use ADB commands. Unless, I am missing something.
EDIT: Still open to suggestions, but am going to try the method posted Here and see if this works. (I have been searching forums, but I didn't find this link until after I posted, sorry admins)
So I was screwing around and booting TWRP through fastboot earlier(fastboot boot twrp-etc.etc), and ran the zip to install it in a stupid way(adb sideload, which I wasn't thinking and should have just flashed in fastboot first).
Now my bootloader comes up, but I have no recovery, and for some reason fastboot is not detected by my Windows PC or my Fedora Linux system.
If I turn the phone off and back on, it gives me ERROR: Slot Unbootable: Load Error.
Am I mega-screwed with a hard-brick since Windows and Linux can't even detect the phone in fastboot/bootloader anymore?
I've been researching was to get into the Qualcomm EDL, but can't find many resources in regards to the Pixel 2
Bought this device from a reputable dealer on Swappa, and it turns out the phone is still in warranty with Google, but not sure if it will cover something
that is obviously my own ****-up
Here's a short list of details that I'm going assume anyone who could help will need to know:
Bootloader: Unlocked
Bootloader: Shows up and gives me standard options [Start->Restart Bootloader->Download Mode->Recovery->Barcodes->Power-Off]
Spitting out ERROR: Slot Unbootable: Load Error
System partition: None
Recovery partition: Corrupted/none
Fastboot: Not working at all(was previously working, and still detects my Verizon Pixel if I go into bootloader menu)
Same exact problem Here...
---------- Post added at 04:41 PM ---------- Previous post was at 03:46 PM ----------
FIXED
I fixed it by completely draining the battery by maintaining the power button held with a rubberband. Then when the little red light was flashing I plugged the phone in the pc and after a few seconds the bootloader showed up and my phone was detected.
Optional: When flashing stock with flash-all.bat I was always betting ''archive does not contain xxxx'' and then my phone wouldn't boot. Ultimately I extracted the 20+ files in the zip image file and manually flashed all img files with fastboot, then I relocked the bootloader and now everything is working fine !
emile567 said:
Same exact problem Here...
---------- Post added at 04:41 PM ---------- Previous post was at 03:46 PM ----------
FIXED
I fixed it by completely draining the battery by maintaining the power button held with a rubberband. Then when the little red light was flashing I plugged the phone in the pc and after a few seconds the bootloader showed up and my phone was detected.
Optional: When flashing stock with flash-all.bat I was always betting ''archive does not contain xxxx'' and then my phone wouldn't boot. Ultimately I extracted the 20+ files in the zip image file and manually flashed all img files with fastboot, then I relocked the bootloader and now everything is working fine !
Click to expand...
Click to collapse
You didn't need to drain the battery completely. Just holding the power button for 10seconds is sufficient for the phone to be detected.
Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please
I think this
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system
Jaco2k said:
Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system
Click to expand...
Click to collapse
I tried to do the same, but everytime I try to boot into recovery from fastboot, I get the same error
- FAILED (remote: Failed to load/authenticate boot image: Load Error)
Even tried different versions of twrp but same is happening
So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
In your first post you say "after installing TWRP"
If you have correctly installed TWRP you should be able to get to recovery by holding down power button and volume up button.
Jaco2k said:
So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
Click to expand...
Click to collapse
I did, installed TWRP quite a while ago before all this.
I was testing the latest dp on my mobile, but later I decided to revert back to stable. I flashed the pie version in local upgrade and wanted to start over.
So after booting once, I rebooted into TWRP and mistakenly selected system partition along with local storage in wipe option.
And now fastboot is the only thing I can boot in
I somehow don't think you are telling the story exactly as it went
I am assuming you flashed a full build and rebooted without flashing TWRP in-between.
Also, I am assuming you have flashed an older build that has the fastboot bug.
This means that you might be pretty screwed.
You can try to ADB push the full OTA via fastboot and flash it there using command line.
I guess at this point you are not caring anymore if you keep your data, right?
Also, there were some patched boot images laying around that might be worth flashing to see if fastboot is working on them.
As you have come across, there is a fastboot bug in some builds - I guess at some point it was fixed and then it reoccurred.
---------- Post added at 03:43 PM ---------- Previous post was at 03:39 PM ----------
BTW, I guess the link already posted in this thread might be your best bet, since you have removed TWRP when you flashed the updated build and you cannot fastboot recovery, as you have found out, due to a bug from OnePlus.
JerryDaBaaws said:
Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please
Click to expand...
Click to collapse
Just get the fastboot ROM for the same version you're on. For example 9.5.10 then you HAVE to use the one for 9.5.10.
https://androidfilehost.com/?w=files&flid=294300
Just download the Fastboot ROM (Make sure it's for your device as well). If on GM21aa then that's the one you use.
Put the phone in Fastboot mode and attach the phone to PC
Type Fastboot devices and make sure it comeback with your device serial number (like 6 or 8 digits, cant remember exactly)
Unzip the fastboot ROM and click on Flash-all.bat
Your phone will be like new as if shipped with 9.5.10 or whatever ROM you're on. There will be no root/TWRP/files (photos or music). You will have to do it all again but your phone will be working.