Anyone experiencing problem to turn TP ON?
I can reboot without any problems but power it down and back on doesn't work most of the time.
Battery is fully charged, no buttons broken, TP was fully restored using WebOSdoctor and then CM9 reinstalled.
Battery widget shows that the TP instead of shutting down goes to some weird state where it draws
as much power as when turned ON. Reset in any button combination will not wake it up.
It can take minutes and sometimes hours to power it back ON and every time the battery is in different state of discharge.
Same problem in WebOS
lifeisfun said:
Anyone experiencing problem to turn TP ON?
I can reboot without any problems but power it down and back on doesn't work most of the time.
Battery is fully charged, no buttons broken, TP was fully restored using WebOSdoctor and then CM9 reinstalled.
Battery widget shows that the TP instead of shutting down goes to some weird state where it draws
as much power as when turned ON. Reset in any button combination will not wake it up.
It can take minutes and sometimes hours to power it back ON and every time the battery is in different state of discharge.
Same problem in WebOS
Click to expand...
Click to collapse
The only thing I can think of is to doctor again, maybe going back to 3.0.0 then updating to 3.0.5 OTA.
Before doing anything, run acmeunistaller, then do the doctoring. Install android again, using acmeinstaller3. Upgrade cwm and moboot. This link will take you to the thread where the files you need are : http://forum.xda-developers.com/showthread.php?t=2080977
I know it's a pita, but it might work.
Good luck.
chicle_11 said:
The only thing I can think of is to doctor again, maybe going back to 3.0.0 then updating to 3.0.5 OTA.
Before doing anything, run acmeunistaller, then do the doctoring. Install android again, using acmeinstaller3. Upgrade cwm and moboot. This link will take you to the thread where the files you need are : http://forum.xda-developers.com/showthread.php?t=2080977
I know it's a pita, but it might work.
Good luck.
Click to expand...
Click to collapse
You can download all versions of webos doctor here http://en.m.webos-internals.org/wiki/WebOS_Doctor_Versions?wasRedirected=true .
Which is a lot less fraught than an OTA.
Hope this helps good luck .
sstar said:
You can download all versions of webos doctor here http://en.m.webos-internals.org/wiki/WebOS_Doctor_Versions?wasRedirected=true .
Which is a lot less fraught than an OTA.
Hope this helps good luck .
Click to expand...
Click to collapse
I don't know, starting to think that there is something corrupt in the bios
I used uninstaller uninstaller then doctor 3.0.5
Used Acmeinstaller3/moboot 0.3.8 /cwm 6 and cm9 latest nightly
What killed my hopes that this problem is in webos as well
Thinking about trying Unbricker 0.1 but don't have a Linux PC or know how
Reformat then CM10
lifeisfun said:
I don't know, starting to think that there is something corrupt in the bios
I dispozici funny uninstaller then doctor 3.0.5
Used Acmeinstaller3/moboot 0.3.8 /cwm 6 and cm9 latest nightly
What killed my hopes that this problem is in webos as well
Thinking about trying Unbricker 0.1 but don't have a Linux PC or know how
Click to expand...
Click to collapse
If you can start up I wouldn't unbrick but I would reformat thaen Doctor 3.0.0 then Dr. 3.0.5 then moboot etc. Instead of CM9 I have moved to Cm10 and been happy on two machines.
Carey4782 said:
If you can start up I wouldn't unbrick but I would reformat thaen Doctor 3.0.0 then Dr. 3.0.5 then moboot etc. Instead of CM9 I have moved to Cm10 and been happy on two machines.
Click to expand...
Click to collapse
I don't think cm9 is the problem since it will do the same thing in webos before android is installed
What you mean format first? I used uninstaller
Why doctor 3.0.0 first and then 3.0.5 again?
I did 3.0.5 only.
lifeisfun said:
I don't think cm9 is the problem since it will do the same thing in webos before android is installed
What you mean format first? I used uninstaller
Why doctor 3.0.0 first and then 3.0.5 again?
I did 3.0.5 only.
Click to expand...
Click to collapse
Doctor 3.0.0 can handle/fix certain partitions that 3.0.5 can't, as I understand it.
Edit : by formatting first, I think he means this guide : http://forum.xda-developers.com/showthread.php?t=1426244
I would try the other suggested solutions first because it's a pita, really. I had to do it, and I was at it for most of a day.
Good luck.
chicle_11 said:
Doctor 3.0.0 can handle/fix certain partitions that 3.0.5 can't, as I understand it.
.....
Click to expand...
Click to collapse
Could you point me to the info, I can't find anything about those changes
Thanks
It sounds to me that you have a fault with the switch , possibly a loose connection of some sort. As you have said that rebooting isn't a problem , if this problem persists even after booting into and shutting down in webos I really can't see why it would be a partition problem .
lifeisfun said:
Could you point me to the info, I can't find anything about those changes
Thanks
Click to expand...
Click to collapse
The commands in the thread I posted before lets you know what's going on. Read the whole thing, I know it's long, but you do learn a lot.
Like sstar said, this might not be the problem, but I go through various steps, until I find / understand what's wrong.
sstar said:
It sounds to me that you have a fault with the switch , possibly a loose connection of some sort. As you have said that rebooting isn't a problem , if this problem persists even after booting into and shutting down in webos I really can't see why it would be a partition problem .
Click to expand...
Click to collapse
I also don't see this as partition problem.
I have to say that in my opinion the power switch is not faulty neither since
it never fails to put it to sleep, wake it up or anything else. (unless there is extra contact to boot or something but I doubt that)
Related
So, when you install the Alpha CyanogenMod 7 build, chances are ClockworkMod Recovery will fail. This tends to be because the custom overclocked kernels in WebOS take up a lot of room in the /boot partition, and ACMEInstaller does NOT (And maybe cannot) resize this partition. If you want to use ClockworkMod, you need to boot it via novacom.
1. Unzip the update-cwm_tenderloin-1012.zip file into the same directory as Novacom.
2. Make sure your TouchPad is plugged into your computer, and reboot it while holding volume up. You should see a USB icon.
3. In the command line, browse to the directory Novacom is installed in.
4. Type this into the command line prompt:
Code:
novacom boot mem:// < uImage.ClockworkMod
You should now be able to flash gapps or whatever else you need to install (Except moboot, which you need to use ACMEInstaller to install)
Novacom is probably installed in: "C:\Program Files\Palm, Inc" for most users.
To get there in the command line, type:
Code:
C:
cd "C:\Program Files\Palm, Inc\"
Then you can continue on to step 4.
Thanks for this info , it worked great. So am I to assume if I remove overclock Kernel thenI wont have this problem and will be able to install CWM through ACme with no problems ?
Edit. Tried to uninstall F15C to no avail.
27scoob said:
Thanks for this info , it worked great. So am I to assume if I remove overclock Kernel thenI wont have this problem and will be able to install CWM through ACme with no problems ?
Edit. Tried to uninstall F15C to no avail.
Click to expand...
Click to collapse
I don't know, but I kinda suspect not, because I brought my touchpad back to stock and *completely* wiped my touchpad before installing CM7, and I had problems with installing CWM through ACME. I don't understand the inner workings, but that seems like it may answer your question?
OP: Thanks!!!
Reckon I will be tied to a cord when it comes to CWM ....
The oc kernels get written to the main boot partition... I'm unsure which, but one of the oc kernel's can consume too much space, not leaving enough room to flash cwm... try booting into webos and removing your oc kernels... and try again... you don't have to flash the entire thing... you can just flash the cwm with the acme installer...
thanks!
I am in the CWM-based Recovery v5.0.2.6 but nothing works, not even the reboot option... any option i select does nothing.
any ideas?
Hold home and power, go back to USB download, start ACME install process from step one. If you follow instructions exactly, it should all work. There are occasions where you need to do the same thing twice... but your patience will pay off.
Yeah I tried to remove the F15C overclock kernel and do just that with the installer . No dice , can't remove the OC kernel go to remove it and reboot to replace and it just reboots into F15C then in Preware go to put the stock kernel on goes through shows install asks for restart and just boots F15C back again .. I have also tried to just flash the CWM zip afew times throught the installer and get the error half way through about there not being enough available space..ugh..
Try installing one of the smaller oc kernels through preware? If not, crack out the webOS doctor..
WebOS Doctor
Tried several times, but the recovery boot did not respond, i see the menu options, backup/restore, reboot, install from ZIP, etc... but when I select the options they didnt do anything...
After several tries I decided, let me start all over so I installed webos doctor. Unfortunately I cannot share the link here..
Unfortunately after I ran it and finally clicked DONE, my touchpad wont boot, has a battery icon with a question mark inside. (The battery level should be at least 25% before you run WebOS Doctor). I left it charging for at least an hour but still on the same status, so I assume it got bricked when running the webos doctor. If the battery just went bad at the same time it would be a big coincidence.
There is a chat support which seems to be pretty good. DO NOT TELL THEM that you were trying to install Android, I assume you all know that lol..
portal dot webos dot com (Sorry, couldnt share the link here)
If battery doesnt work in an hour or 2, then I may have to send it back to repair...
My CVM recovery works.
When I did the install yesterday I put the cm install,cvm,mboot and market all in the cminstall folder everything installed except the cvm, went back into webos and put it back in the cminstall folder and ran the ACMEInstaller again and it was there this time.
Used the CVM to install the google market update this morning.
I had Webos O/C also
I installed mboot, cm7, and cwm with acmeinstaller and my CWM works just fine. Flashed gapps with it no problem....seems like a strange problem for you and misleading if you ask me
I had a similar issue getting clockwork to flash. The problem is that some custom kernels take up too much space in the boot partition and doesnt leave enough room for cwm. Changing your webos kernel should fix the problem.
Sent from my Android powered Tenderloin
crump84 said:
I had a similar issue getting clockwork to flash. The problem is that some custom kernels take up too much space in the boot partition and doesnt leave enough room for cwm. Changing your webos kernel should fix the problem.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
That actually makes perfect sense to me...i probably never had an issue due to the fact i didnt mess with my webos kernel.
+1 for you sir
Stroid01 said:
I installed mboot, cm7, and cwm with acmeinstaller and my CWM works just fine. Flashed gapps with it no problem....seems like a strange problem for you and misleading if you ask me
Click to expand...
Click to collapse
Nothing strage or misleading the OC kernel is the culprit.. Just cause it orks fine on one device does not mean different things will happen on others ...Thats how things work and how this thread got started...
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
crump84 said:
I had a similar issue getting clockwork to flash. The problem is that some custom kernels take up too much space in the boot partition and doesnt leave enough room for cwm. Changing your webos kernel should fix the problem.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
Yeah I thought the smae thing but I can not remove the F15C kernel.. I go through preware and uninstall , reboot , F15C boots up and then go back into preware and install stock kernel and then reboot and F15C still boots up. I have not tried to start from scratch with the Web DR. ... just trying to see if there are any other avenues try first..It's been fun trying to figure some out though lol...
27scoob said:
Nothing strage or misleading the OC kernel is the culprit.. Just cause it orks fine on one device does not mean different things will happen on others ...Thats how things work and how this thread got started...
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Yeah I thought the smae thing but I can not remove the F15C kernel.. I go through preware and uninstall , reboot , F15C boots up and then go back into preware and install stock kernel and then reboot and F15C still boots up. I have not tried to start from scratch with the Web DR. ... just trying to see if there are any other avenues try first..It's been fun trying to figure some out though lol...
Click to expand...
Click to collapse
If you can't switch kernels you may have to use the doctor. Thats actually what I did before I found out about the kernel size. I didnt really care as I dont plan on using WebOS.
Sent from my PG06100 using Tapatalk
I have restored the palm kernel.
But ACMEInstaller doesn't resize partition a second time !
Is there a way to force the installation ?
The boot partition cannot be resized, at least not by ACME. That is the problem. In my opinion, pushing Clockwork Recovery via USB is preferable to uninstalling an OC'd kernel. You should rarely need to use Clockwork Recovery, and in fact, most things you would normally install using it would, in the case of the Touchpad, not work.
: (
I know this is kinda old but im new to this, But im having this problem, I just installed CM9 and it boots nd everything, But no gapps, I went to go flash them and clockwork mod disappeared. So i stumbled on to this, When it goes to flash threw novacom It blinks the linus penguins and white words then gos backinto the boot loader with no Clockwork Recovery. I tried twice, What do i do?
Just trying to install Android on the TP for the first time... I seem to also be having this problem. Is there an update to this problem? Any new fixes? Or is everyone just dealing with either getting rid of an overclocked kernel or being tethered to a PC to get into CWM?
Well my good friend just bricked his Fascinate trying to go to the newest glitch kernel for ICS. It has been handed to me for fixing like many times before . This time though i don't think i can quite fix it. So the phone will automatically boot into ICS Recovery(5.5.0.4).
Here is what I have tried thus far from Recovery:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
This yields no results the phone just boots back into recovery. With that in mind I have/had tried this:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
Install teamhacksung_fascinatemtd-ota-eng.BUILD6.1
This too yields NO results. The phone again boots back into recovery. Actually it didn't boot straight into recovery I had to play with it for a bit.So the logical thing to do from here would be too boot into download mode and go from there either via Heimdall or Odin. Unfortunately neither are doing anything. The phone doesn't get recognized in either program. "Maybe it is your cable or your computer" I wish that were so but when hooking up my Fascinate no issues with either program. I have tried DaleV's methods for both programs and nothing. I have even tried getting the phone into download mode via the charging plug to see if there was any difference with that and no. I don't want to say it but i think the phone is completely BRICKED. So if any of you good forums members have any advice it would be greatly appreciate it.
Aali1011 said:
Well my good friend just bricked his Fascinate trying to go to the newest glitch kernel for ICS. It has been handed to me for fixing like many times before . This time though i don't think i can quite fix it. So the phone will automatically boot into ICS Recovery(5.5.0.4).
Here is what I have tried thus far from Recovery:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
This yields no results the phone just boots back into recovery. With that in mind I have/had tried this:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
Install teamhacksung_fascinatemtd-ota-eng.BUILD6.1
This too yields NO results. The phone again boots back into recovery. Actually it didn't boot straight into recovery I had to play with it for a bit.So the logical thing to do from here would be too boot into download mode and go from there either via Heimdall or Odin. Unfortunately neither are doing anything. The phone doesn't get recognized in either program. "Maybe it is your cable or your computer" I wish that were so but when hooking up my Fascinate no issues with either program. I have tried DaleV's methods for both programs and nothing. I have even tried getting the phone into download mode via the charging plug to see if there was any difference with that and no. I don't want to say it but i think the phone is completely BRICKED. So if any of you good forums members have any advice it would be greatly appreciate it.
Click to expand...
Click to collapse
I had this problem yesterday too. You have to flash build 1 not 2 then flash 6.1 again. It worked for me. Flashing 1 might give you an endless boot loop with your animation, but that's normal. Just pull battery and 3 finger into recovery and flash 6.1
Sent from my SCH-I500 using XDA App
mkuehl06 said:
I had this problem yesterday too. You have to flash build 1 not 2 then flash 6.1 again. It worked for me. Flashing 1 might give you an endless boot loop with your animation, but that's normal. Just pull battery and 3 finger into recovery and flash 6.1
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
3 fingering into recovery CAUSES a bootloop like the OP is describing.
He can try it out, but I'd be surprised if it did anything but bootloop. If I'm reading his post right, he can get into download mode, but the device won't be recognized by the computer? I'd recommend odin and starting fresh, but if the devices isn't being recognized then I don't know. Maybe look into getting/making yourself a jig? Although I thought those were more useful for getting INTO download mode..
I'm not sure, even though you said you can plug your phone in and it'll work, I'd just be trying different ports/cables and crossing my fingers
mkuehl06 said:
I had this problem yesterday too. You have to flash build 1 not 2 then flash 6.1 again. It worked for me. Flashing 1 might give you an endless boot loop with your animation, but that's normal. Just pull battery and 3 finger into recovery and flash 6.1
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
NO DICE. The phone is pretty fudged from what it looks like. I tried to install Build 2 but just the same thing. It boots into recovery and nothing.
k_nivesout said:
3 fingering into recovery CAUSES a bootloop like the OP is describing.
He can try it out, but I'd be surprised if it did anything but bootloop. If I'm reading his post right, he can get into download mode, but the device won't be recognized by the computer? I'd recommend odin and starting fresh, but if the devices isn't being recognized then I don't know. Maybe look into getting/making yourself a jig? Although I thought those were more useful for getting INTO download mode..
I'm not sure, even though you said you can plug your phone in and it'll work, I'd just be trying different ports/cables and crossing my fingers
Click to expand...
Click to collapse
Yup went ahead and tried doing that as well. No other combination of cables does anything. So i believe the consensus here is.....Bricked Not cool but the upgrade deal that best buy is offering makes the Galaxy Nexus all that much more tempting.
I'm wondering how he got it bricked in the first place? If he flashed the correct kernel for his device I don't see how that could happen. Did he flash the wrong kernel for his device? If he did, maybe the you would need the drivers for that phone? Just kinda thinking out loud, that's pure speculation. Did he flash the kernel and then mess with overclocking or anything?
One other thing I've heard of that you might look into is the "unbrickable mod", but as I understand it, it's done at the hardware level so if you're not fairly comfortable with the idea of taking your phone apart I don't know if that would be an option.
Is it possible to flash CWM through ICS Recovery, then say ..stock rom, check if computer can pickup the phone and go from there??
k_nivesout said:
I'm wondering how he got it bricked in the first place? If he flashed the correct kernel for his device I don't see how that could happen. Did he flash the wrong kernel for his device? If he did, maybe the you would need the drivers for that phone? Just kinda thinking out loud, that's pure speculation. Did he flash the kernel and then mess with overclocking or anything?
One other thing I've heard of that you might look into is the "unbrickable mod", but as I understand it, it's done at the hardware level so if you're not fairly comfortable with the idea of taking your phone apart I don't know if that would be an option.
Click to expand...
Click to collapse
My apologies i forgot to mention that. The funny thing is when we first got our phones he bricked his by setting setCPU all the way up LMAO. So i think this was the time of superclean on eclair so we didn't even have any over clock kernels or anything of that nature. This time around he tried doing the same idk what method though. He tried going to 1.4ghz but i don't believe that he properly messed with the multiplier or voltages.Unbrickable mod would be awesome but it would have had to have happened before this instance i believe. Even at that though given the situation i don't think it would have helped.
Hyper_Warp said:
Is it possible to flash CWM through ICS Recovery, then say ..stock rom, check if computer can pickup the phone and go from there??
Click to expand...
Click to collapse
This seems like a good idea but just speaking to him a couple minutes ago he phone is no longer going into recovery either. If it was it may have been worth a shot but I doubt it would have done anything. I think due to his tinkering he has had a hardware failure at this point.
Ah, that makes sense, and yes I'd say you're right about the unbrickable mod. Not sure that it would've been able to help in this case where the hardware was pushed beyond its limits. Just because you have the option to max out the OC settings doesn't mean it's something you should do, lol! He might have been better off with the stock ICS kernel (which doesn't include the ability to OC).
I'm sad to hear this. I've been searching the Internet for people with the same issue. The same thing happened to mine except I have a captivate. I flashed the new ICY Glitch kernel from CWM and my phone buttons immediately went hay-wire, where all buttons performed the "back" function. So I pulled the battery and rebooted to find only a bootloop. The button recoveries nor download modes will work, so I used my jig I made to get into download mode, and just as you said no computers nor odin will recognize the device. Nothing, nada. Although it will charge the phone as it will show the big battery icon charging.. go figure. I wonder if the Glitch guys know about this yet. I would post but I'm still a noob so don't have enough posts or whatever you have to have.
jnthnmc01 said:
I'm sad to hear this. I've been searching the Internet for people with the same issue. The same thing happened to mine except I have a captivate. I flashed the new ICY Glitch kernel from CWM and my phone buttons immediately went hay-wire, where all buttons performed the "back" function. So I pulled the battery and rebooted to find only a bootloop. The button recoveries nor download modes will work, so I used my jig I made to get into download mode, and just as you said no computers nor odin will recognize the device. Nothing, nada. Although it will charge the phone as it will show the big battery icon charging.. go figure. I wonder if the Glitch guys know about this yet. I would post but I'm still a noob so don't have enough posts or whatever you have to have.
Click to expand...
Click to collapse
First, if you're on a captivate, then you could probably be better helped in those forums.
Second, can you not use the volume and power buttons to navigate in recovery?
Believe me ive checked those forums, that is why I am here, looking for any glimmer of hope. No the button recoveries wont work, ive tried a zillion times a zillion different ways.
Sent from my SGH-I897 using xda premium
Help for the love of god
Did you find a fix for this? Because I also have a fascinate that will go into download mode but not the boot mode, it was a completely stock phone and will not be recognized by Odin, help if you can please
Check out #9 in http://forum.xda-developers.com/showthread.php?t=1238070
I am on vacation and my fassy decided to stay in recovery upon boot. It gets stuck in boot loop. I'm running AOKP Build 30 w/ Glitch. My fiance has a macbook with her however, everything I've read says that we can't use Mac for rooting or restoring fassy's. Is there anyway to get out of the boot loop with an option in clockwork. From what I understand we can't use the two button hard boot with ICS roms. I could use some help, I'd rather not be without my phone for a week.
Thanks guys
Keuka79 said:
I am on vacation and my fassy decided to stay in recovery upon boot. It gets stuck in boot loop. I'm running AOKP Build 30 w/ Glitch. My fiance has a macbook with her however, everything I've read says that we can't use Mac for rooting or restoring fassy's. Is there anyway to get out of the boot loop with an option in clockwork. From what I understand we can't use the two button hard boot with ICS roms. I could use some help, I'd rather not be without my phone for a week.
Thanks guys
Click to expand...
Click to collapse
Is there anyway to access a Windows computer? With Parallels, VMWare, a virtual computer lab, or something else?
If so, follow http://forum.xda-developers.com/showthread.php?t=1238070
If no, Hiemdall http://www.glassechidna.com.au/products/heimdall/
Goodluck
Apparently there's no driver for samsung fascinate with mac connectivity. I downloaded Heimall and the full tar package but didn't work. Does anyone know how to generically attatch my phone to the computer. Someone said something about a generic connection as a drive that works with heimall. I'm pretty pissed and can't seem to get this work. I'll pry end up just going down to a lab and hogging that for thirty minutes or so.
Heimdall has its own driver. It'll be in the driver folder in the suite. Also I'd use an older version of heimdall suite if you can. The newer version tried to streamline things but ended up being a downgrade IMO.
Sent from my SCH-I500 using xda premium
I tried to use Heimdall but couldn't locate the driver. I then located a "exitrecovery.zip" that was supposed to be flashed in cwm. I used my gf's phone to download it then switched sd cards and that didn't work. Still stuck in cwm loop. I can't get to a pc where i can download Odin software to. There's no other flashable file i can find to help me get out of this loop.
look at section 9 of my guide...I always keep a cm7 rom on my sd card just incase this happens!
Can I flash a cm7 rom if i'm stuck on a cm9 bootloop??
Keuka79 said:
Can I flash a cm7 rom if i'm stuck on a cm9 bootloop??
Click to expand...
Click to collapse
READ section 9 of my guide in the general section...
droidstyle said:
READ section 9 of my guide in the general section...
Click to expand...
Click to collapse
Thanks man, I got it to work. I'm surprised I didn't think of that before.
You're a life saver man.
No problem, glad to see you got things back up and running!!
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)
I wish I knew exactly what caused this to happen. I was using a Malaysk ROM and starting having the issues. I thought maybe it was the ROM so I downgraded back to the original ROM that came with my unit and I'm still having the same issues. I downgraded through system updates in settings.
I can get it to boot into recovery, but it's just a black screen with pulsating light blue lights on the side of my unit. I have a Joying RK3188 1024x600 with the touch buttons on the left side.
Also when the unit boots up I don't get the Android splash screen anymore, it's also black. The first sign of life is when the car logo screen pops up.
There have also been multiple cases where when I am using the unit the screen has turned black ( if the radio is playing it will continue to play though ) and I can't do anything on the screen. This has to be a related issue.
Does anyone have any idea whats going on here?
I appreciate any help I can get!
Anyone have any ideas?
ahfunaki said:
Anyone have any ideas?
Click to expand...
Click to collapse
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
What is USB method? Just load the files on to a flash drive?
And I've found a picture of the recovery menu and I've tried that multiple times with no success.
Thank you for your help!
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
pa.ko said:
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
Click to expand...
Click to collapse
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
ahfunaki said:
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Click to expand...
Click to collapse
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
gk66 said:
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.
pa.ko said:
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
Click to expand...
Click to collapse
I will look into this, thanks again!
ahfunaki said:
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.!
Click to expand...
Click to collapse
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
gk66 said:
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Thank you for the help, I ended up just installing that other rom with FUSE so everything is good now.
Really enjoying this thing...
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
MueKo said:
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
Click to expand...
Click to collapse
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
oscyp said:
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
Click to expand...
Click to collapse
Thank you for your support. My problem was that my recovery image was damaged. I fixed it by reflashing the recovery image.
thx
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
RS-TLS said:
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
Click to expand...
Click to collapse
Anybody able to help me out here?
RS-TLS said:
Anybody able to help me out here?
Click to expand...
Click to collapse
Is it possible to start your device normal?
No. It just sits at the bootloader.
Sent from my SM-G928F using Tapatalk
Try in recovery mode to enter back in normal boot mode. It's difficult to explain in englisch. I had to pin a small needle into my radio and ca. 0,5 seconds before the LED are flashing, stop with pushing. When you stop pushing you must wait 5-10 second and see if you device boot up normal.
You have to try this often to find the correct moment. Thats how I entered back to normal boot mode.