What should the home screen of the .588 Gbread leak look like? I followed all the proper instuctions, but now I have two contacts icons on the dock, which I dont think should be.
Second everytime I reboot it goes back into the bootloader, and doesnt just reboot? Can I fix this?
The bootloader thing is no good... u most likely need to reflash (or upgrade to .591). As far as the gb (blur) launcher goes, you have icon for phone, and an icon for contacts, and those icons are replaceable, just drag whatever app you want on there to it, same as other launchers
I reflashed back to stock Froyo but everytime I connect my DX to my PC it goes straight to the bootloader. Has anyone got a fix for this?
Thanks,
Steve
Is it booting into the bootloader or clockwork?
Right into the bootloader. This is only when the DX is connected to the PC.
Here's a thought: quit rebooting while connected to computer lol ... is there a reason it has to be connected??
Sent from my DROIDX using Tapatalk
Well if I want to transfer data from the PC to the phone I have to have it connected. Thanks for the advice though.
stevefxp said:
Well if I want to transfer data from the PC to the phone I have to have it connected. Thanks for the advice though.
Click to expand...
Click to collapse
Gingerbread makes you reboot to change the state of the USB connection? It doesn't have a pull down you can change it in?
All,
Sorry if I have not been clear on this. Originally I thought this was a Gbread issue, but its also happening with stock Froyo.
So I just flashed stock Froyo 340 back to my DX. At the end of the SBF flash it tells you its going to reboot the device, and finishes with a PASS. The problem is that it reboots right back into the bootloader. Is this normal behavior? I would think the reboot would take it back to the OS itself. This behavior happens when connected to the PC via USB, and I do a normal reboot. I end right back at the bootloader. If I disconnect the DX from the PC and then reboot I do end up in the OS as though normal.
Has anyone seen this, and if so how do I rectify this? I do want to be able to connect my DX to my PC for file transfers, etc.
Thanks,
Steve
Related
ok i have installed many roms for my g1, have had the hero for sprint for awhile and everytime I try to do the fresh rom i get errors, ive tried wiping it then installed the update.zip, tried to just overwrite it still errors which always forces me to nandroid restore,
I can do the eclair 2.1 no problem, but fresh always gives me errors. atm i have a rooted sprint htc hero, no custom rom on it atm. any help?
What kind of errors?
Have you tried re-downloading the ROM?
well when i first boot it up i does the "fresh" sound and goes though all the boot ups and says ok, then gets to the last one that says like boot up fresh o somethingthen [wait] i wait, it eventually starts up but mainly alot of force closes,
im thinking of unrooting my phone back to stock and I have been looking at pre kitchen, so once my phone is stock, i just plug my phone in and do auto-root? and thats all i have to do?
because im thinking of going stock then auto rooting for ease.
samrozzi said:
well when i first boot it up i does the "fresh" sound and goes though all the boot ups and says ok, then gets to the last one that says like boot up fresh o somethingthen [wait] i wait, it eventually starts up but mainly alot of force closes,
im thinking of unrooting my phone back to stock and I have been looking at pre kitchen, so once my phone is stock, i just plug my phone in and do auto-root? and thats all i have to do?
because im thinking of going stock then auto rooting for ease.
Click to expand...
Click to collapse
The long wait after the first flash is normal and you will see that every almost every rom after the first boot. If your phone is totally stock (you mentioned you tried wiping data) then you definitely shouldn't be getting FC's.
Did you wipe your data after using the 2.1 rom and before flashing fresh rom? That would be the easier way to go about things. But using the RUU to flash back to totally stock and starting over wouldn't hurt either.
yeah i have wiped everything and tried, i mean i rooted and hacked my g1 for over a year numerous times, so idk. just quick questions on how to revery back to stock because this have never done. im downloading the RUU 1.56 from here
http://geekfor.me/news/sprint-ruu-fails/
not really sure on steps to go back to stock once I get that file?
and also new to pre kitchen, once my phone is back to stock and unrooted etc... do i just plug in phone to pc, start pre kitchen and click auto rooter?
samrozzi said:
yeah i have wiped everything and tried, i mean i rooted and hacked my g1 for over a year numerous times, so idk. just quick questions on how to revery back to stock because this have never done. im downloading the RUU 1.56 from here
http://geekfor.me/news/sprint-ruu-fails/
not really sure on steps to go back to stock once I get that file?
and also new to pre kitchen, once my phone is back to stock and unrooted etc... do i just plug in phone to pc, start pre kitchen and click auto rooter?
Click to expand...
Click to collapse
Once you download that file just extract it and run it. It will walk you through it from there and once it's done you will have a stock from-the-factory Hero. Once you get it booted up and stuff then open the kitchen (get 0.2) and go under the help menu and run the diagnostic tests. As long as sendkeys, adb, and rooting tools pass then go ahead and go to the auto rooter and that's it. If any of those 3 fail then you may not be able to use the rooter.
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
not sure if i have to mount her or not because it is connected to my computer
samrozzi said:
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
Click to expand...
Click to collapse
Try closing the RUU, putting your phone in to fast boot and then checking device manager on your computer to make sure you aren't missing any drivers. If you aren't then start the RUU again.
To go in to fastboot power your phone completely down. Then hold volume down and power. This should get you a screen with 3 skateboarding androids. And then I believe it is volume up for fastboot. Make sure it's plugged in to your comp and confirm device manager is clean, and then run RUU.
samrozzi said:
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
not sure if i have to mount her or not because it is connected to my computer
Click to expand...
Click to collapse
I had that problem, and installing HTC Sync fixed it.
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
samrozzi said:
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
Click to expand...
Click to collapse
I have Windows 7, and both HTC Sync and the pre-kitchen work fine on my computer. What is it that you think Windows 7 is preventing you from doing?
samrozzi said:
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
Click to expand...
Click to collapse
A couple of things.
Install HTC Sync or go get the Android SDK to install the ADB driver.
Then run RUU
Boot the phone into fastboot Power off, hold down volume down button while phone is booting back up.
When you are in Fastboot, press Volume up once.
Then plug the USB in and run RUU.
I have Win7 32 and x64 and have been able to do all ADB functions fine with both machines, its a little more cumbersome, but not an issue.
TTG flashing issues
I had TTG and was trying to reflash to MODACO. The Rom wouldn't reflash. I wiped, factory reset.... Just boot looped or froze. A lot of errors and force closes. I'm running GUTTED 1.6 now with no problems. Why would there have been an issue trying to flash MODACO...?
Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks
Soo I had a problem with my phone's charging where I would pull the plug to stop charging the phone, and the batteey would still indicate that it was charging. Also, randomly, my phone would think its connected to the computer and the "USB" notification would pop up and leave every 2 seconds over and over "again (that stopped eventually). Also, when i try to connect my SD card to my computer, it wont connect (even if the phones "USB" notification popped up). I used to use many different chargers to charge my phone and then stopped because I thought that was the problem. Now, my phone still acta a little weird when I charge it, USB is gone, abd I can't recover into CWM recovery. I have the full version of ROM manager, tried going into recovery that way, but when in normal recovery, it just keeps resetting onto that stock recoveey system. This problem started when I had DL30, now I'm using EB01. I wiped data and chache and its still giving me problems...oh and I forgot to mention, if my phone shuts off, I have to connect it to a charger to turn it back on...even if it has good battery. What can I do???
Sent from my SCH-I500 using XDA App
My friend is having this prob.. The 3 button recovery method still works for him.. I still have not fixed his phone.. But all I have tried so far is a franken kernel flash because he has an extended battery.. I will try more next week
Rocking dj05 and jt's voodoo 5
Are you using a different charger than the stock Samsung one? It sounds like your USB port is screwed over.
KitsuneKnight said:
Are you using a different charger than the stock Samsung one? It sounds like your USB port is screwed over.
Click to expand...
Click to collapse
ahhhhhhyep. Sure that is part of it, but the constant flux and what not I'm sure has messed with the phone. Try an odin back to Di01 or dl09 and see if it fixes things.
I had the same exact problem, odin'd back to stock, didnt fix it at all. Had to return the phone. Guy at best buy said he had seen a few others with the same problem. Must be common for the USB port to take a ****?
mikey6p said:
I had the same exact problem, odin'd back to stock, didnt fix it at all. Had to return the phone. Guy at best buy said he had seen a few others with the same problem. Must be common for the USB port to take a ****?
Click to expand...
Click to collapse
It's when incorrect chargers are used. Whether it be voltage or pin arrangement, it's not as uncommon as you think.
No its not uncommon at all...there are many different grades of chargers
Rom manager throws up a red flag for me to begin with. If your CWM is jacked up you should replace it with an odin flash. I've seen a lot of people having trouble with CWM from rom manager lately.
I agree with the probability of the USB port being messed up, but i'd make sure your software is square first.
As far as the usb issues, have you tried using a different usb cable? If you have, and you are still having issues, then I'm guessing your usb port has a short in it and will need to be repaired.
About your CWM problems, if you flash with something like SuperClean v2.4, you will have your kernel, CWM, and rom all replaced at the same time. This way, if you can get into CWM once, then you won't have issues getting back into recovery again, because CWM will be permanently installed.
Don't use the ROM manager's recovery unless you manually the swap the recovery-update.zip file on your SD card:
Daswolven said:
Take the fixed CWM update.zip from the above post. Drop a copy on your sd card. Copy it into the clockworkmod folder and rename the copy recovery-update.zip. Will work on both ends then.
Click to expand...
Click to collapse
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
swampy67 said:
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
Click to expand...
Click to collapse
Would someone (aka moderator) simply sticky a bold
DO NOT REMOVE ANY FACTORY FILES, u goty plenty of room.......
to prevent this kinda stuff
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
dr1337 said:
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
Click to expand...
Click to collapse
but how do i reinstall when im stuck in a boot loop? is there some way to execute adb?
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
anubis13 said:
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
Click to expand...
Click to collapse
Thanks I'll give it a shot
Sent from my PC36100 using XDA Premium App
thanks this worked like a charm. Gotta love the XDA community.
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Chaz36 said:
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Click to expand...
Click to collapse
Okay so this is what i did as directed by the guys above.
1. Download this file. have to warn you though this service is horribly slow http://api.viglink.com/api/click?fo...ww.filesonic.com/file/958397...pdate.zip.html
2. Put your external SD card into your computer, and copy over the file to the root of the card.
3. Rename the file update.zip(make sure it isn't named update.zip.zip)
4. Put the SD card back it the tab.
5. Make sure your tab is completely shut down.
6. Hold down the volume down button and press the power button.( dont let go of the volume down button till the screen turns on)
7. The recovery will boot and the update should hopefully restore your tab.
8.(optional but recommended) follow these steps in order to revert back to the latest OTA american version so that your able to upgrade to 3.1 when it comes out.http://forum.xda-developers.com/showthread.php?t=1101859
Hope this helps.
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Chaz36 said:
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Click to expand...
Click to collapse
Well sorry that didn't work, i am not to experienced with development for this tab, so im fresh out of ideas. It might help to start a new thread explaining that you tried to un-brick your tab via this method and that a boot loop still occurs. Maybe some super smart devs can help you.
Crsdr37 said:
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Click to expand...
Click to collapse
yeah i did that right after i un-bricked it, but thanks for the heads up anyways.
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
SmittyRN said:
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
Click to expand...
Click to collapse
Dude, you just made my day.
Thanks.!!!!!
I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Added video of issue:
https://www.youtube.com/watch?v=M_mncUueCJ8
Edit: Solved the issue through the most scientific methods; insanity and brute force! The phone would boot sometimes with the lock screen in the rotation, and those boots allowed me a brief window of touch interaction which I used to enable emergency mode, which fixed my immediate problem of being locked out and allowed me into an adb root shell. Hurrah.
Thanks all,
Overkill
OverkillSD said:
I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Click to expand...
Click to collapse
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880
Chopstix9 said:
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
Already in progress But the stock tar also flashes over any user data, correct?
OverkillSD said:
Already in progress But the stock tar also flashes over any user data, correct?
Click to expand...
Click to collapse
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again
Chopstix9 said:
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again
Click to expand...
Click to collapse
Right The problem is, there are files I need to get from the device before I do that!
OverkillSD said:
does anybody have a suggestion that would allow me to get the data off the internal storage before wiping?
Click to expand...
Click to collapse
OverkillSD said:
Right The problem is, there are files I need to get from the device before I do that!
Click to expand...
Click to collapse
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.
Chopstix9 said:
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.
Click to expand...
Click to collapse
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)
OverkillSD said:
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)
Click to expand...
Click to collapse
I wasn't able to do this, presumably because com.android.systemui is responsible for this dialog and when it restarts, the problem restarts with it.
what's strange is that i can see my device on windows but the internal storage doesn't mount when the device shows up >.<
would i be able to flash just the systemui.apk and framwork.res files to stock using odin?
EDIT: Was able to get the device into emergency mode after much spamming of buttons and trial/error; this stops the problem I'm having, and I was able to get into ADB. The problem is most likely with Xposed, I'll be able to troubleshoot from here =) Basically, I had a brief window of laggy but responsive touchscreen interaction once out of every 10 boots which I used to get emergency mode enabled (lots of checkboxes) and this worked. It was either xposed or nova or a combination of the two, but it appears that I'm able to hack at it from here xD