Hello, thank you if you are trying to help me.
What did I do?
I started to with Dell Streak running Android 2.2, wanted to upgrade to StreakDroid GingerStreak 2.4.4.
So I downloaded the files referred to in the linked guide in the section
YOU MUST FLASH THE BELOW BASEBAND AND DSP1 IMAGES TO ALLOW THIS BUILD TO WORK CORRECTLY!!
Click to expand...
Click to collapse
I installed device drivers and booted into fastboot, everything worked well.
Then I used the commands listed to flash amss.mbn ja dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c reboot
Click to expand...
Click to collapse
Everything seemed okay, device started to reboot... but it never booted.
Current situation:
Device boots sometimes (not every time) until Dell logo and freezes. I am unable to boot into fastboot or recovery mode.
When connected to PC it shows up as qualcomm device and then installs drivers and lists as USB HID device.
I can use W7 64bit and Vista 32bit to troubleshoot the problem.
Thank you if you managed to read it all through and if you have any suggestions, I am all ears. Do not want to make things worse by doing wrong moves.
If you need any extra info just ask, I might have forgotten something useful.
maatriks.
I also have this same problem on my other streak. I tried going back to stock att 2.2 though from streak droid 1.6 I think. Which ever one is 2.2.2. Flashed recovery and I never changed basband so it was stock still. Stuck at dell logo. Cant get into safe mode to use qdl tool
Sent from my Dell Streak using xda premium
any luck?
maatriks said:
Hello, thank you if you are trying to help me.
What did I do?
I started to with Dell Streak running Android 2.2, wanted to upgrade to StreakDroid GingerStreak 2.4.4.
So I downloaded the files referred to in the linked guide in the section
I installed device drivers and booted into fastboot, everything worked well.
Then I used the commands listed to flash amss.mbn ja dsp1.mbn
Everything seemed okay, device started to reboot... but it never booted.
Current situation:
Device boots sometimes (not every time) until Dell logo and freezes. I am unable to boot into fastboot or recovery mode.
When connected to PC it shows up as qualcomm device and then installs drivers and lists as USB HID device.
I can use W7 64bit and Vista 32bit to troubleshoot the problem.
Thank you if you managed to read it all through and if you have any suggestions, I am all ears. Do not want to make things worse by doing wrong moves.
If you need any extra info just ask, I might have forgotten something useful.
maatriks.
Click to expand...
Click to collapse
Any luck on reviving your phone?. got the same issue. can't pass the dell logo after flashing.
maatriks said:
Hello, thank you if you are trying to help me.
What did I do?
I started to with Dell Streak running Android 2.2, wanted to upgrade to StreakDroid GingerStreak 2.4.4.
So I downloaded the files referred to in the linked guide in the section
I installed device drivers and booted into fastboot, everything worked well.
Then I used the commands listed to flash amss.mbn ja dsp1.mbn
Everything seemed okay, device started to reboot... but it never booted.
Current situation:
Device boots sometimes (not every time) until Dell logo and freezes. I am unable to boot into fastboot or recovery mode.
When connected to PC it shows up as qualcomm device and then installs drivers and lists as USB HID device.
I can use W7 64bit and Vista 32bit to troubleshoot the problem.
Thank you if you managed to read it all through and if you have any suggestions, I am all ears. Do not want to make things worse by doing wrong moves.
If you need any extra info just ask, I might have forgotten something useful.
maatriks.
Click to expand...
Click to collapse
I cannot remember exactly what was said for gingerstreak but I do remember there being some quite specific instructions about the first flash and boot of the rom.
I would suggest reading the whole post and then trying to flash again.
I can remember having the same problem as you when I first flashed this rom but I managed to resolve it by reading the post thoroughly.
If I can find the stand out instructions in the thread I will post them but if you still want the rom have another good read and all should fall into place.
Sorry for not posting solution a year ago. I managed to unbrick my device using this guide: www . calazan . com/how-to-upgrade-your-att-locked-dell-streak-baseband-gausb1a111231-build-6601-to-android-2-2-froyo/
Just make sure you are on 32bit operating system. I personally did it on 32bit Vista. As I did it a year ago I cannot remember the exact details but thought it might help someone googling for bricked dell streak in the future.
Had to put spaces in link because xda does not allow posting links with so few posts.
maatriks said:
Hello, thank you if you are trying to help me.
What did I do?
I started to with Dell Streak running Android 2.2, wanted to upgrade to StreakDroid GingerStreak 2.4.4.
So I downloaded the files referred to in the linked guide in the section
I installed device drivers and booted into fastboot, everything worked well.
Then I used the commands listed to flash amss.mbn ja dsp1.mbn
Everything seemed okay, device started to reboot... but it never booted.
Current situation:
Device boots sometimes (not every time) until Dell logo and freezes. I am unable to boot into fastboot or recovery mode.
When connected to PC it shows up as qualcomm device and then installs drivers and lists as USB HID device.
I can use W7 64bit and Vista 32bit to troubleshoot the problem.
Thank you if you managed to read it all through and if you have any suggestions, I am all ears. Do not want to make things worse by doing wrong moves.
If you need any extra info just ask, I might have forgotten something useful.
maatriks.
Click to expand...
Click to collapse
yeah i got the same problem aswell but with an a10 ics running device (basically a knock off)
any help would be good
Related
Dear All
I'm a new android user, I just get a new A50 from Australia and try to root it. It's successful with z4root and I try to install Thai font to system. Unfortuantely I did wrong by deleting font folder in the system, therefore I can't run the system again. When I power on, it still have only garmin asus android logo and can't use it again. Does anyone please let me know how to restore or resolve this problem, or I have to throw it away? Thank you in advance.
Cheers!
Winext
Android 1.6 or the new 2.1 Eclair update?
It's a new Eclair 2.1 update, is there any solution?
Connect it to your computer via USB cable.
Using ADB, try this:
ADB REBOOT RECOVERY.
If it works, a yellow triangle appears with the green android guy.
Hit the HOME button. A menu appears. Use volume up/down to move through the options. Tap power to select it I beleive.
Reset/wipe to factory is one of the options.
If you need it, ADB is found in the Android SDK.
If that doesn't work, try calling in to Garmin for support.
Sent from my Garminfone using XDA App
Dear Spazmogen
Thank you for your suggestion, but I'm really new with ANDROID.
I downloaded ANDROID SDK and try to install but it dodn't work.
I use Win 7 64bit, do I need another software to run this command.
If possible, please let me know some previous post that already teach for beginner.
Thank you in advance.
Cheers!
Winext
ADB is a command line tool. But you will have to get Android SDK installed on the computer 1st.
Read the instructions for installing the SDK here: http://developer.android.com/sdk/index.html
ADB commands: HERE.
Interesting. I got into the recovery screen using the Quick Boot app,used the home button to show the menu. The arrows and volume buttons move, but can't actually do anything. Probably related to missing files that are reported in the data/cache/recovery folder.
https://www.garminasus.com/en_US/support/eclair/006-B1130-00.update
official 2.1 update came out today for USA GARMINFONES. Not the A50 Nuvifones elsewhere in the world...
Is the update different from the leaked one?
Sent from my Garminfone using XDA App
I am waiting for an answer to that question myself. I have no plans to change from the leaked version Garmin posted in mid-November.
Sent from my Garminfone using XDA App
Apparently someone did a bit comparison and said they matched. Plus, I tried and it told me it was the same version. On the plus side, I messed up my recovery partition and recovered it using the backups I made of each partition after I loaded 2.1 (dump_image). I made img backups and tar backups of all the files in 1.6 (I am anal about backing up). Good thing because 2.1 doesn't come with flash_image.
I can get into fastboot and the driver loads and stuff, but I get no devices listed when I do fastboot devices command. Next stop is Ubuntu
I know it works,just need to know how to get to it. Btw,I tried both the Garmin fastboot and adb drivers as well as adding the device hardware id's into the android drivers and neither worked.
I also need to find out if there is a similar enough kernel that I can use to get a fully functional recovery mode. I did find out that you can use adb just fine in the stock one and it loads a serial driver as well.
any possible way I could get that backup you made? I apparently didnt save my backup to the pc. And currrently I messed up permissions on my Garmin trying to get recovery working. I cant run the update or anything.
I've just stumbled across this forum post from google, I too am need of fixing my phone. All that is faulty is that the recovery mode has been overwritten with an incorrect one. Is it possible to extract the recovery image and reflash it from the optus supplied Android 2.1 006-B1130-00.update file?
Or is there a way of just getting say Rom Manager to work some magic for me?
Yes, it is possible... would be easier if someone could just use dump_image on a phone that has a working recovery mode and root access. I can provide the dump app and instructions.
Where can I get the Optus update, and are you positive recovery works on it? Does it also have working fastboot?
And to the other poster, which partition do you need? Btw, Rom manager has a permission fix mode. I can get you a tar file if it is the system partition or your choice of img or tar for the others.
And to everyone, after updating to 2.1, do a master clear because a lot of 1.6 apps are left over... duplicates.
Also, odexing all apps speeds it up a lot, with the caveat that you have to re-run the odex.sh file (found somewhere here and modified by me to be more thorough) after every app update or you will get force closes.
Oh I just reflashed the update again, and I got my recover menu back!
I'm not sure if i need any help anymore, but thanks for your offer of help merwin.
By working, do you mean that you can get to it with a hardware key combination and can actually select items?
first of all ,i 'm sorry for my english .my a50 is dead too.i also delet font folder and i use the adb command 'adb reboot recovery'.but the error is device not found. and my pohone can not boot .it stop at the android guy . how can i setup the device..Q.......Q......help me ..pls
garmin-asus a50
i have this garmin asus a50 was running 2.1 after installing a few apps.
tried to reboot and now is stuck on android screen.
tried hard reset stuck on android screen with wipe userdata on top
please help!
garmin-asus a50 dead
yoyoset
i think i have the same problem please let me know of any progress
thank you
THIS IS ALL SORTED...DESPITE HAVING A STOPPED ANDROID BOOTLOADER DEVICE...I DISCOVERED THAT I HAD TO USE THE CORRECT FASTBOOT COMMAND AND NOT THE ONE SHOWN....IE I HAD TO USE fastboot -i 0x413c flash recovery recovery.img
SO I JUST HAD THE ANDROID COMPOSITE ADB INTERFACE RUNNING AND BY USING THE 0X413C IN THE COMMAND IT WORKED...
hope somebody can stop me pulling my hair out!
Ive just taken posession of a Dell Streak. Came with the 1.6 android.
Have successfully done the OTA upgrade to Froyo 2.2. NICE
Successfully rooted using SuperOneClick 1.7 rageagainst the cage and allow nonmarket apps.
Want to put clockwork mod on..so can make full backups and perhaps try a rom or two!!
Have downloaded the latest dell drivers (R291096) and Sync Suite(R290209)...
Android Phone - ADB Inteface drivers all good
But i cant for the life of me get the Android Bootloader Interface going so I can use Fastboot commands.
Have tried XP 32bit and & Windows 7 64Bit with same result...have read lots n lots...but whatever i do i cannot get the Android Bootloader Interface to start....advice please my dear experts..
Baseband GAUWB 1A131921-EU
Kernel 2.6.32.9-perf
Build 12792
Thanks in advance...please dont shout out me ive read stuff all over the place and think this is to do with the official 2.2 =OTA upgrade problem...
Dell keepin me out of fastboot and messing with clockwork etc !!
hi there just been having the same problem for the last 2 days i was told that clock work mod wont work with dell streak ?????? look @ this line http://forum.xda-developers.com/showthread.php?t=840326
to boot in fast mode hold the camera button in and press the power button in @ the same time then tap fast boot mode also i have attached a file witch help me also here is a link what helped me 2 n8 when i bricked it in some way lol
http://streakdroid.com/?page_id=78
thanks for that info...i have just started reading through the streakdroid forums and QDL Tool (with drivers) sections...been at it a few hours...am really tired now...time for a rest before i do BRICK it lol......tried some other dell driver but no joy....usually always stick to my flashing in windows XP..for 32 bit and USB compatability but this is driving me nuts....thanks again....ive read read read and reread the pdf file.....
No worries i know what its like i was up till 2a, yesterday trying to do the same and 2 n8 got things working put a file on and it sort of bricked it and i have just sorted it out 20 mins ago
You have XP 64 bit? Isn't that a bit like a mythological beast OS that only exists in fairy tails and Redmond?
Hope you got this sorted out.
sorry should have read windows 7 64bit..only use xp in 32bit mode...all updates installed.
just trying again now...have uninstalled everything dell / drivers...used USBdeview to uninstall already set Android ports and old Qualcom ports from where i flashed my 3 usb stick, and the 3 drivers and software....downloading, again, the android 2.2 drivers and pc suite from dell.....will try again....i see 2.1 users and 1.6 users seem to have fastboot drivers working and clockwork mod....so will start playing all over again ..... at least the night is young!!!
oh bugger this im tired of going over things..guess the 319 version wont let you have proper drivers to "mess" around with the bootloader..ill revisit some time in the future
oh great decided to start again using a factory reset.....now all i get is process com.android.setupwizard has stopped unexepectedly. please try again..
cant get anything but a blank screen cos the setupwizard did not complete..
groan...
UPDATE 1345GMT.....downloaded Streak_319_12792_21.pkg .... renamed to update.pkg.....copied to root of sd card....booted into recovery and selected update from package.....am now back at 2.2 update and screen working...phew....now to spend rest of day setting it up again lol...wonder why doing a factory reset wont clear the caches?
I'm assuming you have sdk setup? If not give this a go great write up.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Sent from Re-Engineered dInc
no not used the sdk files...just the official update which is downloadable....no probs..
Also..update....i have managed to follow the instructions and install StreakMod even though my Android Bootloader device is still not started..Different commands there than what i was using to try n put CWM on.....ill see how that goes...at least im making progress and have saved the Official 319 update package in case i need it another day!! thanks for comments and help on this irritating buisiness...
ALL SORTED NOW..APPARENTLY TO USE FASTBOOT YOU MUST INCLUDE THE DEVICE CODE SO THAT FASTBOOT KNOWS WHAT IT IS TALKING TO!
IE THE FULL PROPER COMMAND LINE IS fastboot -i 0x413c flash recovery recovery.img
CONSIDER THREAD CLOSED..THANKS TO ALL
Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
So before you comment saying "should have searched first" I have tried every way suggested by XDA, Cyanogenmod devs, motorola and various developing websites. It has not worked once yet.
On 2.3.6 Bell Atrix
Rooted with superuser
RSD doesn't recognize my phone, but it did once upon a time (but wouldn't get the image on then either)
Fasboot commands always come up with errors or not implemented unlock notifications.
Using RSD Lite 5.7
newest moto drivers (as far as I know)
Have all my SDK tools
Have fastboot and the adb...dll files
The two computers I have tried on are a brand new HP running Windows 8 64bit and an older HP running Windows 7 64bit
I have been linked to so many threads that never worked.
Any steps, advice, link to new drivers/programs files ANYTHING would be greatly appreciated.
And yes I have the typical Wifi/BT issues as well as a messed up digitizer, but it isn't bad enough to replace yet.
there's a lot of things which can be done... I found this old link which may help? http://www.droidforums.net/forum/droid-hacks/85578-win-7-rsdlite-detecting-probelms-resolved.html
there's also this http://www.droidforums.net/forum/te...33-rsd-lite-does-not-recognize-my-moto-3.html . One of the main points seems to be making sure that you are running RSD as administrator by right clicking on RSD logo and selecting 'run as admin'
Actually great! Thanks!
Will try then post results.
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