[Q] Archos G9 refusing to load ROM - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

Hi all I've updated my G9 80 many times and tried all the available ROM's with a few hiccups but have always managed to recover the tab with the info on this forum. On my latest update the tablet appears to refuse to load a ROM from the SDE menu? If I boot the tab normally it halts at the ARCHOS boot screen but I can see the tab in device manager/Disc drives as ARCHOS_A80S but not in the explorer window and the USB is shown as an unknown device. If I boot up into the SDE/Archos A80S Recovery menu and then select (Update Firmware) it opens up a drive on my win7 system labeled A80S_REC as per normal and I can transfer the (fimware_archos_it4.aos) update file across to the tab but when I select (OK to disconnect) the tab starts the update in progress which fails after about 20 seconds with a Update failed (221) message. This is the method that has always solved any problems in my previous operating excursions but after a few days of trying to solve this problem I'm now at an impasse has anybody any ideas or is it time to upgrade to the Gen 10 and retire this tab as bricked
Thanks for any info
Ken.
I made the basic mistake of trying to update with an older ROM (kicks own backside for making such a basic mistake) aaaaa well back to trying to brick it again but I happy as the screen of my old backup Hannspad is doing my eys in

The 221 error usually means that you have tried to install an older official Archos firmware than the last official Archos firmware you had installed.
If you know exactly which one that was, then you can find a link to download it hidden in-between all of the other rooted and custom ROMs in this list.
Go into Recovery / SDE and do a full Reformat. Do not try to install anything, just go thru the steps (without connecting to your computer) and let it fail the firmware upgrade process. Then exit out so your tablet turns off. Then start back up in Recovery / SDE and do another full Reformat. Then connect to your computer and copy over the Archos .aos file.
If it still shows a 221 error after that, then you may have at some point installed a higher official Archos firmware. Start all over with the above steps, but with the next higher Archos firmware download.
I really do not know just what might happen if say you had the official Archos 4.0.7 firmware installed and then installed a 'rooted' 4.0.25 or 4.0.26 firmware. That could possibly somehow make the tablet only allow you to install that specific official Archos firmware afterwards also.
Let us know what luck you have?

Now OK
Hi I came to the same conclusion myself and solved the problem 5 min after starting the thread but thanks for the info, it's much appreciated. I cannot understand how I missed this for so long as I've loaded the majority of the roms on this site. I solved it by downloading the latest rooted Firmware 4.0.26 from surdu_petru (GENIUS ROM MAKER )
Thanks again
Ken.
55mls said:
The 221 error usually means that you have tried to install an older official Archos firmware than the last official Archos firmware you had installed.
If you know exactly which one that was, then you can find a link to download it hidden in-between all of the other rooted and custom ROMs in this list.
Go into Recovery / SDE and do a full Reformat. Do not try to install anything, just go thru the steps (without connecting to your computer) and let it fail the firmware upgrade process. Then exit out so your tablet turns off. Then start back up in Recovery / SDE and do another full Reformat. Then connect to your computer and copy over the Archos .aos file.
If it still shows a 221 error after that, then you may have at some point installed a higher official Archos firmware. Start all over with the above steps, but with the next higher Archos firmware download.
I really do not know just what might happen if say you had the official Archos 4.0.7 firmware installed and then installed a 'rooted' 4.0.25 or 4.0.26 firmware. That could possibly somehow make the tablet only allow you to install that specific official Archos firmware afterwards also.
Let us know what luck you have?
Click to expand...
Click to collapse

Related

stuck in recovery have i killed my archos

hi i have attempted to root my archos 80 g9 and it worked but after installing sde i got stuck in boot loop then mistakenly i removed the sde menu and now the devices will obly go to boot menu and no matter what other options i select it does not load android please help im affraid i may have killed my device and adb no longer recognises the device, please help im extremely worried as even if i select update firmwae through device menu it sails update failed.
please please please help
soulclaimed said:
hi i have attempted to root my archos 80 g9 and it worked but after installing sde i got stuck in boot loop then mistakenly i removed the sde menu and now the devices will obly go to boot menu and no matter what other options i select it does not load android please help im affraid i may have killed my device and adb no longer recognises the device, please help im extremely worried as even if i select update firmwae through device menu it sails update failed.
please please please help
Click to expand...
Click to collapse
Don't worry, it's not killed.
If your device says update failed, usually it's because aos file is corrupted or file name is invalid. First, make sure that the filename is correct, browsers often modify name when you download same file multiple times.
And if it's correct then try to download it again from Archos website.
If nothing works, choose reformat device then try again.
If the failed is error 101, make sure you have the newest version of the update
Sent from my ARCHOS 80G9 using xda premium
ok so i have managed to get the aos file back on to my tablet so now not so broke but still want to root, the tutorial says i should put the firmware ext and other files on to archos via adb or copy and paste but when i get my tab to show as removable drive its only something like 200mb in size and the ext4 and other files for rooted firmware are over 500mb total...
soulclaimed said:
ok so i have managed to get the aos file back on to my tablet so now not so broke but still want to root, the tutorial says i should put the firmware ext and other files on to archos via adb or copy and paste but when i get my tab to show as removable drive its only something like 200mb in size and the ext4 and other files for rooted firmware are over 500mb total...
Click to expand...
Click to collapse
You boot the tablet as usual and run Paul's root. Then you enable sde. After this, copy the file to the internal storage of the device using your computer. Boot into recovery. Go to development > install ramdisk. Another drive will appear on your PC. Copy the other 2 files onto it and press the power button on the device. Wait and then reboot
Sent from my ARCHOS 80G9 using xda premium
managed to complete root process however superuser does not allow anything also im following the tutorial for installing firmware with root but after installing th zlimage and initramfs however how do i install the ext4 i have no folder called data
soulclaimed said:
managed to complete root process however superuser does not allow anything also im following the tutorial for installing firmware with root but after installing th zlimage and initramfs however how do i install the ext4 i have no folder called data
Click to expand...
Click to collapse
Ext4 isn't installed, it just sits there being mounted
About root: Are you booted into sde?
If not, boot into recovery and select Boot Developer Edition
Sent from my ARCHOS 80G9 using xda premium
very kind of you to advise, its all working again now thanks
Archos have 2 different update for archos 5. One for archose it 5 and 7, and the other is for archos internet tablet 5 and 48, make sure you use the correct one. Go to archos page and download the other one.
HELP MY acrhos 80 g9 wont boot past recovery
i have the exact same problem i rooted my archos 80 g9 followed each step slowly and exactly but get the z image and other file for the honeycomb versoin so then i just got the ics version on it and flashed the kernal and everything so it ended up just getting stuck in a loading screen i thought it just took a while because i rooted it no it stayed over night 12 hours and still loading so i went into recovery and tried to reformat it but it wont show up on my computer so i cant put any files on it i also accidentally removed the sde so now when i turn it on and off it goes straight to boot please help me im screwed can you please answer here or send me an email [email protected] it is super urgent its been stuck for a few days now
kingcyrus9 said:
i have the exact same problem i rooted my archos 80 g9 followed each step slowly and exactly but get the z image and other file for the honeycomb versoin so then i just got the ics version on it and flashed the kernal and everything so it ended up just getting stuck in a loading screen i thought it just took a while because i rooted it no it stayed over night 12 hours and still loading so i went into recovery and tried to reformat it but it wont show up on my computer so i cant put any files on it i also accidentally removed the sde so now when i turn it on and off it goes straight to boot please help me im screwed can you please answer here or send me an email [email protected] it is super urgent its been stuck for a few days now
Click to expand...
Click to collapse
please follow the steps on my guide or look anywhere else on this forum. the problem has come up many times http://forum.xda-developers.com/showthread.php?t=1542058
Stuck in a boot loop
Hi guys and gals, 101g9 250gb is stuck in a boot loop....
SO FAR...
I had sever problems with crashing on the archos FW.
So I switched to a xda dev version (can't remember which one).
It worked well for 2 weeks, then just started a reboot loop.
I tried in this order:
Restarting in safe (button) mode 545434times
uninstalling the dev and reinstalling the archos FW
formatting android
formatting every other thing
Reinstalling the SDE menu - then trying a xdadev
It's still stuck in a boot loop.
Any help would be great.....
thanks

Bricked? Boot-loop? SDE gone. Firmware not installing

Hello,
A few months ago, i rooted our Archos 101 succesfully. Multiboot. Worked nice.
Then the firmware came, and my partner let it install. But it failed halfway.
He tried some things, but no succes.
Now we found this guide on how to install the firmware.
http://forum.archosfans.com/viewtopic.php?f=76&t=54637
This guide seems to be the windows version from http://forum.xda-developers.com/showthread.php?t=1196318
My partner tried the steps, but nothing seems to work.
We have only the recovery menu, without the SDE .....
I tried to use the stock firmware and the sde version. But it stops directly, saying: update failed
I tried the format option, the fw-update version.
I tried downing with firefox and iE8. We use the original file-name
Nothing helps
I hope we are not bricked.
What can we do?
Thanks in advance,
Lydia
joly said:
Hello,
I tried to use the stock firmware and the sde version. But it stops directly, saying: update failed
Click to expand...
Click to collapse
Hi,
What's your tab? it will help us i think.
and, have you all stock menu (except sde menu of course)?
I have no idea, except, your hardware is damaged.
another question comes to me: The full format works well?
Bizcuite
If u can uninstall SDE do it (if you dont have SDE menu skip this step). Try full device reformat. Make sure you download the right firmware for your device cuz many people made the mistake to download the wrong one.
We have an Archos 101 internet 8gb gen8
We used this stock firmware:
update.archos.com/8/gen8/gen8_2.4.83/firmware_archos_android_gen8.aos
and this sde firmware:
archos.com/support/download/firm_dev/firmware_archos_android_gen8.aos
(sorry outside links are not allowed for me yet)
We tried several formats. The guide let to format from within windows. Recently I cleaned my computer. So no ADB of Android sdk intstalled at the moment. The format from the windows-admin is a bit strange, but I hoped the guide was ok.
We tried FAT and FAT32
It seem to work.
We have only the white screen with the boot menu. No SDE.
The firmware worked in the beginning but got stuck and hanged voor about half an hour. Then we interupted it by switching off the tablet
Now it won't start any script.
I do hope it is nothing with the hardware! Could it really go wrong when roootin?
Greetz, Lydia

[how-to] another advenure: From German "unrootable" 3.2 build10 to rooted 4.0.3R5a

[how-to] another advenure: From German "unrootable" 3.2 build10 to rooted 4.0.3R5a
Hi there,
after about 5 nights, this "morning" at 4am, I won over Sony and M$ :highfive:
So i want to write this little tutorial for the ones, who might still be stuck on 3.2 build10.
I bought my tablet S 114DE/S, German with 3G, right before Xmas. Thought, it would be an easy task ... ha-ha.
First thing I read was, that build 10 is unrootable. F#?!
Started reading everyhing on XDA and other forums. Also read Cat McGowan's "adventure". Tried to do it like him... but as my tablet is German region an region changer only works with rooted devices, I could not flash his US files. But the idea was born.
Found the thread: XDA Developers > Sony Tablet S > Tablet S General > NEW Update Links Inc Tablet S/P R5A & Xperia S R6b
The "oldest" downloadable German original Sony FW was ICS R2a. I was not sure if this was still rootable, i would have liked to find a R1a, but what the heck, worst case is a not rooted ICS, which is still better than an unrooted 3.2!!
Downloaded, put on SD an flashed with recovery mode. Went fine.
So all you need to get away from "unrootable" build10 is a rootable original FW for YOUR tablet's country code!!! Hope you find one. There are many in the above mentioned thread.
Installed ADB automatic installer, no probs. i have Windows 7 pro 64bit.
Would be really NICE to add a clearly visible advice to also install the ADB driver (most likely MANUALLY on some systems) before using any special tools... I did not see any advice, maybe I was blind...
At least tell everybody to check, if the driver is working, by booting in recovery and looking at Windows device manager.
Problem is to find the right driver...if you simply choose the INF like for the "normal boot" ADB device, W7/64 does not install properly, you can get an error... really badly misleading message comes from Windows: It's telling something about MTP device ... well, actually you need the ADB driver!! Took me some hours... but as I found that problem only later, it took me 2 nights before, trying Condi's flasher and AIO 5.3 tool, without success...
OK, ADB drivers were installed (I only had the normal boot drivers at that time).
Downloaded Condi's AIO 5.3 tool, used the "root device" option, everything went OK, I was really happy! Rooted ICS R2a. First big step. 3.2 build10 unrootable? Not really... you only need a rootable original Sony firmware, flash it the normal way.
Then, I wanted to upgrade to R5a of course!
Condi's flasher 2.2. did not work. Maybe also because of the missing ADB driver for recovery mode?? Dunno. It always ended with: System.zip and all the other zips "not found", although I also tried pushing them manually to the internal SD before... when checking later, they disappeared.
Tried AIO 5.3 and custom signed zip. Always stuck in recovery mode with "Status 7" Error, like described in post #72 in this post:
XDA Developers > Sony Tablet S > Tablet S Android Development > [FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery!
Also here, it would be nice to bring the advice (install ADB drivers for recovery mode) BEFORE! It does NOT appear in the tool's window IF you are stuck!
After finding the right driver, it was no problem installing the prerooted double-flash zip with the AIO tool... Also here, do not panic when the "Status7" Error appears... it's normal, it disappears after a few seconds and at the same time, the hint about the driver comes up in the command window...
Btw I had no problems with missing google market or apps or any Sony applications. Google play is working, also Sony remote etc.
OK, that's it!
Waiting for 4.2
Have fun with your rooted Sonys!
Many thanks to Condi and the other devs for the tools, videos, tutorials... they may not be perfect, but without, it would be impossible for guys like me :angel:
Daniel

[Q] Archos 101 G9 Turbo dont launching after factory reset

Hello when i, make system recovery, ant me tablet reboot, and don't not loading only show archos logo screen, and i cant use system recovery, where is the problem, how i can fix it?
If you had custom rom installed and made reset to factory settings, then this is an usual problem.
Try to flash rom again.
Check if you can enter in recovery menu by pressing "volume up + power on" on powered off device.
Thank you recovery menu now working, what rom is recomendet for me tablet?
Before installing custom rom, install official rom for your tablet, you can find it on archos website.
I'm using freezenook ROM. Do not reset your config in future with this rom. Only stock rom doing it correctly.
Archos 101 g9 Turbo
Hi All, i'm stuck in Archos A101S recovery mode, also my tablet is missing items from recovery such as...Mount, and i cant get into storage, and it also says on pc that A101S 299mb which means i cant even install a firmware, as it is too small to fit on there, somewhere along the lines...i've messed it up, i have no folders also in recovery mode such as Music, Videos etc
all i see is Archos A101S
would you like to recover your system?
No
Reboot
Update Firmware
Repair System
Format System
Please...any help would be fantastic...i love my Archos and used it all the time, i tried to update my firmware and by reformatting and wasn't sure if i had to Reset Android
Reset Media
Reset Android
Reformat Device
i think i reset everything and now feel a right lemon! 4 doing so, i have tried a lot of sites trying to sort this out but to no avail, i was pointed in this direction for help...because at the moment i have a black cracked tile in my bathroom and the tablet is the right size lol,
Thanx in advance :fingers-crossed:
Glen460 said:
Hi All, i'm stuck in Archos A101S recovery mode, also my tablet is missing items from recovery such as...Mount, and i cant get into storage, and it also says on pc that A101S 299mb which means i cant even install a firmware, as it is too small to fit on there, somewhere along the lines...i've messed it up, i have no folders also in recovery mode such as Music, Videos etc
all i see is Archos A101S
would you like to recover your system?
No
Reboot
Update Firmware
Repair System
Format System
Please...any help would be fantastic...i love my Archos and used it all the time, i tried to update my firmware and by reformatting and wasn't sure if i had to Reset Android
Reset Media
Reset Android
Reformat Device
i think i reset everything and now feel a right lemon! 4 doing so, i have tried a lot of sites trying to sort this out but to no avail, i was pointed in this direction for help...because at the moment i have a black cracked tile in my bathroom and the tablet is the right size lol,
Thanx in advance :fingers-crossed:
Click to expand...
Click to collapse
The stock firmware is only about 206 MB, download from here. http://www.archos.com/gb/support/support_tech/updates_fwm.html
Guide to installing custom firmware is here. http://forum.xda-developers.com/showthread.php?t=1871912
Archos 101 G9
stevemp said:
The stock firmware is only about 206 MB, download from here. http://www.archos.com/gb/support/support_tech/updates_fwm.html
Guide to installing custom firmware is here. http://forum.xda-developers.com/showthread.php?t=1871912
Click to expand...
Click to collapse
Thanx 4 replying...but still can't use this cos my device won't mount!
---------- Post added at 09:22 PM ---------- Previous post was at 09:04 PM ----------
Glen460 said:
Thanx 4 replying...but still can't use this cos my device won't mount!
Click to expand...
Click to collapse
p.s...it isn't actually 206mb...it's packed but when u move it to archos...it unpacks and the size is actually a lot larger
The update firmware option in recovery is what you want. Choose that. Hook data cable up to computer. In windows you should see a new drive pop up saying Recovery or Rec or something. It may say 180mb or something but Archos' firmware should fit on it just fine.
Archos 101 G9 Turbo
Djirin said:
The update firmware option in recovery is what you want. Choose that. Hook data cable up to computer. In windows you should see a new drive pop up saying Recovery or Rec or something. It may say 180mb or something but Archos' firmware should fit on it just fine.
Click to expand...
Click to collapse
Thanx stevemp and Djirin...just tried it the now and it worked straight away...i realised i was mucking it up also by pressing ok after the download which i kept on getting failed: (221)....i downloaded it...took out the usb lead and it prompted me to put usb back in and then i saw it installing with the blue stripe at the bottom of the screen...so happy now...think ill celebrate with a beer cheers buds!! :good: :good: :good:
I'm having the same issues.. my girlfriends kid hates me and bricked my archos 101 good...I only have a three hundred megabytes drive I don't see the actual hard drive for the Archos I put the firmware on there and as soon as it tries to update the firmware disappears and the drive becomes invisable/unreadable again. I do get an archos splash screen occasionally but it locks there.
I have to do the full archos format twice before my computer can see it again I'm trying on both windows 8 & 7.. I've tried with the supplied archos cable and went out and bought a new cable just in case both a 4 pin and 7 pin miniusb. I tried flashing the developer firmware and it booted up to the new splash screen froze there. I left ir on that screen went and did my laundry.. came home and nothing it was still stuck there.. i rebooted and i do not even see the watermark they talk about.. I'm ready to drop kick it but i love it..
I do know that the 300Mb drive does NOT have the correct serial number.. it is formatted fat 32..
With partition manager i can change the allocation from logical/primary. I can change it from a fat 32 to a fat 32 lba.
Or Linux fat 16 or something else. I tried changing the serial number of the drive and after the failed update it is incorrect again. And it wont allow me to enter the pc before the serial just the c.
I'm so frustrated and need help please my archos is my sanity on a 2hour bus and train ride to and from work everyday. This is going on week 3
Thanks for your help if you have any further ideas they are greatly appreciated
If you have only 300mb free I assume you are talking about the flash memory then. The HD models have an internal flash that programs get installed to and then the seperate HD where all your mp3s, videos, etc get installed to.
Have you gone into recovery and just tried to update the firmware from there directly? Same thing as Glen460 was instructed to do

[Q] Rooting Venue 7 3740

Hi all,
I recently got a new Dell Venue 7 3740 (yeah, not my first choice, but it was free for buying a computer). Anyway, started reading up on how to root the thing. I have a couple of apps that require root.
I found this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
and also the main Dell page: http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/
Following Dell's guide to rooting appears to NOT root it. Installing Root Checker confirms I don't have root. Unbricked it and got it back up from 4.4.2 to 4.4.4. By reading the first guide for the 3840, my question is ...
Is the boot image linked there compatible with my 3740?
(yeah, I know this should be in the developer section ... unfortunately I don't have enough posts ... also, I am familiar with rooting/flashing/etc, my first device that I put CM7 on was the original Galaxy S1 ... and I have CM10 on my S3.)
Tried, failed
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
reaper-death said:
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
Click to expand...
Click to collapse
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
ProfM2 said:
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
Click to expand...
Click to collapse
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
Click to expand...
Click to collapse
You better redo the unbrick procces cause as you are now, you won't be able to update your tablet and 4.4.2 has some issues with the clock and browser. The best way to root is by thetered cwm, I did it and it's working great.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Click to expand...
Click to collapse
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
ProfM2 said:
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
Click to expand...
Click to collapse
http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
* For Wifi-only device on A150 and Wifi / LTE device on A195
I see it now, I think I was misinterpreting the above statement which means I've been flashing the A195 rom this whole time. Thank you all for your help! :good:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
ProfM2 said:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
Click to expand...
Click to collapse
It is mentioned somewhere that the 3740 and the 3840 use the same firmware. Assuming that, what you can do is download the latest SuperUser zip, copy it to the internal or external storage, then use THIS, or THIS to root through CWM.
graphdarnell said:
It is mentioned somewhere that the 3740 and the 3840 use the same firmware.
Click to expand...
Click to collapse
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
ProfM2 said:
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
Click to expand...
Click to collapse
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
graphdarnell said:
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
Click to expand...
Click to collapse
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
ProfM2 said:
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
Click to expand...
Click to collapse
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
reaper-death said:
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
Click to expand...
Click to collapse
I have finally settled down and got the tablet rooted. What's really odd, was Win8.1 kept losing the proper driver. I'm not sure exactly why ... but suffice it to say, I got it working. It did appear to be more stable when I hit the Vol+ and plugged in the USB, but then again it may have been a coincidence.
Open source dell
If you follow the link to dell open source, they do have a detailed PDF download for unlocking the boot loader etc. The file was too large for me to upload on XDA. I just found it today while I was researching how to root this tablet. I have not had a chance to try it yet.
http://opensource.dell.com/
That doesnt work for 3740 lte. I;ve done everything that was in PDF. OTA image should be with unlocker bootloader and root but its not. ;/
Its adb root not su big difference
Does anyone have any idea to root dell venue 7 3740 lte
The open source is for venue 7 3740 wifi
how can i hard reset this device please tell me.
Mahisasur said:
how can i hard reset this device please tell me.
Click to expand...
Click to collapse
Reset any android tbalet with ...
Setting >>>>> Backup & Reset >>>>> Factory Data Reset >>>>> Reset Tablet >>> Erase Everything

Categories

Resources