Make sure you use the usb 2.0 plug in your computer and not the 1.0. I wasted hours coming to this conclusion from failed flash after flash after flash when it was sending ram flash.
Good luck and G-d bless.
Related
Hi all
Well I bricked my phone and I'm stuck in AP Fastboot. When I try to start the phone (boot it up from off) It gets as far as the M logo then enters AP fastboot or it might even go directly to fastboot.
What I was doing: I was trying to use Matt's Droid RAZR M utility 1.20 option 1 to go back to stock 4.1.2. That's when my problems started. I had nearly 70% battery when i started (now it says "low battery").
Phone set up: Droid RAZR M 4.1.2; Rooted; Locked bootloader; Safestrap 3.12 and backed up; stock slot was still stock and ROM slot 1 was running Eclipse Custom ROM. To be honest I cant remember if i was back in stock ROM slot or ROM slot 1 when I attempted to use Matt's Utility. And I didn't uninstall Safestrap nether prior to using the utility. Don't know how much those factors played into causing my problem.
What I have tried: I have tried RSD Lite 6.1.4 with xml.zip files from the Droid-Developers SBF web site. But i keep getting this fail message, "Failed flashing process. 1/19 flash partition "gpt_main0.bin" -> Phone returned Fail."
I have tried manually pushing the recovery.img, boot.img and system.img file onto the phone via cmd.exe and it fails with this message for all three attempts, "Battery Low!!" "FAILED (remote failure)".
I have tried Matt's Utility option 1 I get multiple fail messages, "Failed to erase partition", "FAILED (remote failure)", "Failed to flash partition boot", "Failed to write mmc".
I even purchased one of Team Black Hats Factory Programing Adapters (little red adapter) That acts like a factory programing cable (they said they don't sell the cable any more cause the red adapter does the same thing for cheaper).
With the adapter connected I still get the same fail messages in RSD Lite, Matt's Utility, and cmd.exe prompt. I was under the impression that the factory programing cable (adapter) would solve my low battery issue.
Any help would be great. Thank you in advance.
PS: Also, I did not take the last OTA update from a few weeks ago. I was planning to unlock my bootloader. And my computer is a Windows XP (sp3). Thanks Again.
SARM1084 said:
Hi all
Well I bricked my phone and I'm stuck in AP Fastboot. When I try to start the phone (boot it up from off) It gets as far as the M logo then enters AP fastboot or it might even go directly to fastboot.
What I was doing: I was trying to use Matt's Droid RAZR M utility 1.20 option 1 to go back to stock 4.1.2. That's when my problems started. I had nearly 70% battery when i started (now it says "low battery").
Phone set up: Droid RAZR M 4.1.2; Rooted; Locked bootloader; Safestrap 3.12 and backed up; stock slot was still stock and ROM slot 1 was running Eclipse Custom ROM. To be honest I cant remember if i was back in stock ROM slot or ROM slot 1 when I attempted to use Matt's Utility. And I didn't uninstall Safestrap nether prior to using the utility. Don't know how much those factors played into causing my problem.
What I have tried: I have tried RSD Lite 6.1.4 with xml.zip files from the Droid-Developers SBF web site. But i keep getting this fail message, "Failed flashing process. 1/19 flash partition "gpt_main0.bin" -> Phone returned Fail."
I have tried manually pushing the recovery.img, boot.img and system.img file onto the phone via cmd.exe and it fails with this message for all three attempts, "Battery Low!!" "FAILED (remote failure)".
I have tried Matt's Utility option 1 I get multiple fail messages, "Failed to erase partition", "FAILED (remote failure)", "Failed to flash partition boot", "Failed to write mmc".
I even purchased one of Team Black Hats Factory Programing Adapters (little red adapter) That acts like a factory programing cable (they said they don't sell the cable any more cause the red adapter does the same thing for cheaper).
With the adapter connected I still get the same fail messages in RSD Lite, Matt's Utility, and cmd.exe prompt. I was under the impression that the factory programing cable (adapter) would solve my low battery issue.
Any help would be great. Thank you in advance.
PS: Also, I did not take the last OTA update from a few weeks ago. I was planning to unlock my bootloader. And my computer is a Windows XP (sp3). Thanks Again.
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/t...not-going-into-recovery-no-os-on-phone/page-2
Found by
https://www.google.com/search?num=1...j1.6.0....0...1c.1.26.serp..6.0.0.Dd8aoiu_UJI
Thank you for offering help. Will try your suggestions.
Sent from my XT907 using Tapatalk 2
[SOLVED] I was able to get some more help on another forum. My problem was a corrupted utility. I was instructed to perform a md5 check sum on my version if Matts utility. I compared my results to the original file on batakang Web site. That's when I realized my file was no good. So I deleted it an downloaded a clean uninterrupted copy of Matts utility 1.20 and it worked perfectly. I hope this will help other people too. Thanks for your help my friend.
Sent from my XT907 using Tapatalk 2
I cleared the internal storage of my oneplus 2 by mistake and it became brick. I can acceas to the fastboot and twrp. But my pc is not recognising it when i tried adb sideload and fastboot. Pc has winfows 10. I have heard some settings we should do there. So pleasw someone help. How to unbrick it easily. I am a noob here so.. Pls
alwinv001 said:
I cleared the internal storage of my oneplus 2 by mistake and it became brick. I can acceas to the fastboot and twrp. But my pc is not recognising it when i tried adb sideload and fastboot. Pc has winfows 10. I have heard some settings we should do there. So pleasw someone help. How to unbrick it easily. I am a noob here so.. Pls
Click to expand...
Click to collapse
Someone please help. I tried the almost everything available and main problem is pc isnt recognising the phone even as a qualcomm driver.. Adb sideload failed due to the same thing. I can access to the twrp but nothing is there in the internal storage to installand qithout my pc recognising it.. There is no way out
I'm sorry to hear that buddy.. i wish i am expert enough to help you out, but i hope someone comes and helps you
Sent from my ONE A2003 using XDA-Developers mobile app
I haven't used the Qualcomm fastboot recovery flasher. But I guess you just have to boot up the bootloader/fastboot mode, change the drivers under device manager for the Qualcomm ones (might need you to disable driver signing requirement if the driver is unsigned and your running Windows 8 or newer). And from there just run the Qualcomm flasher and watch it complete. However I'm guessing you've been playing around with the experimental beta ROMs and thereby changing bootloader, so you should be able to restore bootloader back to the 2.2.1 one by first running fastboot flash recovery recovery.img with a twrp recovery.img which is compatible with your bootloader (the chinese 3.0 i suppose) and then from there flash the revert to Lollipop zip using TWRP and then fastboot flash recovery the TWRP for OxygenOS 2.2.x/CM13 bootloader.
Skickat från min ONE A2003 via Tapatalk
Hi Alwin,
If TWRP is working on your oneplus 2, you can simply flash the stock firmware by downloading the stock firmware and transferring it to a USB, then using a USB otg connector to flash the zip while in TWRP.
You can find link to stock firmware in benkxda's post.
Hope it helps.
NamanPuri said:
Hi Alwin,
If TWRP is working on your oneplus 2, you can simply flash the stock firmware by downloading the stock firmware and transferring it to a USB, then using a USB otg connector to flash the zip while in TWRP.
You can find link to stock firmware in benkxda's post.
Hope it helps.
Click to expand...
Click to collapse
Thanks..
I wanted to try Slim Rom on One Plus 2.. And before flashing, i wiped the system, data etc.. usually i keep a backup of rom before flashing in case my flash fails.. But due to over confidence i didnt do so in this case.. The flash showed error 7 & failed..
I tried downloading the oos official firmware only to learn it was a flashable zip.. My usb otg is micro usb, so can't place it in internal storage via twrp..
I tried downloading a fastboot firmware.. But the flash all bat failed..
Tried downloading the AIO tool.. downloaded their fastboot rom & tried flashing.. but the command line days oem unlocking is disabled & flash fails..
For some wierd reason, the command prompt is not working in my system.. so can't flash manually either..
I am lost. Please help..
You need to unlock bootloader to use the fastboot method(fastboot oem unlock).
Sent from my OnePlus 2 using XDA Labs
i wanted to install a custom rom onto my phone. to make a long story short, i was foolish and because it'd been a while, i ended up bricking my phone.
it boots to fastboot, but nothing else.
so far, i have tried:
- flashing TWRP recovery (succeeds in flashing but goes back to fastboot after rebooting)
-booting directly into TWRP (fails with the error "Failed to load/authenticate boot image: Load Error")
-using the Mi Flash Tool to flash an MIUI install (frankly im not sure how to use it, it just asks me for a "flash_all_lock.bat" file which wasnt included, and that i dont have)
-switching USB cables and doing all of the above (same results)
-switching to a USB 2.0 port and using both cables to do all of the above (same results...)
if anyone has had this issue, or has any clue how to resolve it, or maybe just to shine some light on how to use the Mi Flash Tool to flash a room without a flash all bat, that'd be swell
nemii said:
i wanted to install a custom rom onto my phone. to make a long story short, i was foolish and because it'd been a while, i ended up bricking my phone.
it boots to fastboot, but nothing else.
so far, i have tried:
- flashing TWRP recovery (succeeds in flashing but goes back to fastboot after rebooting)
-booting directly into TWRP (fails with the error "Failed to load/authenticate boot image: Load Error")
-using the Mi Flash Tool to flash an MIUI install (frankly im not sure how to use it, it just asks me for a "flash_all_lock.bat" file which wasnt included, and that i dont have)
-switching USB cables and doing all of the above (same results)
-switching to a USB 2.0 port and using both cables to do all of the above (same results...)
if anyone has had this issue, or has any clue how to resolve it, or maybe just to shine some light on how to use the Mi Flash Tool to flash a room without a flash all bat, that'd be swell
Click to expand...
Click to collapse
I had a few troubles when I wiped all the data off my phone and the only way to get the phone working again was to manually flash the files our phone needs.
Check this out here -> https://forum.xda-developers.com/t/...-mix-3-5g-stable.3941867/page-5#post-82937133
You have to use the official miui tools (miflash) (https://androidmtk.com/download-xiaomi-mi-flash-tool) as well as appropriate fastboot miui rom (the file you want ends in .tgz)(https://xiaomifirmwareupdater.com/archive/miui/andromeda/).
After downloading your files, put miflash in the root directory of your C:\ drive. Then keep on extracting the rom archive untill you end up with a folder and also put it in the root directory of your C:\ drive.
Reboot the phone into fastboot mode and connect it to your computer.
Then use miflash, select the rom folder, and completely wipe and reflash your phone (remembering to select the option to not relock the bootloader). If the flash fails, try changing your cable.
You then allow for a couple of minutes for miui to start and format the internal storage.
7.2.5.5/2465-diff-7.2.8.5/2877
https://d1s31zyz7dcc2d.cloudfront.net/ac0bfc6c85b2fa5000fdc568c30eed60/update-kara-diff-PS7255_2465_0021911675268-to-PS7285_user_2877_0023723720068.bin
md5Sum=89f4ee800801eae7eb0c0e5fd537d0aa
7.2.7.3/2625
https://d1s31zyz7dcc2d.cloudfront.net/dc64e6a705f8e840217c98b2217938f2/update-kindle-kara-PS7273_user_2625_0022851240324.bin
md5Sum=0741cd9b3c663ff1d10be80e2b20fd64
As I referenced in the other post with the mantis device getting full.bin updates, I was only able to get the diff updates for kara
I have question, my Fire tv stick 4k max is bricked, it was unplugged during update and now doesn't give any signal on tv, no logo, nothing, I've tried to plug it into pc with usb and its detected as mtk 65xx preloader. I installed sp flash tool but I don't have scatter file to flash stock firmware. Do you know where I can find scatter file or if there is any other way to flash firmware. I only managed to find firmware in .bin format but cant flash it with sp flash tool.
Lukatler said:
I have question, my Fire tv stick 4k max is bricked, it was unplugged during update and now doesn't give any signal on tv, no logo, nothing, I've tried to plug it into pc with usb and its detected as mtk 65xx preloader. I installed sp flash tool but I don't have scatter file to flash stock firmware. Do you know where I can find scatter file or if there is any other way to flash firmware. I only managed to find firmware in .bin format but cant flash it with sp flash tool.
Click to expand...
Click to collapse
who can help with installing new firmware or restoring the previous
Lukatler said:
I have question, my Fire tv stick 4k max is bricked, it was unplugged during update and now doesn't give any signal on tv, no logo, nothing, I've tried to plug it into pc with usb and its detected as mtk 65xx preloader. I installed sp flash tool but I don't have scatter file to flash stock firmware. Do you know where I can find scatter file or if there is any other way to flash firmware. I only managed to find firmware in .bin format but cant flash it with sp flash tool.
Click to expand...
Click to collapse
Right now there's no known way to flash the firmware over the bricked device. You'll need to be unlocked which there is no guide for that due to the encryptions of the system. Only time will tell when we do see an unlock guide which can allow you to flash the firmware.
For any XDA users that have the (kara) device and hasn't updated to the latest firmware. Make sure the firmware (excluding the system components update) that's downloading isn't downloading fast or else it'll be under a diff update which isn't the full update and the command to run is adb logcat as soon as the update is downloading in the checking for updates screen. Report here to post the updated firmware and the URL is different compared to the one listed here.
Copy this and put it in front of the .bin link after the logcat.
Remember to enable adb debugging, adb connect ip/USB adb and allow the connection and type in adb devices. In case the update does download in full type in adb shell pm clear com.amazon.device.software.ota
https://prod.ota-cloudfront.net/
I have two (kara) devices locked on 7.2.5.5/2444 and 7.2.5.5/2465 still and I'm getting the update to the 7.2.8.5 diff instead of the newer 7.6.1.4. Help is appreciated. Thanks again.