What you will need:
KingRoot V4.5.0.901 (latest version as of this posting)
Rooting your phone will void your warranty.
Terminal Emulator for Android
Replace KingUser with SuperSU
MtkDroidTools v2.5.3-updated
adbd Insecure v2.00
SP Flash Tool
I am not going to get into how to install ADB drivers, MtkDroidTools, or SP Flash Tool. If you are not experienced with rooting, flashing, etc., please do some research.
Okay, let's get started
First you will need to get your phone rooted. Download KingRoot using the link above and follow this guide.
Next you will need to replace KingUser with SuperSU.
Now that we have the phone rooted and SuperSU in place, we can use MtkDroidTools to make a backup of the phone.
This video will show you how to backup your phone with MtkDroidTools (make sure you have downloaded the version I provided, as this has updated ADB files). Also make sure you enabled adbd Insecure before you connect your phone (you don't need to check enable at boot).
Once you have a successful backup, you need to create the files for flashing (scroll down to PREPARING EXTRACTED MTK ANDROID FLASH FILES FOR FLASH TOOLS) if you need to flash back to the original firmware.
Hopefully you now have a backup of your phone. Now we can install a custom recovery. You can use either TWRP (rename to recovery.img) or PhilZ.
The easiest way to flash the custom recovery is with SP Flash Tool. Connect your phone (you don't need adbd Insecure enabled for this). Run flash_tool.exe as administrator. For scatter-loading File click on the Scatter-loading folder
and navigate to your MtkDroidTools backups folder. There should be a folder that starts with BLU-STUDIO-C. Open that folder and select MT6582_Android_scatter.txt. For the recovery file, navigate to the one you downloaded (TWRP or PhilZ) by clicking on the Location column next to RECOVERY.
Make sure RECOVERY is the only box checked before proceeding. Now you have your scatter file and custom recovery loaded. Click on the Download button. Nothing will happen at this point. Now shut down your phone (not restart). Once your phone shuts down completely, plug it in via USB and you should see it begin to flash the custom recovery. If not, then you need to make sure you have the necessary drivers installed. Once it's complete, you can close out SP Flash Tool and disconnect your phone. After your phone is disconnected, hold down the power and volume up buttons until the recovery menu appears :good:
Post your feedback, and if you encounter any problems, please be as descriptive as possible. Good Luck
Credits:
@AlexZap who was the first to help me along this crazy journey
@yuweng for all his help in backing up the phone and for PhilZ recovery
@bigrammy for porting TWRP Recovery
@rua1 for MtkDroidTools
@carliv for CarlivTouchRecovery
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
cteeto said:
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
Click to expand...
Click to collapse
Glad it worked out for you. Yes, fastboot is also an option (as you all ready know).
Recovery could probably be flashed with Flashify, but haven't tried it. I am not a developer, so no I can't port any ROM's, and take no credit for the custom recoveries listed here.
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
sandix said:
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
Click to expand...
Click to collapse
ABSOLUTLY.......this would just be AMAZING...if anyone could manage to make a Cyanogenmod for this phone.....:good:
Bricked Blu Studio C (D830U)
Hey,
Was wondering if you could help me out here, as I'm a TOTAL Noob when it Comes to BLU phones But not to flashing....
I've Bricked by Phone, The Computer and SP Flash Tools still recognize the phone..
I've Downloaded the proper ROM from NeedRom.com....
My Issues:
1. Can you Verify WHICH Driver I should Be Using for a FULL either Erase/Download Or a Firmware Upgrade (Not Sure Which)
2. I need a Scatter File the Contains ALL the Memory address and Supplies ALL the Check Marks for a FULL Rewrite Flash....The One with the rom is missing Preloader Android, Cache, and usrdata...
When I did JUST the Scatter file flash attempt I got the BROM_ERROR : S_DL_GET_DRAM_SETTING_FAIL ( 5054 )
I googled that and it said the Perloader wsn't right So I added the Perloader (And checked the "firmware.info file" and seen the Memory:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
So I tried Anyway and got the same error except this time it's 4032.
So Basically Can you tell Me Which Files In the ROM I Download Go Into Which SLOTS on SPFTools, and Which memory address' are correct the firmware file or the Scatter??
I really don't want to keep slamming the phone with "STUFF" and REALLY screw something up, I think I'm lucky it's even being recognized at this point....
Also the MTK_Allinone_DA.bin that comes with SPFTools is the right one??!?!
I'm Using Version 5.13.52.200
I'm Assuming Just a FULL Scatter file would solve the problem?!?!?
ANYHELP In this Would be VERY much Appreciated....
Thanks
Mike
EDIT:
Ok, I got it to 4001 Error, And it's saying that error is it's not connecting with the preloader, So I'm thinking (hoping) if I can get those 3 files, even if the cache is empty as long as the memory address is right, and the scatter.txt, and do a Firmware upgrade, Hope, will solve the problem, if not, On to Test Pins...
@bobl61
Could work together to enhance MTKDroid liek as
Increae number of CPU recognize by it (ex. MT67xx - just recognize it - not work with it)
Update the apk included and sued by MTKDroid (like MobileUncle/Root Explorer/SuperSU)
Upload the ROM or the link I think I know what's the problem @Miker1029
Fixed from the dead!
Swaelae113 said:
Upload the ROM or the link I think I know what's the problem @Miker1029
Click to expand...
Click to collapse
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
IMEI Problem
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
Update, Just a Heads Up I'm Assuming from Googling around, that Installing the NVRAM will wipe your IMEI, Still working on this aspect, But it doesn't seem to be Hindering the phone in anyway, As I said It Took along time to boot up, So I'm not sure if Re-writing the NVRAM made it work or not, I do know I formatted + Download, and It Sat On the Splash Screen, I shut down and Flashed just the NVRAM file, and It booted.....
NOW Should I go for a Custom Recovery??? LOL.... I'll wait.... But now that I know I can Fix it......Hmmmmm
Mike
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
bobl61 said:
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
Click to expand...
Click to collapse
Hey Thanks, Maybe you can redo it or whatever, I was bricked for Months (Mainly Because i didn't know the Phone Type), Check out the screenshots to see the extent I went to Googling My Butt Off trying to figure it out, But once I did, All went good, I've flashed Atleast 100 Phones, For me, Friends, Family, Never had the Kind of issues I had with the MTK Chipset...
But now that I have it, It's rooted, Flashed, Xposed Framework Installed and working, Exactly what I was "Originally" trying to do....LOL, It's good now tho...
Now Funny thing I lost My Compass on it, and Sensor detector says it's working fine, So Not sure what's Interfering With it.... Hate to Re-Flash
SOOO, If I GOTTA re-flash Been looking around for 6.0 (Marshmallow) Build for it (No Luck)
1st Pic, Just the Face.
2nd Pic, Where I Cut the Battery Connector (Casing) to the Board so I could Disconnect the Battery without taking the phone apart....
3rd Pic, I left the screws out as There's a Little spring on the Bottom-Left (Looking from the back) that Makes the speaker work, And On the Bottom-Right is the antenna connection that I can't get to "Snap" back in..... So I left the screws out to fix those minor issues, I'm trying to NOT open it anymore then I already have LOL
Mike
I want custom ROM for blu studio c 5+5
[Q
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
bertucci25 said:
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
Click to expand...
Click to collapse
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Miker1029 said:
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Click to expand...
Click to collapse
Ok i'm going to explain my journey from soft-to-revive history:
I was trying to install a custom recovery for my D830U (Blu) and end up in this thread. I made all the steps
-Rooted the phone with kingroot
-Removed kingroot and installed SuperSU
-Instaled insecure adbd insecure
-I made a backup of my stock rom with MtkDroidsTool(wich is the needrom provided, since i flashed my phone while ago)
-Drivers are installed (VCOM)
Everything is downloaded from the links in the post
Ok at this point i did everything exactly like the guide, great
Ok now the part were "something" failed is:
I got the scatter file in the mtkdroidstool backup folder and REPLACED the recovery to the PhilZ recovery.img in the link of the first post. And flashed normaly. Here is where things got bad
I disconnected the phone and realized it got bootloop, couldnt start the phone and can't get into recovery (when i press vol+ button it goes to black screen), because i installed a bad/not compatible philz recovery.img(AGAIN ITS FROM THE PROVIDED LINK) ok now i'm worried but no problem, i tried to reflash with original stock rom and eventually after many tries i got into a normal recovery mode and the phone boots normal..
Now my phone is at the start point. Can you tell me which version of custom recovery are you currently using? Or what procedure should i follow to get into it? Again thanks! Cheers.
Ya I'll upload the recovery i used, I'll get it here sometime today..
I'm not sure which it is, as i said, the power connection for the battery broke off the board awhile ago, so it's either philz or twrp.
Also, if I'm remembering correctly, you have to add the other drivers, not the pre driver, you can try it with the pre, and if you don't get the green check use the other ones, and when you go flash, I'd backup your recovery you have now and put it somewhere safe...
Ill also add the version of xposed i used, if i can find it.. I know i had to install the. Zip files from recovery...
Mike
I believe this is the custom recovery i flashed, i no longer have the phone to test, but i believe i removed all except the stock and custom..
As i said back up your current recovery..
Let me know so i can mark it my puter.. Thanks
Mike
Also let me add, I had a bad philz also, not sure if i got it here, or somewhere else, but i have it marked as philz doesnt work on my computer...
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Miker1029 said:
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Click to expand...
Click to collapse
Hey mike im going to test this today i'll update my progress in a few! wish me good luck :silly:
Related
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted
Credit goes to dbgr for finding this:
https://forum.xda-developers.com/idol-4s/how-to/6055u-root-method-t3598947
Link to download .rar:
https://mega.nz/#!U24zwYbQ!MwbIX_D01OyHHldd8c_9iCmht6wzcw1duNpGO-PRyWI
This is just a simpler, more detailed guide on how to root this phone.
Forgive me for the lack of pictures, its pretty straightforward anyways. I have included a .rar with this post that has all the essential files you will need.
(I only compressed the .rar, everything else credit goes to the creators)
1. Download the rootpackage.rar i have included, and decompress to somewhere safe.
2. Install SugarQct and install the drivers that came with it. (In the SugarQct installer, not the usb driver folder)
3. After that has finished, open the usb driver folder and run the setup.vbs script there. It should only take a second or two to run.
4. Plug phone into pc.
5. Place supersu.zip onto phone. You can put this anywhere, doesn't really matter.
6. Turn phone off and place into download mode. (Phone must be plugged in to allow download mode)
4. Open sugar with phone plugged in. Be sure to upgrade sugar if you can't see the 6055u in the list.
Set to 6055u, go to options, select save user data. Now press upgrade.
5. While sugar is downloading overwrite the r*****.mbn in bin/6055-*****. This folder appears once you start to download to the phone. You must rename the twrp_recovery_idol4_6055.img to the name of the r*****.mbn.
6. Overwrite again while files are being written. Do this as many times as you please. I only overwrote it more than once as a safety precaution.
7. Before sugar has completed fully, but after files are written, this should be around the time when it starts to download more files. As long as the writing completes you are good to go.
8. Turn phone on and enter recovery mode (power + volume up).
9. In the custom recover menu tap install and install the supersu.zip from the directory you placed it in.
10. Give it a couple of seconds (mine took 30 or so)
11. Allow phone to be rebooted and its now rooted!
Now I've had some interest in using magisk instead of supersu, but i haven't been able to install it after supersu. Choose your rom to flash wisely, as its a pain in the ass to go back from.
Please enjoy your newly rooted Alcatel Idol 4!
Thanks all!
P.S. If someone can dump their standard rom before they flash supersu.zip onto their phone, i'd like to try and find a way to get a custom rom goin and that would help.
I'm not seeing the download for the .RAR file. Am I missing something?
SeanMcCarte said:
I'm not seeing the download for the .RAR file. Am I missing something?
Click to expand...
Click to collapse
I thought i attached it to the thread, give me a second and i'll try again.
Edit:
It seems my rar is too large, i'm headed to work now, but i'll try and get something uploaded in a bit.
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
SeanMcCarte said:
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
Click to expand...
Click to collapse
As far as i know it doesn't have to be, but when i was successful i believe i had the phone plugged in. I did try to do somethings earlier today and unplugged the phone, and it was not successful. I do not know if it was because i unplugged the phone or if it was because i had failed to rewrite the recovery flash.
Thank you. I actually didn't want to wait for .rar so I just pieced the files from the forum here. Thank you anyway,at least somebody else will get the RAR. Also,my phone was plugged in when it worked.
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
scofield119 said:
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
Click to expand...
Click to collapse
Theres another guide for the 6055k, i'm not sure if this will work for that one. I know it works for the cricket version and i see no reason why it wouldn't work for the 6055k, but it is a better idea to follow the guide made for the 6055k.
link22534 said:
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Click to expand...
Click to collapse
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
NeonWhitey said:
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
Click to expand...
Click to collapse
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
link22534 said:
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
Click to expand...
Click to collapse
Thanks for the info, but funnily enough i'm having difficulties getting the damn thing rooted again.
Thanks for the write up, I've flashed and reflashed many times... you have to be carefully about when you interrupt the process. Also know that a newer version is out. Cheers mate.
I'm not sure if it's the latest version of Sugar, but I've been trying so many times, but to no avail. Has anyone had any luck on the new version?
SUGAR QCT_SP V11.3.0
I've gotten to the point that when I start the upgrade with Sugar, it says my phone is already rooted. However, when I try to access Recovery, there is no option to install TWRP. It looks like it just loaded the same old recovery...no matter how fast and how many times I replace the Rxxxxxx.mbn file.
Cheers,
Wickster
6055p
is there any guide to root 6055p model
no luck getting this to work guys, could really use some help
Having the same problems as PizzaG - tried all the timing tips no TWRP
Having the same situation as PizzaG - same Cricket version, using the newer version of Sugar QCT 11.1.3. I've tried starting right after it reaches the last written file (4095M), Ive even tried waiting until you get the vibrate and Alcatel logo (which happens at the very end of the download, but was someone's tip), same story, boots into Android recovery. Any other tips?
Possible Solution to Rooting Troubles
I was having the same troubles as the above posters. What seemed to be the problem was that I had set a pin code to unlock my device, which made it encrypted. Unfortunately, the only way to remove a pin is to do a factory reset. Anyway, I did a factory reset and ran sugar immediately after - making sure to start the phone before sugar finished - and it worked! Perhaps there is something simpler to do and I didn't have to do a factory reset, but I don't know what that is, and this worked.
Someone have try with the 6055A?
hmm, im noticing mine says encrypted as well but i never set anything for security. just the swipe. @ ThisEndsInTears did you do a factory reset from stock recovery or from withing the phone settings? Thanks much, hopefully one step closer to getting this rooted. Y has nobody developed cm for 6.0.1 for this? cm13 im pretty sure it is
Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Slightly better picture without anything cut off.
reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Two things, I got access to my old account after a password reset
and, I got my tab back up and running, as well as root & xposed + gravitybox
I'm working on a guide as we speak.
Also, I will be dumping my firmware and adding the 10001885 to the list of stock image dumps on the main onn thread.
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
Ankylo'sburner said:
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Click to expand...
Click to collapse
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
Hey, i've had that same issue but have since fixed it by flashing the rom to the 100011886. I used some of the posts here to flash both vbmeta.img and boot.img to gain root, with success https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing . i eventually went too far and currupted my rom and had a hard time finding the stock ROM. I found the stock ROM to the 100011886 and flashed that to fix the problem, now i run that as my system and it boots up just fine. https://www.mediafire.com/file/107jp6gwbiwq87q/MT8168_ONN_Gen2_100011886.zip/file
fastboot erase super
fastboot flash super super.img
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
onn. said:
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
Click to expand...
Click to collapse
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
KMerrimanJr said:
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
Click to expand...
Click to collapse
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
I wish I would have waited until I read this today instead of further messing with it yesterday. It looks like everything you have is what I need, but now I am battling trying to get the COM port to stay active when the device is plugged in. I'll tinker with it and see if I can get back to the state I had it in yesterday where it was staying connected.
KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
Would you happen to know/remember all the settings you checked in SP Flash Tool (I assume you used that) when you flashed things to get it working? It seems that my PC is able to communicate with the device again, but I'm unsure of how to proceed next.
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
It's hard bricked at the moment unfortunately, so there's no appearance of life to it. Attached picture is the error I get. https://www.gizmoadvices.com/list-sp-flash-tool-error-codes-solution-fix/ appears show info about the error, but it's not something I know how to fix yet.
The only way I can get the tablet to make moves in device manager (which I assume is a sign that the PC can at least partially recognize/see the device) is to click on Download in SPFT, connect tablet to PC via USB cord, and then hold down power button, which led to the error. Errors in SPFT I've received so far are 0xC0060001 and 0xC0060003.
When the tablet is active in the device manager, I assume that the device is in a powered state. However, when the device is grayed out, I assume it's in a powered off state (see other pic). I've yet to find away to actually flash anything to it.
KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
Also, apologies if I'm being a bother, but do you know what version of SPFT you used as well as which DA file?
bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
where did you get this? did you dump it? if so how?