Well, first off, I screwed up big-time.
I accidentally my whole /system/app folder, so I decided to flash a new ROM.
I already had Clockwork, so I flashed the MonsterDroid 1.1i ROM, but when I rebooted, I was greeted by a bootloop at the Motorola logo.
I managed to install the .zip here (http://forum.xda-developers.com/showthread.php?t=1255198) to the SD card through a reader, but when I attempted to install it through recovery mode (Clockwork mysteriously disappeared), the installation hung after displaying "--installing /sdcard" for a few seconds. All text disappeared from the screen and it started blinking off and on. RSD is unable to detect the phone; please help!
Bump for help, pl0x.
Related
Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
I need help. I downloaded rom manager and superuser apps before i rooted my alltel htc hero. i followed directions and it worked. it rebooted fine, and it was in cyanogonmod, but i realized i didn't have any google apps. then i read that i needed to do a google addon in system recovery as a .zip file. so i found the right google addon file and installed it from my sd card in recovery. the i rebooted. the cyanogonmod 7 comes up, then the "Welcome to android, to begin touch the Android". it stays on that screen for about 5 sec. then reboots, it does this over and over. so i went back into recovery and did a restore. then rebooted, samething. then i read that i needed to flash, but there are no flesh file in recovery. there was when i did the root, but not now. i wiped all data. reinstall, but the samething. can some please help me on this thanks.
I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!
After being away all summer and having somebody else customize my N8013 to their liking, I decided to just go for a clean start with a new ROM. When installing Android Revolution HD 9.0 I made a mistake and can't seem to fix it.
As best I can recall, this is what happened:
Downloaded Android Revolution HD 9.0
I wasn't sure what AROMA was while following the instructions so before the Install from SD Card step I just started wiping lots of stuff in TWRP.
At some point I realized I had no OS and had deleted the image I put on my SD card to install.
Used ADB to push the image back onto the SD card.
Tried to install but it wouldn't do anything (I think I was missing a data partition at this point...not sure).
Downloaded Prerooted UEALH2
Tried flashing that with ODIN...it would just go into a boot loop as somebody else experienced here.
Tried flashing it repeatedly because the above link said, "keep trying."
At some point I flashed CWM recovery again.
Downloaded and pushed Redemption Rom(Nocturnalized)v6.1 onto my SD card via ADB.
Installed via AROMA, it rebooted, it played some music and just sat on a blank screen.
Flashed UEALH2 via ODIN again, it rebooted, played some music and is now stuck on a boot animation of SAMSUNG with blue flashing on and off behind it.
Waited ~10-15 minutes on the SAMSUNG boot animation.
Downloaded latest .tar from TWRP and flashed via ODIN because CWM was gone.
Downloaded Redemption Rom(Nocturnalized)v6.1 again as suggested here and verified MD5 hash.
Pushed Redemption Rom(Nocturnalized)v6.1 via ADB onto SD card again.
TWRP as acting wonky...not responding to touch very well.
Installed Redemption Rom(Nocturnalized)v6.1 again.
It rebooted, played some music, and sat on a blank screen...
I seriously spent all of my free time yesterday and an hour this morning on this. If somebody could suggest a fix-all solution that'll bring me back to a usable, stock state I would be very appreciative. And provide a link to whatever you're suggesting? In my searches yesterday I saw a number of broken links and references to things that either didn't exist any more or I couldn't find =\
sonofdays said:
After being away all summer and having somebody else customize my N8013 to their liking, I decided to just go for a clean start with a new ROM. When installing Android Revolution HD 9.0 I made a mistake and can't seem to fix it.
As best I can recall, this is what happened:
Downloaded Android Revolution HD 9.0
I wasn't sure what AROMA was while following the instructions so before the Install from SD Card step I just started wiping lots of stuff in TWRP.
At some point I realized I had no OS and had deleted the image I put on my SD card to install.
Used ADB to push the image back onto the SD card.
Tried to install but it wouldn't do anything (I think I was missing a data partition at this point...not sure).
Downloaded Prerooted UEALH2
Tried flashing that with ODIN...it would just go into a boot loop as somebody else experienced here.
Tried flashing it repeatedly because the above link said, "keep trying."
At some point I flashed CWM recovery again.
Downloaded and pushed Redemption Rom(Nocturnalized)v6.1 onto my SD card via ADB.
Installed via AROMA, it rebooted, it played some music and just sat on a blank screen.
Flashed UEALH2 via ODIN again, it rebooted, played some music and is now stuck on a boot animation of SAMSUNG with blue flashing on and off behind it.
Waited ~10-15 minutes on the SAMSUNG boot animation.
Downloaded latest .tar from TWRP and flashed via ODIN because CWM was gone.
Downloaded Redemption Rom(Nocturnalized)v6.1 again as suggested here and verified MD5 hash.
Pushed Redemption Rom(Nocturnalized)v6.1 via ADB onto SD card again.
TWRP as acting wonky...not responding to touch very well.
Installed Redemption Rom(Nocturnalized)v6.1 again.
It rebooted, played some music, and sat on a blank screen...
I seriously spent all of my free time yesterday and an hour this morning on this. If somebody could suggest a fix-all solution that'll bring me back to a usable, stock state I would be very appreciative. And provide a link to whatever you're suggesting? In my searches yesterday I saw a number of broken links and references to things that either didn't exist any more or I couldn't find =\
Click to expand...
Click to collapse
Try the following :
1. Flash a stock rom from sammobile.com through odin.
2. Probably you will get a bootloop after rebooting.
3. Flash Philz Recovery through odin. http://forum.xda-developers.com/showthread.php?t=2202714
4. Get into CWM , wipe data, cache & dalvik & reboot.
sonofdays said:
After being away all summer and having somebody else customize my N8013 to their liking, I decided to just go for a clean start with a new ROM. When installing Android Revolution HD 9.0 I made a mistake and can't seem to fix it.
As best I can recall, this is what happened:
Downloaded Android Revolution HD 9.0
I wasn't sure what AROMA was while following the instructions so before the Install from SD Card step I just started wiping lots of stuff in TWRP.
At some point I realized I had no OS and had deleted the image I put on my SD card to install.
Used ADB to push the image back onto the SD card.
Tried to install but it wouldn't do anything (I think I was missing a data partition at this point...not sure).
Downloaded Prerooted UEALH2
Tried flashing that with ODIN...it would just go into a boot loop as somebody else experienced here.
Tried flashing it repeatedly because the above link said, "keep trying."
At some point I flashed CWM recovery again.
Downloaded and pushed Redemption Rom(Nocturnalized)v6.1 onto my SD card via ADB.
Installed via AROMA, it rebooted, it played some music and just sat on a blank screen.
Flashed UEALH2 via ODIN again, it rebooted, played some music and is now stuck on a boot animation of SAMSUNG with blue flashing on and off behind it.
Waited ~10-15 minutes on the SAMSUNG boot animation.
Downloaded latest .tar from TWRP and flashed via ODIN because CWM was gone.
Downloaded Redemption Rom(Nocturnalized)v6.1 again as suggested here and verified MD5 hash.
Pushed Redemption Rom(Nocturnalized)v6.1 via ADB onto SD card again.
TWRP as acting wonky...not responding to touch very well.
Installed Redemption Rom(Nocturnalized)v6.1 again.
It rebooted, played some music, and sat on a blank screen...
I seriously spent all of my free time yesterday and an hour this morning on this. If somebody could suggest a fix-all solution that'll bring me back to a usable, stock state I would be very appreciative. And provide a link to whatever you're suggesting? In my searches yesterday I saw a number of broken links and references to things that either didn't exist any more or I couldn't find =\
Click to expand...
Click to collapse
Without knowing exactly what you deleted it could be hard to figure out.
If you can still get into odin mode, have you try to flash back to a stock firmware? How to directions here. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/ The video within the link can be helpful to review the steps before and durning the flash process.
.
.
It's working better, now. Both of your suggestions ended up at the same files. Before I tried the oldest, N8013UEALI3, because it was most familiar, and it didn't work. The most recent, N8013UEUCMD3, did the trick.
Anyway, what's the difference between the back of my Note 10.1 Wifi saying GT-N8013EA and these files? How are they named? The listed carrier for them says
I have a TV110 (Amlogic S805, 1gb/8gb) Android TV Box. I was trying to replace the stock ROM with Openelec v5.0.8 from Kerber. The update went fine until it rebooted to launch Openelec then it hung at the Openelec logo for over an hour. I thought the box was hung so I removed power and rebooted. It hung again in the same place so I decided to use the reset button to launch recovery. I must have cycled power too quickly because it would only show the boot logo and would go no further. Something was seriously wrong with the box.
I created a bootup SD card with TWRP recovery on it. I booted up into TWRP 2.8.6 without any issues but could not restore any of the partitions. TWRP was getting errors trying to mount all the partitions. I figured I could go back to stock (I have a NAND backup). When I try to wipe or restore it fails because the partitions are not mounted. I tried to install the old firmware using the install from TWRP and I get "Error executing updater binary in zip".
At this point I am stumped. What do I do next?? How do I get my box bootable again?? Can I somehow re-create the partitions??
Any help would be appreciated.