Related
Hey I'm new to the whole rooting thing. But I'm trying to use the one touch root for the Lg Revolution. I have unzipped and installed the drivers. I turned on usb debugging and turned on the Internet connection. Hit the root.bat and it just stopped at the daemon start successfull.
If anyone has any idea what I have done wrong would you mind helping a noob out?
Thanks again
Edit - had to run it in admin.
Help needed rooting LG Revo
Skyfntm said:
Hey I'm new to the whole rooting thing. But I'm trying to use the one touch root for the Lg Revolution. I have unzipped and installed the drivers. I turned on usb debugging and turned on the Internet connection. Hit the root.bat and it just stopped at the daemon start successfull.
If anyone has any idea what I have done wrong would you mind helping a noob out?
Thanks again
Edit - had to run it in admin.
Click to expand...
Click to collapse
I can't find any files for this phone. All the so-called one step application links have expired or been hijacked to media download managers. I realize this isn't one of the newest phones. It was easy to get files for the GS3 but the revos all seem to have expired. Has anyone got the files needed to root and install cmod?
Hi there. I have this Android Phone from china called Dapeng i9800. Its a 6inch MTK 6575 using ICS 4.03. I wonder where can I find the original rom for this and if there is any tweaks for this phone. Sometimes sluggish when using it as it only has 512 ram.
Thanks in advance
i also have the same model! have you rooted this phone? i can't seem to find instructions on how to go about doing this. can you please point me the right way?
thanks
zaraki kenpachi said:
i also have the same model! have you rooted this phone? i can't seem to find instructions on how to go about doing this. can you please point me the right way?
thanks
Click to expand...
Click to collapse
I got the root from here
xxx.slatedroid.com/topic/33144-haipad-i9220-mtk6575-android-40/
1.Please download root file on
xxx.t-kstore.com/4.0root.rar
2.Go to*setting-developer options-click USB debugging
3.Connect the phone with computer,turn on usb device.
4.Click the file you download from the link TPSparkyRoot.bat*
5.Your phone will restart first time,after the phone start finish(until you see the unlock),click enter in the window of TPSparkyRoot.bat.
6.The phone will restart second time,still the same as first time we did.Then start third time,same as we did in last two*times.Click enter,then phone was rooted.
7.You will see two more app was installed in your phone,that mean root phone successfully.
thanks! that was very helpful information! i had some trouble getting windows to connect to my device. kept getting the error: device not found. i suppose it is because i didn't have the proper drivers for the device.
but it is surprisingly easier when done in linux. i just needed to mess around a little with the udev rules.
for the benefit of newbies like me, the instructions provided from that link provided by worldbreaker, i didn't completely follow them. you can choose to install your own superuser and root explorer apk here. in my case, i already installed the Superuser app from the play store even before the rooting process. i also installed Root Explorer separately from the rooting process as well. so no chinese apps for me
now what?
worldbreaker said:
I got the root from here
xxx.slatedroid.com/topic/33144-haipad-i9220-mtk6575-android-40/
1.Please download root file on
xxx.t-kstore.com/4.0root.rar
2.Go to*setting-developer options-click USB debugging
3.Connect the phone with computer,turn on usb device.
4.Click the file you download from the link TPSparkyRoot.bat*
5.Your phone will restart first time,after the phone start finish(until you see the unlock),click enter in the window of TPSparkyRoot.bat.
6.The phone will restart second time,still the same as first time we did.Then start third time,same as we did in last two*times.Click enter,then phone was rooted.
7.You will see two more app was installed in your phone,that mean root phone successfully.
Click to expand...
Click to collapse
anyone know how i can flash clockworkmod recovery on this phone? i can't seem to find any information about this.
Please give me a fresh link to this suggested link
worldbreaker said:
I got the root from here
xxx.slatedroid.com/topic/33144-haipad-i9220-mtk6575-android-40/
1.Please download root file on
xxx.t-kstore.com/4.0root.rar
2.Go to*setting-developer options-click USB debugging
3.Connect the phone with computer,turn on usb device.
4.Click the file you download from the link TPSparkyRoot.bat*
5.Your phone will restart first time,after the phone start finish(until you see the unlock),click enter in the window of TPSparkyRoot.bat.
6.The phone will restart second time,still the same as first time we did.Then start third time,same as we did in last two*times.Click enter,then phone was rooted.
7.You will see two more app was installed in your phone,that mean root phone successfully.
Click to expand...
Click to collapse
Hi everyone,
I'm trying to root my phone and this file xxx.t-kstore.com/4.0root.rar is no longer available. I hope that someone can plase give me a copy of it or at least let me know where to find it.
Thank you.
Dapeng i9800 firmware found but links dead! Nead russian help!
Hi, I'm from West-Germany and got into trubble:
First of all, I used A Dapeng I9800 for more than 2 years without any problems!
Then, I got my Winter-Blues and cleaned cache from recovery mode!
After that the device didn't boot, because it wanted a passwort to use the cache, which wasn't set. No prob so far!
The solution I found was, that I have to set back to factory default.
But I took off the battery while it was formatting.
Yes, shame on me, I wasn't patient(!) thats my fault!
Now, I've got two new problems:
Is the EMMC bricked?
My russian isn't good enough to enter this forum: china-iphone.ru
to ask these two guys:
BBV1962 http://forum.china-iphone.ru/member12688.html
and:
designed http://forum.china-iphone.ru/member201062.html
via PM, for a working link they posted for my device in their posts on this sides:
http://forum.china-iphone.ru/n9880-6-0-480x854-1-2ghz-android-4-0-3-2x3000-mah-t21999-120.html
http://forum.china-iphone.ru/n9880-6-0-480x854-1-2ghz-android-4-0-3-2x3000-mah-t21999-140.html.
The MTK6575-77 6" original firmware ROM below the posted picture is what I mean.
I hope, someone can get a link for me AND it is not worthless, because the EMMC is broken, as my own backup dosn't work.
Maybee you can get the info hww to flash back exactly, because I get an 4010 format error with the spflash tool.
Thanks a lot
Hello, i just recently purchased an Allview P5 smartphone, it's really cost efficient but recently i started getting some problems because the phone is not rooted and i was wondering how to root the android 4.04. i tried the superoneclick 2.3.3 and installed adb and something from java, bu when i rung the program superoneclick the program just freezes and it's not responding. any suggestions or guides that i should follow?
best regards
Chris
Try root for HaiPai I9220. For me it works.
Having the same problem here, Superoneclick freezes on step 7 iirc.
HaiPai didn't work for me either
So that: http://forum.xda-developers.com/showthread.php?t=1923764
There you will find this: http://www.mediafire.com/view/?othd1gf76pa97zg
It is 100% functional, but need more knowledge and skill.
Ok, I came a lot further this time, but still stuck.
As soon as I let Cygwin `patch` the recovery.img, it does the patching and stuff, but it doesn´t create a new recovery.img for some reason..
If you check page 13 of that PDF manual: I get all the same messages in Cygwin, except for that "Repacking" bit.
Any Idea why it isn't repacking?
Losing my nerves a bit because of Cygwin, what a horrible program to get to work properly. Installation went on beyond 100%, till about 2000% and then just started to count further in negatives >____<
You must have installed 7-zip archive program.
SuperOneClick should work for this device. You may try this:
1) unmount the sd-card, turn ON usb-debugging
2) turn OFF usb-debugging
3) connect device to PC
4) click "Root"
5) when "Waiting for Device" appear turn ON usb-debugging
6) when "Starting ADB Server..." turn OFF usb-debugging
7) then turn it back ON
8) and back OFF
9) repeat this while "Waiting for Device" appears again.
@Stovka: I have 7zip installed, the unpacking/extracting of the recovery.img goes fine in Cygwin, but for some reason it just skips the repack part.
@AndreyETO: As soon as I disable debugging mode, superoneclick stops the procedure, so I didn't get far with that
So sorry, I don't really know what is the problem...
It was all ok for me - the one problem was that I had not installed 7-zip, but after installing it worked exactly according to instructions.
If it were successful: after recording recovery.img to the phone is first necessary to go into CWM mode (no run phone) and install the root file attached. End CWM recovery mode is classically done by clicking on "reboot system now", but after the first time there appears one more option (just I don't know what name), which must be confirmed! Otherwise, when you restart the phone again, then will be loaded the original file and the recovery process must be repeated - upload modified recovery.img and then root file via CWM.
Found another way to root, and it worked
I used the method in this topic: http://forum.xda-developers.com/showthread.php?t=1886460 )I used the current newest version:V15)
The first time it didn't work, but after rebooting the phone and trying again it was succesfull
Anyway, thank you guys for trying to help.
Flapperbol said:
Found another way to root, and it worked
I used the method in this topic: http://forum.xda-developers.com/showthread.php?t=1886460 )I used the current newest version:V15)
The first time it didn't work, but after rebooting the phone and trying again it was succesfull
Anyway, thank you guys for trying to help.
Click to expand...
Click to collapse
Hey, i also tried this, and it didn't work, after clicking on restore that the device restared and than on the comand promp console it said error: device not found, i tried repeating the process several times but it didn't work, any other ideeas?
Neither of those above work for me either.. So... any other suggestions?
Confirmare
sics3th said:
Hello, i just recently purchased an Allview P5 smartphone, it's really cost efficient but recently i started getting some problems because the phone is not rooted and i was wondering how to root the android 4.04. i tried the superoneclick 2.3.3 and installed adb and something from java, bu when i rung the program superoneclick the program just freezes and it's not responding. any suggestions or guides that i should follow?
best regards
Chris
Click to expand...
Click to collapse
( for P5 allview mtk6577 4.0.4 ics2 )
Search this Root_with_Restore_by_Bin4ry_v15.7 on the forum. It works like a charm (both on linux and windows ).
It use restore feature on the phone.
The link is here http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/attachment.php?attachmentid=1398011&d=1350123242
Anyone found a safe way to root this phone? Or maybe a custom rom for this one?
I think it is a great phone which should has a place into xda forum
Root_with_Restore_by_Bin4ry_v15
i have downloaded version 15 of this, because v17 for some reason did not worked...
so go ahead and enjoy.
Flapperbol said:
Found another way to root, and it worked
I used the method in this topic: http://forum.xda-developers.com/showthread.php?t=1886460 )I used the current newest version:V15)
The first time it didn't work, but after rebooting the phone and trying again it was succesfull
Anyway, thank you guys for trying to help.
Click to expand...
Click to collapse
i can confirm that this works.
now, can anyone tell how i can make a nandroid for this phone? couldn't find any image to boot with so i can see the partitions and use linux dd
U all can use this metod:http://forum.xda-developers.com/showthread.php?t=1886460 for rooting P5 Mini.
And watch this video tutorial:http://forum.xda-developers.com/showthread.php?p=33470626#post33470626
I rooted my P5 Mini with "Root_with_Restore_by_Bin4ry_v15" and it works fine.
works for P6 also
Flapperbol said:
Found another way to root, and it worked .
Click to expand...
Click to collapse
Same experience on Allview P6 Stony (P6_0201_V1179 software build). This method works for me - similarly I had to run the script (and the reboot cycle) 2x before it had an effect.
As pointers for others, before you try this method you need to make sure you have ADB drivers installed. Trying to install stock google drivers didn't work at all for me, what worked for me was installing latest PdaNet drivers (pdanetZ350.exe) from here: junefabrics.com/android/download.php *
Don't forget to install OTA Rootkeeper app afterwards and run it once - hopefully saves you the hassle of rooting again if the P6 should receive an incremental update.
Enjoy, thanks Flapperbol!
(*= sorry Im not allowed to post links)
Version 18 also works
Just to let you guys know that version 18 of Root_with_restore works. I just the ADB drivers from the PDAnet install (which I cancelled after the drivers were installed) and the phone is now rooted!
Does anybody know how to get rid of those ugly allview icons? I hate those things.
neelz said:
Just to let you guys know that version 18 of Root_with_restore works. I just the ADB drivers from the PDAnet install (which I cancelled after the drivers were installed) and the phone is now rooted!
Does anybody know how to get rid of those ugly allview icons? I hate those things.
Click to expand...
Click to collapse
u can install a new home launcher.i use nova launcher 2.0 prime and u can download icon package and install in nova
The Problem:
Phone stuck on LG logo screen with "Security Error" written underneath.
How I Got Here:
Rooted and installed recovery using apks found in these forums. I successfully restored a CWM backup zip found on these forums. Next, I decided to try flashing a ROM. SuperLuminal gave me a "Status 7" error, but when I checked over the thread, I realized that the P769 was not specifically mentioned as a compatible device. So, I decided to give PACman ROM a try, but got the same error.
I googled "status 7 error" and found a guide for fixing this (removing "assert" line in updater-script line). I was aware of the danger in doing this, but since PACman ROM stated "P769" right there in the title, I gave it a shot. Now I'm stuck with the "security error" screen.
What I tried:
I could no longer get into recovery, so I thought restoring it might be a good idea. I tried to use fastboot using the method described in this thread (http://forum.xda-developers.com/showthread.php?t=2310569). However, I quickly realized that I didn't know how to put the phone into a "download mode" like most other phones I've worked with.
I then tried B2CAPP, but phone couldn't be detected. Went and learned how to get into s/w upgrade mode, ran recovery and got an error message saying "updating is not possible any longer due to a fatal error..."
Next, I tried uninstalling all LG software and rebooting PC. Installed LG PC Suite found here (http://en.kioskea.net/download/download-19186-lg-pc-suite), allowed the program to update to latest version. Then tried to run Emergency Firmware Recovery, which opened a window asking if I want to run LG Mobile Support Tool. I clicked OK and was taken to an app that looked exactly like B2CAPP and gave me the same error as above.
So in conclusion, I can only access two screens: the LG logo security error screen and the s/w upgrade screen. Neither appears to give me access to fastboot/adb nor to LG's recovery tools. Am I permanently bricked or is there a way out of this mess? I've been searching these forums extensively and have tried every method I could find. I'm out of options, so I'm kinda freakin out here. Can anyone please help me figure out what else to try?
You did some studying for sure, but you needed to do some more before jumping in.
1. http://forum.xda-developers.com/showthread.php?p=41768774
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sent from my LGMS769 using xda app-developers app
Kuma82, I can't thank you enough for your helpful response.
Here's a shortened version of what I did, in case someone out there finds themselves in a tough spot like I was in:
1. Installed OMAP drivers using method described in link above (right-click on device in Device Manager, manually install driver, etc.). Fastboot worked after this
2. Using Lelus' Fastboot, flashed option 6 (load JB xloader and uboot). This gave me an inverted purple LG logo that still said "security error"
3. I think tried to use fastboot to flash the p4_769.img recovery file. No change. Loading up s/w upgrade mode and the LG Mobile support tool (B2CAPP) was no use (stuck at 15%, no connection to phone).
4. Once again, using one of the links above, I downloaded 3 .img files and proceeded to erase uboot, boot and recovery and flashed those .img files instead. When I rebooted the phone, I got the regular LG logo for a second, then a white flash and then a smaller LG logo with "security error"
5. Now, I installed the LG United mobile driver, went into s/w upgrade mode again and ran the Mobile tool. Got the "updating is not possible..." error again
6. Searched for the offline flash fix method and followed it step-by-step, word-for-word. Phone works again!
I'm pretty sure I could have just done steps 1, 4 and 6 and achieved the same result.
Hope this helps someone, and thanks again Kuma82!
I've had this happen to me twice and was able to get out of it really easily. Basically, I just have my desktop set up for offline flashing and my laptop for online. Just popped into S/W update mode and plugged it into the laptop, started the b2c app, clicked on the "recovery phone" option, and went for a snack. Fixed when I came back.
No problem, glad I could help.
Now that you know how to use fastboot, you are pretty much ready for everything.
It took me a couple of tries to get it running.
Use the new root method, http://forum.xda-developers.com/showthread.php?t=2338816
If you plan on staying on stock, get the cwm for locked bootloader, but first get this busy box http://forum.xda-developers.com/showpost.php?p=43395803&postcount=260
Then this cwm
http://forum.xda-developers.com/showpost.php?p=41613095&postcount=220
Sent from my LG-P769 using xda app-developers app
kuma82 said:
You did some studying for sure, but you needed to do some more before jumping in.
1. http://forum.xda-developers.com/showthread.php?p=41768774
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Dear, Kuma82!
Thank you very much fot your instruction! It really saves my LGP768 from "security error"! I follow 3 steps and it works, GREAT!
Thank you again and this forum too!
Please help! Bricked LGMS769 (P769)
Solved. The LGMobile Support Tool needed to run on a different computer. It worked when I put the phone into SW Update Mode (press up volume key and plug in USB) and then ran the LGMobile Support Tool.
By the way, this is how I got the phone recovered after it was booting to the small LG logo with the "security error" message as mentioned in Step 4 above.
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