Related
Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Ok, let me rephrase simply.
Can someone with a working Hipstreet Titan, rooted or not, please send me, or post a link to their ROM?
Click to expand...
Click to collapse
I know people have this device, and it's quite reasonable to assume that not all of them are bricked, therefore this request is technically feasible. Further, with a number of people posting about this device in technical forums, I know people with technical knowledge own this device.
I would really hate to throw out an otherwise perfectly good tablet.
Jarod997 said:
I would really hate to throw out an otherwise perfectly good tablet.
Click to expand...
Click to collapse
Hi - did you ever resolve this issue?
beach9000 said:
Hi - did you ever resolve this issue?
Click to expand...
Click to collapse
Not yet. I had given up for a while. Most of my internet searches kept coming back to the same few articles on this website.
I have a lead on someone who has another Titan, but they live seven hours away - it's been difficult coordinating a meeting.
Jarod997 said:
Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Click to expand...
Click to collapse
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: http://www.androidtablets.net/forum...eet-titan-a13-7-inch-tab-firmware-needed.html was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
es0tericcha0s said:
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: (link manually removed) was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
Click to expand...
Click to collapse
Thanks for the help! I'll have a look at some of those. I'd really like to have a tablet back that doesn't have a 3.5" screen.
So I managed to get LiveSuit 1.11 installed on Win 8-64, yes it IS doable. But, my problem is I can't get the tablet recognized. The Power+Vol boot takes it in to "recovery" mode, (so reports "adb devices") - does this keep it from being able to be used by LiveSuit?
"adb wait-for-device" hangs
In my Device Manager I have Android Device->Android ADB Interface, and Universal Serial Bus controllers->USB Device(VID_1f3a_PID_efe8) with a yellow exclamation.
I know I had "adb wait-for-device" passing fine at one point, but I don't remember what I had to do to get there. So much trouble for a free tablet.
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
cmstlist said:
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
Click to expand...
Click to collapse
So I managed to get a system backup off of my father-in-law's Titan - just have to figure out how to get it on my brick. I'm having great difficulty trying to do a restore while in recovery mode.
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
cmstlist said:
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
adb backup
Jarod997 said:
adb backup
Click to expand...
Click to collapse
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
cmstlist said:
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Aw crap, really? The cutting board a-la-iPad commercial is sounding like such a good idea at the moment.
On the good tablet I could get in the shell - "adb shell", and then "su", but then what? How do you copy all the files off the system through the USB onto the computer from the shell? For whatever reason (and I dislike ADB for this) I could not do "adb pull /* /destination-folder/*" - it kept saying that it was skipping a lot of files. Or otherwise if I was trying other variations on commands and parameters, adb would just spew its help page - never mind telling me what's wrong with the command I just entered.
Why, oh why, is it so hard to take a copy of a good working OS and put it on to another tablet?
But, make you a deal - help me get a good system image off this working tablet and I'll toss it to ya.
If you can find the right mount points on the partition table got may be able to make a system dump using dd. But restoring it I have no idea since there's no custom recovery available for this tablet.
Sent from my Nexus 7 using Tapatalk
Hello,
Just purchased this phone and would like a root in order to expand its storage. It's a new offering from TracFone and is limited for on-phone storage. Other than that, it's a fairly decent phone considering it is a TF. I searched the forums and found other similar phones, but none matched this one. If someone would be willing to help, you would get a lot of thanks from TF users who bought this phone.
MiMtnBiker said:
Hello,
Just purchased this phone and would like a root in order to expand its storage. It's a new offering from TracFone and is limited for on-phone storage. Other than that, it's a fairly decent phone considering it is a TF. I searched the forums and found other similar phones, but none matched this one. If someone would be willing to help, you would get a lot of thanks from TF users who bought this phone.
Click to expand...
Click to collapse
If you have PC follow these:
Try to download "kingo android" in your pc
then connect your device to pc via USB cable
open kingo android and start
If you dont have a pc and you have recovery mode in your device follow these:
search this: root (your device name) .zip file
and if you are successful put that zip file on root folder(the folder you see when you open your built-in file manager)
switch your phone to recovery mode
volume up, volume down, and menu button are the controls
navigate it to "apply update"
then choose your the zip file
If you dont have a pc and dont have a recovery mode follow these:
download "framaroot" "rootmaster" all apk
Hope it helps
cedie said:
If you have PC follow these:
Try to download "kingo android" in your pc
then connect your device to pc via USB cable
open kingo android and start
If you dont have a pc and you have recovery mode in your device follow these:
search this: root (your device name) .zip file
and if you are successful put that zip file on root folder(the folder you see when you open your built-in file manager)
switch your phone to recovery mode
volume up, volume down, and menu button are the controls
navigate it to "apply update"
then choose your the zip file
If you dont have a pc and dont have a recovery mode follow these:
download "framaroot" "rootmaster" all apk
Hope it helps
Click to expand...
Click to collapse
Thank you for your suggestions. I have tried several of the one-click methods for root (Kingo, Genius, towelroot, framaroot, etc.). All of which have been unsuccessful. Obviously, there is no rom available for this phone. If anyone has any other info, I would really appreciate it.
Expand Memory
I got the same phone same problem while i didnt find a root for it i found out how to install to sd very useful
go to google and type in how to install apps to sd card no root then click on the link for instructables i cannot post link because im a new user worked for me
would really appreciate a root method if anyone has one the storage issue is really annoying -_-
I realize this is an older thread, but I have devised a fully working root strategy for the Alcatel A564C. If anyone is interested let me know. If there is any interest I'll start a root thread for this device.
MotoJunkie01 said:
I realize this is an older thread, but I have devised a fully working root strategy for the Alcatel A564C. If anyone is interested let me know. If there is any interest I'll start a root thread for this device.
Click to expand...
Click to collapse
Hi MotoJunkie01. I saw your post today, and I just got an Alcatel A564C from TracFone. I would be very interested in rooting this device, since the accessible internal memory is so small it makes it almost unusable. Please open a root thread for this device if you feel there is enough interest. Or, if you would be willing, just send me a PM with the instructions. I have been able to gain temporary root permissions on this device using KingRoot, but they go away with every reboot. Also, I have not found any way to unlock the bootloader. Any help would be greatly appreciated. Thanks!
jp2006 said:
Hi MotoJunkie01. I saw your post today, and I just got an Alcatel A564C from TracFone. I would be very interested in rooting this device, since the accessible internal memory is so small it makes it almost unusable. Please open a root thread for this device if you feel there is enough interest. Or, if you would be willing, just send me a PM with the instructions. I have been able to gain temporary root permissions on this device using KingRoot, but they go away with every reboot. Also, I have not found any way to unlock the bootloader. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
I'll get a thread and a guide posted on rooting the A564C. I've had some PMs with interest as well. I'll post the link here once done.
MotoJunkie, fellow R.F. guy here, I have been browsing this site for well over a year and just signed up in fact this is my first post. I was following your information on the LG zone 3 as well. I own a brand new in the box A564C and just can't get it rooted. I too, tried different ways and actually was able to get temp root once with kingroot when the phone was really lagged out for some reason I had root until reboot. But now every version of kingroot that I run comes back with a network error which is strange and didn't used to happen. So please, let us know what you have found out. I am eager to hear back from you. And, thank you so very much for your willingness to share your knowledge.
Just checking back in, to see if any advancements or progress has been made. I'm excited about finally rooting this device and anxiously waiting.
MotoJunkie01 said:
I'll get a thread and a guide posted on rooting the A564C. I've had some PMs with interest as well. I'll post the link here once done.
Click to expand...
Click to collapse
I'm getting a thread started, as well as threads for other various devices. I know you're anxious, but please be mindful that XDA rules prohibit asking for ETAs and such. It's not that I particularly mind, I just don't want to see you sanctioned for rule violations by a moderator.
A couple of things, I I may....
First of all, aside from the rules (not that I'm saying that I don't respect them, I do but at the same time want you to know what I'm about to say is genuine and not out of fear of getting booted off the forum) I want to personally apologize if I came off as asking for an ETA or came off as rude or unappreciative in any way, shape or form. That was not my intent at all, and rather than PM you I wanted to publicly say that I am sorry for that and to let you know as I previously mentioned how much I enjoy reading your posts and am thankful for your willingness to share your knowledge. With that said I won't get off subject or topic again. I just felt that I needed you to know that I was just excited that someone had it figured out is all and I will pay closer attention on how I come across from now on. Take care.
JustinJay said:
A couple of things, I I may....
First of all, aside from the rules (not that I'm saying that I don't respect them, I do but at the same time want you to know what I'm about to say is genuine and not out of fear of getting booted off the forum) I want to personally apologize if I came off as asking for an ETA or came off as rude or unappreciative in any way, shape or form. That was not my intent at all, and rather than PM you I wanted to publicly say that I am sorry for that and to let you know as I previously mentioned how much I enjoy reading your posts and am thankful for your willingness to share your knowledge. With that said I won't get off subject or topic again. I just felt that I needed you to know that I was just excited that someone had it figured out is all and I will pay closer attention on how I come across from now on. Take care.
Click to expand...
Click to collapse
You're are both respectful and courteous, qualities that are coveted and always welcome here at XDA. I didn't take any offense to your questions but I appreciate your kind words. On an update for this device, I'll be posting a root thread early this week coming -- Tuesday or Wednesday most likely. I have threads for this and at least 4 more devices I'll be posting.
Thanks again for your kind words. By the way I'll be posting the link to my thread here, so check early in the week.
I certainly will...thanks for your reply, and can't wait! I will keep checking back periodically. Thanks again!!
Update: I'm experiencing a boot loop on my own device from trying to flash custom recovery. Trying to get this snag worked out and get the tutorial posted. Sorry for delay.
Hey,..noooo problem on this end...again, just grateful you're both willing to work through the issues and obstacles as they come your way (and if it's anything like that happens to me they sometimes seem to come out of no where, just about when I think my task is complete) but also appreciative that you're willing to share. I would like to start a new thread, not to pile on your list of people bugging you about things already, but need to find the right section. It is more of an R.F. type related question with regards to the modems in the phones and weather the modulation techniques and bands capable are software driven like a software defined radio or more hardware dependent. I know as far as bands go the frequency coverage would have to depend on hardware all the way from the local oscillator to the RX strip to the TX PA as far as gain and linearity, duplexors of some type, antenna (s) being resonant at the middle of the desired band (s) but as far as modulation techniques being more software controlled somehow? Anyways, stuff that I am very interested in but haven't found a section??
MotoJunkie01 said:
Update: I'm experiencing a boot loop on my own device from trying to flash custom recovery. Trying to get this snag worked out and get the tutorial posted. Sorry for delay.
Click to expand...
Click to collapse
MotoJunkie01 - I'm curious to know if this boot loop issue has resulted in you stopping work on rooting this device? Although I am still interested in obtaining root on this phone, I'm cool either way. I'm just posting to see if you think obtaining root and posting a tutorial is still in the cards?
Thanks again for your work on this. I really do appreciate it.
I'm sorry guys. Upon trying to flash the device with a stock fir!mware image to fix the boot loop, my device is now hard bricked. I can tell you, in order to root your device, use the latest KingRoot apk. This will give you temp root only, meaning root will not survive a reboot. So, to gain permanent root, install BusyBox (any version should suffice), then download SuperSU-Me Pro from the Play Store (paid app). This will eradicate the KingRoot root binaries from your device and replace them with the latest version of SuperSU. You will then have full root.
To root Alcatel One Touch Pop Icon A564C with KitKat 4.4.2 TracFone, download KingRoot for pc in English from this site. It rooted on the 2nd run.
On the xda-developers forum, find the following:
android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
RAWilson100 said:
To root Alcatel One Touch Pop Icon A564C with KitKat 4.4.2 TracFone, download KingRoot for pc in English from this site. It rooted on the 2nd run.
On the xda-developers forum, find the following:
android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Click to expand...
Click to collapse
Hello.
I will thank you if this method would work on my phone, but I am unsure my root would be successful. I would appreciate the steps you took in order to root the A564C(such as time to root, USB debugging, etc.) and if you can post how your phone is doing since the root. I would be much thankful.
I have tablet Teclast X10 Plus ((F2D6) Intel Z8300 Cherry Trail CPU. Android 5.1 only. Unable to find any information on how to root this device. Assistance will be appreciated. Thanking you.
Same here, no info from the company. Worse, we are theoretically supposed to be able to install Windows 10, but Teclast does not give any drivers for that. With only 2go of RAM, I don't care that much about Win 10, but not being able to root is frustrating. I've tried fastboot OEM unlock on the device, it said it worked, but it actually didn't
There's no OEM information for stock firmware flashing?
If you go there : teclast.com/en/firmware/ and type: f2d6 , then you have the only thing that they gave us, it's an Intel flash tool with the current firmware and android 5.1. I guess that there is something in there we could start with, but I'm not an expert. Other than that, the company give no support whatsoever and doesn't answer emails.
As for other information: I've tried to root with KingoRoot, it shows successful, my device rebooted, but seems to hang after the second boot stage, unable to load the O.S. anymore. I had to re-flash the device to fix it.
Somebody found a way to root: hispatablets.com/tablets-teclast/root-teclast-x10-plus-solucionado-t8419.html
I’ve never been that happy to know more than one language
If you need help with the instructions (in Spanish), just ask. I’ve tried and it’s working, my x10 plus is now rooted.
Still, the procedure is a bit clunky and I’m sure we can optimize the process (and fixed the reboot needed problem after the --daemon).
This is a good step and it seems like with this and the package given by Teclast we have enough information to do a lot of things… Still, there is work to do…
how i can get dualboot? I need windows 10 / android version but unfortunatelly i bought android only
Found a review saying this tablet has 'upside down' problem. Basically, it displays some apps upside down and there's no way to fix it.
Do you experience that too?
Flyagaric : It's not impossible, but it is super easy to fix (for those with this bug), you just choose one particular position (I suggest landscape), you go in options and lock the rotation. Every apps will properly open in the current position.
ZTE Warp 7 N9519 for Boost - Any help to unbrick
I have ZTE Warp 7 N9519 for Boost, I try to root it by kingroot apk last verison. After successfully root this device, I restart it but no longer work, only boot with ZTE logo then black screen.
When I connect it to PC, it appears as (Qualcomm ZTE .....).
Please, Can any one help me to unbrick it.
Flash stock rom
google it
Thats weird because 90% of the people get the issue that they get temporary root then the phone reboots by itself and removes root. I never got a black screen when it finished rebooting. You may have a technical issue or you went to far and did something else.
Has anyone got twrp for this phone I can get temp root but can't find twrp to install when I have temp root
No, the only way to get perm root is to unlock bootloader but the phone doesn't seem to have one.
I think there might be a way I Can't get into recovery to fix it either. So got an idea from what was done on HTC desire 526 to unlock the bootloader but the bootloader option won't work for us but the part we need may work, Unless ZTE turned the feature off which I hope they didn't since since they screwed us on fastboot. So I'd like to try and make the phone boot completely from the ext. SD card. As I understand it's a less than known feature in case something happens to the Emmc. Also we would be able to have almost complete access to be able to change anything even flash custom roms without touching the internal memory . I realize it's not the same chip set as the HTC desire 526 is 8909 and our warp 7 is 8916. But still a Qualcomm and it's a good chance this is built into most Qualcomm based chip sets. As I understand it it can still work for our device and other Qualcomms. We just need someone kind enough to make a COMPLETE backup for us using dd commands. Then we can try and write that to an SD card to be an exact copy of the internal phone SD. but that may not work so we would have to use db boot tools but unless someone can give me a solid educated reason y it's a waste of time. I'm willing to put in the effort to try if I can get someone kind enough to post the complete copy. Would love to try this on my ZTE grand x3 too. So please anyone up to offer they're help with providing a complete image or constructive help would be awesome.
I think this device can only be temporary rooted. I know it is too old post but if you still need help, contact me. I have full qualcomm firmware for qfil (v07., v.09 and v10 (readed firmware))...
mbairaq said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
What lol
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?