Jump to content


Photo

Reboot loop after flashing

- - - - -

  • Please log in to reply
8 replies to this topic

#1
DopT1

DopT1

    Newbie

  • Members
  • Pip
  • 16 posts
  • Gender:Male
  • Location:Schelle
  • Devices:Acer Cloudmobile
Hi guys,
I'm new to this forum, but have been playing around with Android some time. Now I ran into a wall ;) Problems started after failing the official Acer update for JB on EMEA MBSD. Acer couldn't help. It had something to do with my build though.

Smalbandversie: Acer_AVO43_QV153611_S500_1.016.00_EMEA_MBSD


Kernel: 3.0.8+


Imageversie: Acer_AVO43_S500_RV13RC01_EMEA_MBSD


Androidversie: 4.0.4 (ICS)



I've unlocked the bootloader with the tool provided in a previous topic, and it worked ( unlocked true, tampered false). So I flashed CWM and then the trouble started. After booting up, the homescreen background stays black (app icons do appear), then I get a pop up saying "Process system not responding " withe options to wait, rapport, and ok. Whatever option I choose, it reboots after a few seconds. And it keeps on rebooting... I tried the Cirrus ROM from Vache, and the same problem appeared. Lucky I've backed up the system with CWM, but when I restore the same thing happens.
I am able to boot in fastboot, recovery (stock), and CWM via Acer S500 tool 0.3. I was thinking of flashing it with the original firmware with the ADT, but I can't find the version for my build. Any help or links (that work) ?

  • 0

#2
razvankim

razvankim

    Diehard

  • Members
  • PipPipPipPip
  • 409 posts
  • Gender:Male
  • Location:Sibiu
  • Interests:Developing
  • Devices:Samsung Galaxy SIII I9300
  • Twitter:@none
Reinstall the firmware from cwm

  • 0
Cheers | Hit THANKS if I helped you.
razvankim@MoDaCo

#3
BannedHost

BannedHost

    Newbie

  • Members
  • Pip
  • 17 posts
  • Gender:Male
  • Location:Cluj-Napoca
  • Interests:Software testing
  • Devices:Acer Cloudmobile
After wiping data/cache

Edited by BannedHost, 11 June 2013 - 10:26 AM.

  • 1

#4
razvankim

razvankim

    Diehard

  • Members
  • PipPipPipPip
  • 409 posts
  • Gender:Male
  • Location:Sibiu
  • Interests:Developing
  • Devices:Samsung Galaxy SIII I9300
  • Twitter:@none

After wiping data/cache


Thanx!

  • 0
Cheers | Hit THANKS if I helped you.
razvankim@MoDaCo

#5
DopT1

DopT1

    Newbie

  • Members
  • Pip
  • 16 posts
  • Gender:Male
  • Location:Schelle
  • Devices:Acer Cloudmobile
Thx for fast reply,

Where do find that firmware (http://vache-android...1_EMEA_MBSD.zip) doesn't exist anymore?
These where my last steps: Restored backup from CWM, wipe data and cache, wipe dalvic, fixed permissions. But
I still have the reboot problem

  • 0

#6
razvankim

razvankim

    Diehard

  • Members
  • PipPipPipPip
  • 409 posts
  • Gender:Male
  • Location:Sibiu
  • Interests:Developing
  • Devices:Samsung Galaxy SIII I9300
  • Twitter:@none
http://vache-android...mages/EMEA_MBSD


Flash with Acer Download TooL

  • 0
Cheers | Hit THANKS if I helped you.
razvankim@MoDaCo

#7
DopT1

DopT1

    Newbie

  • Members
  • Pip
  • 16 posts
  • Gender:Male
  • Location:Schelle
  • Devices:Acer Cloudmobile
thnx for the link, but when I try that, the ADT says "no bin". Where can I find that?

There are only 3 file present in that archive (set up, eeuusetup and dotnetfix) Can i extract the bin files from the setup maybe?

Edited by DopT1, 11 June 2013 - 11:21 AM.

  • 0

#8
razvankim

razvankim

    Diehard

  • Members
  • PipPipPipPip
  • 409 posts
  • Gender:Male
  • Location:Sibiu
  • Interests:Developing
  • Devices:Samsung Galaxy SIII I9300
  • Twitter:@none

thnx for the link, but when I try that, the ADT says "no bin". Where can I find that?

There are only 3 file present in that archive (set up, eeuusetup and dotnetfix) Can i extract the bin files from the setup maybe?

\


oh..just double click on setup

  • 0
Cheers | Hit THANKS if I helped you.
razvankim@MoDaCo

#9
DopT1

DopT1

    Newbie

  • Members
  • Pip
  • 16 posts
  • Gender:Male
  • Location:Schelle
  • Devices:Acer Cloudmobile
Ok, problem is solved. Here's how I managed it. The main thing with the exe was, due to all the wipes, all settings were lost, including the usb connecting setten in the dev options. I noticed that after wiping the Dalvic, the phone stayed booted just long enough to navigate around briefly (about 10 sec after unlocking the screen post boot. And that the changes were saved to. So, I disabled auto back up by Google ( I read somewhere that that sometimes could cause the process to stop), disabled wifi and 3g, I was able to enable usb debugging too. After that I started the exe, and luckily the phone powered on just long enough for Set up to detect the drivers. After that, the phone went into fastboot, and the new image was flashed. As a bonus, my phone automaticly gave notice of an available update, so once I connected to my wifi, the JB update came in and installed just fine. So...thank you guys for the fast and more importantly, acurate help. I still thinking of rooting though, cause I don't like some apps that came along with the firmware. I should be able to root with the tool from the ru site, right. As far as I understand it is based on the Vache method? Or should I go via cmd with the adb-fastboot method. I only need root, not so much CWM.

  • 1




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users