Hi folks,
Im new to this forum and i might have solved the random reboot problem. Mine is working fine for the last two hours and normally it would reboot at least twice every hour. Still have to keep monitoring though.
Like most of you, i have updated the prime to ICS OTA and suffered from random reboot ever since. Due to the quality of primes wifi, i though perhaps some system files got corrupted while downloading.
I downloaded the same firmware from asus' website on my pc and performed the update manually using a SD card. Prime allows you to install a firmware version that is already installed. Problems seems to be solved now......
Go to: Service.asus.com/TF201_fwupdate. You will find the instructions there.. No OTA updates for me anymore!
FYI, for rooted users, this will not only unroot, but also break Voodoo OTA rootkeeper. Although there are ways to root even the newest Asus firmwares, this may not hold true in the future.
ryanwk1982 said:
Hi folks,
Im new to this forum and i might have solved the random reboot problem. Mine is working fine for the last two hours and normally it would reboot at least twice every hour. Still have to keep monitoring though.
Like most of you, i have updated the prime to ICS OTA and suffered from random reboot ever since. Due to the quality of primes wifi, i though perhaps some system files got corrupted while downloading.
I downloaded the same firmware from asus' website on my pc and performed the update manually using a SD card. Prime allows you to install a firmware version that is already installed. Problems seems to be solved now......
Go to: Service.asus.com/TF201_fwupdate. You will find the instructions there.. No OTA updates for me anymore!
Click to expand...
Click to collapse
....... yet another victim to thinks the lockups are gone..... give it 48 hours it will lockup by then.
PrimeTimeBro said:
....... yet another victim to thinks the lockups are gone..... give it 48 hours it will lockup by then.
Click to expand...
Click to collapse
Oh ye of little faith.
i have follow the instruction, but still cannot install a fireware.
is it just dl the fireware> unzip> put the unzip files META-INF folder and blob file to SD card> plug in sd card and switch on the TF201
after start, it will show the triangle in the notification bar.... but mine, didn't show the triangle.
Is there any step i'm missing?
Pls help, thx
Just tried this. It lasted 3 minutes before rebooting.
toronto929 said:
i have follow the instruction, but still cannot install a fireware.
is it just dl the fireware> unzip> put the unzip files META-INF folder and blob file to SD card> plug in sd card and switch on the TF201
after start, it will show the triangle in the notification bar.... but mine, didn't show the triangle.
Is there any step i'm missing?
Pls help, thx
Click to expand...
Click to collapse
Just unzip to the upmost level of the SD card. No need to even look at what files it includes. But yes, just download to your desktop (PC), then right-click and choose extract files, then select your SD card.
Mubble said:
Just tried this. It lasted 3 minutes before rebooting.
Just unzip to the upmost level of the SD card. No need to even look at what files it includes. But yes, just download to your desktop (PC), then right-click and choose extract files, then select your SD card.
Click to expand...
Click to collapse
will it show the triangle immediately after rebooting?
toronto929 said:
will it show the triangle immediately after rebooting?
Click to expand...
Click to collapse
Mine did yes. Double check its the right firmware file.
Mubble said:
Mine did yes. Double chek its the right firmware file.
Click to expand...
Click to collapse
My version is TW_epad so i dl the TW version V4.2.11, rite?
I've already had my prime for over a month and never had a single lock up or reboot. Am I the only one?
rand4ll said:
I've already had my prime for over a month and never had a single lock up or reboot. Am I the only one?
Click to expand...
Click to collapse
No you are not the only one the majority of Primes do not have the lockup issue with ICS........
Done it finally, but do I need to restore factory again?
I was advsied by Asus to return mine to BB and get another unit...second unit has worked flawlessly in every aspect; no rebooting, wfi issues, GPS, etc...yet. Keeping my fingers crossed for continued success as this is a terrific piece of electronics!!!
toronto929 said:
Done it finally, but do I need to restore factory again?
Click to expand...
Click to collapse
from what ive seen, it is recommended to reset before and after you manually apply
FIREMANMIKE said:
I was advsied by Asus to return mine to BB and get another unit...second unit has worked flawlessly in every aspect; no rebooting, wfi issues, GPS, etc...yet. Keeping my fingers crossed for continued success as this is a terrific piece of electronics!!!
Click to expand...
Click to collapse
UPDATE: STILL WORKING GREAT...NEW UNIT NO REBOOTING EVEN AFTER ICS UPDATE. I AM HAVING HOWEVER THE GPS ISSUES AND NOT PICKING UP SAT;S...WHAT THE FIX FOR THIS, ANYONE GET IT YET???
Related
Ok, so last night my phone downloaded the update (guessing Gingerbread). I'm still running 2.2.1 on my Thunderbolt, as I was out of the country for the past few months. I caught the phone before it completed the installation and thought that if I removed the PG05IMG.zip file from the sd card, that would prevent it from being able to install the update. I turned the phone back on and it began to attempt to install the update again. I would like to flash a new ROM to the phone (as I was simply rooted without a custom ROM before) so that I am running 2.3+ but I don't want to have to re-root the phone. I would like to be able to back everything up before I flash a new ROM. How do I prevent the phone from installing the OTA update that was inadvertently downloaded last night , which will unroot my phone??
Please help! Thank you
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Someone fee free to correct me, but if you flash the CWM recovery it will prevent the update from happening?
Essentially, I just use the phone for wireless tether, so that's mainly why I root. Doubt that changes much of anything...
hallstevenson said:
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Click to expand...
Click to collapse
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
tomgillotti said:
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Click to expand...
Click to collapse
That's a common problem as I recall from a few weeks back. I saw threads about it but never read them as I wasn't affected. I don't know if it's a dead-end or easily fixed or complicated to fix...
Sent from my ADR6400L using XDA App
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
tomgillotti said:
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
Click to expand...
Click to collapse
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Thread moved to Q & A
tomgillotti said:
Any thoughts on how to prevent VZW from pushing this update from now on?
Click to expand...
Click to collapse
Install a non-stock ROM. Don't worry, you can get Sense-based ones that won't be anything "new".
It appears that VZW will eventually force the update so there's no way that I'm aware of to stop it while running stock (even rooted stock).
tomgillotti said:
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Click to expand...
Click to collapse
Flash a ROM that has the update. There are a few around here that are 2.11.605.5 that you flash in Recovery so that it'll stop bugging you to update. Just pick one that is already rooted. You can do a backup of your currrent rom, flash the 2.11.605.5 then restore your data and your all set....
jv
There are a couple threads on preventing ota updates. A quick search will tell you what file to rename and how to.
Sent from my infected thunderbolt.
i modified some files and now my prime wont boot up. it satys on the asus loading screen. i am on locked bootloader rooted .14. how do i replace the files with adb? i made a copy of the files i made and renamed them wit .bak at the end. i tried holding power+vol down and then vol down and got an android with a red triangle. i then tried adb shell from the command prompt but it said device not found. can some one help? thanks.
no one? i guess ill just go to asus for help.
newvet said:
I had been fighting with the same exact problem for the past 2 days!
I just fixed it by downloading the .21 firmware from Asus and renaming the extracted file EP201_SDUPDATE.zip. Manual update method from http://forum.xda-developers.com/showthread.php?t=1570696&page=13 post 128.
I am now up and running and if I can get adb going again I will do the downgrade and root. I probably will not mess with the build.prop for a while. Good Luck
Click to expand...
Click to collapse
LTLFTCer said:
Thanks. I will try that. You just stuck the file on a microsd and booted into stock recovery?
Click to expand...
Click to collapse
newvet said:
Exactly.
You probably know already but remember to unzip the downloaded file and rename the zip within.
Click to expand...
Click to collapse
Give this a try. Worked for us
did this delete your camera pics and videos? i did that last time and i lost my pics. but it was probably because i had done a factory reset before i tried this thinking that would fix it. but this shouldnt touch those files because its like an update right?
I can`t say 100% because I also did a factory wipe first. But I`m pretty certain it is just a manual update and you should be ok.
thanks alot bro. it worked and my stuff is still there.
Glad it all worked out! Enjoy
newvet said:
Give this a try. Worked for us
Click to expand...
Click to collapse
I tried this method by renaming the zip from within the extracted file and put in on a microsd card then i rebooted into system recovery and got the android with the red ex, so i rebooted but it goes back to the black screen after the epad logo and never forces the update. Any suggestions?
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Gabewalters said:
So I updated to the .28 update this morning, and it all went good. then it got to the stage of booting up, and it doesnt go any farther than the Asus logo with the spinning wheel underneath. I tried doing a reboot by holding the power button but nothing helps. I am rooted on the .21 update and not unlocked. Anyone help? I dont want to have to RMA. Thank you so much in advance!
Click to expand...
Click to collapse
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
shreddintyres said:
Try hitting the factory reset or use one of the brick fixes detailed in the dev section stickies.
By chance had you modified any system files or were you bone stock with just root access? i ask this because i upgraded to .28 with no problems with root.
Click to expand...
Click to collapse
I have only edited one /system/app file and it was to paste the Svoice app to see if it would work. I am pretty sure I deleted it though. Would this be why? And what do you mean by hitting the factory reset?
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
tkdsl said:
I am in the same boat the update killed My Prime.
I tried the volume down restart no luck gets stuck on ASUS logo
I tried the Volume down and delete user data and restart no luck gets stuck on ASUS logo
any help
Click to expand...
Click to collapse
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
I checked the Sticky on the Dev Section and they don't cover this type of damage.
This means I have to send my prime to ASUS. dang it.
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Gabewalters said:
I am glad Im not the only one. I know how you feel! I hope we can get this thing back up and running. :-|
Click to expand...
Click to collapse
I tried restarting with the recovery kernel and I get an android logo laying down with red exclamation mark. not sure what that means how to fix that yet.
---------- Post added at 11:52 AM ---------- Previous post was at 11:44 AM ----------
MRCANNADY said:
Guys, the update didn't brick your Primes, sometimes fooling around with the system files can have a negative effect. If the update was no good, ALL of our Primes would be bricked, not just some.
Good luck though!
Click to expand...
Click to collapse
the only thing is, I did not change system files on my prime, I kept it stock. and I have received updates and updated them before. I just found out that the repair center for ASUS in Los Angeles does not service Primes.
The update may have bricked your prime. Although updates succeed with some devices they can fail with others. There is a long history of such issues across platforms.
Sent from my Transformer Prime TF201 using Tapatalk 2
try a hard reset.... insert a paperclip into the hole by the SD card to reset.
If not ping Gary Key or the other Rep, I forget the name and see if they can have an Asus tech offer some other solution. If not RMA it is..
just dont say its rooted
good luck!
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
sledgie said:
I just wanted to have a little post for those of you like me that may have tried updating after downloading the .28 OTA update, then the Prime freezing on the Asus Splash Screen and not rebooting...I found the solution after finally downloading the update this morning from Asus' TW site.
I only have the Prime as my computer and I have an Android phone. No PC for me - was going to try to use a friends last night to get into ADB but it just wasn't happening.
So for me - this is what I had to do.
If after your prime reboots you are still stuck on your asus splash screen, and nothing will get it to boot up - do this:
You must know your Prime's version of the update.
Goto ftp://ftp.asus.com.tw/pub/ASUS/EeePAD/TF201/ or check cky2000's thread right here
forum.xda-developers.com/showthread.php?t=1429873
Download the **COMPATIBLE** update of .28 (I tried .21 plenty of times - .21 would not update my Prime)
If on an Android phone (like I was) goto ES File Explorer and open the **UpdateLauncher.zip file
It should say something like **_epad-user.9.4.2.28.zip
Extract the file to the root directory of your microSD card
Now, goto your microSD card
rename the **_epad-user.9.4.2.28.zip to
EP201_SDUPDATE
**don't rewrite the extension so that it's EP201_SDUPDATE.zip.zip, ES File explorer will only allow you to rename the name, not file extension**
You should now have EP201_SDUPDATE.zip on your microsd
**make sure you charged your prime at least 30 min if it turned off previously**
Put microsd in your Prime
Hold the Volume Down button and the Power Button until it resets and something is written at the top asking if you want to boot into a certain mode press volume up.
Immediately press Volume Up. Make sure Microsd with EP201_UPDATE.zip is in Prime.
It will start to switch to the Android Operating Mode screen with the Android lying sideways with some nuclear fission animation going on.
Blue status bar should start within 3 minutes.
Reboot and rewrite should take approximately 5-10 minutes. When done, your About should show .28 update. Hope this helps anyone who was in the same boat as me. I believe my Prime was bricked a certain way - not sure how.
Click to expand...
Click to collapse
Sent from my VS910 4G using Tapatalk 2
I had the same problem. My Prime is on its way to Asus. Does anyone know what their procedure in these cases? Do they reinstall the system and ship the tablet back or is there more to it? I take it this is all under warranty since the tablets were not unlocked?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I don't need it, but it's nice to know with stock recovery. I thought recovery was just missing.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks! I had same issue, just fixed it using this guide! Many thanks to author too!
It's Alive and thank you again for the post and the link, I was really worried about the
If anyone else runs across this thread, you guys don't give up so early. If your prime shows a sign of power, it's fixable without the prime leaving your house.
Congratulations to the guys who are now back up and running. That's amazing. I know how scary that can be to brick an expensive device.
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
Dont you need to have to be unlocked to be able to install .zips from recovery?
Bait-Fish said:
Here's some info from another thread where sledgie recovered from a brick updating to .28 Hopefully this could help some of you.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Gabewalters said:
I dont know what you mean by downloading the compatible version for my prime. Mind helping me out?
Click to expand...
Click to collapse
He likely means make sure you download the proper sku version. For example, if you have a u.s. prime, can be seen in settings and about tablet info, then you need to download the version for u.s. primes. If you ww. Then you need to download version for ww. If you De. Version, then you need to download De version for your prime.
So I downloaded the right version but when you unzip it, you get a folder, not another zip file. Any help?
EDIT: Figured it out. Apparently unzipping and then moving to the sd card isnt the same as moving to the sd card and unzipping.
Hello. I'm annoyed
I rooted to get rid of problems... So
I followed these tasks: http://forum.xda-developers.com/showthread.php?t=1653566 and the root worked for a few days - then moved into a boot loop.... how/why... I don't know.
Ive tried many of the different .aos files to find a correct one for my 101g9 250gb, but I still can't get it out of the loop.
This is where I've been getting the different Aos files: http://forum.xda-developers.com/showthread.php?t=1468925
I get 2 different results 1)error 207 (update failed) or 2) boot loop.
One stange thing did happen once - It's managed to reload the android installer, I selected a language, then it crashed again. Of course I tried the same thing again, but it never got past the boot loop again.
After 2 weeks of trying, I'd like some help.
I always have it plugged in. It's not the battery. It's the HDD model and I don't know exactly which version came with the device. I think 4.0.25.. not 100% sure
Please help
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Djirin said:
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Click to expand...
Click to collapse
Thanks for your help, but no luck- that didn't work. I'm sure I lost all my data a long time ago with the amount of reformats I've done. What I'm curious about is, can the tablet actually become a brick just by using these rooted firmwares? I'm assuming that it's fine and that I just have to 'crack to code' to installing the right firmware in the right order.....
I'm still curious if anyone else has had this problem..
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Djirin said:
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Click to expand...
Click to collapse
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
pwnami said:
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
Click to expand...
Click to collapse
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
julle131 said:
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
Click to expand...
Click to collapse
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
pwnami said:
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
Click to expand...
Click to collapse
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Code 207 is issued by aosparser when the .aos upgrade file doesn't
pass the signature check.
...
There's more bad news... If the genuine original .aos files are also
giving the same error it means the signing keystore may also have been
damaged.
Click to expand...
Click to collapse
Of course, this is for Archos 5, so hopefully this is not the case.
julle131 said:
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Of course, this is for Archos 5, so hopefully this is not the case.
Click to expand...
Click to collapse
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
pwnami said:
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
Click to expand...
Click to collapse
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
So, do you know if I can access/use ADB on a win7 pc when the archos doesn't have an aos on it?
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
noaddress said:
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
Click to expand...
Click to collapse
I gave up on this 6 months ago. but I turned it on 2 days ago and it magically worked.... Now, it's back in a bootloop again. Everything was working for two days, except sometimes the HDD wasn't reading the files, or the system wasn't detecting the HDD...
Could the HDD be damaged? If so, is there a way to check if it is (I was thinking about the ssd option)
Hi guys,
I've been using my Sola for over a year now and I like the phone, i got the CM9 build from freeXperia on it (FXP 210 CM 9 PEPPER) with cwm on it and loved it.
Two weeks ago trouble began when the phone was very unreliable, it rebooted several times a day, sometimes I noticed that the phone got very warm when rebooting.
I found out that there was no diskspace left, so I deleted some of the playlists on Spotify that I downloaded and that gave me back about 2 gb of internal room.
Since yesterday some processes where quitting and this happened a couple of times (it was the google media process), this morning after being on the adapter for the night the problem was still there. So I rebooted the phone (normal reboot) and then the trouble really kicked in.
When I boot now I see a message stating "Android is being updated, starting apps" then I see my normal lockscreen and the errors start rollling in.
The only errors I can see are the "android.phone process stopped working" and "NFC service stopped". When I press close on those they keep coming back, so fast I cant't even get past my lockscreen anymore.
On the phone is some very critical data to me, I have to restore that data (its in a encrypted app database). As long as I can save that data and restore it to use when the android/app is restored I'm fine.
Can someone give me advise on how to continue?
**bump, I really need my phone
VeldMuijz said:
**bump, I really need my phone
Click to expand...
Click to collapse
Bump! Getting desperate here...
VeldMuijz said:
Bump! Getting desperate here...
Click to expand...
Click to collapse
Where is that data located? If it's on internal memory in it's own directory it will remain intact if you repair/flash firmware.
EDIT: some other thoughts, try to remove the SIM or switch to airplain mode.
I'm not 100% percent sure where it is located, It's on the internal memory but I'm not sure if where it is exactly. It's a database of an app.
Won't I lose all my files on reflash? Reflash can be done with fastboot right? And I should reflash the firmware (kernel?)? Not the rom itself?
Already tried rebooting with SIM and sdcard out, no luck though.
No luck on connecting to ADB, I tried but USB debugging is turned off and my drivers seem to let me down... I can get connect to fastboot
Other ideas?
VeldMuijz said:
I'm not 100% percent sure where it is located, It's on the internal memory but I'm not sure if where it is exactly. It's a database of an app.
Won't I lose all my files on reflash? Reflash can be done with fastboot right? And I should reflash the firmware (kernel?)? Not the rom itself?
Already tried rebooting with SIM and sdcard out, no luck though.
No luck on connecting to ADB, I tried but USB debugging is turned off and my drivers seem to let me down... I can get connect to fastboot
Other ideas?
Click to expand...
Click to collapse
Too bad USB debugging is off.
If database is on device memory than it will be lost if you wipe data on flash. If you don't wipe data you may still have those errors, but you can take your chances and try without wiping data.
Yes with flashtool, do you have the FTF file for the firmware you are currently using?
Is it tooted and have CWM on it?
I don't have the FTF anymore, but I know where to find it.
Luckily I have CWM on it.
Do I have to reflash with the zip or just run the update?
VeldMuijz said:
I don't have the FTF anymore, but I know where to find it.
Luckily I have CWM on it.
Do I have to reflash with the zip or just run the update?
Click to expand...
Click to collapse
I think best is to make your own FTF.
Start repair with PC Companion, and when it finish downloading the files and ask to shut down the phone, stop and create the FTF as explained here.
The FTF can only be flashed with flashtool.
I don't mean to sound rude but why do I want my own FTF?
Do you mean a FTF from the OEM firmware, they can be downloaded from XDA as well.
Or do you mean creating an FTF from the files that are now on my phone?
VeldMuijz said:
I don't mean to sound rude but why do I want my own FTF?
Do you mean a FTF from the OEM firmware, they can be downloaded from XDA as well.
Or do you mean creating an FTF from the files that are now on my phone?
Click to expand...
Click to collapse
I've seen a few people hat flashing firmware they download didn't work well for them but flashing with SUS or PCC did.
I'm not twisting your hand, if you rather use FTF you can download somewehere and it works then do that.
Ok so i tried to flash the kernel, the flashing went well but the error persists.
I think it's time to conclude that my data is gone..
It gave me some headaches and I sweared a lot but i got it working again.
I've flashed the boot.img, didn't resolve the issue.
I've updated the same rom over my old rom, didn't solve the issue.
I wiped cache only (to try and see if it would work) and this worked.
So it might have been a cache problem after all.
The updating android thingy was shown again only this time it said it had to update 100+ apps, and it did. After that I could use my phone again.
First things first, lets make a backup .
Thanks ChickeD (i've thanked you on XDA for your help)
This can be marked as [RESOLVED]