Hey gang,
Brand new problem that has me a little perplexed. I have been using the 'Returntosctock2.3.5.script' that has been posted in a previous thread, and restoring to 2.3.5. via AP Fastboot along with the Stock Restore .bat file, but now that is not working. It is now showing that after running the script, it goes through its steps but then says:
...
sending 'mbmloader' <39 KB>... FAILED <command write failed <no such file or directory>>
sending 'mbm' <256 KB>... FAILED <command write failed <no such file or directory>>
rebooting into bootloader... FAILED <command write failed <no such file or directory>>
sending 'cdt.bin' <16 KB>... FAILED <command write failed <no such file or directory>>
{
"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"
}
Now, after it does the rest of its business, and after the reboot, it bootloops from splash screen to boot animation and back again, continually. I tried using RSD Lite for the first time and restored 2.3.5. and without any issues. So, what's up with restoring through AP Fastboot not working but the other method does? I have restored using AP Fastboot countless times, and without any problems. I don't get it.
Damn gremlins
I for one have not used the "returntostock" script. I didn't even know it existed until now. I did use RSD lite for the first time the other day and am impressed at how quick and well it worked. Kinda stinks they don't make it compatible with Linux. Doesn't make sense really.
mtnlion said:
Damn gremlins
Click to expand...
Click to collapse
I know, right?
KEB64 said:
I for one have not used the "returntostock" script. I didn't even know it existed until now. I did use RSD lite for the first time the other day and am impressed at how quick and well it worked. Kinda stinks they don't make it compatible with Linux. Doesn't make sense really.
Click to expand...
Click to collapse
I was just happy that RSD worked, and worked well. Still, I'm very befuddled as to why the script method didn't yield the same results it has for me every other time I've used it. I just don't get it...
Related
If any of you want to change your splash screen, it's pretty easy. I just followed this guide. Please give TrueBlue_Drew thanks.
Requirements:
Unlocked
Rooted
S-OFF
This might work for other Butterfly devices as well, but I'm not 100% sure.
As a test, I found a random splash screen, resized it to 1080x1920, converted and flashed it using EZ Splash Screen Flasher, and bam, changed splash screen. The htc development message is still there, though.
Here are some images I used:
HTC Anime Girl
Hero Droids
The above images were found in the guide I linked above, so original credit goes to whoever provided those images. I'd be happy to credit them here if I find who they are.
If you don't want to go through the process of creating your own splash screen, you can download the attached zips with the img file inside, put the img file somewhere you can use the fastboot command. You'll need to put your phone in fastboot and use the command
Code:
fastboot flash splash1 splash.img
Then, just reboot and you should see the change right away.
Thanks
Thanks it has worked for me...!
hi
I checked that thread and question I have.
How to create 1080x1920 image by SplashFlasher_1.0??
thanks
not allowed
I'm S-OFF and unlocked, but I get an error flashing splash1:
sending 'splash1' (4050 KB)... OKAY
writing 'splash1'... FAILED (remote: not allowed)
Anyone an idea?
{
"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"
}
Some anime's splash images
http://androidfilehost.com/?fid=22946563261203120
I have uploaded private album.
http://forum.xda-developers.com/picture.php?albumid=9471&pictureid=36117
http://forum.xda-developers.com/picture.php?albumid=9471&pictureid=36118
I unquestionably longed for to rise a acknowledgement to be means to appreciate we for all a glorious contribution we have been display on forum.xda-developers.com . My enlarged internet poke has right away been famous with great strategies to go over with my friends as well as family. we would demonstrate which most of us visitors essentially have been unquestionably sanctified to exist in a conspicuous village with really most undiluted people with profitable hints. we feel indeed beholden to have detected your web pages as well as demeanour brazen to so most some-more extraordinary mins celebration of a mass here. Thank we again for all a details.
webdepp said:
I'm S-OFF and unlocked, but I get an error flashing splash1:
sending 'splash1' (4050 KB)... OKAY
writing 'splash1'... FAILED (remote: not allowed)
Anyone an idea?
Click to expand...
Click to collapse
u need to flash eng hboot first .
Ok, so when I turn on the phone, it gets stuck on the HTC screen logo forever. With the volume down and power button, I'm able to get into hboot/hboot usb plug when connected to the computer. The recovery, factory reset, image crc options don't work. In my linux computer, when I type fastboot devices, I'm able to get serial number of the phone. The picture links below summarize my current state
{
"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"
}
The commands that I've tried are below.
(command): /fastboot devices [output] SH******** fastboot -- (note: here I did get my serial number but I know better than to post it here.
(command): ./fastboot oem rebootRUU [output]... FAILED (status malformed (1 bytes))
(command): ./fastboot flash zip PD15IMG.zip [output]: sending 'zip' (322693 KB)... FAILED (status malformed (1 bytes))
Tools in hand: android-sdk-linux, linux mint, PD15IMG.zip and phone
note: I also tried all of the above commands on windows 7 home premium 64 bit with adb installed and got the same error messages from fastboot. I tried the official htc bootloader unlocker but kept getting that error: 120 battery less than 30%.. although my battery is fully charged and that stopped the tool from unlocking the boot loader.
I read somewhere If i find the orginal stock recovery image, I might get out of this but I cannot find it anywhere yet.
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
RUU?
gesange said:
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
Click to expand...
Click to collapse
Yeah I tried RUU and it gets stuck all the time at Rebooting bootloader or waiting for bootloader
Because of the incredibly slow and laggy tablet I have I decided to try to do something about it.
So going from some thread here I decided to try to Root it using Motochopper, it seemed to go well but then the SuperSU app did not run, giving me a error No SU binary. I found out the supposedly Motochopper doesn't work with the 10.6.1.14.10 build. Anyways I later read that rooting wasn's necessary when adding custom roms so I unlocked with official app and then tried installing via fastboot a custom recovery TWRP 2.7.0.0
After running the command it just seemed to be stuck, nothing happened. I allowed it to go on but in the end I think the table was out of battery power and this was left on my command prompt.
{
"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"
}
anyone have any idea what the problem might be?
ingovals said:
Because of the incredibly slow and laggy tablet I have I decided to try to do something about it.
So going from some thread here I decided to try to Root it using Motochopper, it seemed to go well but then the SuperSU app did not run, giving me a error No SU binary. I found out the supposedly Motochopper doesn't work with the 10.6.1.14.10 build. Anyways I later read that rooting wasn's necessary when adding custom roms so I unlocked with official app and then tried installing via fastboot a custom recovery TWRP 2.7.0.0
After running the command it just seemed to be stuck, nothing happened. I allowed it to go on but in the end I think the table was out of battery power and this was left on my command prompt.
anyone have any idea what the problem might be?
Click to expand...
Click to collapse
You may want to put the twrp.blob in the adb directory/folder and try again, good luck.....:fingers-crossed:
LetMeKnow said:
You may want to put the twrp.blob in the adb directory/folder and try again, good luck.....:fingers-crossed:
Click to expand...
Click to collapse
Haha, no I did not forget to do that. Perhaps it was because the trwp.blob was blocked or something, but tried again and it worked instantly now.
thank you.
ingovals said:
Haha, no I did not forget to do that. Perhaps it was because the trwp.blob was blocked or something, but tried again and it worked instantly now.
thank you.
Click to expand...
Click to collapse
It is good to hear that it worked out for you...:good: I recommended that because I did not see the twrp.blob from your screen shot when you were executing the fastboot command. In your adb directory, you have only four files, two .exe for adb/fastboot and two libraries or dll supporting adb/fastboot....
Congratulations by the way!!! :highfive:
Successfully Done
✓ bootloader unlock
✓ TWRP Recovery twrp-merlin-2.8.7-r7.img
All most try all super user
{
"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"
}
but after flash super user zip phone stop work at bootloader warning
same thing happen to me too..plz someone answer.
Prior to flashing supersu.zip, open twrp>advanced>terminal and enter (without quotes) enter the command
Code:
"echo SYSTEMLESS=true>>/data/.supersu"
Now SuperSU would install in systemless mode. The latest betas automatically install in systemless mode (I am using 2.74). Check if now it works.
Broadcasted from Zeta Reticuli
@Gravemind2015 is correct, that is the command needed to make it work... note that since you already tried flashing several SuperSU versions the old way, if it continues to be a problem you may need to reflash the factory images and verify booting prior to trying the mentioned systemless method.
mindjek07 said:
...after flash super user zip phone stop work at bootloader warning
Click to expand...
Click to collapse
I had the exact same issue on my 16 GB xt1540, running stock, fresh 6.0. Trying to root with SuperSU's (over TWRP), several versions up to 2.74, earlier versions down to 2.4 ish... I'd freeze at boot logo every time, after what appeared to successful installs.
After reading somewhere about someone else's luck, I gave 2.65 a go, a version I must not have tried (and one I notice is not on your screen shot), and it worked. I certainly didn't expect it to, and obviously it could be completely coincidental. I'm pretty sure, however, that I did nothing differently on that install to what I had done other times.
HTH
Buena suerte
Love you!!!
You pacified my pain.
I have been trying to update my phone for a while now but for some reason I am unable to, when I got the phone I followed this guide to convert it from CN to WW, and it worked well
But right now I am stuck at at version 18.1220.2109.126,
Every time I try to update to android 12 I am greeted with this
{
"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"
}
if anyone could help me with this I would be really grateful, no matter what version I use I am always getting the same message
Update incrementally up to the version you want to get to.
Andrologic said:
Update incrementally up to the version you want to get to.
Click to expand...
Click to collapse
its not working man, i almost tried every firmware
Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com
twistedumbrella said:
Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried both, but every time I try to run a script, be it flash raw or the flash_all, I keep getting waiting for devices, even though my phone is connected to my pc(through the side port) and is in fastboot/bootloader.