Hi there,
Got a small problem (not sure it's so small though).
What i did :
Tried to update my Archos 70H - 250GB to the latest version via recovery menu(2.4.82) (wifi update didn't work - it said that internal storage is not available - i think i'll have to replace the HDD too-got an 160 gb Drive that i'll pop in this weekend to test)
It had Froyo before (i have to aos file for that one too but i can remember the version).
Problems:
-Boot loop at first Archos Logo.
- Can't enter Recovery menu with Power + Volume Down
(I pressed power for 12 seconds to make sure it's off. after that i tried to enter recovery menu)
All i get is a boot loop. If i try to enter the recovery menu i get a black screen after the Archos logo.
-The PC (Win Xp Pro SP3) doesn't see the Archos connected unless i'm in the recovery mode to load the new firmware
Questions :
-Can i try a "blind" flash - going trough the menu options even without seeing them ( if someone around would tell me exactly how many Volume-/Power to press and when)
- IF anyone has any suggestions please let me know as i ran out of ideas.
Thank you.
Solved
This is what worked for me :
1. Opened the tablet.
2. Took it apart.
3. De-soldered the battery wires from board
4. Scanned the original HDD in my PC ( everything working fine)
5. Left it like that while i was at work
6. Re-soldered the battery wires
7. Put it back in 1 piece (including the HDD)
8. Start
Is started straight in the new android.
The hdd is working again (i still don't know what the problem was)
The developer os is working too
Wrote everything here in case anyone needs it.
i have a problem too on my archos 70h if u try to start on i just entering in recovery menu. not from its original os. can you help how to flash this android to restore from its original state.
Related
I've just bought a user Archos 70 IT with a 1Tb disk upgrade. It's started refusing to complete the boot sequence. It flashes up the "Entertainment your way" screen, then goes black a couple of times, then gets stuck on that screen.
I've tried:
- Holding the power button down for 20 seconds to reset it
- Rebooting to recovery mode and selecting the "repair system" option (disk check)
- Rebooting to recovery mode and re-installing the firmware using the gen8 AOS file downloaded from the Archos site - this failed.
Before it died I managed to transfer about 50,000 music tracks to it, but did have the odd problem with USB along the way:
- the unit would only recognise the connection of the USB cable if it was connected before powering it up. If I inserted the USB cable at any time when the tablet was running nothing happened (although sometimes I got an audible tone from the PC, indicating that some sort of connectivity had been made)
- applications (e.g. camera, music) were unable to access the storage device, and suggested that it may be because USB was connected (even though the USB cable was disconnected)
Now I'm stuck unable to reboot it. Can anyone suggest anything?
Well all I can imagine is using the reformat option... but u will loose all data.
Did u have SDE installed before?
If - u also could try installing UD.
So you bought a unit that was opened by some guy, that then installed a 1TB harddrive?
The connection cable is very fragile and if he wasn't 110% accurate this might have come loose or broke.
So check with that guy, open the case again and check the cables.
FrEcP said:
Well all I can imagine is using the reformat option... but u will loose all data.
Did u have SDE installed before?
If - u also could try installing UD.
Click to expand...
Click to collapse
I managed to find an option on the Repair menu (in recovery mode) which re-initialised storage without wiping the HDD. Thankfully this left my music intact and revived the system. Phew....
Thanks for the feedback
Thanks in advance for reading this and for any suggestions you might have!
I have a Archos Home Connect 35 Gen 8 device. I had it rooted on 2.4.82 firmware just fine. I wanted to update to 2.8.83 to get rid of the update notification I kept getting. I wanted to do it from a fresh clean slate as I wanted to reset my device anyway. First I used the Recovery Menu (White Menu) to restore back to default, then removed the SDE menu via the option to remove it in the SDE menu.
I then followed the guide that chrulri posted that I followed last time, but with 2.8.83 files. http://forum.xda-developers.com/showthread.php?t=930197 (Note for Archos 35's you have to hold the power button for ~6 seconds, then double tap it to get to recovery instead of holding Volume Down like on other Gen8's). I was doing this on my MacBook Air at the time. (I rooted it before from my Windows PC). I went to 'Update Firmware" on the recovery menu, then took the SDE firmware file, and copied it over USB to the drive and safely removed the drive, then hit "OK" on the device. It proceeded to do the update it seems but only took 2-3 seconds so I'm fairly sure something didn't go right as it usually takes longer. It then said press ok to Reboot so I did.
After the reboot from that, the device turns on but I get a White screen. No Archos logo or anything. Usually this white screen comes on for a few seconds, then I would get the Archos Logo even if I was booting recovery. No luck. I tried resetting the device by holding power button for 20 seconds, waiting 10 seconds and turning it on, same issue. Recovery will not work either, I tried two dozen times to try and get it to load by doing the usual ~6 seconds holding power button then double tapping and no luck.
I tried hooking the device up USB and in Windows all I get "Unknown Device" in device manager, with DeviceId of USB\Unknown. I attempted to force both Archos' ADB driver and the Universal ADB drive onto it with no success. (I'm pretty sure its my device since normally when a device shows up and its capable of ADB you will get a difference device ID in Device manager like USB\ADBDEV1 or something. On my Mac, when I plug it in, all USB devices (Multitouch pad mouse included) will lock up for ~5 seconds, then in dmesg I can see it has a error on USB device and it disabled the device.
So something weird is going on with my Home Connect for sure. Any suggestions on what to try? I'm thinking somehow the filesystem or firmware on it got screwed up during the SDE flash and it can't boot anything even the recovery now. I have a MicroSD card I can use if there's some recovery feature built into it to get it to boot from the MicroSD slot or something to do a firmware recovery.
My only other option if there is no way to try and get it back would be to try and send it back to Archos for repair simply stating it was updating firmware and this happened. (No actual modified firmware is on it now as well, and i was flashing the Archos approved SDE firmware, so they should be okay with it).
Also the battery was fully charged when doing this. It seems different that the White Screen bug the Archos 101 and others get when the battery accidentally runs too low with older firmware.
Thank you again for your replied!
If you can't get into recovery anymore, then it is over. I would suggest to RMA the device.
divx118
From all my searches through Archos forums and here that seems right.
I'm shocked there's no failsafe recovery mode for Archos. My Asus Transformer TF101 had one, where even if the firmware was screwed and you couldn't get to recovery, a special key combo would boot it up and you'd load some special recovery driver for it (Not adb something with nVidia in it, has to do with Tegra2 chipset i suppose) and upload the firmware to it and it recovered. Even iPhone's have DFU fallback mode as well for when things are totally forked and iTunes will restore the firmware.
Just an update. I did RMA the unit and Archos sent me a brand new boxed up one back. (I have an extra charger and cable now since they said not to include them ). Have my new 35 setup rooted with .83 now.
I think I figured out what happened. After I installed the SDE, before I flashed the new kernel and such, if I booted the Developer Edition option from recovery, it would get stuck at a blank white screen until I power cycled. On my old 35 I had removed the option to boot regular so it booted the Developer Edition that was rooted every time. I think when I restored the original firmware, it of course removes the Developer Edition kernel I had flashed before, but it somehow didn't set the menu back and was trying to boot Developer Edition every time, which it lacked the kernel for, and went to the white screen. Not sure if it explains recovery not working though.
To make sure it doesn't happen again i've left the options all in tact and left it so I manually have to go to recovery if I reboot the system to boot the developer kernel for root. Since the device goes weeks and months without the need to reboot since it's just an Alarm Clock really that's fine with me.
So I bought this cheap tablet off of ebay and after about a week I connected it into the charger and forgot to unplug it.. Only next morning I saw and when I disconnected it it had turned off. So I turned it on and it was stuck in the newsmy logo and wasn't booting up.
There was nothing on the internet, but somehow I got it working again and for everybody's sake I'm posting what I did here.
First off, even though there are some references that this has allwinner A10 inside, ITS NOT. you will brick this if you flash an allwinner variant kernal.
If you are one of those brave souls who flashed on a allwinner kernals and bricked the thing, you would not be able to go to download mode even. Here is the steps to flash a fresh rom that would resolve most of issues:
1. Download driver pack from the attachment of this post
2. Download RKBatchTool here: http://www.x-drivers.com/catalog/fl...s_electronics/models/rk_batch_tool/27576.html..
3. Now turn off your tablet. If it doesn't turn off press a needle head into the reset pinhole and hold it for 5 seconds
4. Open device manager from your computer
5. Then hold the power on button and volume up(that is the one closer to power button) until it turns on. It'll boot your tab in download mode. After the green robot icon appears connect it to the computer by carefully monitoring device manager of computer
*** If you have flashed an allwinner or other rockchip kernal based ROM earlier and do not go in to download mode or no new device installation in your PC there's a real possibility your download mode combination may have changed. Turn it off by pressing needle to reset pinhole. Then turn off and connect it to PC. Then turn it on and then while in boot screen hold volume up. if not try similar procedure by holding volume down or back buttons. If you see driver installation in the PC and nothing in the tablets screen, thats fine. You can continue with the flasing
6. The driver installation probably will fail. Identify which device that is newly added to the device manager.
7. Right click on the device -> Update Driver. Then manually select -> Have disk then give rockusb file from drivers you just downloaded(if your system is 64-bits use files in amd-64 folder)
8. Then select RK29 as the device and update the driver
9. Now extract and run RKBatchTool and you must see under connected devices button #1 highlighted in green
10. Download official ROM here: http://220.168.57.227:1949/cunchu/20120312T3youhuaruanj.rar
There are other ROMs for T3 here as well. But this is the only thing that works
11. Extract it and give its update.img file path to RKBatchTool FW Path
12. Hit Restore
13. Wait few minutes for flash to complete
14. Then the tab will restart once or twice and will start booting up. This process should take maybe 5 minutes or more. Be patient
15. Then it'll finally boot.
I will post a Jelly Bean ROM for this tab here as soon as I cook one
Comments are much appreciated
Thank you! Thank you! Thank you!
Was searching for a guide to get my brothers Newsmy Newpad T3 up and running.
Thank you for this guide. will definitely try it out and leave a feedback.
P.S. Jellybean sounds interesting.
OK. After spending two days I finally got it to detect the Newsmy Newpad T3.
I had to install Android SDK for the USB drivers. (Don't know if it detected from that.)
Then downloaded super one click root. Found the android drivers in it, and when it asked which driver you want to install I gave "Android Composite" not sure but something in those lines.
Successfully rooted it.
Then off the tab and connect the USB cable, press power and volume up (one that is near the power) and when the tab boots
If it asked for drivers please do same as above
Now run the firmware installer provided inside the update.img folder that you downloaded from the original post by suki300me step 10. It is in Chinese and the first option is to change it to English found on the bottom screen.
If everything is set your tab will be in a black screen only thing you know is that it is on is the sound windows 7 makes when the phone is connected to it. Choose the udate .img file and press upgrade.
It will run up to 3-4 stages and will say data copy error. Remove the cable and press power, it will star installing ICS give it few minutes and you are done.
It took me many attempts so don't give up if it didn't work on your first try. Hope this helps someone.
Boot
Hi
I get one newsmy t3 tablet from my friend. The only problem the system is never loaded (stuck at the boot). I try the power+volume up but just the black screen appaers. Btw only turns on when its plugged. Please give me some tips.
Hi,
my Pipo M6 per wifi hangs itself while starting, i.e. he gets stuck with the loading picture. Indeed, with the Reset he restarts, however, gets stuck also again. After he gets stuck, he can be also switched off no more, except by Reset.
And I also do not come to the Recovery mode, I thought, maybe helps a new firmware. However, sometimes he registers if I hold the keys while starting low-spirited, that Android little manes with open belly and warning sign. see below.
If I hang him by USB on my Win7 pc, a wrong driver's file is installed constantly, either Samsung or HTC, so that the Flashtools register that no suitable device is connected. With the USB driver of Pipo the pc says that that is no suitable driver's file.
What can I do?
And over again for stupid ones: I come to the Recovery fashion, nevertheless, dur volume press ESC and power at the same time, or?
Please, can anybody help me?
Nobody can help?
Is the tablet an fall for garantie?
Anybody any idea?
Please help.
Try one of the 2 methodes
gnom68 said:
Is the tablet an fall for garantie?
Anybody any idea?
Please help.
Click to expand...
Click to collapse
A This is the easiest way: Do a HARDRESET
Recovery Mode (for Factory Reset):
-----------------------------------------------------------
1. [Reset] (on the backside)
2. [Power] + [Vol-]
3. green Android shows up
4. press [Vol-] + [Vol+] + [ESC] together till Menu shows up (if it's not showing up try to press it a few once more)
OR
B For advanced users: Flash the original Firmware (download from here it is a very slow download )
and use the howto which is delivered within the downoad.
Maybe you can find some usefull information here
Hope i could help u. For me it was working fine.....
Hi folks,
I Soft bricked my hp 8 g2 1411.
I was trying to install a recovery rom so I could install a lollipop rom.
I'm now stuck at the HP powered by Android screen. See attached.
I can't get to the recovery screen as its probably gone.
I also have the complete original ROM downloaded from HP with a folder with recovery on it...
I don't know how to get to fast mode or download mode.
Can anyone help?
Thanks,
Steve.
I Hope This Could Be Of Any Help
We have exactly the same device and I had exactly the same problem for like 2 weeks and I was able to fix it fortunately. So I would like to help you if in case you still needed one. I created a tinyurl of the website you got to download the stock firmware from and not the one from HP website. Then save it on the root folder of your external sd card with update.zip as the file name. Now with your tablet off simultaneously press power + volume up + volume down and once you see the HP logo release them all and you'll once again see HP logo and then the stock recovery of your tablet. Use the volume keys to navigate to "apply update via sd card" then choose the "update.zip" you downloaded. It's gonna install for about 3-5 minutes and you're good to go.
I'll pm you the link for I am not allowed to write one yet!
Cheers!
Nicole:victory:
I have the same device and the same problem. However when I push the power+ volume up + volume down buttons at the same time and release when I see the HP logo, all I aver get is then HP logo Powered by Android. It never gets to the recovery screen.
Thanks Ted
Please share the link. Recently my tablet bootloop for no reason.
I had the same problem with mine and found no solution to fix it other than flash the firmware .img with a micro sdcard created with phoenix card. Sadly the firmware .img is not available from HP ...
Now 3 weeks later I compiled a custom firmware for the HP 8 G2 1411 and got everything working in Android and most of it working in TWRP (custom recovery environment)! I am in the final stage of tweaking TWRP and I should be done with it in the next days.
The release will contain:
Custom Android KitKat 4.4.2 for HP 8 G2 1411
(without HP bloatware)
Google Now default launcher
Custom recovery TWRP 2.7.01
Possible to flash superSu .zip to gain root
Flashable sdcard (need to be burn with PhoenixCard)
I can't post link in the forum right now, send me a PM if you need it!
This will fix a softbricked tablet but you will loose all your data.
It' done! How to fix a softbrick on the HP 8 G2 1411:
-Download and install PhoenixCard 3.1.0
http://www.mediafire.com/file/rlccciim76vsqnv/PhoenixCard_V3.1.0.rar
Download my custom ROM from:
https://mega.nz/#!YvRlXY5S!6Sg8r-DzMoV5Y1FUP1loCN7PbN7dwbOoPSMQXglcljI
-Prepare a micro-sd card with PhoenixCard
-Turn off tablet
-Remove top cover (where the usb port is) and put sdcard in
-Turn on tablet (be sure you have enough battery, the process takes around 3min)
-Wait until the green bar is filled, it should say Card OK on top when it's done and the tablet will turn off
-Remove sdcard (put back the compartment cover if you want)
-Turn the tablet back on again
-wait.... and...
-That's it, it should boot into Android KitKat!
If you want to boot to Recovery use adb (check google for instruction on how to install) or use a "custom power menu app"
*Don't boot to fastboot or to bootloader, this is not supported by this tablet, it will softbrick the tablet and you will have to start the process again
Features:
-Custom Android KitKat 4.4.2 for HP 8 G2 1411
(without HP bloatware)
With Google Now default launcher
-Custom recovery TWRP 2.7.01
(Possible to flash superSu.zip from recovery to gain root)
*Install from sdcard (need to be burn with PhoenixCard)
Known issues:
TWRP can't mount data partition or external sdcard
Volume button wont work during boot (they work fine once Android is loaded)
Once in a while the might wifi stop working, a reboot will fix it (very rare)
Enjoy!
I still using this tablet. I using ur rom as well. It's good. But I just realise it doesn't come with swap ram.
nicolepulga said:
We have exactly the same device and I had exactly the same problem for like 2 weeks and I was able to fix it fortunately. So I would like to help you if in case you still needed one. I created a tinyurl of the website you got to download the stock firmware from and not the one from HP website. Then save it on the root folder of your external sd card with update.zip as the file name. Now with your tablet off simultaneously press power + volume up + volume down and once you see the HP logo release them all and you'll once again see HP logo and then the stock recovery of your tablet. Use the volume keys to navigate to "apply update via sd card" then choose the "update.zip" you downloaded. It's gonna install for about 3-5 minutes and you're good to go.
I'll pm you the link for I am not allowed to write one yet!
Cheers!
Nicole:victory:
Click to expand...
Click to collapse
Hi, may i know the link you the device?
imranclick said:
I still using this tablet. I using ur rom as well. It's good. But I just realise it doesn't come with swap ram.
Click to expand...
Click to collapse
I did what I was able to do with my limited knowledge, at least I was able to salvage the device! I'm far from being a programmer and I think it's sad that no one tried to port a custom ROM for this device...