Related
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
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Twink225 said:
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Click to expand...
Click to collapse
It's hard to understand all of that but it sounds like perhaps you deleted some bloat that you should have, you sound like having driver issues, and possibly wrong TWRP version. Need to clear that up and then reinstall the stock Disney ROM.
I'd start here it has all the tools/TWRP/ROM's you need.
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
So sorry hun, toshiba is driving me nuts and I'm having a bad add moment or three lol. I read about you retiring. so I tried hard not to bother you. now I'm really confused. I've read your nabi2 general info post and even ran across your youtube vids. the problem is I'm not familiar with adb. & the included NabiLabGUI drivers, win10 either fails to finish saying it was interrupted. or it just won't install the 32 bit drivers, I thought I as suppose to use.
The 64bit driver 3 out of 4 install but, I can not get the Google Inc, driver to install properly even with the inf file. (ie the android_winusb.inf ) it says the system can't find the file, it can install the older versions from NabiLabGUI or naked drivers. but doesn't show in add/remove and it still won't detect the tablet most of the time lol.
Pda also has conflicts with adb, I got the nablab disney option to detect it but still failed to install twrp saying it can't find devise and I noticed in device manager 2 driver problems that will not let me update manually or they go missing if I try to force windows to reinstall. (device descriptor request & set address failed)
I must be missing something big, I also tried the 15sec and minimal adb. I assume because the tablet won't fully boot up, windows doesn't know what to do with it. when I tried different cables. windows 10 enterprise won't play nice at all now. so I will format again to be safe but lost what to try next.
I guess my questions should be is there a work around or a full inf version of the newer drivers for NabiLabGUI2015 that might work with this demonic disney nabi2.
&
Is NabiLabGUI compatible with .net framework 4.6 advanced services? (I may have to downgrade o/s. on the nabhacks site is says .net 4.5 is a prerequisites.) I don't know much about the app but saw 4.6 comes preinstalled, I can't install 4.5 yet, I saw there has been compatibility issues. and it won't let you revert versions easily if at all.
I'm to tired of this tab to think straight anymore and so grateful any help I'm in way over my head here.
Update
I lost the battle but I won the war, now google & supersu are messing with me as usual but it boots so I win lol :victory::silly:
So I scoured this website and Google search to find the answer to my dilemma but no luck. Here's what I have going on. I recently got this tablet for 99ยข from AT&T. It was unbearably slow so I decided to root it so I could get rid of some of the bloatware. Used Kingroot to aquire root. That went fine. Next I wanted to install SuperSU. That also went fine. Used root checker app and everything worked great. Root access with SuperSu. Then I needed to update the binaries so I did that and it was successful. Now I know I was supposed to uninstall the Kingroot and associated installs that came with it however, after the binaries were updated and before I had a chance to remove them, the tablet rebooted. When it started up, the LG screen came on as usual and the the AT&T ball screen came on. The ball rotated about 2 times and then froze. I rebooted a few more times and the same result. I don't know if this issue was caused by me not uninstalling the Kingroot stuff. I tried a factory reset but that doesn't help either. I can get it into download mode but I can never get the USB mtp driver to download so it won't recognize it on my Windows 7 desktop. Even if it would recognize it, I have no firmware to use with it. I tried using the LG flashtool, LG mobile support tool, LG bridge etc. I am not a noob as I have rooted many devices and am familiar with installing custom roms through recovery or using fastest and command prompt. If I could somehow find the stock firmware for this somewhere I might be able to get it up and running again. I just want to know what my options are and if there is anything that I can do. Any advice will be greatly appreciated. Thanks in advance.
Hi,
I'm brand new to this forum and my name is Jessy, and it's my pleasure to be here!
I recently bought this AT&T GoPhone (for around $29) at Walmart, and I was following this guide to allow me to use my SD Card as an internal memory storage unit for my phone, but I found out that I need to unlock the Bootloader, install TWRP, SuperSU and Link2SD apps to the SD card and my phone. Since this smart phone is similar to the Idol 3, could I use this method to unlock the Bootloader for my phone or do I have to try a different approach?
I appreciate your time and I look forward to contribute further to these forums! Thanks again!
-Jessy
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Merazomo said:
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Click to expand...
Click to collapse
Hey I used this app to remove king root and my phone bricked do you know how to fix?
ipodhero said:
Hey I used this app to remove king root and my phone bricked do you know how to fix?
Click to expand...
Click to collapse
My Alcatel Ideal 4060A froze a few times during the removal of KingRoot, but all I did was: turn off the phone, remove the battery, and finish the procedure once the phone was on. The phone was only $10 on Black Friday, so you could say it was only an experiment on my part. Unless it's a really good phone, where you can go to the manufacture's website and download the original firmware and install it through your PC, there's not much you can do to unbrick a cheap phone that is practically unknown.
Merazomo said:
Mario
Click to expand...
Click to collapse
Thank you Mario for your help! I'm having a little trouble having my phone being recognized by Kingroot, although I have ADB enabled from the developers option, it seems not to pickup my phone still. I'm still trying though and I'll let you know if I get it to work properly, and perhaps document my mistake so others following this post who happen to have the same problem could know what to do.
- Jessy
*UPDATE*
Just wanted to update that I found out what was my mistake, which is a really simple and basic mistake, I apologize!
What I did was that after I had enabled ADB through my phone, it was already connected to my PC right after I had downloaded Kingroot, so my solution here was simple. I turned off my phone first, then I turned it back on while still connected with Kingroot still running then Kingroot finally read my phone and it rooted it as you outlined. Thanks again for your help, it is too valuable for me!
Here's the guide that I'm following so that I could install more apps to the phone through my 64 GB SD card if you guys were interested, to make the phone more useful, and I also installed my obama phone SIM card on it as well (from lifeline wireless, because hey why not? )
Here's the link to add more internal memory to this phone
www
.howtogeek.
com/114667/how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card/
shushi_boi said:
Thank you Mario for your help! I'm having a little trouble having my phone being recognized by Kingroot, although I have ADB enabled from the developers option, it seems not to pickup my phone still. I'm still trying though and I'll let you know if I get it to work properly, and perhaps document my mistake so others following this post who happen to have the same problem could know what to do.
- Jessy
*UPDATE*
Just wanted to update that I found out what was my mistake, which is a really simple and basic mistake, I apologize!
What I did was that after I had enabled ADB through my phone, it was already connected to my PC right after I had downloaded Kingroot, so my solution here was simple. I turned off my phone first, then I turned it back on while still connected with Kingroot still running then Kingroot finally read my phone and it rooted it as you outlined. Thanks again for your help, it is too valuable for me!
Here's the guide that I'm following so that I could install more apps to the phone through my 64 GB SD card if you guys were interested, to make the phone more useful, and I also installed my obama phone SIM card on it as well (from lifeline wireless, because hey why not? )
Here's the link to add more internal memory to this phone
www
.howtogeek.
com/114667/how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card/
Click to expand...
Click to collapse
No problem. I'm glad you got the phone rooted. I originally picked up the phone to use as an MP3 player, so I removed most of the unnecessary stock apps with "System app remover (ROOT)", but now that I see how good the phone is (at that price), I plan to use it as a backup phone. It even has a notification LED light for unopened messages LOL; anyway, good luck.
My Alcatel bricked too using this method stuck at boot logo and does nothing... Any fix?
Thanks for writing rooting method for Alcatel 4060a Ideal Pop445. Need some help
Merazomo said:
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Click to expand...
Click to collapse
I've been an iPhone user for many years, I'm almost new to android. I have unlocked the bootloader from the hidden developers options in the settings app. I haven't found any thing useful to root my new Alcatel Ideal 4060a (Pop 445) (at&t unlocked). There are tons of bloatwares and many apps that I can't transfer to sd card. I hope you two can help me out here as I don't want to brick my device.
Question 1: Do jessy did something wrong(regarding your given steps to root) that makes her device rooted OR she has just been lucky? Because someone just posted that he/she has bricked his/her device.
Should I go ahead and try my luck with your method you there would be some advice you would like to give?
Question 2: If I would be able to root this device, would I be able to install Android 6.0 Marshmellow?
Don't root this yet
Source thread:
http://forum.xda-developers.com/android/help/alcatel-ideal-4060a-bootloader-custom-t3476422/
c627627 said:
Same answer ValdamarlSaCOCK was given, goes to you too, feel free to ask any questions:
http://forum.xda-developers.com/devdb/project/dl/?id=21707
Click to expand...
Click to collapse
Rooted already.
faxanidu said:
Don't root this yet
Click to expand...
Click to collapse
I have rooted with Kingroot 5; latest windows version on their website. Now I'm working on replacing it with Supersu or Supersu-me.
I think there always be some solution as far as you are seeing something on your phone's screen.
Just a note from another user with an Alcatel Ideal 4060a... (got for $10 from Best Buy on Black Friday)
Don't try using King-O-Root, then proceed to install Super SU from Google Play. It works that first launch, but on rebooting...
It's permanently bricked. And yes, I tried everything, including adb, recovery (doesn't have an option to flash a rom), from-pc flashing (wouldn't connect/wasn't recognized by adb or the other tools), fastboot (wouldn't launch), etc.
I don't know about the alternate Kingroot app, though. That probably works as some people have said it does for this model.
I was stupid and assumed King-O-Root would work as well, since it seems pretty generic and worked for another phone. I've learned my lesson and will now only follow guides for the specific phone model I have.
Why am I even writing this if it's a different rooting app? Cause I spent 6 hours just to end up killing one of my phones, and this is my best attempt at feeling like there was some worth to the waste. (the chance of preventing someone else the misfortunate, and just ranting)
Anyway, I'm going to bed. (So annoying because I only barely was brash enough to go ahead without a phone-specific guide--was on the fence, but landed on the unfortunate side) Argh! Argh! Argh!
Venryx said:
Just a note from another user with an Alcatel Ideal 4060a... (got for $10 from Best Buy on Black Friday)
Don't try using King-O-Root, then proceed to install Super SU from Google Play. It works that first launch, but on rebooting...
It's permanently bricked. And yes, I tried everything, including adb, recovery (doesn't have an option to flash a rom), from-pc flashing (wouldn't connect/wasn't recognized by adb or the other tools), fastboot (wouldn't launch), etc.
I don't know about the alternate Kingroot app, though. That probably works as some people have said it does for this model.
I was stupid and assumed King-O-Root would work as well, since it seems pretty generic and worked for another phone. I've learned my lesson and will now only follow guides for the specific phone model I have.
Why am I even writing this if it's a different rooting app? Cause I spent 6 hours just to end up killing one of my phones, and this is my best attempt at feeling like there was some worth to the waste. (the chance of preventing someone else the misfortunate, and just ranting)
Anyway, I'm going to bed. (So annoying because I only barely was brash enough to go ahead without a phone-specific guide--was on the fence, but landed on the unfortunate side) Argh! Argh! Argh!
Click to expand...
Click to collapse
Any solution for this? I want to replace King-O-Root with Super SU.
None that I know of.
I have another Android phone that I was also trying to get root on, and that one gets it temporarily using King-O-Root as well, but I'm too paranoid to try to make it permanent on that second one. Losing both my Android phones would be too painful.
If anything, I guess try the KingRoot program, from the pc, and then use the "SuperSU Me" app, as the person on the first page of this thread described. That way worked for at least one person apparently. (though the poster just after said it bricked theirs, so beware)
By the way, is your root from King-O-Root temporary (till restart) or permanent? I installed Super SU during the same launch I used King-O-Root, so I never got to see whether King-O-Root itself would have worked as a permanent (though non-ideal) solution. (I know that on my other Android phone it's temporary)
King-O-Root = Bricked Phone
KingRoot5 = Root Successful + it is possible to replace with SuperSU
http://forum.xda-developers.com/devdb/project/dl/?id=21707
Recovery Retrieved!
I was able to pull the recovery from this phone. Can someone make TWRP for this device using the stock recovery?
Here is the actual recovery image file that I pulled:
(Forgot my old XDA password, had to make another account. Can't post links)
https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing"]https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing
Ch3if-0f-Skull5 said:
I was able to pull the recovery from this phone. Can someone make TWRP for this device using the stock recovery?
Here is the actual recovery image file that I pulled:
(Forgot my old XDA password, had to make another account. Can't post links)
https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing"]https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing
Click to expand...
Click to collapse
Did you manage to unlock the bootloader? If not then you cant flash anything and building twrp would be useless.
arolust said:
Did you manage to unlock the bootloader? If not then you cant flash anything and building twrp would be useless.
Click to expand...
Click to collapse
I pulled the boot file. Could someone maybe look at that? I cannot boot to the bootloader.
I could try to flash_image twrp to the recovery and try that.
I got this phone on black friday, shortly after I got root with kingroot 5 pc and it was all great, however I got greedy and replaced kingoroot with supersu :silly:. First reboot and it goes into boot loop. Now its been sitting in a drawer. I think that purify deleted some app it looks at boot.
It looks like the simplest way to get a restore is 'IF' TCL/Alcatel does an update, someone intercepts the signed zip file, then that zip file could be distributed and used with the stock restore.
Hopeful everyone here can work a better solution... thanks for all your hard work everyone.
yes u r right
many time happen with me, Happen with me on asus KA10, But i got fastboot update img lucky. hope that u will get Fast boot image some day or we may able to get recovery for this device . in that case your your phone may start working
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
the core question "How to unlock Alcatel Ideal 4060A (walmart) Bootloader?" still unanswered. Kindly help.
My phone is rooted, but not able to unlock bootloader so far ...
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!!!