Database Users

Odd boot problems after root

I'm seeing some weird problems after rooting my phone. I just got a replacement Droid X after my last one's screen went bad. The replacement came with 2.2 installed.
I downloaded the `TDFOneClickRoot`, which uses the 'rageagainstthecage' explot. After rooting, I installed all the apps I had on my old phone. All the apps were installed via the marketplace. I also remounted /system as r/w and copped two sound files over (one to /system/media/audio/ringtones and one to /system/media/audio/ notifications). Then I rebooted and started having my problems.
- If I reboot normally, I get the moto logo, I hear the 'droid' sound and then it will sit there. It will replay the notification sound every so often, but it doesn't reboot.
- If I hold down the 'search' key, hold down power until the moto logo shows, and then release power the device will boot normally.
I'm worried about trying the different recovery methods described in the forums, because most of them talk about different scenarios than this one. Does anyone have thoughts?
EDIT: I've tried getting into the recovery menu without success.

I'm going to try putting custom ringtones in my /system/media/audio/notifications folder and let you know if it hoses my system. I'm suspect of that being your issue.
I'm making a nandroid right now and will let you know in a few minutes.
EDIT: I used ADB to stop my interface, copy the file to my /system/media/audio/notifications folder, then rebooted. Worked without a hitch. You might try a factory reset and go from there.

Thanks for the advice. I went ahead and did a factory reset from the settings/privacy menu. Unfortunately, I seem to have the same problem even after the reset.
What's the best way to do a factory reset? I've read a bit about the SBF, but I'm not sure if that's the right path. Before this, I had a Droid Eris, that was very easy to reflash. I'm worried that this is more complicated and easier to mess up.

If nothing seems to work a SBF would be your best bet. But do be careful though as if you are on 2.1 DO NOT flash the OTA 2.2 SBF, you will be bricked. Search around Google for the SBF file.

OK, so I want to do the SBF, but I want to make sure I'm using the right one.
Here's the package I downloaded:
rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
VRZ_MB810_2.3.15_1FF_01.sbf is the SBF file. From what I can tell the procedure seems straight forward:
- hold down vol- and camera, then power up
- connect via usb
- run rsd lite
The drivers are installed, and the phone does show up on rsd
Code:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x003003
DRM Version: N / A
AP Die ID: <<number>>
BP Die ID: <<number>>
AP Public ID: <<number>>
BP Public ID: <<number>>
Is it normal that many of the fields return 'N/A'?

Just make sure you open up RSDLite 4.8 Go to Config>Device ID Options>Check the Box that says "First-Come-First-Serve Device ID Mode"
Then go ahead and click start and just wait it out.

I've gone ahead and done that. Now that I've done the SBF, all is back to normal.
Thanks!

Anytime! Have fun

HTC Tattoo bricked? Doesn't boot, goes to fastboot...

Hey!
This is the issue: when I try to turn the phone on by just pressing the red button it goes directly to the fastboor menu. If I try to go to the recovery from there shows "TATTOO" for hours. If i try to go to the recovery dirctly by pressing HOME+ red button, it firsto shows the fastmenu for a second and tries to boot unsuccessfully. During this boot tries, I try to get some info with adb logcat, but the device is not casting anything. And well, if a picture is worth a thousand words, I guess a video is way better:
youtube.com/watch?v=zAejyMIVNGk (newbie, no urls!)
sorry for my english
And well, I have no idea how I got to this, this used to be my phone, but I bought a Nexus One and gave this to my sister, who has no idea what happened (as usual). Oh, this morning somehow I managed to get to the recovery menu, and booted until the android bootscreen, then vibrated and died again. I got to the recovery again, made a nandroid backup and wiped all data, it booted successfully, but the rom had no home application and ran really bad.
I was about to try to make a goldcard and install the stock RUU rom, but if I have no adb I cannot make one...
Any idea?
PS: the rom was nFinity 1.18 (2.2 Froyo) and the recovery was the lastest Clockwork.
PS2: I just realized that in every place I say fastboot I mean HBOOT, sorry again

sounds like recovery is still there, if you hold home + menu when phone if off , and then click red power button you should get recovery menu.
Then hopefully you can try full wipe and install a rom , rember the first time u boot a rom might take a few minutes
let me know how it goes

Yup, not using that method but I can manage to get to recovery sometimes. I'm trying to flash another ROM, but for some reason it doesn't let me. I've tried KalimochoAz (gingerbread) and HDCR (donut) and says something about assertion failed when checking if the device was click on the first case and in the second, complains about unsupported stuff...
I was about to try another roms by random but the SD does not refresh or even mounts, there must be something really messed up with this phone...

You can try to flash your stock rom from fastboot.
You don't need a goldcard, just run the update utility on pc, go to your temp directory and take the rom.zip file, rename it to CLICIMG.zip, copy it to sd card, put card on device and on fastboot menu pres vol down to start flashing the rom. I is the same version with the rom that device has before rooting, you will not get any errors.

I think there's a little misunderstanding here, mainly because of my confusion, it's not the fastboot menu qhat I get, but the HBOOT menu, and pressing the back button in order to access fastboot doesn't work...

oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?

manutenfruits said:
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
Click to expand...
Click to collapse
Of course will not work like this.
You must first run the RUU utility on pc and while is open to search your temp directory(maybe is inside another folder) for rom.zip file. This is the rom, the executable is an installation program which contain the rom and the app to flash the rom from pc packaged. You need only the rom.zip for flashing from sd card.

I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.

manutenfruits said:
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
Click to expand...
Click to collapse
You don't need to go so far. Just run the ruu utility and when the first screen appears go to temp dir(c:\users\you user's name\local\appdata\temp on windows 7). The executable is an encrypted package and when you run it extracts all included files and then starts the installation program. These files will deleted after this program exits(when the installation complete or an error occurs)

Cool! I just renamed it to CLICLIMG.zip and I finally loaded. The problem now is that when it finishes, instead of asking me to flash it, says
"CID Incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No"
While running the RUU I made sure that it was for HTC Tattoo since it showed me the device during the steps. And I got it from a post describing the steps to flash it using the goldcard.
Furthermore, this error is something similar to what happened when I tried to flash from the recovery. This is REALLY weird...

Probably this isn't the sama as your device's stock rom. I think goldcard needed for flashing any htc original rom, but without goldcard only the device's version will be flashed successfully. Try to download other original roms if you don't know which you had before.
Here is a site with shipped roms for tattoo:
http://www.shipped-roms.com/index.php?category=android&model=Click

The RUU wasn't a problem, I tried now with a goldcard and flashed successfully! I could not get ADB connection to make it, but I once made one and still had the .img in my mail inbox.
But still nothing has changed...
pressing on drives me to the HBOOT screen, whose only options that work are "simlock" to flash CLICIMG.zip, and recovery (freezes on "TATTOO")
EDIT: does not freeze, but goes back to HBOOT after a while... ¬¬

You say that now you have the stock HTC rom and again you cannot boot it and instead the device reboots again to HBOOT?
Then maybe you have a hardware problem which leads to this behaviour.

OK, now I guess it still has warranty, but the problem is that I rooted it.
But now that I flashed somehow the original rom, should be no problem right?

Yes, if you successfully flash the stock rom, you're not root any more.

had that problem to, but theres easy fix for it without doing all whats being sayd here
Even tho phone dont boot annymore and stays on logo plug in the usb cable
and work with adb shell and reflash recovery (to be good tattoo-hack.ko etc tricks need to be done before doing it or you get errors)
http://forum.xda-developers.com/showthread.php?t=716282 step 1.5 and tools from step 1.3
and ether get Amon RA recovery or clockworkmod and use
Code:
./flash_image recovery /sdcard/recovery.img
then reboot into recovery
HTML:
adb shell "reboot recovery"
mount usb put in a custom rom and flash it
if all done well should work (had same problem)
bascly adb still work even if you think you bricked phone just have to let it "startup"
Greetings

I'm afraid that won't work. I've been trying all the time with adb logcat and adb devices unsuccesfully. I thought that the TATTOO bootscreeb would give me some feedback in all cases, but now doesn't seem to work...

I've had similar problems when trying to flash nfinityGB.
My problem was that I missed something on the way from
- creating a gold card
- rooting device
- installing recovery
- flashing rom
All I did was to download and execute "RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe" (or any other ruu).
Be shure to have SDK with all drivers installed properly.
After this your device is in unrooted (original) state as dancer_69 already told you.
Now you can decide whether to claim warranty or properly follow the guides on xda to get root and flash custom roms.

I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)

manutenfruits said:
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
Click to expand...
Click to collapse
Something like this thought when I said that maybe is a hardware problem.

Fastboot/Clockwork - stuck on old ROM - Green user -

Hi.
I swapped my old Toshiba TG01 to Dell Streak - unlocked, with the ROM DJsteve - I think because I do not know how to check what ROM I have
But it seems to me that something is wrong with the system on the phone. As if part of the function does not work.
So I decided to upload the new ROM - exactly StreakDroid 1.9.0 (aka The Final Frontier)
And the problems started.
Acted according to the attached instructions:
1.Download update-1.9.0.zip from the links below
2.Place Zip file into root of SD Card
3.Make a text file and type in the options you would like to chose as shown above.
4.Save file under sdcard> install.txt
5.Boot into StreakMod or Clockwork Recovery
6.Select Update from Zip File> Select Zip File From SD Card> update-1.8.0.Zip
7.Wait for installation.
Boot 8.First May Take Longer Than a normal boot. Things are being installed, the stuff is being generated. Patience.
9.Enjoy.
I stopped at the point 5
The phone is angry at me - I asked, begged, cursed, and plucked off the hair of my head ... nothing is helping.
I install Clockwork on my phone - I tried to boot from it - yes the phone will restart ... and only this - just simply restart.
I tried the method - Volume down / up, and Power ON - show me the menu:
1. Factory Reset
2. Software 2.Software Update.pkg upgrade via a SD Card
3. Screen calibration
4. Power off
Point 2 - does not work, does not recognize the file pkg - simply nothing happens - screen is black with light back light (probably the fault of the ROM DJSteve)
I tried the Fastboot from the console. (After few hours searching of method how to start this app - its not easy to find a drivers, programs and clear instruction)
Fastboot devices - can not detect anything - just showing another line in DOS
Fastboot-and flash recovery 0x413c c: \ recovery.stock.img (or any other recovery) hangs on - waiting for the device.
I thought I'd upload the ROM TG01 was difficult (wires, rubber bands and a lot of luck - yes - adventure with Nokser - priceless), but Dell streak and fight with him for several days overwhelmed me.
I tried fastboot on Windows 7 64bit, 32bit, Windows XP Pro - and nothing works.
I'm stuck in the ROM which I do not like. I can not upload an attempt StreakDroid 1.9.0 or ROM O2 2.1. Clockwork only restart phone. Runing with Volume UP(or Volume DOWN or Home) and Power ON - hang phone until I dont remove battery. I read XDA Forum, Modaco, plenty of website about fastboot and roms in Android - now I just want to back to o2 or Dell ROM
Pls help me ... or kill me
Totaly green in Android - Wrzaskun

You have to flash the recovery and then use the fastboot command to reboot the phone (fastboot -i 0x413c reboot) and then as the phone restarts hold both camera buttons down. If you let the phone boot up normally the stock recovery will overwrite the custom recovery.
If your phone is rooted you can prevent this by renaming the file install-recovery.sh to something else.
To make the fastboot commands easier try this tool.
Here is a gallery that shows what streakmod recovery should look like.

Thank You for help... but
I download MultiRecoveryFlasher - nice matrix-like fonts... and its works
Adlast my phone show something on screen not only Fastboot Mode
recovery done... and restart.. and phone back to old ROM - normal restart.
"and then as the phone restarts hold both camera buttons down" - volume? or I have somewhere second camera button (its not silly question - TG01 have reset button under battery cover, HTC Diamond - reset button under stylus )
I try both volume... and we see....
YES! both volume - my hearth stops on blinking touch buttons - and NICE blue fonts on my phone -
Finding update - ok
Installing update .... - Dell 2.2.2 - 345 - underway
Thank you Marvin
PS. if I want to install ROM Final Frontier after DELL 2.2.2 I can also use this - MultiRecoveryFlasher ?

It doesn't matter how you get Streakmod recovery on your phone, but that's what you need to flash Streakdroid 1.9
You flash a .pkg file with a stock recovery and flash a ROM that is in a zip form with a custom recovery like streakmod recovery.
You can use the MultiRecoveryFlasher to change the recovery when you need to.

Thank You for help.
If I find a manual to change ROM write so clear like this 2 posts

Motorola Bravo HARD BRICKED

Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens

ssfirme said:
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
Click to expand...
Click to collapse
Press both volume buttons on the screen with the android and exclamation mark. That'll take you to stock recovery where you need to wipe data and factory reset.
If you have to flash the sbf again, try using sbf_flash on Linux. It'll flash in times where RSD won't recognize your phone.
Linux Live\sbf_flash tut
sbf_flash binary is in attachments
Only use Defy 2nd-init for recovery
(and once its installed, steal /system/bootmenu/* and /system/bin/bootmenu from Defy CM9 from June 5th on up -- touch bootmenu is pretty awesome; replacing the bootmenu isn’t for the feint of heart.)

the only problem is i dont have linux i have windows 7

Use rsdlite sri I don't have a link on me
Sent from my Galaxy Nexus using XDA

Had same type of problem on Friday. Followed this post http://forum.xda-developers.com/showthread.php?t=1559109 now I'm back up and running.

ssfirme said:
the only problem is i dont have linux i have windows 7
Click to expand...
Click to collapse
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.

ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone

yes i have it in bootloader mode

Did you install everything before plugging phone in?

Try uninstalling everything motorola related and reinstalling just the drivers....On a previous Win7 install nothing was recognized, but on a reinstall of the entire system it worked fine and still does. I still recommend the Linux way over RSD because it will flash your phone regardless, provided you can access the loader.
I still haven't gotten native tethering to work with Windows, but then again, I quit trying sometime around December or January.

ssfirme said:
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
Click to expand...
Click to collapse
This is for all those people who are having trouble flashing with RSDlite in Vista & WIndows 7.
If I am right, RSD lite does not seem to recognize the sbf file after you select it and instead the "start" button remains grayed out.
If that's the case, here the solution:
I had a similar problem and sucessfully used the command line parameters for RSDlite to force a flash. I managed to get a signed/unsigned firmware installed.
You need to copy the firmware you want to flash into the RSDlite directory in your program files folder.
Make sure you are in bootloader mode first.
Then, open command prompt and "cd" to the RSDlite directory
eg:
> cd C:\
> cd Program Files
> cd motorola
> cd RSDlite
>
now for the flashing type:
> SDL.exe -f xxxx.sbf -t 2
where xxxx.sbf is the firmware you are flashing to the phone.
flashing will begin shortly afterwards.
It worked for me, but in the end, show FAIL STATUS.

skeevy420 said:
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
Click to expand...
Click to collapse
Thank you sooooooooooooooooo much!
After several hours of messing with my brothers Bravo, I finally got it working by following your instructions.
Really: I'm speechlees man.

hard bricked my phone
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes

dzdonce said:
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
Click to expand...
Click to collapse
Not sure if this will help since I did not watch the video myself, but a quick Google search gave me a video describing how to take a Motorola USB cable and modify it to unbrick a phone. I did not watch the video yet so I don't know how relevant it is to your problem. But just by looking at the video preview it looks like the difficulty level may be pretty high... Here is the link:
http://m.youtube.com/watch?v=XwwI_6doBWk
Sent from my LG-D415 using XDA Free mobile app

[Q] [SOLVED] LG L7 Soft-bricked recovery?

Hello XDA (I'm new here)!
I'm having a very difficult problem (For me atleast), but i will begin at the start:
When i bought my LG, my proximity sensor was corrupt. Every call i started, my phone immeadietly locked the screen.
So a few weeks ago, I flashed the KDZ from homero (P700 V10K+Root+CWM etc..). After that I was able to flash CM10 to my phone.
But this is where the problem starts, I wanted to fix the proximity sensor bug, so i added the following line to my build.prop:
"gsm.proximity.enable=false".
I did it like this:
adb pull /system/build.prop C:/ *Pulled my build.prop*
adb root *made sure i was having root access*
adb remount *to access the /system/*
adb push C:/build.prop /system/ *and it succesfully copied*
adb pull /system/build.prop C:/test.prop *to check if everything changed succesfully*
Then i rebooted my phone, and now it's bricked(Can't boot CWM, Can't boot CM10, can only boot to Emergency Mode, no ADB). Because it was such a small change, I don't have any backups, which is really frustrating. I have very, very important data on my phone, so I need to recover some files.
Does anybody have a solution to this problem? Please don't suggest anything related to ADB, cause even ADB won't find the device.
Thanks so much for reading, hope you understand my problem and want to help me.
(I'm sorry for my very bad English)
EDIT:
The solution:
- First of all remove your battery,
- Then press and hold the vol- key + power
- When the lights turn on, press the menu key.
- Release the power key when your lg vibrates
- Your in CWM
- Use a custom update script, there are plenty out there, to push your original build.prop.
- Reboot & everything's fine.:victory:

Just tried to use the (Homero v10k) KDZ, but when i use the KDZ_Updater, will i lose my data ? (When going from cm10 > v10k?).
KDZ_Updater crashes, but if anybody knows, I can try again.
Please help me, I really need some data on there.

Got KDZ_Updater to work, currently it's busy... I will edit this post, if it's back alive again, hopefully it will help other people with the same problem
EDIT:
Okaayy... KDZ Updater finished, phone still dead. It stays about an hour at the LG Logo (The animated one, so it's booting Android), can't manage to get to CWM.
Is it possible something in Homero's KDZ isn't right? I try to boot into CWM using the vol-+ buttons and the power button. After LG logo, i release the power button, still no result...
Could anybody, please, please help me? I can't live a day without my phone... (I don't care about the data anymore, almost everybody knows it, so it's alright... )