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
I'll try to get as straight tot he point as possible.
Been using my Mobile one touch pix 7 for a little over a year and always installed Ota updates. Well I rooted the tablet not too long ago, forgot which method I used, but was working fine.
an Ota update came through and totally forgot it was rooted, and tried to install it, at which point the whole tablet got bricked.
It ended up in recovery, and I selected due to failure, to format and wipe the data.
Anyhow, The unit will stay at the boot screen for a while then show command error and then show the recovery screen, my only options are:
reboot
update from sd card
update via adb
update via memory
reboot Bootloader
power off
Well I've tried updating by downloading system images via adb, they return a verification error.
I've tried using adb side load to try to install an Ota update file I found for it, returns a verification error.
I cannot get into download mode, fast boot mode I think does not work as windows reports 3 android devices, but the mobile update software cannot see anything, and fast boot gets stuck at waiting for devices.
I suspect the tablet is for lack of a better description totally bricked and just a paperweight.
I am at a loss of what to try from this point. I'm sure wiping the data after the failed update killed it completely but not sure.
Anyone have any guidance here? I've downloaded a few images from the web I found that say they are for this tablet model, but still getting verification error.
Is there any flashing software I can get that may be able to access the tablet or can I copy a file to the scared and have it try to run an update from there. I don't care if it is rooted or not, just want to get it usable again.
I can run Mac OS, windows 10, windows 7, windows xp, or even have no issue getting a linux version going, whatever will work best for this I can use it. windows 10 I was able to manually add the drivers but windows 7 is not letting me do it the same way. I can connect via adb sideload only, no other adb functions seem to work.
I'm not a total news when it comes to custom rooms, as I have done it with another tablet, and an android car radio, but those were pretty straight forward and bootable so never ran into a brick issue yet.
I have a feeling this is toast and I hope that is not the case.
If anyone here can help out, I would appreciate it.
Thanks again....
Need help here to. Been searching with no luck. Any my issue is.
Rooted kingroot, flashed twrp with flashify and now I'm stuck on twrp. Been searching for any custom stock rom. I forgot to unlock the bootloader but I did enable usb debugging (i didn't see any oem options).
Any k 28532Jonsunf of help would be greatly appreciated.
This sorta happen to me. I rooted pixi 7 with kingroot, and was able to delete a lot of bloatware. However, when I was using lucky patcher it pretty much messed up the play store. But it was fine. I could download stuff through the Internet. But sooner or later I needed to fix it. Tryed a lot of ways but it didn't help. So I factory reset the tabletand now im stuck at the Setup Wizard. It just won't let me let me through. I thought its was over, but then I get a message saying there is an update available. So I download it and installed it. But all I get at the end is error. So now I need to flash it with stock. I tried the img. too, but it doesnt show up in the recover menu. If you found a solution please tell me
Can anyoonneee help me find a good Custom Rom for the alcatel one touch pixi 7 (9006W)? Sucks that there's not much info for this device (probably cause the device sucks lol) I'm running on lollipop 5.0.2 and am not able to get OTA update due to rooting. Unrooting didn't help. It seems only answer is custom rom but don't want to risk bricking it as I don't have a computer at home. Also, I am new to this so if anyone can share some insight, I'd be eternally grateful
P.s
It's a t mobile device but I only use it on wifi.
Am using kingroot.
Have never installed a custom rom
****ing device is 8 gigs. 1 gig Ram.
Is it possible to get Nougat?
Help meeee lol
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 ...
Hello XDA Forums,
I have been a guest on the website for a while now when looking for android knowledge and I usually grasp a good amount of whatever I am trying to accomplish. However, the issue I am currently having I feel is considered IMPOSSIBLE to fix and I want to confirm that by this community.
Phone: Blu
Model: NEO XL N110U
Android build version: 6.0
Custom build version (It’s a stock a downloaded, ill explain in a sec)” BLU_N110U_V10_GENERIC_MARSHMALLOW 05-08-2016 16:30
What happened is that about a year ago or so I updated the android version from lollipop to marshmallow using the OTA update (which is the wireless update). Worst decision ever as I found out that this update gave me 4 specific viruses that sends my information over to a Chinese server. Here are links on the virus:
https://www.droid-life.com/2016/11/15/blu-security/
https://blog.malwarebytes.com/cybercrime/2016/11/mobile-menace-monday-adups-old-and-new/
https://android.gadgethacks.com/new...be-affected-by-adups-chinese-spyware-0175014/
With this problem, I thought “I can just root my device and delete the files… right”? I never rooted a device before, but I have jail broken iphones, modded psps, and ds so I felt like this would be easy……Turns out its impossible if you already updated to that wireless update with marshellow. I also tried unlocking bootloader and that failed super hard as well! Here is what I tried:
1. Tried Kingroot app – failed
2. Tried kingroot on pC – failed
3. Went into developer options and enabled usb debugging and oem unlocking to TRY and unlock the bootloader. – that part worked……HOWEVER
4. Went into the recovery and choice reboot to bootloader. Then connected my Blu phone to my PC, went into Command prompt and typed, “fastboot oem unlock” (I believe I had to download fastboot and adb tools first). – This was painful for me. It gave me the option to unlock the bootloader using the up and down volume buttons. I need to press “Volume up” on my phone to confirm the OEM unlock……..HOWEVER THAT HAS BEEN COMPLETELY DISABLED. The buttons work, but when I need to confirm the oem unlock, it doesn’t allow me to do this. THIS I BELIEVE HAS BEEN PURPOSELY DONE.
5. I downloaded a stock version of my phone’s rom but at a lower android number (5.1) and tried to flash it to the phone using SP Flash tools. – Failed. It would stay illuminated black and the intro sound would come on but I wouldn’t see anything. I looked into that and I believe that is because there is something called version binding where if I update the version build, I can’t downgrade to use the same exploit.
6. Since the phone was bricked, I wanted to try to bring it back to life by downloading the stock rom for my phone at the same virus build version I’m at now and flash it to the phone. – It worked with viruses and all.
7. I Then thought, “Can’t I use open the rom file and delete the viruses I want, then flash it to the phone?” So I tried that by using mtk extractor which allowed me to open the system.img file for the stock rom which contains the android data. From there I went into the apps folder and deleted the 4 virus apps. Then I packaged the system.img back together into one file and then used that system.img when I used sp flash tool to flash the rom onto the phone. – It was stuck on the logo……I can still access the recovery fine and still doesn’t allow me to oem unlock.
This is where I have given up. At this point, I feel like I would need to learn more about the system.img file and what it looks for in the beginning. I just want to fool it into booting without those apps. I know there is something stopping it from booting because when I go into the recovery part and select the option to do a “root integrity check” it tells me those specific apps are missing. Is there any way to change the root integrity check to not look for those apps?
So I know this a lot of information but I need to write this down for all the steps I toke. I hope that this thread can help anyone with a Blu Neo XL device come to some information. If I can confirm from this forum that there is nothing that can be done. I feel then a law suit with Blu is in order and everyone should throw out there compromised phones. I have seen numerous other posts on this subject and so far NO ONE HAS ANSWERED EVEN ONCE. One pore guy had to keep bumping his thread of months until he gave up; atleast tell me its not possible! Here are the link I saw on this from here:
https://forum.xda-developers.com/android/help/tried-to-root-sort-blu-neo-xl-t3559702
Here are my main questions:
Is it possible to access the root (either via pc with command prompt or linux with terminal or even on the device itself) without rooting or unlocking the bootloader (since both seem to be impossible).
Can you extract a system.img file, modify it, then put it back to get together to flash it to a device without unlocking bootloader?
Infact can you modify any part of the rom or .imgs and flash it to spflash tools? (Or maybe I was doing wrong?)
Is there anyway to figure out how to modify the tamper bit if I have to find a way to get around the virus bug on my device that doesn’t allow me to use the “Volume up” button to confirm that I want to unlock the bootloader? (I’m not even sure if this phone has that, I just saw that for this oneplus and thought maybe it can be on all phones in a different way?) Here is a link on that-
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
The goal is get rid of the virus that sends my data back to Chinese servers. Also, the goal is to get an answer from the community here to put this to rest.
If you need any information on this or want me to upload anything please let me know.
Thank you for your time!
Bump as I need hope.
I understand people may not have this phone but I need some sort of reply to confirm that this isn't possible. I want this thread to be the first post anyone sees if they type in "Blu Neo XL" for rooting purposes.
Even if anyone that has a phone that is similar that is affected, that would be anyone who has:
R1 HD
Energy X Plus 2
Studio Touch
Advance 4.0 L2
Neo XL
Energy Diamond
bump
Waited around for awhile but now its time be obnoxious. I will bump my other thread as well and just start hi-jacking other threads until mods ban me or someone answers me for once.
bump
bump
bump again and again and ****ing again!
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
Also, I got a Moto G5S Plus instead finally. It toke me awhile to save the money because I don't make much but atleast I have phone that isn't sending my data over to china.....or maybe it still is sending my data who knows where. Either way, Bump.
Hey man, I didnt read through your entire post. But can't you just downgrade the version to one that is possible to root?
Or you can also get another phone that does have root as an option. Also, I don't think you should bump your own threads. Just wait it out, or ask in other threads for help.
Edit: Oh Man, I didn't even notice someone responded to this! Awesome.
It says in the rules to ask here. So I decided to ask here espcially since this phone doesn't have its own dedicated forum. I got a new phone about a month ago and its pretty good so far.
This is more of a lost cause but I bring this up just in cause other people get affected. I believe the Blu company had to pay the Justice department for this so they got away with it and thats no big deal now of days. lol
erickkg said:
Hey man, I didnt read through your entire post. But can't you just downgrade the version to one that is possible to root?
.
Click to expand...
Click to collapse
Also for those of you out there suffering, the above statement is not possible because the newer versions of Android OS have "version binding" so downgrading to an OS that is lower that way you upgraded to wont allow the phone to get pass the bios or whatever the android bios recovery start name is. (I don't remember right now) Even if you mod the recovery or bios file.
So here it is almost a year later from you writing this post and I have found myself in the same predicament you were once in and was hoping there was answers somewhere, but from the looks of it I am guessing I'm better off just breaking this phone in half and getting myself a new, virus free, root-able phone. Am I correct?
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!!!