Related
My question is regarding flash stock + unroot using the Nexus Root Toolkit v 1.6.3
I have already unlocked and rooted my phone using the tool.
I am now trying to flash stock + unroot using the Nexus Root Toolkit.
I downloaded the build from Google's Factory Image Download page.
I get passed Which Factory Image? by clicking Other/Browse
Choice: I downloaded a factory image myself that I would like to use instead.
Choose a google facotry image: mysidspr-ga02-factory.tar
Analyzing factory image; please be patient
Hascheck Verification
Enter the md5 has given for: mysidspr-ga02-factory.tar
I enter: c93156606b39a6b61d371ef935a6a6ba from googles website.
Message pops up: Your file is good to extract and flash! Press OK to continue.
Please be patient...Checking ADB Status
Device Connected Rebooting your device into bootloader mode
Chekcing Fastboot Status
Device Connected
Checking Fastboot Status
Device Connected
CMD window opens
Booting up your freshly flashed stock device
Wait for your device to finish booting up...
- It will appear to be boot looping; just wait...
-It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember to re-enable USB debugging if you plan on using the toolkit to perform other operations
Press any key to exit...
My phone remains on the Bootloader screen with the robot laying down with its hatch open.
Bootloader is on Start
below robot:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - toro 32GB
HW VERSION - 14
BOOTLOADER VERSION - PRIMELC03
BASEBAND VERSION - L700, FC12 COMA - L700, FC12
CARRIER INFOR - NONE
SERIAL NUMBER - 0A3C2C620401C009
SIGNING - production
LOCK STATE - UNLOCKED.
I have gone through this over and over and have waited anywhere from 15 minutes to 3 hours. Nothing else occurs.
So I click Press any key to exit from the command window and restart my phone and it is still on Android 4.1.1
Any suggestions/help would be greatly appreciated.
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Doesn't work for me too..
tessorodesoto said:
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Click to expand...
Click to collapse
I tried to do both ways but it doesn't work for me either..
I have Galaxy Nexus with Android 4.2.1. I have managed to unlock and root my phone easily using Nexus Root Toolkit 1.7.1. However when it comes to flash rom+unroot process, it is not working.. I tried to flash Android 4.2.2 and Android 4.3 by choosing both options but the process always stopped in the beginnig of CMD prompt window..
same problem
I rooted my newly aquaried nex which was a fully stock 4.1 in anticipation of flashing to boost and custom roms and all that fun stuff. NOW I cant flash I CANT change os. I CANT FACTORY RESTORE I CANT DO CRAP I HAVE A FREAKING PAPER WEIGHTT because I don't want sprint and there is no way ill put this back on ebay and give the head ache to someone else. HAS ANYONE FIGURED ANYTHING OUT YET? I can really use a hand. Ive spent over 15 hours researching downloading flashing fast booting etc. and I've gotten nowhere ANY HELP would be GREATLY APPRECIATED.
Hello everyone,
I got Atrix 2 from my friend. I really like the phone except few things:
1. I can't arrange the icons manually.
2. Mine is Indian version mobile & it doesn't support any Call Recorder. I can install the recording app, but it is not working.
3. There is no bubble type notification for any app like - WhatsApp, Gmail, Facebook etc.
4. There is no quick access Icons in notification area for Bluetooth, Mobile Data, Wi-Fi etc like Samsung.
This is my first Android phone so I don't know anything about CFW & how to install in my phone.
Anyone please help me to install CFW step by step
I'm Running Android 4.0.4 Official Firmware.
When I Press and hold the Power and Volume down buttons, a black screen appears says:
AP Fastboot Flash Mode (S)
0A.73
Battery OK
OK to Program
Connect USB
Data Cable
When I Press and hold both Volume Up & Down + Power, a black screen appears says:
Boot Mode Selection Menu (0A.73)
Vol Up Selects, Vol Down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
BP Tools
When I select Recovery, First show the Moto Emblem & then stuck with logo with triangle exclamation .
When I select Fastboot & BP Tools, my boot as normal.
1. What is Recovery Mode? How to install this?
2. What is ROOT? How to ROOT?
3. Which one do first - Install Recovery Mode or ROOT?
4. If I need to install CFW, do I need to copy all the files in Memory card or use RSD (I seen one video in youtube)?
SEEN LOTS OF POSTS SAYING 'HOW TO INSTALL CUSTOM ROMS' & I MORE CONFUSED WITH Recovery Mode, ROOT, RDS.
IF THERE IS A DOWNLOAD LINK, IT'S OK. BUT PLEASE DON'T GIVE LINK TO 'FOLLOW THIS'!!!
vichumvk said:
Hello everyone,
I got Atrix 2 from my friend. I really like the phone except few things:
1. I can't arrange the icons manually.
2. Mine is Indian version mobile & it doesn't support any Call Recorder. I can install the recording app, but it is not working.
3. There is no bubble type notification for any app like - WhatsApp, Gmail, Facebook etc.
4. There is no quick access Icons in notification area for Bluetooth, Mobile Data, Wi-Fi etc like Samsung.
This is my first Android phone so I don't know anything about CFW & how to install in my phone.
Anyone please help me to install CFW step by step
I'm Running Android 4.0.4 Official Firmware.
When I Press and hold the Power and Volume down buttons, a black screen appears says:
AP Fastboot Flash Mode (S)
0A.73
Battery OK
OK to Program
Connect USB
Data Cable
When I Press and hold both Volume Up & Down + Power, a black screen appears says:
Boot Mode Selection Menu (0A.73)
Vol Up Selects, Vol Down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
BP Tools
When I select Recovery, First show the Moto Emblem & then stuck with logo with triangle exclamation .
When I select Fastboot & BP Tools, my boot as normal.
1. What is Recovery Mode? How to install this?
2. What is ROOT? How to ROOT?
3. Which one do first - Install Recovery Mode or ROOT?
4. If I need to install CFW, do I need to copy all the files in Memory card or use RSD (I seen one video in youtube)?
SEEN LOTS OF POSTS SAYING 'HOW TO INSTALL CUSTOM ROMS' & I MORE CONFUSED WITH Recovery Mode, ROOT, RDS.
IF THERE IS A DOWNLOAD LINK, IT'S OK. BUT PLEASE DON'T GIVE LINK TO 'FOLLOW THIS'!!!
Click to expand...
Click to collapse
If this is your first android then you're going about it all wrong. It is highly recommended that you take the time to read about what you're doing and what you need to do to get to where you want to be with this phone. I'm strongly opposed to reiterating step by step directions because I feel it leads to trouble for new users that, too quickly, get in over their heads without the necessary knowledge to get themselves out of trouble but I'll help you with some general info to get you started. :thumbup:
The very first thing you should do is find out which FXZ (stock firmware) is the correct one for your specific phone. Then you'll need to download RSD lite and familiarize yourself with how to use it for flashing the stock firmware. If/when it becomes necessary to use these tools you'll be glad that you took the time to learn rather than searching and posting frantically to figure out how to recover a soft brick.
Stock recovery is useless for what you're trying to accomplish.
There are multiple root methods available and can be found in both the general section as well as the development section. After you get rooted you'll need to download and install Boot Menu Manager (aka BMM) in order to install custom ROMs. There are tutorials on how to install and use BMM in the general section.
The most important tool you can have at this stage is patience. Take the time to educate yourself and you won't be sorry. Good luck and welcome to the community.
Thank you 1BadWolf.
I don't know which FXZ (stock firmware) is the correct for my phone.
This is my phone datails
Can u tell me which FW is that & download link?
Before flashing with the stock firmware, I need to backup all my data. How do I do that?
vichumvk said:
Thank you 1BadWolf.
I don't know which FXZ (stock firmware) is the correct for my phone.
This is my phone datails
Can u tell me which FW is that & download link?
Before flashing with the stock firmware, I need to backup all my data. How do I do that?
Click to expand...
Click to collapse
At the top of your screenshot you'll see the system version as
672.1.18.MB865.AsiaRetail.en.03
Go to this page:
http://sbf.droid-developers.org/phone.php?device=17
And find the corresponding firmware that will say
Blur_Version.672.1.18.MB865.AsiaRetail.en.03
That's the one you need.
I'd say that once you download that and RSD lite then familiarize yourself with what to do with it via:
http://forum.xda-developers.com/showthread.php?t=1909319
then you be safe to go ahead and root it. You'll need root to get a good backup of everything anyway. The main thing is learning to recover from a soft brick before it happens. That thread has all the info you need for that.
1BadWolf said:
At the top of your screenshot you'll see the system version as
672.1.18.MB865.AsiaRetail.en.03
Go to this page:
http://sbf.droid-developers.org/phone.php?device=17
And find the corresponding firmware that will say
Blur_Version.672.1.18.MB865.AsiaRetail.en.03
That's the one you need.
I'd say that once you download that and RSD lite then familiarize yourself with what to do with it via:
http://forum.xda-developers.com/showthread.php?t=1909319
then you be safe to go ahead and root it. You'll need root to get a good backup of everything anyway. The main thing is learning to recover from a soft brick before it happens. That thread has all the info you need for that.
Click to expand...
Click to collapse
Today I flashed my Atrix 2 with stock ROM that u given in the link.:good:
It is successful without any bricks & errors.
I also followed the video that in YouTube:good:
When the first boot after flashing, the screen was locked & when I try to unlock, it won't unlock.
So followed this thread & tried with the SIM. It worked.
And I aslo find how to get wipe/reset data & cache in stuck with logo with triangle exclamation .
When appear this triangle exclamation, just hold both Volume Up+Volume Down button.
What is the next thing I need to do? ROOT?
vichumvk said:
Today I flashed my Atrix 2 with stock ROM that u given in the link.:good:
It is successful without any bricks & errors.
I also followed the video that in YouTube:good:
When the first boot after flashing, the screen was locked & when I try to unlock, it won't unlock.
So followed this thread & tried with the SIM. It worked.
And I aslo find how to get wipe/reset data & cache in stuck with logo with triangle exclamation .
When appear this triangle exclamation, just hold both Volume Up+Volume Down button.
What is the next thing I need to do? ROOT?
Click to expand...
Click to collapse
That's it. Just root and install BMM then you'll be ready to go. After that comes the hard part.... deciding which of the awesome ROMs to install, hahaha. :sly:
I rooted my phone with these downloaded tools.
And installed almost 4.4.4 CFW without any brick & errors.
I like LiquidSmooth 4.4.4.
I found these helpful links for Beginners:
1. Beginners Guide
2. Tutorial For Official Firmware
3. Tutorial For Custom Firmware
4. Tutorial Thread
AND
Senior Member 1
Senior Member 2
Thank you 1BadWolf & Aceofzeroz
Don't know if this is a good place to post but after days of searching various threads and forums
I decided to make a general HUAWEI G6 thread to help myself and others!
So a friend gave me this phone and I know very little about its history, only that it was rooted.
Also on the battery it says sample, not sure if that changes anything. It's all functional.
Bugs that I have found:
1) Screen doesn't always wake after pressing power button, but the keys do. Installed gravity app, same problem, so it's not the button.
2) Wifi keeps connecting and disconnecting.
3)Major battery drain (maybe after I rooted again and turned on mobile data) lasts about 6hours even when idle.
So I wanted to flash a new rom.
First I rooted the phone with RootGenius and it gave me a message prior to rooting that the phone is rooted. Since I couldn't use some
apps that required root I did a Quick root and gained root and King User was installed.
Second, tried to find L-22 firmware. I found only G6 L-11 and G6 L-33, so I wonder are they compatible?
Third, tried to flash CWM recovery but when rebooting into recovery I always get stock android recovery.
And, when looking in Rom manager, under Recovery Setup, under Recovery Already Installed I get CWM Recovery and
Team Win Recovery Project (TWRP). This one baffles me.
Fourth, do I have to unlock my bootloader and how? (do I need a code or is there a faster way?)
I tried installing L11 firmware downloaded from Huawei support by enetering stock recovery but the instalation
aborted and I got a message: update packages ext name error.
And this that I noticed:
Power button + up - enter recovery
Power button + down - bootloader (but my phone always gets stuck on the logo and I have to wait for the battery do die)
So I hope that somebody will be able to help and make this thread useful for others.
How to flash, unlock, which rom is compatible and so on...
I see lots of small threads regarding this phone but none of them are helpful.
This is a great phone and I would love to be able to use it.
So I guess I'll take this in little steps.
Can somebody tell me if this is normal? (attachment included)
I charged my phone all night, went to work, listened to about 45 min
of music, used about 10 minutes of reddit is fun app, got an occasional
text or call.
Mind you that I have uninstalled all bloatware, stock apps that I don't use,
most of google services, run a black background, use only 3g (had to install Xposed
and Intelli3g to achieve that). There were approx 150 apps, now maybe 60 that came with
the system. I think that I disabled almost everything I could in order to preserve the battery.
Is it maybe that the battery is weak? Phone was used before and I don't know to what extent,
but I somehow doubt that it could be used so much to wear it this much. Since it is rather new
on the market.
I would be ever so grateful if anyone could put their 2 cents, this is my first better phone and I would
hate to have to give up on it.
CityofSyria said:
Don't know if this is a good place to post but after days of searching various threads and forums
I decided to make a general HUAWEI G6 thread to help myself and others!
So a friend gave me this phone and I know very little about its history, only that it was rooted.
Also on the battery it says sample, not sure if that changes anything. It's all functional.
Bugs that I have found:
1) Screen doesn't always wake after pressing power button, but the keys do. Installed gravity app, same problem, so it's not the button.
2) Wifi keeps connecting and disconnecting.
3)Major battery drain (maybe after I rooted again and turned on mobile data) lasts about 6hours even when idle.
So I wanted to flash a new rom.
First I rooted the phone with RootGenius and it gave me a message prior to rooting that the phone is rooted. Since I couldn't use some
apps that required root I did a Quick root and gained root and King User was installed.
Second, tried to find L-22 firmware. I found only G6 L-11 and G6 L-33, so I wonder are they compatible?
Third, tried to flash CWM recovery but when rebooting into recovery I always get stock android recovery.
And, when looking in Rom manager, under Recovery Setup, under Recovery Already Installed I get CWM Recovery and
Team Win Recovery Project (TWRP). This one baffles me.
Fourth, do I have to unlock my bootloader and how? (do I need a code or is there a faster way?)
I tried installing L11 firmware downloaded from Huawei support by enetering stock recovery but the instalation
aborted and I got a message: update packages ext name error.
And this that I noticed:
Power button + up - enter recovery
Power button + down - bootloader (but my phone always gets stuck on the logo and I have to wait for the battery do die)
So I hope that somebody will be able to help and make this thread useful for others.
How to flash, unlock, which rom is compatible and so on...
I see lots of small threads regarding this phone but none of them are helpful.
This is a great phone and I would love to be able to use it.
Click to expand...
Click to collapse
Hello !
When your device enter in bootloader mode , is the same like " phone always gets stuck on the logo " - so right now your device is in bootloader mode !
You can acces device only with fastboot commands and NOT with adb commands !
You can put your device in bootloader mode : manually ( by pressing combo key ) or by this command : adb reboot bootloader
You can reboot device from bootloader mode : manually ( press & keep power button more than 15 sec. ) or by this command : sudo fastboot reboot ( for linux ) or fastboot reboot ( Win ) !
It seems that your device still have an locked bootloader because you are not able to reboot your device in CWM/TWRP mode , after you already installed one of them !
Flash custom recovery : sudo fastboot flash recovery twrp-recovery.img
Reboot device : sudo fastboot reboot
Reboot your device in TWRP recovery : adb reboot recovery
Now if your device boot into stock recovery, it seems that you have a device with a locked bootloader .
To unlock your device bootloader you should search on Huawei support if your device is able to be unlocked .
Best regards !
Thanks for replying! I'll try and follow what you said.
Thank you!
Problem with rooted phone
Hi,
I rooted my Huawei G6-L22 using KingoRoot. I'm able to access as su from ADB.
I succeed to mount /system but any file that I put here, gets removed after phone reboot.
I tried to do unroot with KingoRoot but it didn't work.
Android Version: 4.3
Build Number: G6-L22V100R001C649B138
Is there any explanation to this problem?
Thank you.
The BLU LIFE XL phone is an unlocked GSM platform device.
Currently there are absolutely no threads on the internet with information related to this device. I am not responsible for any damage done to your device, you assume sole responsibility for whatever you do to your devices. If you have questions, please reply to this or PM me, I'll be glad to help any of you!
================
Things you should know before you do anything listed in this post:
- Bootloader unlocking WILL ERASE USER DATA!!!!
- Successful root attempts disable OTA updates. (Unroot + Factory Reset MIGHT fix this)
- You must have OEM unlocking & USB debugging enabled in the developer menu.
- Common sense, don't flash anything you find on the internet randomly, you will cause irreparable damage, I learned that the hard way.
- Download & install the ADB Universal drivers & Android SDK tools (links @ bottom)
================
If you'd like to make a backup of your stock ROM, you can use romdump, it's a nifty tool that does exactly what it says, and it works on pretty much any rooted android phone. (yay) DL: http://d-h.st/ErS
- Download & extract to root directory of your sdcard.
- Open Root Browser (Or any file browser that's for rooted devices)
- Navigate to the path where you copied/downloaded romdump
- Move romdump to /data/local/
- Long press romdump and check all 3 rows of boxes above and press"OK"
- Open terminal emulator (or any equivalent terminal emulator app)
- Type "export PATH=/data/local/bin:$PATH"
- Type "su"
- Type "chmod 04755 /data/local/romdump"
- Type "/data/local/romdump"
- Wait until the process finishes, do NOT do anything with your device, set it down and leave it.
================
Rooting The Device:
- Have USB debugging, OEM unlocking & unknown sources enabled.
- Download & install the latest version of KingRoot.
- Swipe up three times, press "try it"
NOTICE: If your device restarts through the process, don't worry, your device isn't broken, but there's a good chance the root attempt failed.
================
Unlocking/Locking The Bootloader (THIS WILL ERASE ALL OF YOUR DATA!):
- Power off the BLU LIFE XL
- Hold down POWER + VOL UP until the phone turns on.
- Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
- Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
- Plug your phone into your computer
- Navigate to your android SDK folder, and find fastboot. (If you don't have the android SDK downloaded, refer below)
- Type fastboot devices and see if your android device is recognized.
- Type "fastboot oem unlock"
- A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
Alternatively, if you wish to re-lock your bootloader, follow these steps above, however type "fastboot oem lock" instead of "fastboot oem unlock"
================
FACTORY MODE & DEVICE TESTING MENUS:
- Power off BLU LIFE XL
- Press POWER & hold VOL DOWN until the phone turns on.
- Release grip of power button, whilst holding VOL DOWN.
================
Downloads:
Android SDK: https://dl.google.com/android/android-sdk_r24.4.1-windows.zip
ADB Universal Drivers: http://www.mediafire.com/download/uo3t409a9vz3kh3/adbdriver_v1.0.zip
KingRoot: https://androidmtk.com/download-kingroot-application
Romdump: http://d-h.st/ErS
My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?
redkvothe said:
My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?
Click to expand...
Click to collapse
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
By the way, I also replied to your comment on reddit.
TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse
blkkalel said:
TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse
The ROM I have dumped has personal applications and accounts integrated, I will get around to dumping a clean ROM for you guys soon.
Papa bless
Click to expand...
Click to collapse
BLU Life XL needs all that the mainstream devices have.
Thank you for the info above. It's such a shame this device has such limited info online. I'm not really a Noob, but also not close to a developer. How does one go about creating a custom recovery and a sweet ROM? Do you think you tube might have a how to that is on point or is there a spot here that we as users could request pros to check on it?
BLUE LIFE XL (L050U) has anyone else been successful using this root kit?
@do_root / TheDarknessz0rz, hey just wondering if the BLUE LIFE XL (L050U) you designed this tutorial for had a specific build that is needed to do this without bricking (like markressler/redkvothe whotf-ever did with his device)? In other words what was the build# of the L050U you designed this root process around? Just wondering man so I can get this done without any worries. I shouldn't have any issues using your root process on my BLU LIFE XL (L050u) Build: ALPS.L1.MP6.V2.15.2_6592.WET_P37 Custom Build version: BLU_L050U_V12_GENERIC, right? I've rooted every android device I've owned back to the original Droid1 without ever bricking during the flashing process. Just wondered if there might be a specific reason this other dude bricked his device.
Thanks in advance for even making a root kit for this device. Would appreciate any advice you have here.
-jim :fingers-crossed:
Edit: I'm ready to do this - just wanted to hear your feedback before I give it a rip.
@heatgap, I also have a L050U device. Where you able to unlock bootloader and root your BLU LIFE XL using the procedure desribed above? BTW, Thank you @TheDarknessz0rz
I am new at rooting, etc... Any additional steps you had to do? Or any advice you might give a rookie/noob to be able to get this done?
Many thanks!
Sisafokker
MOSTLY Stock images / Seeking assistance with recovery
Okay, I've dumped all of the raw images.
Most of them are stock, with the exception of system.img and recovery.img
recovery: insecure ADB, which really does no good until I can put together a custom recovery, or at least get a shell.
system: pre-rooted with SuperSU. Also, will NOT reflash recovery to stock on reboot.
Coming from stock, after you've backed up your user data (because it will be wiped), boot into fastboot mode.
Issue a "fastboot oem unlock-go" to unlock the bootloader. (This only has to be done once.) THIS WIPES EVERYTHING!
Then "fastboot flash system system.img" (This takes a while.)
After first boot and setup, download SuperSU from play store, install and update.
I'm working on putting together a working custom recovery, but I'm not an expert at this.
Succeded!!! Rooted device!
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker
This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance
br21763 said:
This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance
Click to expand...
Click to collapse
I do not have any stock images, the images i have are for my device specifically, i'd have to rid the image of custom files first.
Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again
br21763 said:
Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again
Click to expand...
Click to collapse
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.
sisafokker said:
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker
Click to expand...
Click to collapse
My device always returns status locked when I tell fastboot to dump the variables. I'm not sure why, bootloader unlock process says it's successful, however when it comes time to press VOL_UP to finish the process, none of the hardware keys are recognized, I've even issued fastboot continue from command prompt, yet the bootloader refuses to unlock. I'm going to try once more with "fastboot oem unlock-go" and see what happens from there.
TheDarknessz0rz said:
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.
Click to expand...
Click to collapse
Don't mean to sound so clueless but how would I go about doing that? I mean I couldn't find any firmware anywhere, even for other models so could you help me with that part? Also would I be flashing it from the "apply update from sd card" option on the stock recovery?
Thanks a lot
Never mind, I was able to figure out how to flash the system.img file onto my phone. Now it seems to be working perfectly. Thank you very much for all of the help and for uploading the img files, i really appreciate it.
Have a nice day
blu-life-xl Hard brick No problem !!!!!
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site
BLU download site
samgr said:
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site
Click to expand...
Click to collapse
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file
hard brick NO! problem
Rickrocks013 said:
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file
Click to expand...
Click to collapse
try it it works!!!!!!!!!!!!!!!!!!!:laugh:
Hello Guys,
i had some problems with my tablet and deleted my system (doh) ...
Now i see just "Powered by Android" and nothing is working to get
into Download Mode or Recovery or whatever.
My question is: can i do something or is the tablet lost?
Thanks,
regards.
Neeschar said:
Hello Guys,
i had some problems with my tablet and deleted my system (doh) ...
Now i see just "Powered by Android" and nothing is working to get
into Download Mode or Recovery or whatever.
My question is: can i do something or is the tablet lost?
Thanks,
regards.
Click to expand...
Click to collapse
You need to be able to get to download mode.
If not, you'll have to send it to a repair shop that offers JTAG serbice.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Thank you for replay,
i found that i can switch to EDL because of a post from gandharva.
Now the Sugar-App finds my tablet, but is failing at switching to download mode
and says that i need to check driver and handset.
The question is, what can i do now? I just know about sugar but if it cant switch
to download mode .. i will charge the tablet and hope it helps, because it was
all on over night (it wassnt going off).
Im in panic-mode and sry for the bad english ^^
UPDATE: Found out that EDL is the emergency download mode ... how i can use that to flash
android and/or recovery? Why is sugar trying to enter download mode and fails if the tablet
is in the edl. There is a text "BEWARE: ..... needs 2 accu-bars for download": Means that for
switching or the download of the android system? hmmm ...
Neeschar said:
Thank you for replay,
i found that i can switch to EDL because of a post from gandharva.
Now the Sugar-App finds my tablet, but is failing at switching to download mode
and says that i need to check driver and handset.
The question is, what can i do now? I just know about sugar but if it cant switch
to download mode .. i will charge the tablet and hope it helps, because it was
all on over night (it wassnt going off).
Im in panic-mode and sry for the bad english ^^
UPDATE: Found out that EDL is the emergency download mode ... how i can use that to flash
android and/or recovery? Why is sugar trying to enter download mode and fails if the tablet
is in the edl. There is a text "BEWARE: ..... needs 2 accu-bars for download": Means that for
switching or the download of the android system? hmmm ...
Click to expand...
Click to collapse
Are you sure you have the USB drivers for your device model number properly installed on your PC?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I used the driver that comes with new sugar version ...so i dont know if its the correct one
or not. I try a bit with the drivers (got 3 or so), maybe its working then but i just get the
device into edl if its fully empty (and i dont press at any time power button ...or its in bootloop
again and doesnt go off. Holding the power button just restarts the device and then edl issnt working anymore).
I really dont want a stone for 130euro ... ^^ (hope it can be flashed sometime)
Neeschar said:
I used the driver that comes with new sugar version ...so i dont know if its the correct one
or not. I try a bit with the drivers (got 3 or so), maybe its working then but i just get the
device into edl if its fully empty (and i dont press at any time power button ...or its in bootloop
again and doesnt go off. Holding the power button just restarts the device and then edl issnt working anymore).
I really dont want a stone for 130euro ... ^^ (hope it can be flashed sometime)
Click to expand...
Click to collapse
Here are the device drivers that you should have installed on your PC.
https://androidmtk.com/download-vodafone-usb-drivers
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Thanks,
i installed it but the same problem:
http://abload.de/image.php?img=hangingj7kxc.png
Still hanging and the same error that i need to check driver/handset.
What is with an another tool like SW Downloader, QPST and so on?
SW Downloader doesnt got my chipset but maybe an other
app can do an stock flash? PCs are much easier to handle ...
UPDATE: Okey, any other Software doesnt find the tablet and i think
its not the edl mode if i use volume up + down for 10secs (in black screen)
and then connect usb ... but any other combo breaks the tablet (like i said above).
Maybe its a good idea to go to a repair shop ... but maybe the repaircosts are the same
like a new one (and my issnt that old).
Neeschar said:
Thanks,
i installed it but the same problem:
http://abload.de/image.php?img=hangingj7kxc.png
Still hanging and the same error that i need to check driver/handset.
What is with an another tool like SW Downloader, QPST and so on?
SW Downloader doesnt got my chipset but maybe an other
app can do an stock flash? PCs are much easier to handle ...
UPDATE: Okey, any other Software doesnt find the tablet and i think
its not the edl mode if i use volume up + down for 10secs (in black screen)
and then connect usb ... but any other combo breaks the tablet (like i said above).
Maybe its a good idea to go to a repair shop ... but maybe the repaircosts are the same
like a new one (and my issnt that old).
Click to expand...
Click to collapse
Maybe you don't have USB debugging enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Oh yes,
i resettet it and then the option is disabled again ...oh damn ...
but without a system, there cant be usb debugging mode on or ...
Can a shop bring the tablet into usb debugging mode or can i do
that ? I think i need to open it ... not really much tutorials in the net
for this tablet, thats really a problem but 130€ for a 2gb ram device
was a good shot. damn damn damn ....
But thanks for your help, never had so much problems with flashing
and co... with wii, psp, galaxy and so on ^^
Sry for doublepost but im in Recovery (cyanogenmod)!!!!
What need i to do now? Can i activate usb debugging there?
I saw a video (and testet it ..but however, this time it worked volume down + power, because it was off not in bootloop)
I will love you if u can help me to revive it
PS: I see the device now in ADB ..but i really dont know how to flash it now, because i got just the backup
from sugar, but thats so many files. Got an boot.img (thats patched) from the Root-Thread here on xda.
Is there a source, there i can download a rom for flashing with cyangenmod-recovery or adb? (a trustworthy
source ...i dont find any (on mtk too) for vf1400.
Update2: I tested if i can go into edl over ADB and it worked ... Sugar finds the device and can boot into
download mode ... but the download is very slow, so i decided to try what MrFX did and renaming the
old firmware to the new one ... so i closed sugar ...and now my device is again in the bootloop ... so i need
to wait for the battery to get off or i cant get it into recovery again.
I will post tomorrow more if i get anything to work ^^
Neeschar said:
Sry for doublepost but im in Recovery (cyanogenmod)!!!!
What need i to do now? Can i activate usb debugging there?
I saw a video (and testet it ..but however, this time it worked volume down + power, because it was off not in bootloop)
I will love you if u can help me to revive it
PS: I see the device now in ADB ..but i really dont know how to flash it now, because i got just the backup
from sugar, but thats so many files. Got an boot.img (thats patched) from the Root-Thread here on xda.
Is there a source, there i can download a rom for flashing with cyangenmod-recovery or adb? (a trustworthy
source ...i dont find any (on mtk too) for vf1400.
Update2: I tested if i can go into edl over ADB and it worked ... Sugar finds the device and can boot into
download mode ... but the download is very slow, so i decided to try what MrFX did and renaming the
old firmware to the new one ... so i closed sugar ...and now my device is again in the bootloop ... so i need
to wait for the battery to get off or i cant get it into recovery again.
I will post tomorrow more if i get anything to work ^^
Click to expand...
Click to collapse
If adb is recognizing the device then you should not need to worry about USB debugging.
If your device uses fastboot then you might can just directly flash your stock firmware.
Or extract the firmware to separate the individual .img files then use fastboot to fastboot flash the individual .img files.
Or you might can use dd commands to dd the individual .img files to their respective partitions (mmcblk0). The dd commands have to be exact or you'll make things worse.
If you aren't fimiliar with dd commands then I wouldn't use them until you researched how they work and research exactly which partition (mmcblk0) is which on your device and which .img goes to which mmcblk0.
I'm not familiar with Sugar so I don't know how to help you with that.
If you are booted into recovery then you should be able to flash a custom ROM if any exist for your model number.
You might need to use the Cyanogenmod recovery to convert over to TWRP recovery. If I remember correctly, Cyanogenmod recovery tends to give issues with root, SuperSU and ROMs.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Thanks for your answer,
i didnt understand all of your text, so i needed google for it.
I revived my Device and for the share, i want to do a tutorial.
Some Infos:
EDL: You can enter EDL with ADB. Just download the minimal setup of ADB with Fastboot.
Check with the command "adb devices" if your device can be found. To enter EDL, just type
"adb reboot edl" into terminal and hit enter. You need USB Debugging on under Development-Options
under android to boot into EDL. If you got no android (system) on your device, just go into recovery
and then boot into EDL with ADB (USB Debugging is not important then, bc sugar can flash it so or so).
Recovery: Your device need to be completely off (black screen). If you got bootloop (powered by android),
let the battery go off (empty battery). After the battery is empty, plug it into usb adapter for loading and
wait so 30min (you can check the state of battery if you press short on power button). Press Power-Button
and Volume-Down-Button at the same time and hold it till the recovery appears! Connect the usb cable
now to the pc.
If you got no system on your device, the tutorial is right for you. If you got an system, you need USB-Debugging
on for booting into EDL with ADB but maybe you dont need it, if you are booting into custom-recovery but
thats a maybe.
What you need: Driver, Device in Recovery-mode (cyangenmod ..maybe TWRP/stock works too), ADB, Sugar (and an Backup of Sugar-Firmware-Files if you got), INTERNET
(U can find driver/adb/sugar here: https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560)
Tutorial:
0. Load the Files from xda (driver/adb/sugar_QCT).
1. Read at top "Recovery" because your Device need to be in Custom-Recovery (maybe TRWP/Stock works too)
2. Start ADB and type "adb reboot edl" (without quotes) and hit enter
2.1. Copy your backup of Sugar-Firmware-Files to /Sugar/bin (Like: /Sugar/bin/VF1400-2AVDDE1/1BEJFDJ1)
2.2 If you dont got a backup, go to Step 3.
3. Start Sugar, choose VF1400 from top left (list)
4. Hit "UPGRADE".
4.1 If your loadingbar (at bottom) issnt jumping to 40%~ (after 1-3min), then Sugar doesnt found your Backup. Rename (from backup) 1BEJFDJ1-Dir to "Available Version" (but without "v" at the start)
You find the newest Version-Name in the Table of Sugar after Sugar loaded the FOTA-Infos from the internet. If you want to load the newest Firmware, jump to step 5.
4.2 If you dont got an backup, jump to step 5.
4.3 Repeat step 1 to 4 if the Backup wassnt found. (Sugar deletes the Backup in /bin/ after you close it,
thats why u need to repeat and while the phone goes into bootloop again, so you need to wait till the phone is empty again (battery), then start all over)
5. Wait till Sugar is finished (in the bottom and a popup window will appear in the end)
6. The device will restart, load up (so 5-10min) and you got the setup screen.
7. Finished!
Maybe you need much time because of the bootloop after existing Sugar or because draining the battery but its working great and after Sugar
says "writing data", u can relief. Hope it helps someone. If you need further help, just contact me (and best in german) if you doesnt understand
my bad english
Thanks to you Droidriven for trying to help me!
Best regards.
Neeschar said:
Thanks for your answer,
i didnt understand all of your text, so i needed google for it.
I revived my Device and for the share, i want to do a tutorial.
Some Infos:
EDL: You can enter EDL with ADB. Just download the minimal setup of ADB with Fastboot.
Check with the command "adb devices" if your device can be found. To enter EDL, just type
"adb reboot edl" into terminal and hit enter. You need USB Debugging on under Development-Options
under android to boot into EDL. If you got no android (system) on your device, just go into recovery
and then boot into EDL with ADB (USB Debugging is not important then, bc sugar can flash it so or so).
Recovery: Your device need to be completely off (black screen). If you got bootloop (powered by android),
let the battery go off (empty battery). After the battery is empty, plug it into usb adapter for loading and
wait so 30min (you can check the state of battery if you press short on power button). Press Power-Button
and Volume-Down-Button at the same time and hold it till the recovery appears! Connect the usb cable
now to the pc.
If you got no system on your device, the tutorial is right for you. If you got an system, you need USB-Debugging
on for booting into EDL with ADB but maybe you dont need it, if you are booting into custom-recovery but
thats a maybe.
What you need: Driver, Device in Recovery-mode (cyangenmod ..maybe TWRP/stock works too), ADB, Sugar (and an Backup of Sugar-Firmware-Files if you got), INTERNET
(U can find driver/adb/sugar here: https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560)
Tutorial:
0. Load the Files from xda (driver/adb/sugar_QCT).
1. Read at top "Recovery" because your Device need to be in Custom-Recovery (maybe TRWP/Stock works too)
2. Start ADB and type "adb reboot edl" (without quotes) and hit enter
2.1. Copy your backup of Sugar-Firmware-Files to /Sugar/bin (Like: /Sugar/bin/VF1400-2AVDDE1/1BEJFDJ1)
2.2 If you dont got a backup, go to Step 3.
3. Start Sugar, choose VF1400 from top left (list)
4. Hit "UPGRADE".
4.1 If your loadingbar (at bottom) issnt jumping to 40%~ (after 1-3min), then Sugar doesnt found your Backup. Rename (from backup) 1BEJFDJ1-Dir to "Available Version" (but without "v" at the start)
You find the newest Version-Name in the Table of Sugar after Sugar loaded the FOTA-Infos from the internet. If you want to load the newest Firmware, jump to step 5.
4.2 If you dont got an backup, jump to step 5.
4.3 Repeat step 1 to 4 if the Backup wassnt found. (Sugar deletes the Backup in /bin/ after you close it,
thats why u need to repeat and while the phone goes into bootloop again, so you need to wait till the phone is empty again (battery), then start all over)
5. Wait till Sugar is finished (in the bottom and a popup window will appear in the end)
6. The device will restart, load up (so 5-10min) and you got the setup screen.
7. Finished!
Maybe you need much time because of the bootloop after existing Sugar or because draining the battery but its working great and after Sugar
says "writing data", u can relief. Hope it helps someone. If you need further help, just contact me (and best in german) if you doesnt understand
my bad english
Thanks to you Droidriven for trying to help me!
Best regards.
Click to expand...
Click to collapse
Good to go, glad you got it fixed.
Try starting a new thread to write a guide for doing what you did. That way it will show up for others when they search.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Neeschar said:
Thanks for your answer,
i didnt understand all of your text, so i needed google for it.
I revived my Device and for the share, i want to do a tutorial.
Some Infos:
EDL: You can enter EDL with ADB. Just download the minimal setup of ADB with Fastboot.
Check with the command "adb devices" if your device can be found. To enter EDL, just type
"adb reboot edl" into terminal and hit enter. You need USB Debugging on under Development-Options
under android to boot into EDL. If you got no android (system) on your device, just go into recovery
and then boot into EDL with ADB (USB Debugging is not important then, bc sugar can flash it so or so).
Recovery: Your device need to be completely off (black screen). If you got bootloop (powered by android),
let the battery go off (empty battery). After the battery is empty, plug it into usb adapter for loading and
wait so 30min (you can check the state of battery if you press short on power button). Press Power-Button
and Volume-Down-Button at the same time and hold it till the recovery appears! Connect the usb cable
now to the pc.
If you got no system on your device, the tutorial is right for you. If you got an system, you need USB-Debugging
on for booting into EDL with ADB but maybe you dont need it, if you are booting into custom-recovery but
thats a maybe.
What you need: Driver, Device in Recovery-mode (cyangenmod ..maybe TWRP/stock works too), ADB, Sugar (and an Backup of Sugar-Firmware-Files if you got), INTERNET
(U can find driver/adb/sugar here: https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560)
Tutorial:
0. Load the Files from xda (driver/adb/sugar_QCT).
1. Read at top "Recovery" because your Device need to be in Custom-Recovery (maybe TRWP/Stock works too)
2. Start ADB and type "adb reboot edl" (without quotes) and hit enter
2.1. Copy your backup of Sugar-Firmware-Files to /Sugar/bin (Like: /Sugar/bin/VF1400-2AVDDE1/1BEJFDJ1)
2.2 If you dont got a backup, go to Step 3.
3. Start Sugar, choose VF1400 from top left (list)
4. Hit "UPGRADE".
4.1 If your loadingbar (at bottom) issnt jumping to 40%~ (after 1-3min), then Sugar doesnt found your Backup. Rename (from backup) 1BEJFDJ1-Dir to "Available Version" (but without "v" at the start)
You find the newest Version-Name in the Table of Sugar after Sugar loaded the FOTA-Infos from the internet. If you want to load the newest Firmware, jump to step 5.
4.2 If you dont got an backup, jump to step 5.
4.3 Repeat step 1 to 4 if the Backup wassnt found. (Sugar deletes the Backup in /bin/ after you close it,
thats why u need to repeat and while the phone goes into bootloop again, so you need to wait till the phone is empty again (battery), then start all over)
5. Wait till Sugar is finished (in the bottom and a popup window will appear in the end)
6. The device will restart, load up (so 5-10min) and you got the setup screen.
7. Finished!
Maybe you need much time because of the bootloop after existing Sugar or because draining the battery but its working great and after Sugar
says "writing data", u can relief. Hope it helps someone. If you need further help, just contact me (and best in german) if you doesnt understand
my bad english
Thanks to you Droidriven for trying to help me!
Best regards.
Click to expand...
Click to collapse
not work on stock recovery