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.
Related
OK.
I think I screwed up - BAD.
I was attempting to unlock the bootloader. During the process, I accidentally did a factory reset. Its easy to do. I watched myself do it nearly in third person and was horrified.
I cannot get it to be recognized via ADB.
During a normal boot, it gets to the LG Setup Wizard but it will not complete. It crashes and tries again.
I can get it in S/W Upgrade mode.
Using the LG Mobile Support Tool without the hosts file fix, it gets stuck on the second phase being "Analyzing phone setting..."
With the hosts file fix, The Phone Update tool gets stuck at 15% and in the error field below _isPhoneConnected(0)
Updated USB drivers to the latest. 5.10
Ideas?
babcocca said:
OK.
I think I screwed up - BAD.
I was attempting to unlock the bootloader. During the process, I accidentally did a factory reset. Its easy to do. I watched myself do it nearly in third person and was horrified.
I cannot get it to be recognized via ADB.
During a normal boot, it gets to the LG Setup Wizard but it will not complete. It crashes and tries again.
I can get it in S/W Upgrade mode.
Using the LG Mobile Support Tool without the hosts file fix, it gets stuck on the second phase being "Analyzing phone setting..."
With the hosts file fix, The Phone Update tool gets stuck at 15% and in the error field below _isPhoneConnected(0)
Updated USB drivers to the latest. 5.10
Ideas?
Click to expand...
Click to collapse
Look for adb and fastboot install directions. This is what I did:
http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
Good luck!
Nathan.7118391 said:
Look for adb and fastboot install directions. This is what I did:
http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
Good luck!
Click to expand...
Click to collapse
The attachment linked to in that article is missing. The one at "HERE".
I sent a private message to shrucut to update it. The instructions for the post you linked to didn't align with omap4boot-for_optimus-v1.21 that I found at the original post of the article you linked to.
The one I sent you was for the fastboot which should send you to another for omap4boot those ate the only ones I use.
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
Fastboot Problem
I got a proper version of the fastboot script for L9.
I get this when attempting to do fastboot.
usb_read got: 0, expected: 4, errno: 31
usb_read got GEN_FAILURE - got: 0, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
It wont continue
It won't continue because you need omap4boot installed first. Dude read everything or you still won't succeed. You have to follow directions. Good luck.
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
Post OMAP4BOOT Install
Hey!
I finally got the OMAPFlashInstaller dated 3/9/2011. I installed the driver on XP 32 bit.
I get the same error as above.
Any thoughts?
Will a kind person do some more in depth troubleshooting via join.me?
I just cant get my phone unbricked as fastboot will not recognize the phone. (My XP box does have USB 3 ports but I am not using them.)
Thanks!
Screenshot
Its the same as
http://forum.xda-developers.com/showpost.php?p=41960008&postcount=34
babcocca said:
Its the same as
http://forum.xda-developers.com/showpost.php?p=41960008&postcount=34
Click to expand...
Click to collapse
Please try Lelus fastboot, http://forum.xda-developers.com/showthread.php?t=2292828
And you can find thread about it in forum. You need to install fastboot driver, in device manager before and after connect usb cable, to make fastboot works.
Wow!
I just found a greyed out device driver in "Software Devices" for LG P769. I deleted it. I now see the greyed out LG P2 device in Other Devices AND I just need to enable unsigned driver installation.
Its alive!
Used option 5 in the Lelus script.
Then the LG tool saw it without problems.
Loaded 20f.kdz
Hey all,
So I successfully rooted my phone, and then I was going to go into recovery reboot mode to install a downloaded rom. I'm not sure what did it, but on that restart I got LG Security error. I first attempted on three different computers to do LG Mobile Support Tool. It stopped everytime when it was going to begin downloading the files. I'm pretty sure if I still had the Security Error image, I would be fine, because I now know of ways to bypass the LG Support Tool, and edit the host file, and then get it downloading.
Either way, in my research after no success with LG Mobile Support Tool, I came across Fastboot. So I got fastboot, I got the drivers installed, but I'm pretty sure my problem was, on the command prompt screen when Fastboot asks' you questions I said yes on them. I believe this is what caused my phone to have the black screen. It will not go into S/W upgrade mode now. It will not do anything, just black screen. I found a tutorial over on Android Forums, and with using Fastboot, I was able to sucessfully flash "p4_769.img" According to that tutorial, after doing that I should have a dead android guy logo, and then just be able to hard reset... but that didn't change anything. Still have the black screen. Still won't go into S/W Upgrade mode.
Now according to what I've read, the next step would be to flash KDZ Afresh...I've looked for this, whatever it is, specific to my model phone, but I can't find anything. If anyone else has any ideas, I would love to hear. I'm so frustrated at this point. Very much appreciate any help. Thank you.
It sounds like now what I have to do is, using how I flashed that recovery img, I first should flash the x and uboot.bin files to my phone. Then I will be able to get into S/W mode, and then restore from there. I just have to find these bin files. I don't have a friend or anyone nearby with the same phone as mine that can:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
with theres.
Hi dlipford370, you could try this http://forum.xda-developers.com/showthread.php?p=51206080
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
Hey guys, I seem to have soft-bricked my E970 (which was running stock ICS) in the process of trying to get the bootloader unlocked using Freegee's ZIP method.
I was able to get into Download Mode, so I got LGNPST installed and flashed a TeenyBin, but 85% through the process (after the reboot) I got an error from LGNPST about the device disconnecting along with a Windows "USB device not recognized" notice.
I was able to get reconnected and complete the flash (100%), but my device still didn't get past the LG logo. I figured the interruption might have screwed the flash up, so I tried it again, but I got the same error, only this time I wasn't able to complete the session, and now my device isn't being detected in LGNPST at all
Am I SOL? I can still get into Download Mode, and my device is still showing up in Windows. Any suggestions? What are my options if I can't get my device recognized in LGNPST anymore? I dug around on the forums but couldn't find a solution.
Quick update: I tried following this guide to unbrick my E970 without having to use LGNPST, but am unable to download the KDZ file for my phone since I don't have a way of getting the serial number. I got the IMEI from my carrier but no luck there either.
Anybody?
Bump
ct456568 said:
Bump
Click to expand...
Click to collapse
Finally figured it out with some help at the freenode IRC chat. I reinstalled LGNPST from scratch on a clean Windows 7 install and LGNPST picked up my phone like a charm. Must have been some kind of driver issue. I ended up flashing the Teenybin ALTbin and then the latest stable CM10, along with a hybrid 84/27/84 radio to fix some call issues.
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
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!