Here's my issue. My keyboard a week ago started to have issue, some of the letters wouldn't work (the physical one). T-mobile will be sending me a warranty replacement. So I need to get unrooted.
I was going to use this method --> http://forum.xda-developers.com/showthread.php?t=491350
Problem is the splash screen is the one for CM 4.0.4 ROM. So I can't type in the recovery console (CM 1.4). I need to get rid of that splash screen.
So some XDA'er's gave me an idea. My girlfriend has an unrooted G1. I loaded Flash Recovery (one-click root method). I did a backup of her perfectly stock 1.5 image. I took out the SD card, dropped it in mine. Loaded into CM 1.4 recovery, went to "restore latest backup" and I got a "Error performing restore! Try running nandroid-mobile.sh restore from console.". I'm stumped cause I can't use recovery console since some of my keyboard keys don't work. Can I flash thru Better Terminal flash_image to go back to unrooted stock 1.5, stock recovery and stock splash image? What's the exact command? What do you think I should do guys?
Thanks in advance.
flash the 1.22 radio
flash DangerSPL
BRICKED!!!!!!! No evidence
HAHAHAHAHA damn that's evil
if you have a second splash screen (splash2) then do this in fastboot
Code:
fastboot erase splash2
flashing the DREAIMG.nbh file will change everything else back to stock
caolinlin said:
Nice work--thank you for sharing-
Thanks so much for this. I appreciate the effort. It really helps a lot.
{
"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"
}
Click to expand...
Click to collapse
if you are referencing me in any way, what effort? to type a few sentences
EDIT: I just got ADB to work. Woohoo. Only @ work it works, lol.
I need to get rid of this splash.
So last night after I posted this, I looked at the recovery-backup.img that flashrec made. I thought to myself "damn that's a small 5MB file for the 1.5 OS". I went into Better Terminal and flash_image the image. Rebooted the phone into recovery mode and only that changed. I figured it was too good to be true from just a 5MB img file.
I'm installing adb at work now to see if I can get this damn thing to work.
I was wondering if I flash some early 1.5 rom (Haykuro ADP 1.5Hr3) would it bring back the old splash screen and then I can just reverse to stock via the unrooting steps?
typed:
Code:
fastboot erase splash2
and it says: "erasing 'splash2'....FAILED (remote: partition is not existed!)"
Maybe I should format my SD card and remove all the partitions? I don't think he has to do with that, but I don't know what else it could be.
flexnix said:
typed:
Code:
fastboot erase splash2
and it says: "erasing 'splash2'....FAILED (remote: partition is not existed!)"
Maybe I should format my SD card and remove all the partitions? I don't think he has to do with that, but I don't know what else it could be.
Click to expand...
Click to collapse
You have the new spl which removes the splash2. With the new spl you only have splash1.
supremeteam256 said:
You have the new spl which removes the splash2. With the new spl you only have splash1.
Click to expand...
Click to collapse
So what do I do then? fastboot erase splash1?
Because I did that (splash1) and it says "erasing 'splash1' ... FAILED (remote: erasing error)"
I hope this has nothing to do with me switching back to the stock recovery using girlfriend image (flash_image) thru terminal. Should I go back to CM 1.4? Even though I'm in the bootloader?
flexnix said:
So what do I do then? fastboot erase splash1?
Click to expand...
Click to collapse
Get the original T-mobile splash screen pic. It's on here a couple places and instead of deleting it just flash the original over your custom. And yes it will be splash1.
Now I'm confused. When I first boot up the phone, the T-Mobile screen comes up. Then a few seconds later it use to show the regular animated ANDROID logo when cupcake came out. But since I installed CM 4.0.4 it shows the other CM's ANDROID animated logo after the T-Mobile logo.
What part of "flashing the DREAIMG.nbh will overwrite everything" did you not understand. To unroot your phone ALL you do is flash that file. stop making this so much more difficult. after you flash rc-29, wait for your phone to update.
flexnix said:
Now I'm confused. When I first boot up the phone, the T-Mobile screen comes up. Then a few seconds later it use to show the regular animated ANDROID logo when cupcake came out. But since I installed CM 4.0.4 it shows the other CM's ANDROID animated logo after the T-Mobile logo.
Click to expand...
Click to collapse
Well what you wrote is confusing everyone else you should have stated that in the begining. The animated screen is not a splash screen. Splash1 and splash2 is what would appear before the animated gif. And just like david said flash RC29 and your done.
Related
Hello,
I seemed to have messed my phone up pretty bad, I was trying to unroot my phone and everything was going fine... but afterwards it just keeps booting into SPL, I can boot into recovery, and I can flash newer offically signed roms, but no matter what whenever i boot normally it just goes to the old rainbow spl screen. Any suggestions..?
Edit: Also I know it's not the camera button being stuck because it acts differently if I do so, i.e. if I press down the camera button it'll want to flash the .nbh but otherwise it just boots into the spl without mention of it.
worldestroyer said:
Hello,
I seemed to have messed my phone up pretty bad, I was trying to unroot my phone and everything was going fine... but afterwards it just keeps booting into SPL, I can boot into recovery, and I can flash newer offically signed roms, but no matter what whenever i boot normally it just goes to the old rainbow spl screen. Any suggestions..?
Edit: Also I know it's not the camera button being stuck because it acts differently if I do so, i.e. if I press down the camera button it'll want to flash the .nbh but otherwise it just boots into the spl without mention of it.
Click to expand...
Click to collapse
Wrong Forum ask in Q&A
since it will read the .nbh file, have you tried applying it?
no, you are wrong. this is a weirder brick
{
"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"
}
gridlock32404 said:
Click to expand...
Click to collapse
ummmm can i flash the old radio then the 1.33.2005 spl onto this and kill it? it scares me
david1171 said:
since it will read the .nbh file, have you tried applying it?
Click to expand...
Click to collapse
I tried applying it, and it goes through fine, but it just keeps rebooting to the spl...
worldestroyer said:
I tried applying it, and it goes through fine, but it just keeps rebooting to the spl...
Click to expand...
Click to collapse
is it the stock spl?
have you set up adb/fastboot before
hmmm, i remember someone else having this problem before but i forget what the solve was
I got this same problem. A temporary workaround is just to do
fastboot reboot to reboot into android as that command forces it to reboot directly, ignoring any other input commands (ie. Home+Power, Camera+Power).
h.nocturna said:
I got this same problem. A temporary workaround is just to do
fastboot reboot to reboot into android as that command forces it to reboot directly, ignoring any other input commands (ie. Home+Power, Camera+Power).
Click to expand...
Click to collapse
yeah i remember you saying you had that problem a while back, did you ever get a work around for it? or did you have to get a new phone?
maybe this might be helpfull to know
gridlock32404 said:
hmmm, i remember someone else having this problem before but i forget what the solve was
Click to expand...
Click to collapse
I had this problem too. It would boot just fine if I left the battery out for over 10 hours. But any reboots after that will go right to the SPL. Flashing RC29 doesn't solve it either. I ended up getting it replaced (waiting on it being shipped back).
david1171 said:
yeah i remember you saying you had that problem a while back, did you ever get a work around for it? or did you have to get a new phone?
Click to expand...
Click to collapse
No. That's the only way I can get it back into android =/
Fortunately, I bought another phone and now I just use that one for testing ROMs that aren't stable enough for me to keep.
I'll probably end up selling it for parts and recover a fraction of what I spent on it.
What did you do to get that way?
weird brick
Ok first of all your phone is not bricked.the defintion of a bricked phone is one that you cannot access recovery or fastboot.
Secondly it sounds as if the rc29 file you are flashing is corrupted can happen many different way I will give yoy an idea how to proceed
1st download dreaimg.nbh google it (download from a different source then you did last time)
2nd enter recovery. (Home + power) wipe phone
3rd turn off your phone remove battery and sim and sd card wait 10 seconds install battery and sims leave sd out)
4th format sd to fat 32 after formatting copy dreaimg.nbh to sd for computer install sd card into phone
5th power on the phone holding the camera button down to second stage till you get spl showing (rainbow)screen
6th set up phone
If this fails replace your sdcard and repeat the process
someone is late to the party.
weird brick
This should be posted in q&a mods
are you getting this error on your android device
Hazen said:
This should be posted in q&a mods
Click to expand...
Click to collapse
you have utterly failed. like for real.
david1171 said:
someone is late to the party.
Click to expand...
Click to collapse
Better late then never
So im installing 4.1.9999
Im following this steps, but
1- Perform a Backup......nandroid, etc
2- Download: http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image. This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download my ROM. Posted Below
4- Mount your phone and place BOTH 1.6 Image and my ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
8- Apply sdcard:choose zip *Pick cm-4.1.99-signed.zip* from the list.
9- Reboot!
-When I applied "dream_devphone_userdebug-ota-14721.zip" i kept holding home.. during the whole installation.. and my phone never rebooted.
-so should I reboot it and press home to install the other .zip , or should I just install it now?
Your not suppose to hold home the entire time thru out the installation, just when it reboots. I would just flash that again and do it over.
ugh really?
you didnt read. it didnt say hold it during installation. it said hold it during reboot...which you dont really hafta do
flash htc. when it puts you back to your recovery, flash CM. when it puts you back to recovery again, reboot. when you get back to recovery again (not having to hold home at all) reboot again and let it load.
i never even reboot between htc and cm flashes. i am hardcore.
Hey guys, I got an error when applying "dream_devphone_userdebug-ota-14721.zip" again
E: Multiple firmware images
E: Can't store radio image
Installation Aborted
Click to expand...
Click to collapse
How can I fix this?
david1171 said:
i never even reboot between htc and cm flashes. i am hardcore.
Click to expand...
Click to collapse
Yes you are.
{
"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"
}
Hey guys, I got an error when applying "dream_devphone_userdebug-ota-14721.zip" again
E: Multiple firmware images
E: Can't store radio image
Installation Aborted
Click to expand...
Click to collapse
What recovery do you have?
And I'm talking bout your regular recovery not the htc 1.6 one
supremeteam256 said:
And I'm talking bout your regular recovery not the htc 1.6 one
Click to expand...
Click to collapse
It says "android system recovery <2>"
..okay so i decided to do this:
I rebooted the phone and re-applied the (dream_devphone_userdebug-ota-14721.zip)
so I did this.. and I was SUPER READY for when the little package installer came up to hit HOME button, but instead everything installed and the phone never rebooted lol
so im back on home screen
should I apply 4.1.9999.zip now?
supremeteam256 said:
And I'm talking bout your regular recovery not the htc 1.6 one
Click to expand...
Click to collapse
..........
ROFL
xologist said:
It says "android system recovery <2>"
..okay so i decided to do this:
I rebooted the phone and re-applied the (dream_devphone_userdebug-ota-14721.zip)
so I did this.. and I was SUPER READY for when the little package installer came up to hit HOME button, but instead everything installed and the phone never rebooted lol
so im back on home screen
should I apply 4.1.9999.zip now?
Click to expand...
Click to collapse
I'm confused, so the phone never rebooted but the phone is on you main screen of your phone.
i mean i still have not gone to home screen.. that would be dumb
everything i said above i meant on the recovery.
ill re-phrease it
okay so i decided to do this:
I rebooted the phone to recovery and re-applied the (dream_devphone_userdebug-ota-14721.zip)
so I did that.. and I was SUPER READY for when the little package installer came up to hit HOME button, but instead the "dream_devphone_userdebug-ota-14721.zip" installed and the phone never rebooted.. keeping me on the home screen of the recovery.
so im back on recovery screen
should I apply 4.1.9999.zip now?
yes, go ahead flash the rom and reboot
seriously....go download the 1 click 999 flash and then upgrade to 9999 afterwards. 2 totally separate flashes.
knowfear said:
seriously....go download the 1 click 999 flash and then upgrade to 9999 afterwards. 2 totally separate flashes.
Click to expand...
Click to collapse
i have never seen it so hard to wipe, flash, flash, reboot in my life.
xologist said:
i mean i still have not gone to home screen.. that would be dumb
Click to expand...
Click to collapse
Gahhhhhh....
You're my hero
i lost so many iq points reading this
i was gone for two days...wtf happened to xda
B-man007 said:
i lost so many iq points reading this
i was gone for two days...wtf happened to xda
Click to expand...
Click to collapse
Exactly thats what happens. Don't miss two days again otherwise this will keep happening.
I was about to buy my friends N1, after he cleared the data, it is now stuck on boot screen, he has sent this to me to try to fix since he is not a technical person at all, but I am also dumbfounded by it.
here is what happened:
1.) He went to settings and clicked restore to factory defaults
2.) It rebooted and got stuck to 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"
}
He send unit to me just now.
1.) Removed bat to turn off since power button no longer works to shut phone off
2.) Pressed POWER+Vol Down to enter Menu
3.) Selected Clear Storage
4.) asked to confirm, so I did, it said it will reboot in 5 seconds, so it did and still stuck with this screen.
Alternatively,
I chose recovery, then wiped everything, reboot still the same.
Tried downloading multiple roms, renamed to update.zip, but it will give me an error in recover mode, not signed.
This N1 is unlocked.
Now, I want to follow the instructions here but I am wondering if it is worth it or I will just return the n1. Certainly a bad sign having seconds thoughts on moving to Android
How To: Load a Custom ROM on the Nexus One (Updated 1.11.10) | TheUnlockr
Had the same issue
Had *exactly* the same issue a few weeks ago and tried dozens of different options but eventually gave up. I sent it back to HTC for repair and it came back in two days *with a new screen* (which I didn't ask for). The screen replacement cured the screen alignment/keyboard offset issue that I was getting multiple times a day. So I was happy Excellent service from HTC!
I had a similar problem. Reflashing the recovery image, then reflashing the ROM fixed it for me.
Try pushing over Clockwork recovery, or at least reflashing Amon_RA's recovery image. If you stick with Amon's, upgrade to 1.7.0.1 while you're at it.
The reason to try Clockwork, though, is that it allows you to disable signature checks. Plus, ROM manager integration is awesome. It saves time if you flash a lot!
FIRST, try renaming the zip file just "update". NO .zip or quotes. Sometimes the PC OS adds an extra .zip.
Ken
Gave up on it too, sent it back to HK yesterday, hopefully, they will replace it too. Thanks everyone!
I would have flashed the stock factory image on to it. That's different from flashing a zip, in that the image copies the sector bit by bit, so if there is any kind of bug, it gets overwritten.
ATnTdude said:
I would have flashed the stock factory image on to it. That's different from flashing a zip, in that the image copies the sector bit by bit, so if there is any kind of bug, it gets overwritten.
Click to expand...
Click to collapse
I assumed that would have worked for me too, but it didn't. Had to send it back....
I would have flashed boot, system and userdata, it was in the recovery so it wasnt bricked...
ah well
Update your recovery first.
So I did an OTA to ICS, and it was working fine. So I rooted, safestrap'd, and loaded Eclipse 1.3 Hybrid. Was working ok. Messed with the DPI a bit, and got itself stuck in a bootloop.
So I tried a nandroid restore - boot loop.
Tried reloading Eclipse 1.3.2, wiped data et. all - bootloop.
Tried restoring my stock build - bootloop.
Went back to safe mode off - black screen, no boot anim, PC gets motocrap popping up.
Fastbooted back to 217 - black screen, PC gets motocrap popping up.
Suggestions?
Are you still getting the safestrap splash screen?
My advice would be to do a factory reset in stock recovery. If that doesn't fix it, fastboot everything manually. If by chance you did it manually the first time, this time use RSDlite.
It sounds to me like you either missed something the first time (it happens to the best of us), or you got really unlucky and developed a hardware problem randomly. Since it sounds like safestrap was coming up before, I doubt it's hardware.
Sent from my Amazon Kindle Fire using xda app-developers app
No safestrap anymore. I did the factory reset in stock to no avail through RSD and the MotoICS tool. And unfortunately, I can't send it in for warranty repair because it has an unlocked bootloader.
mxgoldman said:
No safestrap anymore. I did the factory reset in stock to no avail through RSD and the MotoICS tool. And unfortunately, I can't send it in for warranty repair because it has an unlocked bootloader.
Click to expand...
Click to collapse
How did you get an unlocked bootloader?
Also, what happens when you try to boot into fastboot mode?
Sent from my XT894 running ICS
Internal Engineering sample. It'll go to fastboot mode, but it does give a warning about the bootloader being unlocked. I've done the fastboot with the 217 files, then booted to recovery and wiped data/cache. No luck.
{
"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"
}
Where did you get that?!
Also, that could have to do with the issue I guess. Try fastbooting GB instead of ICS, then reinstalling the ICS patch like you did before, maybe?
Sent from my Amazon Kindle Fire using xda app-developers app
you need to flash fastboot files immediately until battery will be discharged. or you have to make motorola factory cable
Yes, the rate of discharge the D4 suffers from when OFF is ridiculous. I once had the phone discharge 40% in 24 hours...with the phone turned OFF
You really should have a factory cable or adapter and you will be able to fix it very quickly with RSD Lite and the full XML.zip of fastboot images.
The factory cable will bypass the battery and charging circuit and power the device directly, allowing you to flash and recover it no matter what state the battery is in.
That's a very unusual device and it would be a shame not to be able to fix it.
There is no reason, with a factory cable, a complete recovery would not be possible if you can get to the boot menu as you have shown in your pic.
podspi said:
Where did you get that?!
Also, that could have to do with the issue I guess. Try fastbooting GB instead of ICS, then reinstalling the ICS patch like you did before, maybe?
Click to expand...
Click to collapse
Holy snackycakes, that worked! AWESOME.
... I want that bootloader! :good:
Glad to hear you are back in business!
hu every body my xperia x1 start in bootloader mode every times i start it i try to flash it and still the same probleme can any one help :crying::crying:
no :crying:
samisou said:
no :crying:
Click to expand...
Click to collapse
try to charging your batery with desktop charger first,, i think it cannot start flashing coz your batery is not enough/sufficient
sorry for ma bad english
You should try a sdcard based flash... just put a rom image named kovsimg.nbh in the root of the card and wait. if after the flash you phone still booting on spl mode, try opening you phone and clean the volume keys and camera button.... maybe there is a stucked button
connect the phone to a USB, run the command line fastboot reboot
I think what he means LK Bootloader (blue text).
romanck said:
I think what he means LK Bootloader (blue text).
Click to expand...
Click to collapse
Hello, I also have a problem on my X1, I wanted to run andorid on my phone, but everytime I run HaRET in WM or using LK and entering recovery, my phone keep on reboot automatically. One thing that I know is my camera button cannot respond when pressed. I assume that the button is stucked. How can I un-stuck the button? I already tried to clean it but still not working.
BrianXP7 said:
Most likely your camera button really is stuck but I think it might loop into recovery due to a certain "Reboot to Recovery" signal. Did you ever successfully ran Android or at least installed it properly?
Click to expand...
Click to collapse
NO, I have not, because all the android I wanted to run will make the phone reboot, both with HaRET.exe or with LK recovery.
After installing the LK recovery, if I didn't half push the camera button, the phone is only stuck in fastboot mode (but there is still no ROM inside my phone), when I halfpush my camera button, the phone reboot itself.
Do you ever have any experience with stuck camera button? Or the problem is just the same for instance in your normal phone, holding the camera button while entering the recovery will send the reboot signal to the phone?
Anyway, where is the "Reboot to Recovery" signal come form?
===UPDATED===
I already cleaned my camera button, so that it can operates normally, but still have the reboot problem when trying to enter the recovery. The strange things is when I view my device information, it only shows that my ram is 128MB instead of 256MB. Strange, any idea?
BrianXP7 said:
This is very strange. Try reflashing ClockworkMod Recovery.
Click to expand...
Click to collapse
I don't know then, I already tried to reflash the CWM, reflashing to stock WM, stock radio and stock SPL, but it still in 128MB memory status. The handset just cannot boot normally without pushing the reset button 1 times.
I attached the picture in case you are courious:
{
"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"
}
solved
BrianXP7 said:
Sorry. I can think of anything that may have caused this. I'll get back to you when I found something.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No problem my friend, after doing this things, my problem is solved:
1. reflash the stock rom
2. reflash stock spl
3. pull out the baterry, put the phone without battery the whole night.
After reinsert the battery, the phone can boot normally without needing to push the reset button, and the RAM shows 256MB. Everything boots normally, not stuck in any bootloader stuff anymore.