So recently I've been messing around my Sensation, adding custom bootanimations and splash screens.
I've backed up the old one using
Code:
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/splash.img
So to restore it I'd thought I'd do the opposite
Code:
dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p1
Bad news, the phone is dead.
I can't boot into recovery or anything. So... is there a cure?
Matt1408 said:
So recently I've been messing around my Sensation, adding custom bootanimations and splash screens.
I've backed up the old one using
Code:
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/splash.img
So to restore it I'd thought I'd do the opposite
Code:
dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p1
Bad news, the phone is dead.
I can't boot into recovery or anything. So... is there a cure?
Click to expand...
Click to collapse
If that second line is the actual one you used, then you pushed the splash screen img file to mmcblk0p1 instead of mmcblk0p19.
Crap, looks like I made a typo and messed it up.
{
"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"
}
have you tried flashing stock RUU to restore?
Forgive me for asking, but where is this RUU.exe?
Oh no! good luck matt.
Matt1408 said:
Forgive me for asking, but where is this RUU.exe?
Click to expand...
Click to collapse
depends on your model, but i can help ya
is it unbranded? or bell/tmobile etc?
It's the Bell version
and you cant get into bootloader at all?
have you tried pulling the battery for 5-10sec, put it back in, then old VOL.DOWN + POWER?
I've tried pulling the battery, and booting into recovery, but to no avail.
However, when I plug in the phone to my computer, I get something about "qhsusb_dload." But thats about all that happens. Adb doesn't work, and such.
thats actually a really good sign!
do you have ADB on your computer? you WILL need that for sure, if not ill get ya a link
Of course I do, what do you think got me in trouble in the first place
hahaha oh yeah, just looked at first page
ok so go into cmd, connect phone via usb and type - adb devices
edit* also, just noticed your name is matt and you live in toronto, as is/am i
also, sorry im doing a million things at once cuz im at work, so some posts might be short 1-2 steps
Code:
C:\Users\Matt\Desktop\New folder>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
No devices show up.
are you running cmd as admin? thats important
Yup. No dice.
can you check battery discharge? i just wanna see what level of control you have.
enter
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
it will say "CHARGING" or "DISCHARGE"
As I said, adb doesn't detect the phone.
But the phone was about 90% when I killed it.
ok well it seems thats its in download/recovery mode from you're earlier post, so lets try fastboot
fastboot reboot
OR
fastboot reboot-bootloader
EDIT* also, are you rooted, superCID or anything special like that?
<waiting for device>
... nothing
Related
I can't be the only one who likes Halo and can't wait for Reach to come out.
Here's a couple of splash screens I created with that in mind.
They are similar, but the second has one of my favorite quotes from Halo 3 and any one who has read the books knows what it means.
Let me know what you think. (Be gentle though, these are my first ones)
{
"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"
}
They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App
The reason I used that quote was because of the references in the halo: the fall of reach (the book). But if anyone wants a specific quote let me know and I'd be happy to include it.
Sent from my Fresh'd out Evo 4g
using XDA App
blkswanpres said:
They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Here ya go.
Hi, was hoping you could help me with this. I followed instructions on how to flash this and the actual sending of it worked but when it tried to write it, it said FAILED (remote: not allowed). Any ideas on what that would mean? Thanks!
You need to have ADB enabled. Put the evosplash1.rgb into your sdk/tools folder. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
fastboot flash splash1 evosplash1.rgb565
fastboot reboot
FattySparks said:
You need to have ADB enabled. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
adb remount
fastboot flash splash1 evosplash1.rgb565
fastboot reboot
Click to expand...
Click to collapse
First, thank you for replying to my post! You are the first one to state the "adb remount" part. I did that but it is saying device not found now. My phone does show the red fastboot usb so do you any further suggestions because it still failed on the writing part. The sending part went fine but I guess it is failing since it cannot find my phone. Might I have the sdk set up incorrectly?
One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.
eaglenest608 said:
One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.
Click to expand...
Click to collapse
when you're in fastboot it shouldn't show up in adb devices. I also forgot to mention to put the rgb565 file into your sdk/tools folder. Other than that it sounds like your setup properly.
Edit: Also the adb remount code isn't needed. I was so used to using it from messing around with bootscreens, I forgot it isn't needed for fastboot.
Yes, it seems I am setup correctly from what I have read. Maybe I should flash to a different rom and see if that helps me. My wireless tether app is giving me problems as well so not sure what has happened but it may be time to give something else a go. Unless you can think of anything new that is, lol. Thanks a bunch though for you help...really appreciate it.
Well, for those that actually care I have now resolved this issue. It turns out that the HBOOT version that I had did not allow me to perform this flash. I had to actually downgrade it to a different one and it worked perfectly. I wish to thank those that actually took the time to reply to my post...it was greatly appreciated!!
Realize I posted the screen of the new quote, but didn't attach the file... duh
Halo Reach Boot animation
http://forum.xda-developers.com/showthread.php?p=8419483#post8419483
PLEASE
Can you do one that says
"Halo:Reach>MW2"
That would be epic
Sorry for the delay, got married last weekend.
Here ya go.
Ohhh this is Perfect the delay is no problem but seriously thanks alot and congrats on the marriage
Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have 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"
}
What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Major kudos to diego930 for such a nicely detailed description of his problem!
Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.
Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!
When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.
ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.
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:
When I use "fastboot reboot fastboot" command it only reboots and turns on the phone.
I want to try install a GSI rom but I can't get into it.. Is there a way to make it happen?
Am I wrong trying to install it this way? I was reading some forums and I tried a few things without results.
speedmetal444 said:
When I use "fastboot reboot fastboot" command it only reboots and turns on the phone.
I want to try install a GSI rom but I can't get into it.. Is there a way to make it happen?
Am I wrong trying to install it this way? I was reading some forums and I tried a few things without results.
Click to expand...
Click to collapse
Try this:
First reboot to recovery, once you're there select reboot to bootloader, then press and hold VOL UP while it's rebooting, after that voila your now on Fastboot mode.
{
"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"
}
Thx for your reply! And sorry for my poor explanation about the problem, I know how to get into fastboot mode but there is another instance of it, and its fastbootD mode that allows you to make modifications on the dynamic partition called "super", the suposed way to get into it is typing the command "fastboot reboot fastboot" in the normal fastboot mode, but nothing happens, the phone just reboots into normal system.
When I try to erase system in normal fastboot mode it cannot find that partition cause this is in super, it will be great if we can experiment with that but Im stuck right now...
I dont know if this worth it.... Any of you already tried a GSI rom?
speedmetal444 said:
Thx for your reply! And sorry for my poor explanation about the problem, I know how to get into fastboot mode but there is another instance of it, and its fastbootD mode that allows you to make modifications on the dynamic partition called "super", the suposed way to get into it is typing the command "fastboot reboot fastboot" in the normal fastboot mode, but nothing happens, the phone just reboots into normal system.
When I try to erase system in normal fastboot mode it cannot find that partition cause this is in super, it will be great if we can experiment with that but Im stuck right now...
I dont know if this worth it.... Any of you already tried a GSI rom?
Click to expand...
Click to collapse
Yes, but unfortunately their SW REV was just 0, but by device’s one is always 1 (i.e. too high for TWRP and GSI’s atm)
(* Samsung blocks SW REV downgrades at all, the only way to bypass is to run the below for not waiting)
Now it needs waits, or if you don’t wait, you instead need to shut MTK ‘‘secure’’ boot and ‘‘secure’’ Download off at all.
Helix-one said:
View attachment 5299239
Click to expand...
Click to collapse
Are you going to flash TWRP by ADB sideloads on the A12's Recovery mode? If yes, good luck!
Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"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"
}
Device is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.