Related
So,a few days ago I decided on advice from a friend to root my phone, a Galaxy S 4G (T959) from T-Mobs I got in January. The process itself was easy and made me feel (apparently) over confident.
After doing a little reading I decided if it was that easy, I should upgrade it from 2.3.6 Gingerbread up to Ice Cream Sandwich, I mean what could possibly go wrong?
I ran into more than my fair share of glitches.
Well at some point I tried solutions for problems with ExRom 2.0
E:Short write of /tmp/sideload/package.zip (no space left on device)
and then from code.google zip
E:signature verification failed
New ROM Data fix
E:failed to verify whole-file signature
E:signature verification failed
At some point I should have stopped myself, but I kept reading tips and solutions. 9 hours of reading post on XDA and half a dozen other forums, thinking, "I used to build desktops, I'm sure I can do this myself." Trial and error, again, what could possibly go wrong?
Now 3 days later and some 35 hours of reading posts, I've managed to get my phone to a point where, no three button combo seems to bring it download mode, perhaps its actually stuck in download mode. It will only bring up "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and an image of phone to computer when i hit any key or plug it into a USB power source (this is download mode, no?).
I'm assuming this is the everlasting reference I keep finding of "soft bricking" as I can't do much with the phone.
So, I've got Odin v1.85 and a bunch of downloads I don't think I know which are which anymore. I keep finding threads where I think, "this is it!" only to find a cold link. I've not spent the better part of 35 hours in the past three days trying to fix my phone. I'm on the road for work and the only communication tool I have is my laptop (thank goodness for this at least).
Since my brain is fried, could someone tell me is it fixable, or is it really what I think and the phone just doesn't like me anymore and wants to do nothing? Could someone point me to right files for ICS for T959 and installation instructions, or to the *correct* thread with instructions. I'm worried I followed the wrong instructions enough already. Any help would be appreciated.
Right now, any time i plug my phone in or touch a power button or any combo i get this the image of phone to computer, "Firmware encountered an issue..." Odin will give me a yellow window (0:[COM4]) so it does see it which I believe leaves me in good condition to save the phone. I can find the pit file, I just need perhaps a ROM or a tar for ICS for my T959V?
THANKS GUYS,
Regards
The image you see is download mode. Follow the guide in the second link of my signature and flash with bootloaders. You will be fixed up.
We don't have ICS yet. Only flash ROM's from this forum to your phone. And after following the guide - only flash Gingerbread based ROM's. The guide in the first link of my signature can help you with that.
P.S. I only read the first and last paragraph of your post.
lumin30 said:
The image you see is download mode. Follow the guide in the second link of my signature and flash with bootloaders. You will be fixed up.
We don't have ICS yet. Only flash ROM's from this forum to your phone. And after following the guide - only flash Gingerbread based ROM's. The guide in the first link of my signature can help you with that.
P.S. I only read the first and last paragraph of your post.
Click to expand...
Click to collapse
Thanks so much for responding, funny enough, I found another post similar to mine that you responded to, and decided while I wait I would follow that link... Maybe I'm capable afterall! Will follow up this afternoon!
Thanks again for responding!
orlandodiesel80 said:
Thanks so much for responding, funny enough, I found another post similar to mine that you responded to, and decided while I wait I would follow that link... Maybe I'm capable afterall! Will follow up this afternoon!
Thanks again for responding!
Click to expand...
Click to collapse
Also you said that you have a SGH-T959V, so I'd stay on the T959V forums and flash nothing else from any other forum, unless of course you want an expensive paperweight.
Please can someone help me out.
i am sort of technically minded but not quite a computer wizz.
my wife has a huawei ascend but since updating to ics the phone seemed very sluggish slow and bloated. i got online and found a lot were having the same issues and then i found instructions on how to load a custom version of ics that would not slow and was generally better. i did find the instructions quite straight forward but stupidly i missed one step so once it came to the final stage the custom ics just would not load. i left the phone for a few days, planning to just repeat everything from scratch but before i had a chance an update became available on the phone and my wife choose to install it. which then lead to this message, "image signature verify fail your app boot image may have an incorrect signature. please update your image to a signature official one.
although i dont fully understand un rooting a phone i guess this is the reason.
As i have said i am not a computer wizz so wont understand a lot of technical terms but i can follow instructions so if anyone knows what i can do then please please help me.
Thanks
I've rooted and have custom-ROM'd my G300 nearly 30 times now, so I hope I can be of help.
Could you please let us know, what exactly you've done so far, or link to which instructions you followed?
Then, I should be able to point you in the right direction for a fix
5DChan said:
I've rooted and have custom-ROM'd my G300 nearly 30 times now, so I hope I can be of help.
Could you please let us know, what exactly you've done so far, or link to which instructions you followed?
Then, I should be able to point you in the right direction for a fix
Click to expand...
Click to collapse
The same happened to my G300... After an OTA Vodafone update, when the phone seemed to finish the update and reboot, that message appeared with the exclamation mark...
I've tryed everything to try and root my Samsung Galaxy Tablet 10.1 4G(Verizon) SCH-I905. I've used Bin4ry, tryed to flash cwm via odin(says it successfully flashes, then i try to flash superuser, the recovery still says android.) I've searched and tryed everything to no avail. Can anyone point me to some good directions on how to root this dang device.
Specs:
Samsung Galaxy Tab 10.1 16GB
SCH-I905
Current Android Version: 4.0.4
Anything else just ask.
Hi,
Please give me a few minutes to see what I can come up with as I don't find that device on XDA.
Back soon with my findings- check Post #4.
I'm pretty sure this is the guide that can help. It even claims to be super easy.
http://forum.xda-developers.com/showthread.php?t=1657758
People report success in the thread. But as hinted above, may want to ask in this thread if its for sure for your model.. Before flashing anything.
Good luck!
Edit: I looked through the thread a bit....apparently its outdated. Also, there's posts claiming there's no root method for 4.0.4 for the i905. Perhaps my colleague above will have better luck.
Pony Express said:
Hi,
Please give me a few minutes to see what I can come up with as I don't find that device on XDA.
Back soon with my findings- check this post.
Click to expand...
Click to collapse
Edit: Here is a post on XDA that will hopefully guide you to success in rooting your SCH I905.
And a bit more info from Google.
Also be cautious as Verizon models have been known to be difficult or even not possible to root.
As always, read carefully before proceeding and remember to make a backup first.
Update: Tryed using this meathod: http://forum.xda-developers.com/showthread.php?t=1837605
Official ClockworkMod 6.0.1.2 Recovery:
When i try t flash it says
"Write data size is too big[8|SOS]! [Data:5685248(B) -> Part: 2560/2560(2kb)]
Tegra_Nand_Write: Error to DownloadPartition_odin![0xffffffff]"
The problem I see here is most the guides and posts about that device are quite old. Links end up dead after so long and the files are hard to find.
Its not part of XDA, so use at own risk , but the link "Google" that Pony Express posted may be your best bet.
Hopefully it works out. ?
Pony Express said:
Edit: Here is a post on XDA that will hopefully guide you to success in rooting your SCH I905.
And a bit more info from Google.
Also be cautious as Verizon models have been known to be difficult or even not possible to root.
As always, read carefully before proceeding and remember to make a backup first.
Click to expand...
Click to collapse
I just keep getting the same crap "Signature verification failed" I still have the "Android system recovery <3e>" I've tryed to get CWM recovery flashed but get the error i posted in the last reply i posted.
I can only find out dated info here on XDA. And dead links.
Did you try the Google link above?
Also i've tryed that google one 5 times to no avail says everything goes smooth but then i try root checker or look for SU, nope lol. I mean i've never rooted a tablet before but many phones like Droid X, Droid X2, Rzr Maxx, Rzr Maxx HD. So i mean i know the gist of what should happen yet nothing.
Well, honestly, I could post a dozen links to other websites here....but I don't know what works and what doesn't out there.
My advice at this point. Google "root sch-i905 2014". Look for things posted from this year. I've seen a lot, but can't read them all, or try them obviously. Lol
Hopefully you find what you need. Seems there's others as frustrated as you with the same device. That's what happens when devices age.
Again, good luck!
lancemdewitt said:
I just keep getting the same crap "Signature verification failed" I still have the "Android system recovery <3e>" I've tryed to get CWM recovery flashed but get the error i posted in the last reply i posted.
Click to expand...
Click to collapse
It has been known to happen that once root has been achieved on a device, a manufacturer or carrier will come back and provide an update that causes the root exploit not to work. I have had that personal experience while helping a friend root a device a few months ago.
In summary - your process appears to be sound - unless however there is a device specific recovery ( the one above is for a galaxy s 3 ) that is released after the last carrier/manufacturer update it is likely not to work.
Well thanks for the help anyways I guess I'm SOL, sucks because I don't even like this POS figured I'd like it more rooted....
Hello all Mediapad users.
[EDIT 23-05-2015]Found something that may or may not me a sham. My device being bricked and all, I can't check it out, so I leave it up to you guys.
Check out this site. [/EDIT]
This marks the first step to a whole slew of development and such for our devices.
First and foremost:
i)This is an Alpha project, meaning that nothing is finalised; bug reports, reviews, constructive comments and truckloads of dedication are needed. NOT for the faint of heart.
ii)I need all the help I can get for this project. Any developer is welcome to take the files I upload, work on them in any way necessary, notify me of errors... you get the point
iii)I am in no way responsible for any damage, physical or otherwise, that may happen to anything or anyone as a result of following any instructions I or anyone else may post on this thread.
That having being said, I'll upload the files now, and create a guide soon. If you beat me to it, feel free to take all the credit.
There are two files.
original_recovery is, as the name suggests, the original recovery i pulled from the device itself.
alpha_recovery is the one I got from the cwm recovery builder, and is to be the basis of all future builds.
Kris the wizz 15 said:
Hello all Mediapad users.
Today marks the first step to a whole slew of development and such for our devices.
First and foremost:
i)This is an Alpha project, meaning that nothing is finalised; bug reports, reviews, constructive comments and truckloads of dedication are needed. NOT for the faint of heart.
ii)I need all the help I can get for this project. Any developer is welcome to take the files I upload, work on them in any way necessary, notify me of errors... you get the point
iii)I am in no way responsible for any damage, physical or otherwise, that may happen to anything or anyone as a result of following any instructions I or anyone else may post on this thread.
That having being said, I'll upload the files now, and create a guide soon. If you beat me to it, feel free to take all the credit.
There are two files.
original_recovery is, as the name suggests, the original recovery i pulled from the device itself.
alpha_recovery is the one I got from the cwm recovery builder, and is to be the basis of all future builds.
Click to expand...
Click to collapse
Thanks for the recovery... just a question:
How did you manage to bypass huawei CRC verification signature in recovery.img? Beacouse if the recovery in't signed it wot'n boot, cause the bootloadet locked
By the way, i installing using this comamnd:
dd if=/storage/sdcard1/alpha_recovery.img of=/dev/block/mtdblock3
and as i said, your recovery is'nt booting...
You're awesome
puntoazul said:
Thanks for the recovery... just a question:
How did you manage to bypass huawei CRC verification signature in recovery.img? Beacouse if the recovery in't signed it wot'n boot, cause the bootloadet locked
By the way, i installing using this comamnd:
dd if=/storage/sdcard1/alpha_recovery.img of=/dev/block/mtdblock3
and as i said, your recovery is'nt booting...
Click to expand...
Click to collapse
As I said, I need all the help I can get. I hadn't thought that far, so that hasn't happened.
Thank you puntoazul for pointing that out, I could't figure out whay it wouldn't boot. Such a simple thing escaped my thought.
I'll contact huawei and get them to help me with unloking the bootloader
Thanks again
[Update]
No commmunication from Huawei, not even to confirm they received my email.
Therefore, either we are on our own, or huawei is taking uncommonly long to communicate.
[/Update]
BTW, does fastboot oem unlock work for anyone?
Also, can someone post how to set up rhe fastboot for this device?
I haven't the time to do it myself
any progress regarding this tablet...?
vwong said:
any progress regarding this tablet...?
Click to expand...
Click to collapse
None yet.
The brick wall is the fact that the boot loader is locked, and huawei won't tell us how to unlock it. I've emailed them twice already, and have received no response.
Until huawei decides to help, we're stuck.
@Kris the wizz 15
any further progress for this device..?
Thanks.
Not yet no, as huawei remains remarkably unhelpful, and without them, we can't progress
For bow we're confined to root tweaks, nothing more.
@Kris the wizz 15
any new development..?
http://en.club.vmall.com/emotiondownload.php?mod=unlock&action=apply
Anyone try this to unlock bootloader?
Sent from my HTC Butterfly s using Tapatalk
Possible solution
I was digging around online, and found out that its actually quite easy. There's a catch though.
The various methods support many rockchip versions(that's what our device chip set is) except the one our device has, the rk3168.
Now, the rk3188 is supported, and is the closest number wise to our chip set.
Apparently, all we have to do is get the recovery.fstab from our stock recovery, and replace the one in the cwm build with it.
I'm going to let you guys go crazy with this, as I can't work on it myself right now (IGCSEs)
Links below.
For the 3188 cwm builds:
http://androtab.info/clockworkmod/rockchip/rk3188/
For the thread where I found the helpful recovery.fstab tip (try the generic one first):
http://forum.xda-developers.com/showthread.php?t=2578563
Good luck people!!
Some Possible Progress!!
Kris the wizz 15 said:
Hello all Mediapad users.
Today marks the first step to a whole slew of development and such for our devices.
First and foremost:
i)This is an Alpha project, meaning that nothing is finalised; bug reports, reviews, constructive comments and truckloads of dedication are needed. NOT for the faint of heart.
ii)I need all the help I can get for this project. Any developer is welcome to take the files I upload, work on them in any way necessary, notify me of errors... you get the point
iii)I am in no way responsible for any damage, physical or otherwise, that may happen to anything or anyone as a result of following any instructions I or anyone else may post on this thread.
That having being said, I'll upload the files now, and create a guide soon. If you beat me to it, feel free to take all the credit.
There are two files.
original_recovery is, as the name suggests, the original recovery i pulled from the device itself.
alpha_recovery is the one I got from the cwm recovery builder, and is to be the basis of all future builds.
Click to expand...
Click to collapse
Well, as we all know, this project has been dead in the water for forever now. What if, though, I told you there may be hope after all?
While browsing the net, I came across a few articles, which, when combined, may actually be the way forward for our aging device.
I won't go into much detail, but it involves porting a CWM made for the RK3188 chip (our device has a RK3168 chip). The idea of porting came from this thread.
Learn more about this whole process here. Make sure to download the Generic ramdisk-only image, or just grab it directly here.
Credit goes to Androtab, and to all those unnamed commenters who put the idea in my head.
Go crazy guys, and be sure to post ANY PROGRESS, so we can all enjoy it!
I'm sorry that for the next three weeks, I personally cant work on this, as I'm in the middle of an exam session.:laugh:
Hope this works:fingers-crossed:. Good luck all. Please drop a thanks if this helps you!
Keep tight, Kris.
Check out the edit
puntoazul said:
Thanks for the recovery... just a question:
How did you manage to bypass huawei CRC verification signature in recovery.img? Beacouse if the recovery in't signed it wot'n boot, cause the bootloadet locked
By the way, i installing using this comamnd:
dd if=/storage/sdcard1/alpha_recovery.img of=/dev/block/mtdblock3
and as i said, your recovery is'nt booting...
Click to expand...
Click to collapse
I've edited the main post, check out the edit.
Help
Kris the wizz 15 said:
I've edited the main post, check out the edit.
Click to expand...
Click to collapse
Is there any progress to this device or is it that it's over for him
Use of this device has become very bad and became very slow
I can not even Lanier to cancel additions developed by Huawei on this machine
Even after renovation frimware Its thought it would be a little faster, but it became worse and slower
I hope if there is any way or any rom can Feature by thanking you
Thank you for your efforts and I hope to find a solution to this
Any progress on this tab regarding cwm. I own a mediapad s7-721u rooted with supersu installed, bootloader unlocked.. however I'm having a hard time flashing recovery, does this recovery working?? If not is the anyway we can compile one??
To all:
I have this far been unable to bring back my tab from the dead, so development for it is in a hiatus. Sorry for that. Feel free to continue development without it
Huawei MediaPad 7 Youth Bootloader Unlock code
The bootloader unlock code for the Huawei Mediapad 7 Youth is 2311541926080197
Please make the custom recovery soon.
---------- Post added at 02:36 PM ---------- Previous post was at 02:28 PM ----------
Kris the wizz 15 said:
As I said, I need all the help I can get. I hadn't thought that far, so that hasn't happened.
Thank you puntoazul for pointing that out, I could't figure out whay it wouldn't boot. Such a simple thing escaped my thought.
I'll contact huawei and get them to help me with unloking the bootloader
Thanks again
Click to expand...
Click to collapse
The bootloader unlock code for the Huawei Mediapad 7 Youth is 2311541926080197
Please make the custom recovery soon.
ARTechStuido said:
The bootloader unlock code for the Huawei Mediapad 7 Youth is 2311541926080197
Please make the custom recovery soon.
---------- Post added at 02:36 PM ---------- Previous post was at 02:28 PM ----------
The bootloader unlock code for the Huawei Mediapad 7 Youth is 2311541926080197
Please make the custom recovery soon.
Click to expand...
Click to collapse
That's your key, which you can use in order to unlock the bootloader.
However, every huawei device has it's own key, which means that this code won't work for others.
Also, I'm going to try to port TWRP to this device, as it isn't easy to find a device with the same chipset as ours. Otherwise, I'll try building from source.
Will make an attempt next week, when I've replaced my digitizer.
Let's get the ball rolling with this thing... I am new to blu
Search shows SP Flash tool as a main flash tool.
I expect to get root with towel root or kingroot.
If we do acquire root, the next step is to dump a stock ROM, I haven't done much dev. since jellybean, but hopefully we could map partitions (important), and do a raw dump (.img) backup, etc. A secure kernel, could prevent that, I think. If we are able to make or acquire a stock ROM, we have something to fall back on. There's always hope, they will allow unlock of bootloader from developer options in settings, or fastboot oem unlock. It looks like quite a few other blu devices have been unlocked. If worst came to worst, I'm sure we could pony up some donations to get this device into a developers hands to help.
Once we get bootloader unlocked, all we need is a custom recovery, and some source code bits, and its off to the builds, we hope!
Please share any beginning steps to help get things moving here....
this looks promising.. http://androidxda.com/download-mtk-droid-tool
Thanks!
Yes let's get the ball rolling. I'm eagerly waiting for this device. The source for the x10 is released so it looks like we're in the green for now.
Sent from my A0001 using Tapatalk
Rooting
chrisrotolo said:
I expect to get root with towel root or kingroot.
Click to expand...
Click to collapse
No luck with either of those. I've tried a lot of "one-click" apks and none of them work. It looks like I'm going to have to dig out an old desktop from my basement and make myself a Windows machine (urgh!!). I agree, Sp Flash Tools and MK Droid Tools look like a good place to start.
SP Flash Tool for Linux
I've been trying to get my linux (Ubuntu 14.04) to recognize the phone with this s/w but no luck so far, even though the system finds it (see screenshot).
http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
You kernel messages suggest you have the Allview version... Is it possible that software or partitioning differences in the default load of the Allview vs. the Blu may make a difference in whether the root apps work?
clipcarl said:
You kernel messages suggest you have the Allview version... Is it possible that software or partitioning differences in the default load of the Allview vs. the Blu may make a difference in whether the root apps work?
Click to expand...
Click to collapse
I have no way of knowing.
I sure hope the developers jump all over this phone.
xathras said:
I have no way of knowing.
Click to expand...
Click to collapse
So it could be too soon to assume that the current rooting apps won't work on the Blu phone just because they don't work on the Allview.That is, if Blue has their own software stack they install that is different than the Allview...
Rooting from PC failed
I now have a Windows 7 machine running so I've tried a couple of root from pc apps.
Drivers http://androidxda.com/download-gionee-usb-drivers
I installed the Gionee E8 drivers from here successfully - or so Windows said.
Root Genius v2.4.1 http://androidxda.com/download-root-genius-application
First ticked "USB debugging" under "Developer options" on phone. Ran Root Genius and it found the phone first time. Click on "Allow Computer" box that pops up on phone. Root Genius started, got to a couple of % and then crashed. Rebooted PC, clicked on "Revoke USB debugging authorisation" for a clean start and tried again. Same result; click "Allow computer", start program and crash. Tried a couple more times with same result.
iRoot v1.8.5 http://androidxda.com/download-iroot-application-all-versions
Used same procedures as with Root Genius. iRoot started, found the phone, went all the way though it's operations before reporting that rooting failed (i.e. it did not crash). Retried a couple of times with the same result.
The only plus is that the driver I used appears to be OK for Windows 7 at least (both programs found the phone).
Later I tried Kingo Root http://androidxda.com/root-android-device-using-kingo-root
It couldn't find the phone using the driver I previously used or it's own driver, although the "Allow computer" box popped up on the phone both times
xathras said:
I now have a Windows 7 machine running so I've tried a couple of root from pc apps.
Drivers http://androidxda.com/download-gionee-usb-drivers
I installed the Gionee E8 drivers from here successfully - or so Windows said.
Root Genius v2.4.1 http://androidxda.com/download-root-genius-application
First ticked "USB debugging" under "Developer options" on phone. Ran Root Genius and it found the phone first time. Click on "Allow Computer" box that pops up on phone. Root Genius started, got to a couple of % and then crashed. Rebooted PC, clicked on "Revoke USB debugging authorisation" for a clean start and tried again. Same result; click "Allow computer", start program and crash. Tried a couple more times with same result.
iRoot v1.8.5 http://androidxda.com/download-iroot-application-all-versions
Used same procedures as with Root Genius. iRoot started, found the phone, went all the way though it's operations before reporting that rooting failed (i.e. it did not crash). Retried a couple of times with the same result.
The only plus is that the driver I used appears to be OK for Windows 7 at least (both programs found the phone).
Click to expand...
Click to collapse
Cool... It's good to test this stuff. More information is always a good thing.
BUT, since the software / partitions of the Blu Pure XL phone will almost certainly be different than the Allview phone you have your tests really don't really tell us anything about the Pure XL for certain. The hardware may be exactly the same (or there may be differences in the radios) but if the software and / or partition layout is different then what works on your phone may not work on the Pure XL and vice versa.
So I'd request that you keep posting your useful information... BUT that you clearly post that you don't actually have a Blu Pure XL but the Allview phone so you don't confuse people. Yes, they may be based on the same hardware but that does not make them exactly the same as one another. For example, there are different versions of the LG G4 and they all have pretty much the same hardware but they can't all use the same ROMS or the same rooting techniques.
So what you are posting helps because more data is better, but is not definitive for the Pure XL because your phone is NOT a Pure XL.
Thanks,
Carl
clipcarl said:
Cool... It's good to test this stuff. More information is always a good thing.
BUT, since the software / partitions of the Blu Pure XL phone will almost certainly be different than the Allview phone you have your tests really don't really tell us anything about the Pure XL for certain. The hardware may be exactly the same (or there may be differences in the radios) but if the software and / or partition layout is different then what works on your phone may not work on the Pure XL and vice versa.
So I'd request that you keep posting your useful information... BUT that you clearly post that you don't actually have a Blu Pure XL but the Allview phone so you don't confuse people. Yes, they may be based on the same hardware but that does not make them exactly the same as one another. For example, there are different versions of the LG G4 and they all have pretty much the same hardware but they can't all use the same ROMS or the same rooting techniques.
So what you are posting helps because more data is better, but is not definitive for the Pure XL because your phone is NOT a Pure XL.
Thanks,
Carl
Click to expand...
Click to collapse
Thanks Carl, you're quite right of course. I'll check back in a couple of weeks once you guys have actually got your hands on some genuine Blu. When you do these adb tools (http://androidxda.com/download-best-android-adb-driver) and MTK Droid Tools worked v2.5.3 work on my Allview.
xathras said:
Thanks Carl, you're quite right of course. I'll check back in a couple of weeks once you guys have actually got your hands on some genuine Blu. When you do these adb tools (http://androidxda.com/download-best-android-adb-driver) and MTK Droid Tools worked v2.5.3 work on my Allview.
Click to expand...
Click to collapse
Please don't stop posting your test results! Just let people here know they're for the Allview and thus may not be the same as what would happen on the Pure XL. But it's also quite possible that your phone is exactly the same with the same software and layout just with cosmetic changes. We just don't know yet. It's also possible that your phone could be flashed to be exactly the same as the Pure XL even if it's not out of the box. In any case it's definitely useful information you are providing!
@xathras - Have you tried flashing SuperSU from recovery or otherwise injecting root from a recovery package?
http://www.recovery-mode.com/android/gionee-elife-e8.html
neatojones said:
@xathras - Have you tried flashing SuperSU from recovery or otherwise injecting root from a recovery package?
http://www.recovery-mode.com/android/gionee-elife-e8.html
Click to expand...
Click to collapse
Flashing SU from recovery fails and although I haven't tried the other option I'm fairly sure that that would fail too, due to /system being a secure read only partition. It is going to take someone with the necessary skills to extract boot.img, make the needed changes and re-packing it. I've seen a webpage for a china wholesaler for the Gionne version of this phone who offers an "unlock and root" option for $2.99 per device, so it must be doable.
Bootloader unlocked
Have look at post #108
http://forum.xda-developers.com/pur...v-friendly-t3197751/post63383416#post63383416
xathras said:
Have look at post #108
http://forum.xda-developers.com/pur...v-friendly-t3197751/post63383416#post63383416
Click to expand...
Click to collapse
Great! You were one step ahead, that was going to be my next suggestion. Now with an unlocked bootloader you should be able to make a TWRP and flash whatever you want including injecting su or flashing a completely modified ROM with root.
Posting this here so we can have a to go to thread.
xathras said:
Now that some of you look like your'e about to get your hands on this device I'll post a few of the resources you might need. The MediaTek X10 Helio (mt6795 based) is only now beginning to appear in phones; there is little help from devs as yet (Hey! Your'e An Early Adopter). The Gionee version has just gone on sale in India so something (in English) might appear there soon. Due to MTK devices being common in Asia you'll find a lot of help in sites there.
Blu related sites
BLU Products Development Team - Community - Google+
https://plus.google.com/communities/117846429749085694805
BLU Developers Repository
http://www.blu-dev.com/
Asian sites
China Devices
https://www.china-devices.com/
China Phone Arena
http://www.chinaphonearena.com/forum/Forum-MTK-General-Tools
Android Urdu
http://androidurdu.net/mediatek-scatter-files-download/
http://androidurdu.net/sp-flash-tool-database/
MTK Roms
http://www.mtkroms.com/
http://www.mtkroms.com/2015/03/mtk-bootimg-unpack-repack-tool.html
http://www.mtkroms.com/2015/02/how-to-root-your-mediatek-device.html
http://www.mtkroms.com/2015/03/philz-touch-recovery-for-all-mtk-devices.html
and many others.
Rooting and flashing
http://whiteboard.ping.se/Android/Rooting
http://whiteboard.ping.se/Android/BootLoader
https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro#Common_fastboot_commands
https://wiki.cyanogenmod.org/w/Template:Fastboot_oem_unlock
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
MTK Droid Tools 2.5.3
http://forum.xda-developers.com/showthread.php?t=2160490
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
This tool does not work on this phone because it can't recognize the new 64-bit SOCs. I thought that when it found my phone it might work but the "TotalBytesPerChunk Not Found" error (see attached screenshot) is fatal. However, it does do one useful thing in that it displays a blocks map even thought it can't create a scatter file. I'd like to know if the Allview and Blu blocks maps match.
MTK Droid Tools is sadly no longer being maintained.
Attached files are the MTK Droid Tools screenshot (too big - had to zip it) and the Allview build.prop file. I'd be interested in seeing the Blu version.
Click to expand...
Click to collapse
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
Can we as a community keep hammering Mediatek to release the helio x10 sources so we can start porting roms to the pure xl? I'm doing my fair share of posting on their social media sites. We'll be able to get 6.0 if they post up the sources. They had them up on github but they removed them I don't know why.
FuMMoD said:
Can we as a community keep hammering Mediatek to release the helio x10 sources so we can start porting roms to the pure xl? I'm doing my fair share of posting on their social media sites. We'll be able to get 6.0 if they post up the sources. They had them up on github but they removed them I don't know why.
Click to expand...
Click to collapse
This is probably where I stop being useful since I'm a "monkey see, monkey do" kind of guy as far as rom development goes, although I'm up for testing stuff.
Is this any of use to you?
http://www.mediafire.com/download/dx698xy19xg5xq8/MT6795.kernel-master.zip
https://github.com/jawad6233/MT6795.kernel/tree/master/alps/kernel-3.10
Both from this link:
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886
xathras said:
This is probably where I stop being useful since I'm a "monkey see, monkey do" kind of guy as far as rom development goes, although I'm up for testing stuff.
Is this any of use to you?
http://www.mediafire.com/download/dx698xy19xg5xq8/MT6795.kernel-master.zip
https://github.com/jawad6233/MT6795.kernel/tree/master/alps/kernel-3.10
Both from this link:
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886
Click to expand...
Click to collapse
Dude you're awesome at researching and finding useful Intel! I'm going to go over everything you've provided over course of today and tomorrow and start working on the phone. I should get it by tomorrow evening. I built my own rom before privately so hopefully I have enough know how to get Development rolling in here. I just hope I can motivate others of better skills to come over once it's proven roms can be ported over and such.
Sent from my A0001 using Tapatalk
FuMMoD said:
Dude you're awesome at researching and finding useful Intel
Click to expand...
Click to collapse
I can resist anything except flattery!
In my Allview build.prop there's a line that says "ro.gn.gnromvernumber=GiONEE ROM5.0.16". I'd be very interested in knowing what your Blu build.prop has to say.