Database Develop

[Q] Think I screwed up?

Ok so I have an unlocked Nexus One that I rooted when I first got the phone 6 months ago. I've been running CM6 no problems at all, everything has been great.
Heres where my problem starts I decided to flash the stock frf91 image onto the phone and did not check superuser permissions or whatever option they gave me before i did it. I was doing this because I thought I was selling my phone. Now I'm not and want to go back to CM6.
The problem is I cant get into recovery at all I get the error with the ! in a triangle with android standing next to it. I've searched everywhere and tried everything. Fastboot and ADB gives me errors like waiting for device (even though my drivers are up to date and it recognizes the phone?) or status failed too many links.
I tried doing a backup from my nandroid information through my nandroid backups on my computer (aka pulling system.img etc) I tried going through the terminal but Im getting denied superuser permissions.
Im just not sure where to go from here ive looked through so many articles and threads and posts and im very confused.
After I flashed the stock image I thought i would still be able to boot into recovery but i guess i dont have recovery? I try to flash the recovery but with no avail.
Anyone have any advice or even just somewhere to start I would really appreciate it. Thanks

When u flashed the stock rom it wasnt a rooted version so u have the stock recovery search for how to root the stock Rom once rooted u can put a custom recovery on there hope this helps

The procedures for the different handsets kind of blur together in my memory, so just want to check.
When you booted into recovery and got the "!" screen with the android did you try holding either the volume up, or volume down key <along with the power button> to bring up the menu?

The ! With the Android is the stock recovery image if I remember correctly if u press the power button the menu should pop up

No Nandroid on restored non rooted rom.

So tonight I was close to a freak out. I made a Nandroid backup of my CM 6.1.1 system. And then I restored a backup of an old 2.2 stock rom. After that I did a wipe / factory reset thing since I wanted to play with plane untweaked and new stock rom. When I got bord of it I booted into recovery mode via "power + volume down" and tried to restore the CM Rom which it refused to do. One point showed up and then it aborted and said something about "something wrong, nandroid restore doesn't work" - cant remember the exact words. So I thought "**** maybe the backup is corrupt". So I tried another one. Which didn't work either. So I actually ended up trying every single of my 22-ish backups. None of them worked. So instead of having a heart failure I just went to bed and told myself I would deal with it today. So today I wanted to boot into recovery mode so instead of dealing with my broken power button I installed 1-click universal androot and quick boot. I soft rooted the phone (obviously stock roms are not known for its rootedness) and rebooted into recovery mode where my restoration attempt succeeded like it always does. So now I'm curious why it worked today. And I must admit it sounds obvious. But it has to have something to do with the fact that I rooted my phone. So is that true? Can recovery managers only write the images of a nandroid backup when the phone is rooted. I thought the fact that there is a recovery image that is capable of backing up and restoring a system has all necessary rights through its bare existence? Just curious... =)

arminsoyka said:
So tonight I was close to a freak out. I made a Nandroid backup of my CM 6.1.1 system. And then I restored a backup of an old 2.2 stock rom. After that I did a wipe / factory reset thing since I wanted to play with plane untweaked and new stock rom. When I got bord of it I booted into recovery mode via "power + volume down" and tried to restore the CM Rom which it refused to do. One point showed up and then it aborted and said something about "something wrong, nandroid restore doesn't work" - cant remember the exact words. So I thought "**** maybe the backup is corrupt". So I tried another one. Which didn't work either. So I actually ended up trying every single of my 22-ish backups. None of them worked. So instead of having a heart failure I just went to bed and told myself I would deal with it today. So today I wanted to boot into recovery mode so instead of dealing with my broken power button I installed 1-click universal androot and quick boot. I soft rooted the phone (obviously stock roms are not known for its rootedness) and rebooted into recovery mode where my restoration attempt succeeded like it always does. So now I'm curious why it worked today. And I must admit it sounds obvious. But it has to have something to do with the fact that I rooted my phone. So is that true? Can recovery managers only write the images of a nandroid backup when the phone is rooted. I thought the fact that there is a recovery image that is capable of backing up and restoring a system has all necessary rights through its bare existence? Just curious... =)
Click to expand...
Click to collapse
1) Paragraphs...look it up
2) When you reloaded your stock rom you lost custom recovery. That's why you couldn't re-flash your cm backup.

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.

whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery

Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....

send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too

The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....

whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

Bad situation need help fast!

Hi guys I'm caught in a bad situation. I tried to install a ROM but it went bad so I booted into CWM and erased everything including /data and /system as well as /cache and everything else except for /0 amd /clockworkmod. I then proceeded to install another ROM but it went fine until halfway through it quit and went back into CWM. I didn't know what to do so I restarted the phone into the bootloader and just clicked factory reset hoping it would fix something. But it restarted and stayed on the HTC screen that has the development text and copyright warning on the bottom. It got stuck there for quite a while so I restarted the phone again and tried to go back to CWM but now it just flashes briefely before restarting itself to do the same thing over again! Help please I'm scared I might have bricked it

URGENT - Need help with S5570

Hey guys
Samsung Galaxy Mini 5570 is a pretty old device now and definitely not worth to talk about, but It's for my aunt and she said i HAVE to fix it otherwise she will kick my butt.
This is the whole story:
Phone was running a very low android version (it was 2.1 or something) that i could barely install apps on it (Just installed WhatsApp), I decided to upgrade it to a higher version so i could install other applications like Line and Telegram for her, so basically i had to flash CWM file first because it was required, I flashed it using this link:
http://www.droidthunder.com/root-install-clockworkmod-cwm-recovery-samsung-galaxy-minipop-gt-s5570/
They said flash the cwm file and factory reset your phone but i flashed the cwm file and rebooted my phone without factory reset, everything was working fine :good: but i decided to follow the instruction so i rebooted into the recovery mode and factory reseted my phone (by my phone i mean her phone, but i'm gonna say my phone instead) and guess what, it never booted up again. stuck on Samsung logo.
But i could go into the download and recovery mode, so basically i followed this instruction:
http://www.droidthunder.com/update-samsung-galaxy-minipop-gt-s5570-android-4-2-1-cyanogenmod-10-1/
which is from the same guy, I flashed it using recovery mode and flashed gapps too, everything went normal without any errors. So i rebooted my phone and ............
a black screen poped up, I was really worried because i couldn't boot my phone, nor could i go into the recovery or download mode. I don't know if i could or not but the only thing I'm getting right now is a black screen or a backlight.
The only thing that seems to be working is when i hold Power+Volume UP button, my laptop can detect my phone (as Samsung CDMA Technologies) but can not flash anything using Odin, it stucks on "setup connection" message. Nothing else is working, I tried:
Home+power+volume down
Home+power+volume down+volume up
Power+volume down
Power+home
etc
I also tried a hundred different ways like completely uninstalling the drivers (with or without kies) pulling battery out, try those key combination while battery is out and reinsert battery while holding them but nothing is working.
I found this article yesterday which is for unbricking the hard bricked phones, but ADB can not detect my phone:
http://www.engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
Please help me guys, And do not suggest me to take it in Customer Service because i would if i could.
Thanks in advance