Database Info

Unable to restore after failed update

I just updated to EOS 156 via goo manager (and latest gapps) backed up before flashing via clockwork
Something went wrong on update and now tablet boots but when it gets to lock screen I enter pattern and it just freezes (I get a popup after a while system is not responding and to wait or FC)
So rebooted into clockwork to restore and it came up no files found! - Had a look just via "flash a zip" and it seems directory structure has changed and root now has just 3 folder... '0'. 'legacy' & 'obb', going to '0' shows my normal root where I can navigate to clockwork dir and shows all my backups but no way of manually choosing where to restore from
Tried flashing EOS 155 again and it just refuses to boot and sits on logo, reflashed 156 and again same issue of just freezing on lock screen
USB mount in clockwork dont seem to work either just pauses for a few secs and takes me back to front screen so no way of pulling any data off or putting a new rom on
Any ideas?

same issue
ViaraiX said:
I just updated to EOS 156 via goo manager (and latest gapps) backed up before flashing via clockwork
Something went wrong on update and now tablet boots but when it gets to lock screen I enter pattern and it just freezes (I get a popup after a while system is not responding and to wait or FC)
So rebooted into clockwork to restore and it came up no files found! - Had a look just via "flash a zip" and it seems directory structure has changed and root now has just 3 folder... '0'. 'legacy' & 'obb', going to '0' shows my normal root where I can navigate to clockwork dir and shows all my backups but no way of manually choosing where to restore from
Tried flashing EOS 155 again and it just refuses to boot and sits on logo, reflashed 156 and again same issue of just freezing on lock screen
USB mount in clockwork dont seem to work either just pauses for a few secs and takes me back to front screen so no way of pulling any data off or putting a new rom on
Any ideas?
Click to expand...
Click to collapse
I am having the same issue. I cannot flash back to anything before 156...

Spent ages sorting it in the end I I reinstalled 155 and factory reset once booked moved old backups back to normal dir then restored that way
Finally got it working again after hours so sticking with 155 for now

same issue
ViaraiX said:
Spent ages sorting it in the end I I reinstalled 155 and factory reset once booked moved old backups back to normal dir then restored that way
Finally got it working again after hours so sticking with 155 for now
Click to expand...
Click to collapse
Would you be kind enough to list out step by step what you did? I am unable to get back to 155. It hangs at team eos logo with anything but 156. I did a factory reset etc. really weird. I also cannot add my gmail account to 156, don't have play store app, but when i go to store via browser, it thinks all of my apps are installed but they aren't. i haven't seen this before at all. any help would be GREATLY appreciated!

HTC one V bricked?

Last night, I messed up with my android. I am not able to figure out what went wrong
So here is exactly what I had been doing:
1. My phone is already unlocked.
2. I had root my phone by installing "r1-primo-superboot" ( I had used the gsm version)
3. Next, I had flashed a recovery image using fastboot.
4. Installed "Blue Sense". Everything was going well. MADE A NANDROID BACKUP.
5. After an hour, tried to install CM10. Didn't work. Get's stuck in the logo screen of CM10.
6. So flashed "hellboy.img"
7. Now, CM10 gets installed. But gets error notifications like "your phone has stopped". There is no option for text or call or settings.
8. Now I try to go back to "Blue sense" through RECOVERY but, it doesn't work. I'm stuck.
IS THE PROBLEM DUE TO FLASHING OF TWO DIFFERENT .IMG FILES? Please help. I am a noob.

abhilekh619 said:
Last night, I messed up with my android. I am not able to figure out what went wrong
So here is exactly what I had been doing:
1. My phone is already unlocked.
2. I had root my phone by installing "r1-primo-superboot" ( I had used the gsm version)
3. Next, I had flashed a recovery image using fastboot.
4. Installed "Blue Sense". Everything was going well. MADE A NANDROID BACKUP.
5. After an hour, tried to install CM10. Didn't work. Get's stuck in the logo screen of CM10.
6. So flashed "hellboy.img"
7. Now, CM10 gets installed. But gets error notifications like "your phone has stopped". There is no option for text or call or settings.
8. Now I try to go back to "Blue sense" through RECOVERY but, it doesn't work. I'm stuck.
IS THE PROBLEM DUE TO FLASHING OF TWO DIFFERENT .IMG FILES? Please help. I am a noob.
Click to expand...
Click to collapse
Here is solution , don't forgot to hit thanks
:: youtube . com/watch?v=nHzmGny6mLA

abhilekh619 said:
Last night, I messed up with my android. I am not able to figure out what went wrong
So here is exactly what I had been doing:
1. My phone is already unlocked.
2. I had root my phone by installing "r1-primo-superboot" ( I had used the gsm version)
3. Next, I had flashed a recovery image using fastboot.
4. Installed "Blue Sense". Everything was going well. MADE A NANDROID BACKUP.
5. After an hour, tried to install CM10. Didn't work. Get's stuck in the logo screen of CM10.
6. So flashed "hellboy.img"
7. Now, CM10 gets installed. But gets error notifications like "your phone has stopped". There is no option for text or call or settings.
8. Now I try to go back to "Blue sense" through RECOVERY but, it doesn't work. I'm stuck.
IS THE PROBLEM DUE TO FLASHING OF TWO DIFFERENT .IMG FILES? Please help. I am a noob.
Click to expand...
Click to collapse
i am having same exact problem in almost same scenario, what did you do to restore your phone back to normal ?

Am I going to have to send it in to Samsung for reflash?

I hadn't touched my tab for a couple weeks since I only really use it in my car as a GPS and Entertainment center but when I grabbed it to charge it up, it was completed drained. No problem here since this has happened before and I'd just charge it up. So I boot it after the full recharge and it's stuck on the Samsung Galaxy Tab logo. After a little while I check it again and I'm like, "Crap, it's bricked. I'll need to reset it with Odin."
I proceed with Odin and nothing. It's still bricked. I do a factory reset and this is where I notice my big problem. When I do a factory reset or reboot I get
E:Can't open /data/log/recovery.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernel_log.txt
I tried reflashing the kernel, pit and firmware and I'm getting nowhere. What gives?

try removing the SD card and see if it boots up.

DigitalMD said:
try removing the SD card and see if it boots up.
Click to expand...
Click to collapse
Still no go but this did give me an idea. I just tried a simple reboot from recovery WITHOUT the SD card and got the error:
E:Failed to mount /sdcard
E: is the SDcard so I will create the directory with the files I mentioned above. I found the files on a different thread regarding a Samsung Galaxy phone. This may work.
I'm also going to try another flash without the SD installed to see if I have any luck there.
Thanks.

Issue is fixed
I decided to reflash while the SD card was removed and it got passed the initial splash screen. It was stuck at some wierd lock screen asking for a password. I went into recovery to do a wipe and factory reset and that brought the tablet back to life on reboot.
All is good again.

[Q] Boot-loop on failed CM install, please help!

Hi friends,
So I was running CyanogenMod 10.1.3 on my S3 and decided to update to the CM 10.2 snapshot that was available for download through the settings page. After messing around with it a bit, I decided I didn't like it and re-installed 10.1.3 through the same page. When it came back up, the CyanogenMod logo just kept turning and turning. I tried to re-install the CM 10.1 .zip file I had on the phone, but Clockworkmod couldn't find it. I also tried to restore to a backup, but again, CWM couldn't find any.
As I see it, all I need to do is get a new CM .zip onto the phone that I can flash from recovery. I downloaded adb for this purpose, but can't get it to open on my computer (Windows 7 x64). So, can anyone tell me another way to get the .zip onto the phone?
I greatly appreciate any help.

berichardson13 said:
Hi friends,
So I was running CyanogenMod 10.1.3 on my S3 and decided to update to the CM 10.2 snapshot that was available for download through the settings page. After messing around with it a bit, I decided I didn't like it and re-installed 10.1.3 through the same page. When it came back up, the CyanogenMod logo just kept turning and turning. I tried to re-install the CM 10.1 .zip file I had on the phone, but Clockworkmod couldn't find it. I also tried to restore to a backup, but again, CWM couldn't find any.
As I see it, all I need to do is get a new CM .zip onto the phone that I can flash from recovery. I downloaded adb for this purpose, but can't get it to open on my computer (Windows 7 x64). So, can anyone tell me another way to get the .zip onto the phone?
I greatly appreciate any help.
Click to expand...
Click to collapse
Hey it sounds like you have a couple issues there, not sure where to start. One thing I can help with is getting adb on the Win7 PC. What you need to do is download the Android SDK at http://developer.android.com/sdk/index.html. Once the Android SDK is on your machine then use that to get the Android Platform-tools. ADB.exe is part of the platform tools. I hope that helps.

did you save the CM .zip file to your phone's internal storage or an SD card? if internal, it may have been erased when you flashed back to CM 10.1. if you put it on your SD card, try reinstalling the SD card and reboot. i've had issues with my S3 where the SD card would come unseated when i put the back cover back on.
also, did you do a wipe when you reinstalled CM? sometimes that helps get you out of bootloop (but it erases all of your data, so hopefully you did a backup).
berichardson13 said:
Hi friends,
So I was running CyanogenMod 10.1.3 on my S3 and decided to update to the CM 10.2 snapshot that was available for download through the settings page. After messing around with it a bit, I decided I didn't like it and re-installed 10.1.3 through the same page. When it came back up, the CyanogenMod logo just kept turning and turning. I tried to re-install the CM 10.1 .zip file I had on the phone, but Clockworkmod couldn't find it. I also tried to restore to a backup, but again, CWM couldn't find any.
As I see it, all I need to do is get a new CM .zip onto the phone that I can flash from recovery. I downloaded adb for this purpose, but can't get it to open on my computer (Windows 7 x64). So, can anyone tell me another way to get the .zip onto the phone?
I greatly appreciate any help.
Click to expand...
Click to collapse

I've had bootloop problems with cm after trying to downgrade from cm10.2. Wiping data, cache, etc didnt help, it still boot looped for me. A TWRP backup was the only thing that saved me. I have used this to get out of a soft brick before, maybe try that as a last resort? Good luck, and i recommend using twrp recovery instead of cwm, it has given me problems before. Good luck!
dkh7m said:
did you save the CM .zip file to your phone's internal storage or an SD card? if internal, it may have been erased when you flashed back to CM 10.1. if you put it on your SD card, try reinstalling the SD card and reboot. i've had issues with my S3 where the SD card would come unseated when i put the back cover back on.
also, did you do a wipe when you reinstalled CM? sometimes that helps get you out of bootloop (but it erases all of your data, so hopefully you did a backup).
Click to expand...
Click to collapse

[Q] Stuck in bootloop after Cyanogenmod install error

Hi folks,
This evening I decided to install Cyanogenmod on my Moto G. All seemed to go fine until I started getting "Unfortunately, System UI has stopped" errors that meant I couldn't even get into any of the phone's menus. I tried to reset the phone to reinstall the ROM, but got stuck in a boot-loop where the phone won't boot to allow my PC to see it, so I can't copy the necessary files to it to re-flash the ROM. I also can't push them with ADB for the same reason.
I am stuck! Please offer any advice. Thanks!

evh5150ni said:
Hi folks,
This evening I decided to install Cyanogenmod on my Moto G. All seemed to go fine until I started getting "Unfortunately, System UI has stopped" errors that meant I couldn't even get into any of the phone's menus. I tried to reset the phone to reinstall the ROM, but got stuck in a boot-loop where the phone won't boot to allow my PC to see it, so I can't copy the necessary files to it to re-flash the ROM. I also can't push them with ADB for the same reason.
I am stuck! Please offer any advice. Thanks!
Click to expand...
Click to collapse
did you install a custom theme? does your computer recognize your phone when in recovery?

Just a failed installation of Cyanogenmod. Windows can recognise the phone but gives an error when installing the driver, meaning I can't copy anything to it to re-flash.
On the phone itself, I can get into TWRP in recovery mode, but I don't know how to get files onto it to re-flash.

evh5150ni said:
Just a failed installation of Cyanogenmod. Windows can recognise the phone but gives an error when installing the driver, meaning I can't copy anything to it to re-flash.
On the phone itself, I can get into TWRP in recovery mode, but I don't know how to get files onto it to re-flash.
Click to expand...
Click to collapse
Go to my profile, and I started a thread about this. Go to "started by".
My work: SmoothGKernel for the Moto G, and remember always hit the thanks button if anyone helped.