{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Code:
[SIZE="3"] * Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.[/SIZE]
Working :
Everything
Procedure :
First Unlock Bootloader
Switch off Device
Copy twrp_yunique.img to ADB Folder in Laptop or PC
Hold Volume Up + Power
Select Reboot to Bootloader
Hold Left Shift + Right Click in ADB Folder
Select Start Command Window Here
Type Command in ADB Shell { fastboot flash recovery twrp_yunique.img }
Then Type Command in ADB Shell { fastboot reboot ]
Phone will restart.
Now Switch Off Device Hold Volume up + power to Boot TWRP
Enjoy !! And press Thanks please.
I hope you all Understand Development is not a easy work, So please press the Thanks Button as much as you can to Encourage Me
Download :
ADB Drivers : LINK
Adb Tools for YU Yunique : LINK
TWRP For YU Yunique : LINK
Stock Recovery in case if you want Revert : LINK
Root Method :
If you Want Root Access then Copy SuperSU.zip to Internal SD Card and Flash wih TWRP : LINK
If you use my work in part of your ROM I have no problem but Give Proper Credits
Reserved 1
Reserved 2
Just got my phone yesterday. Will first check and test hardware and decide if something is amiss so that I can return it.
Then I will try your work. I am so relieved to have a custom recovery and root is available for this handset.
Till now been using only and only HTC since ten years....
This is a kind of 'backup' piece.
Looking forward to a custom ROM ...because though there is no junk OEM installs ...there is only around 4 GB internal memory available.
Thanks Anurag.
Semi-CM ROM on the Way
kalya said:
Just got my phone yesterday. Will first check and test hardware and decide if something is amiss so that I can return it.
Then I will try your work. I am so relieved to have a custom recovery and root is available for this handset.
Till now been using only and only HTC since ten years....
This is a kind of 'backup' piece.
Looking forward to a custom ROM ...because though there is no junk OEM installs ...there is only around 4 GB internal memory available.
Thanks Anurag.
Click to expand...
Click to collapse
Wait for Few Hours Semi-CM ROM will be up any moment for YU Yunique
Checks Screenshots for Now and Keep Patience !! & Press the Thanks Button
TWRP not working even after flashing thrice.
arunmcops said:
TWRP not working even after flashing thrice.
Click to expand...
Click to collapse
Try fastboot boot twrp_yunique.img
and in fastboot mode check fastboot devices
anuragdc said:
Try fastboot boot twrp_yunique.img
and in fastboot mode check fastboot devices
Click to expand...
Click to collapse
it gets booted in twrp but after i restart my device and again go back to recovery stock recovery comes up.
vinaysalunke said:
it gets booted in twrp but after i restart my device and again go back to recovery stock recovery comes up.
Click to expand...
Click to collapse
Download the image file of recovery and try flashing with rashr or flasher tool. It will get installed.
Hit thanks button if helped.:fingers-crossed::good:
---------- Post added at 11:40 PM ---------- Previous post was at 11:37 PM ----------
anuragdc said:
Wait for Few Hours Semi-CM ROM will be up any moment for YU Yunique
Checks Screenshots for Now and Keep Patience !! & Press the Thanks Button
Click to expand...
Click to collapse
Anurag, it would be awesome if yunique gets full cm rom. Semi-cm rom is good but still lot of bugs like the stock rom. Hope you will be working for it and we get it soon.
I'm having a bit of an issue which i hope one of you can help.
I got the phone today, everything was working, so I decided to Unlock and install TWRP
everything went good
but when I pressed Volume Up + Volume Down + Power
The phone just stays on black screen
I get no ADB or FASTBOOT anymore
PC detects some "QHUSB_BULK" device
I can't turn it off, it won't respond to anything
did i just kill it by install TWRP ?
Sefy said:
I'm having a bit of an issue which i hope one of you can help.
I got the phone today, everything was working, so I decided to Unlock and install TWRP
everything went good
but when I pressed Volume Up + Volume Down + Power
The phone just stays on black screen
I get no ADB or FASTBOOT anymore
PC detects some "QHUSB_BULK" device
I can't turn it off, it won't respond to anything
did i just kill it by install TWRP ?
Click to expand...
Click to collapse
On the black screen you get fastboot mode. On pc, you need to install the drivers. Google qhusb_bulk drivers installation and follow the instructions. After installing the drivers, you will get fastboot and adb.
Installing custom recovery doesn't affect this.
Hit thanks button if i helped.
vikphogat said:
On the black screen you get fastboot mode. On pc, you need to install the drivers. Google qhusb_bulk drivers installation and follow the instructions. After installing the drivers, you will get fastboot and adb.
Installing custom recovery doesn't affect this.
Hit thanks button if i helped.
Click to expand...
Click to collapse
Even after installing the drivers, the phone wasn't accessible from ADB or Fastboot.
However, after pressing the Power Button for atleast 15 sec, the phone decided to turn on
So I was able to flash CWM and then TWRP and installed CM 12.1 :silly:
Sefy said:
Even after installing the drivers, the phone wasn't accessible from ADB or Fastboot.
However, after pressing the Power Button for atleast 15 sec, the phone decided to turn on
So I was able to flash CWM and then TWRP and installed CM 12.1 :silly:
Click to expand...
Click to collapse
You may not access adb after doing tha, but fastboot is available. You can connect to pc and install stock firmware by doing that.
Restart your phone into fastboot and check if the pc is showing you same "qhsbulk_usb" device. Also tell me the version of your pc windows.
vikphogat said:
You may not access adb after doing tha, but fastboot is available. You can connect to pc and install stock firmware by doing that.
Restart your phone into fastboot and check if the pc is showing you same "qhsbulk_usb" device. Also tell me the version of your pc windows.
Click to expand...
Click to collapse
As i've mentioned, the problem was resolved but keeping the Power Button pressed for 15 sec and the phone turned on again.
Sefy said:
As i've mentioned, the problem was resolved but keeping the Power Button pressed for 15 sec and the phone turned on again.
Click to expand...
Click to collapse
Can u please clearly tell me what your problem was?
I think you said fastboot and adb is not working.
Is it working now?
Need help to unbrick my yunique
Hi Anurag,
After successful flashing Jalebi CM12.1 recovery image, I am unable to browse through internal or external storage.
Can you please help me.
I need someone to test a MM AOSP ROM for me. I don't own the device. Email me or hangouts me at [email protected] Please, need to get feedback asap.
Someone please try this rom. Tell me if it works. If not, logcats are amazing. http://desolationrom.com/aosp_jalebi-ota-eng.root.zip
It's aosp marshmallow
Issue with the recovery
anuragdc said:
TWRP is an open source .....
....
TWRP For YU Yunique : LINK
Stock Recovery in case if you want Revert : LINK
Root Method :
If you Want Root Access then Copy SuperSU.zip to Internal SD Card and Flash wih TWRP : LINK[/SIZE]
If you use my work in part of your ROM I have no problem but Give Proper Credits
Click to expand...
Click to collapse
Hey dude,
Thanks for the recovery and fabulous work.. However I am having some trouble with it. Whenever I am trying to flash a CM Nightly, It keeps on failing Saying this package is for device Yunique and this device is YU4711!! Just dosen't allow me to flash. I have unchecked signature verification. I have attached the log with this post, would you be so kind as to please look into it and let me know?
Cheers!
EDIT:
You can take a look at this ongoing thread on CyanogenMod forum to get the full picture of the issue I am facing.
ashhem said:
Hey dude,
Thanks for the recovery and fabulous work.. However I am having some trouble with it. Whenever I am trying to flash a CM Nightly, It keeps on failing Saying this package is for device Yunique and this device is YU4711!! Just dosen't allow me to flash. I have unchecked signature verification. I have attached the log with this post, would you be so kind as to please look into it and let me know?
Cheers!
EDIT:
You can take a look at this ongoing thread on CyanogenMod forum to get the full picture of the issue I am facing.
Click to expand...
Click to collapse
thats because this recovery is NOT for your device! there are 2 things you must check:
CHECK THEM CAREFULLY OR YOU GET A HARDBRICK
1. are all partitions set correct in recovery? /system /data /cache and /boot ?
2. why you use this recovery and not your own? us there a recovery for your phone?
if you are 100% sure partitions are set correctly.... then do the following ON YOUR OWN RISK :
go to advanced-> terminal
there enter:
setprop ro.product.device YUNIQUE
setprop ro.build.product YUNIQUE
then try to flash the rom.... like i said above be 100% carefully because if partitions are seted wrong you may get a hardbrick!!!
btw (to the dev) the terminal gets flooded by a mtp error
Sent from my Xperia T using XDA Free mobile app
Related
Tried my best to search the forums for anyone else having this issue, couldn't find much.
My N7 isn't rooted at all. It worked fine until last night, the screen wouldn't turn on so I held the power button down to turn it off, booted it back up and it goes into a screen with a red triangle and says "No Command". It sits on this screen for a while and then reboots, and does the same over and over. I can get into fastboot (it also throws the "No Command" when trying to get into recovery), but I'm not sure what my options are. I'm hoping I don't have to resort to wiping the device, so any suggestions would be appreciated, thanks!
AW: [Q] Boots Into "No Command" Screen
When you boot in recovery and the red triangle appears, have you tried to press volume down and power again? It should boot in recovery
Sent from my SK17i running Android 4.1.2
Use fastboot to flash a custom recovery, and then do a nandroid backup. From there, you can mess around without fear of losing your data. Perhaps you will need to re-flash the boot or system image, but I can't imagine what could have happened to it in the first place.
AW: [Q] Boots Into "No Command" Screen
korockinout13 said:
Use fastboot to flash a custom recovery, and then do a nandroid backup. From there, you can mess around without fear of losing your data. Perhaps you will need to re-flash the boot or system image, but I can't imagine what could have happened to it in the first place.
Click to expand...
Click to collapse
He said he has no root and so I guess the bl is locked so he would loose his data while unlocking, right?
Sent from my SK17i running Android 4.1.2
I contacted support and they pretty much immediately started to process an RMA. She said someone had called in earlier today with the same problem and they couldn't figure anything out. I have a feeling they don't send new ones for these types of things, so I'm still going to try to fix mine. Thanks for the suggestions.
Here's a pic, I'm still confused on how little I've found about this "No Command" screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mihahn said:
When you boot in recovery and the red triangle appears, have you tried to press volume down and power again? It should boot in recovery
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
Woah, did you mean power and volume UP? Because that works... it brings up the recovery menu.....
Am I missing something? Is it normal to have to press power + volume up to see the recovery menu?
Okay, so I guess the real problem is that I'm stuck booting into recovery. Was there an OTA update?
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Leadsuit said:
Woah, did you mean power and volume UP? Because that works... it brings up the recovery menu.....
Click to expand...
Click to collapse
Just for future reference, when at the red triangle, you can get into recovery by holding vol up and power?
Sent from my SGH-I777 using xda premium
From efrants android 101 sticky:*I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:/system/etc/install-recovery.sh <== this is the script that installs the patch file/system/recovery-from-boot.p <== this is the patchYou have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my GT-I9300 using xda premium
---------- Post added at 06:17 AM ---------- Previous post was at 06:10 AM ----------
That is the cause of the No Comnand screen.
Sent from my GT-I9300 using xda premium
please explain the steps to fix the NO COMMAND on your tablet
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
please explain the steps to fix the NO COMMAND on your tablet?
tHanks
help please
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
hi Sir! I'm having the same problem, please help me. i dont know anything about adb drivers..
please tell me steps to use adb side load my android spice dream uno mi498
Leadsuit said:
I ended up fixing this. Once I realized what I was seeing was recovery mode, I tried clearing data + cache, but that didn't work. Still booted into recovery mode every time. I went through the mess of installing the right drivers (no idea if it's just me but I always have issues with my computer recognizing my devices), and I used the android SDK to unlock the bootloader and then flashed the factory image. Lost all my data but oh well, better than going through the RMA process.
Thanks again for the help. I seriously would have never realized that silly screen was recovery. Why can't it just show the menu by default...
edit: one other thing, the biggest hurdle I ran into was that I didn't have the drivers installed at all. but since I couldn't boot up I couldn't install the adb driver. I was able to install the fastboot one just fine, but the fastboot commands didn't work until I installed the adb driver. only way I was able to install the adb driver was to go into the 'sideload using adb' option in recovery, at that point windows prompted for the drivers. not sure if there's a manual way of installing the driver but yeah. hopefully that made some sense.
Click to expand...
Click to collapse
I have spice dream uno 498 6.0.1 my phone showing no command Pls tell me steps of using adb +command to give via pc
The best feature of Android - It's open. You can modify Android to have the best performance from your phone. My previous Atrix's hardware had some problem. So I didn't root my/unlock my Atrix. However, after seeing the upcoming CM10 for my set &; a battery friendly ROM yet 100% stable ROM, I finally decided to flash a custom ROM. What's great? I'm successful.
Yesterday, I was determined to unlock my bootloader & flash MROM on it. But I was afraid if I do anything wrong, my phone will not boot. I've not any other phone other than this & it's very precious to me. It's my beloved Atrix. I was unrooted, unlocked. Meant - I didn't do any modification at all. If you're on AT&T 4.5.141 (OTA Upgraded) then this tutorial is for you. (Bell/International users close your tab now!)
I'll not be responsible if you do any harm to your device
(You know the drill )
How to Unlock Motorola Atrix Bootloader (4.5.141) AT&T
I'm a noob. So I was searching for a perfect & easy tutorial. The automatic bootloader unlock seems really confusing to me. So I decided to do it manually. It's more easy &; clear than the automatic version.
I'll be writing this tutorial only for AT&T Atrix running 4.5.141 - Android 2.3.6 version. This tutorial will also work for AT&T 4.5.91 version.
But don't try this on AT&T 4.5.145/Bell/other international version. Once you flash CM7, don't flash Motorola's ROM with SBF. It'll brick the phone..
(Means your phone is dead!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We'll be flashing a custom ROM directly after unlocking the bootloader. So please download a custom rom &; it's Google Apps to your internal memory/SD Card. The main purpose of unlocking bootloader is to flash roms. So I don't care whether Motorola's buggy, laggy, sluggish, default blur ROM works or not.
Pre Requirements
We'll be needing a couple of tools.
We need the drivers for Atrix 4G. Download &; install it from here*(31.60 MB)
We'll need fastboot to unlock. Download fastboot from here (4.73 MB)
We'll need RSDLite. Download RSDLite 5.3.1 (4.33 MB)
Only for AT&T Atrix running 4.5.91/4.5.141 -*We'll need the 1.1 MB Unlocker Only SBF for AT&T Atrix. This tool will make ready your smartphone to unlock via fastboot command.
How to Unlock Bootloader Now?
If you've rooted already, take a backup of your apps with Titanium Backup. If not, then you're gonna loose all your apps.
Unlocking Atrix 4G Bootloader 4.5.141 Step-by-step
First of all, install RSDLite & extract the file*4547-fix-try2.sbf on your desktop.
Extract fastboot to C://fastboot.
Open RSDLite.
Power off your phone. Press power button+volume down together. You'll see a text "fastboot". Then start pressing the volume down again &; and again until you see "RSD". Once it comes, press volume up button. It'll say "Starting RSD Protocol"
You'll see that RSDLite has detected your phone in the menu. (SE Olympus or something like that)
Now Click the "..." button in RSDLite &; navigate the*4547-fix-try2.sbf file from your desktop.
Click Start.
Wait 5/6 minutes It'll restart your phone. You'll maybe see a boot error. (Just ignore it. Cause we're gonna flash a new ROM anyway).
After waiting some minutes, it'll say it's saying "starting fastboot protocol"
We're half done. We've extracted our fastboot files in C://fastboot
Open Command Prompt with Admin Privilege
Code:
Type "cd.."
Code:
Type "cd.."
Code:
Type "cd fastboot"
Type "
Code:
fastboot devices
".You'll see if your devices gets recognized or not.
Now type "
Code:
fastboot oem unlock
it'll give you a unique ID to unlock your phone.
Type "
Code:
fastboot oem unlock "XXXXXXXXXXXX (Unique ID)"
BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!
Flashing ClockWorkMod Recovery
(I've downloaded the latest recovery from romracer from here & placed it into the fastboot folder already)
Reboot your phone into fastboot mode again. (If power button doesn't do it, do a battery pull. To get into fastboot, Press power button+volume *down together until you see fastboot &; then press volume up)We're in the command prompt still.
So write*
fastboot erase recovery
Then write
fastboot flash recovery recovery.img
YAY!!! BOOM! We've flashed unlocked the bootloader & flashed recovery!
To flash a rom now, go to recovery mode (Press power button+volume *down together until you see*fastboot*&; then keep pressing volume down &; until you see "Android Recovery". Once you see it, press volume up.
The ROM flashing guide is easy. Choose install zip from SD card &; select your rom package &; it'll be installed. Reboot to enjoy your first custom ROM
Previously Published on my site http://saifhassan.info!
Emergency AT & T Atrix 4g (2.3.6) 4.5.145 Original 4547-fix-try2.sbf
Friends, let me urgent need to file 4547-fix-try2.sbf. Phone "failed to boot one" has failure. then the first term is no longer soft.As I understand it from RSD lite rom (4547-fix-try2.sbf) need to install. I'm searching, but I could not find. Links are broken. URGENT PLEASE HELP
(I'm sorry for my english is bad.)
saiftheboss7 said:
...BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!...
Click to expand...
Click to collapse
Finally) I'm done! 10ks!
Help please
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks
ukmed said:
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks
Click to expand...
Click to collapse
try "fastboot devices" to make sure your device is connected and recognized.
lehjr said:
try "fastboot devices" to make sure your device is connected and recognized.
Click to expand...
Click to collapse
Tried that, nothing happens...
Help!?
ukmed said:
Tried that, nothing happens...
Help!?
Click to expand...
Click to collapse
Make sure you download the USB Driver for WIndows. I posted the link in the OP. Read it thoroughly.
i need help
all my volume buttons are not functioning, how can u help me unlock........
If you have root, you might be able to use adb and the internal reboot command to reboot into various modes (recovery, fastboot...).
Tonyanaky said:
all my volume buttons are not functioning, how can u help me unlock........
Click to expand...
Click to collapse
Just flash TWRP after download, rename it to recovery & replace with the one that comes with fastboot extracted folder.
help
my 4547-fix-try2.sbf failed to work......what do i do???
Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?
Xfire68 said:
Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?
Click to expand...
Click to collapse
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!
Xfire68 said:
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!
Click to expand...
Click to collapse
there is a set of drivers that are for win 7 64 bit that i found early this morning via the droid x forum. I'm not at home right now, but i will post the link here when i do get home. hopefully it helps with issues with this os setup
Edit
File uploaded. even thought it says droid, it should still work
Works for 4.5.141 ?
Hi! Does this method work for Atrix 4G AT&T 4.5.145 as well? I want to get bootloader unlocked of my phone and install any ROM which supports 2-way Call Recording. Kindly suggest a stable ROM also that supports call recording function.
I am bit confused as the thread title says for 4.5.141 only.
Thanks in advance!!! :good:
Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Enviado desde mi MB860 usando Tapatalk 2
andresrivas said:
Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Click to expand...
Click to collapse
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.
sony108 said:
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.
Click to expand...
Click to collapse
yes, its called read post #1 and delete the recovery.sh in your phone before flashing cwm
I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?
NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.
Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.
I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.
I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.
answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.
Hello guys,
Here a easy way to fix a bootloop on your rooted Zenfone 2, if you make the error of apply an OTA while being rooted for example.
The only inconvenient of this method is that you will lost your internal data (like SMS, apps, downloads... But not your photos if they were in your SD Card). Another thing, you must have enabled the USB debugging before.
PS : I’m French sorry if my English is not perfect
Step 1
In your Zenfone 2, verify that you can go in fastboot mode : power off your Zenfone. Then, press the Power-On button until the phones vibrates twice. Release it, then go press the Volume+ button until this screen appears :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If that works, connect your Zenfone to your PC.
Step 2
Now go in Asus Website for download the most recent stock ROM of your Zenfone 2 (size : around 1.1 Go) :
ZE551ML : https://www.asus.com/fr/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
ZE550ML : https://www.asus.com/fr/Phones/ZenFone_2_ZE550ML/HelpDesk_Download/
ZE550CL : http://www.asus.com/fr/Phones/ZenFone_2_ZE500CL/HelpDesk_Download/
Remove the SD Card of your phone and copy it the zip, you can do it after if your connection is slow.
Step 2.5
I’m not sure if this is mandatory but do it by prevention : install “15 Seconds ADB Installer” : here a guide for intall it :
http://forum.xda-developers.com/showthread.php?t=2588979
Step 3
When this is done, download the folder named : “CWM_Zenfone_2_Intel.zip” :
https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2
Extract the files, then open the folder :
Step 4
Run “cai_dat_CWM.bat”
Type “ACCEPT” in the command window, in capitals, then press Enter.
Then, if your Zenfone 2 is connect to your PC in fastboot mode and if the script is blue, that’s perfect !
Type “T4”, press Enter, and normally something like this will happen in your Zenfone 2 :
Step 5
Shortly after, your Zenfone will reboot in CWM Recovery Mode
With the buttons, go in :
Install zip > choose zip from external sd card > *name of the stock ROM* > Yes, install
When the installation is done, reboot your device, and normally the bootloop will be fixed ! CONGRATULATIONS :good: :victory:
i tried to wiped cache in recovery mode but before it completes i restarted the phone
so now when i start my phone it just blinks error bot and even when i select recovery mode same thing happens
i also tried to solve it with ADB method but it do not detect my phone
PLZ HEPL ASAP!
Worked! Thanks!
Thank you so much! :good:
It worked for me. Although I had to clear cache and dalvik cache before installing the zip, otherwise my phone would reboot into fastboot when trying to flash the zip.
And best of all: I didn't loose any data!! Just had to root again using method 3 and install busybox.
I edited my build.prop because on the Amazon App Store there is an app (Navigon Europe) that can't be installed because Amazon says my device would be incompatible which it isn't because the Play Store says it's fine. Anyway, upon rebooting I was stuck at the splash screen. Luckily I was still able to get into fastboot...
Thanks again!
Still doesnt boot up
Hi! Thank you for your guide! I ran into a bit of a problem, maybe you will be able to help me out.
I by mistake did an OTA update while rooted, and my phone is now stuck on ASUS logo. I tried to flash different roms from external SD card, but even though they install correctly, phone still does not boot....
Fastboot gives me "permission" problem, ADB says device not found....
Any help would be greatly appreciated, because I am about to give up and go buy another phone.
Thanks a lot in advance
pozum said:
Hi! Thank you for your guide! I ran into a bit of a problem, maybe you will be able to help me out.
I by mistake did an OTA update while rooted, and my phone is now stuck on ASUS logo. I tried to flash different roms from external SD card, but even though they install correctly, phone still does not boot....
Fastboot gives me "permission" problem, ADB says device not found....
Any help would be greatly appreciated, because I am about to give up and go buy another phone.
Thanks a lot in advance
Click to expand...
Click to collapse
Tried other usb ports and cables? do you have all necessary drivers?
ElmirBuljubasic said:
Tried other usb ports and cables? do you have all necessary drivers?
Click to expand...
Click to collapse
yes and yes, different ports, different cables, 2 different computers - nothing... thanks
Same problem
I'm having the exact same issue as Pozum. ADB won't detect device. It won't boot. Is it completely bricked or can I do something?
try flashing full rom from SD card, rename it so that it can be recognized.
Sent from my ASUS_Z00AD using Tapatalk
luisoman2000 said:
try flashing full rom from SD card, rename it so that it can be recognized.
Click to expand...
Click to collapse
I have the stock android recovery utility. It doesn't give an option to flash/install anything. Or am I missing something?
Help
hello ...i recently rooted rooted my zenfone 2 and deleted the bloatware . I have and app call kingroot which i used to uninstall those apps ... this app also has a thing called Purify . i used it and it told me to restart and so i did . now the phone is stuck in bootloop . This is the 1st time I've restarted after rooting . Will your process work on mine ? Thanks in advance
I think yes, try it
Mael_RadecFR said:
Hello guys,
Here a easy way to fix a bootloop on your rooted Zenfone 2, if you make the error of apply an OTA while being rooted for example.
The only inconvenient of this method is that you will lost your internal data (like SMS, apps, downloads... But not your photos if they were in your SD Card). Another thing, you must have enabled the USB debugging before.
PS : I’m French sorry if my English is not perfect
Step 1
In your Zenfone 2, verify that you can go in fastboot mode : power off your Zenfone. Then, press the Power-On button until the phones vibrates twice. Release it, then go press the Volume+ button until this screen appears :
View attachment 3458839
If that works, connect your Zenfone to your PC.
Step 2
Now go in Asus Website for download the most recent stock ROM of your Zenfone 2 (size : around 1.1 Go) :
ZE551ML : https://www.asus.com/fr/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
ZE550ML : https://www.asus.com/fr/Phones/ZenFone_2_ZE550ML/HelpDesk_Download/
ZE550CL : http://www.asus.com/fr/Phones/ZenFone_2_ZE500CL/HelpDesk_Download/
Remove the SD Card of your phone and copy it the zip, you can do it after if your connection is slow.
Step 2.5
I’m not sure if this is mandatory but do it by prevention : install “15 Seconds ADB Installer” : here a guide for intall it :
http://forum.xda-developers.com/showthread.php?t=2588979
Step 3
When this is done, download the folder named : “CWM_Zenfone_2_Intel.zip” :
https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2
Extract the files, then open the folder :
View attachment 3458828
Step 4
Run “cai_dat_CWM.bat”
Type “ACCEPT” in the command window, in capitals, then press Enter.
View attachment 3458829
Then, if your Zenfone 2 is connect to your PC in fastboot mode and if the script is blue, that’s perfect !
View attachment 3458830
Type “T4”, press Enter, and normally something like this will happen in your Zenfone 2 :
View attachment 3458840
Step 5
Shortly after, your Zenfone will reboot in CWM Recovery Mode
View attachment 3458841
With the buttons, go in :
Install zip > choose zip from external sd card > *name of the stock ROM* > Yes, install
When the installation is done, reboot your device, and normally the bootloop will be fixed ! CONGRATULATIONS :good: :victory:
Click to expand...
Click to collapse
Why in the **** did you link the french site to this?
This does not work because when the phone is bricked the SD card is not mountable.
Thanks the solution is jst perfect BUT AFTER UPDATE TOUCH PANEL DONT WORK
QA88 said:
Hello buddy,
I really need your help. I rooted my Asus with your method. But at that time you had not post CWM Recovery. Unfortunately, my nephew play with my Asus then he touch update OTA. Finally My device being stuck on Asus logo, while it doesn't have CWM Recovery.
Could you please give guidance
Click to expand...
Click to collapse
I brought you here, check on first post, hope it help. Good luck
Hi there, hope there's a chance of a reply !
So I've got the blinking Android robot with red explanation mark! and I'd just like to know how long it takes for the phone to reload after installation?
Its stuck on the Asus boot up screen with the loading symbol under it !
I did the same thng.
chetank08 said:
i tried to wiped cache in recovery mode but before it completes i restarted the phone
so now when i start my phone it just blinks error bot and even when i select recovery mode same thing happens
i also tried to solve it with ADB method but it do not detect my phone
PLZ HEPL ASAP!
Click to expand...
Click to collapse
Hello. I believe I did the same exact thing . Did you by chance ever get back into Recover y mode or get the PC to recognize your phone. I'm a total novice with this, and very lost. Thank you.
Yesterday I did it too. Follow this guide http://valuestuffz.blogspot.com/201...uck-in-recovery-wipe-cache-partition.html?m=1
i was hope ... but
Hi! there.
i spend last to days literelly trying to fix my zf2 ZE551ml, it gets frozen when i wipe cache so i force power off... what a mistake.
i was trying to fix it, and i got it worst. i think i erase recovery menu, so i can't adb sideload, fastboot saids that can not load image system.img, asus flash tool said "flash image failure (failed with error #1), xFSTK works to bring fastboot menu, but since i don't have the file to put on OS dns space, it didn't work, but, after hours and hours, in my last try of a long nigth, i did this guide.
when i see a cwm icon, i can't believe it!! almost made my entire two days, but suddenly, it was all sad, when i tried to install from external sd card it says that there is an error. And the problem still there. here is an option to install zip by sideload, but in de pc said not device detectec.
i really don't know what to do, i'm really tired, and my options are getting over...
any ideas??
Thank you all!!
maciek90 said:
Yesterday I did it too. Follow this guide http://valuestuffz.blogspot.com/201...uck-in-recovery-wipe-cache-partition.html?m=1
Click to expand...
Click to collapse
Thank you for suggesting this guide! It did help me to get back into the recovery mode, however, after following the steps within the guide very diligently. I am still unable to get past the initial loading screen. . I received the permissions denied error just as the post suggested I would. I wiped the cache partition at the end of following the steps as suggested. Still. It will not load to the Welcome screen .
Hi Everyone
This is Guide how to repair your phone who was dead
My phone doesn't worked for 3 days so i get small trick and successfully repaired from dead
My phone was 5 times not worked like dead,Screen not Works ...only LED works,when i connect to pc usb device not recognized and nothing....
Explanation about my Problem:
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
So we are starting the GUIDE:
1.First you need the drivers so you can get from this https://drive.google.com/folderview?id=0B1T7tp6tJ_3kX3p6SUxWb2NfWTQ&usp=sharing
2.After you installed the Drivers go to. Download mode if not goes try this... Press Volume UP and Volume DOWN and connect to usb to your pc
3.Go to device Manager to view the Port ,so the port can be "Android HS-USB QDLoader 9008 (COM3)"
4.Download the Panasonic Firmware Eluga and Extract (don't worry this is the same like idol 3 only name changed)https://docs.google.com/uc?id=0B01OmzpKE6vAVDhaSFN2aVFzaVU
5. After Extract you wil find EB-90S55EWLv1009.exe so run as administrator wait to load data
6.select 6045 and in the list down you can find your phone
7.and press the button "download"
8.So process starting ..indetifying your device you will get informations about imei..rooted or no .....
9.so automatically started to flashing the firmware (my it's go to 45 % and then i get error)
10.Don't worry press the button Reboot Device
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
12.So device successfully repaired from dead
If you want to go to CM or Stock for Idol 3
-i will write guide to unlock bootloader and flash TWRP recovery
-You must have Minimal Adb and Fastboot
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing " .powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-You successfully unlocked the bootloader one step more to flash the recovery
-Download the TWRP RECOVERY FROM THIS LINK:
https://www.androidfilehost.com/?fid=24421527759881858
-Then copy from when you downlaod and paste the recovery in C:\Program Files\Minimal ADB and Fastboot
-Press Shift in the directory and click Right on mouse and open command promt here
-Type fastboot -i 0x1bbb flash recovery twrp-3.0.0-1.img or fastboot -i 0x1bbb boot twrp-3.0.0-1.img (if you want to test before installation)
-so successfully installed recovery and flash CM Or whatever you want
[/SIZE][/COLOR][/B]
Sorry for Grammatical Errors!
This guide will repair from dead....
in my case , buttons also doesn't work , how did you opened the back cover?
xZrender said:
in my case , buttons also doesn't work , how did you opened the back cover?
Click to expand...
Click to collapse
here's video how you can open
https://www.youtube.com/watch?v=FrFE8FdTXrY
Alek Dev said:
Hi Everyone
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
Click to expand...
Click to collapse
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
xZrender said:
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
Click to expand...
Click to collapse
Eject cable from motherboatd....insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
problem with idol 3 4.7 6039K
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
nipozzano said:
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
Click to expand...
Click to collapse
Hello
This Guide only works with Idol 3 5.5
but i will explain how to restore your device
Can you try with Mobile upgrade Q to restore,if doesn't work
Use this guide from wiemar ,it should help to you because it's for your model
http://forum.xda-developers.com/showpost.php?p=63709274&postcount=113
If you any questions ask me
Hi ! I follow the guide up to the section 9, unfortunately, in the Panasonic Firmware Eluga and Extract after pressing download it stops after 2% and I have got the error message "load nprg error error code 5002". Does someone know how to fix that ?
Thanks !
Error
I get: "Master Clear: FAIL Flash Status: [COM3->PC[3]] COM3->PC[3] failed to erase misc (Error code = 40016) " :crying:
Now I get the same error that matcail... did you solved it ???
Good tutorial but it does not help me. My phone keeps on rebooting.
Schumi_wk said:
Good tutorial but it does not help me. My phone keeps on rebooting.
Click to expand...
Click to collapse
Tell me info About your phone? Model,Country,ROM...../?
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Schumi_wk said:
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Click to expand...
Click to collapse
More Looks like Hardware Problem Try again with Mobile q if not works...Send to warranty repair.....
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
peito said:
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
Click to expand...
Click to collapse
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
eXoSaX said:
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
Click to expand...
Click to collapse
Alek Dev said:
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
Click to expand...
Click to collapse
That is exactly what I'm doing,entering in Download mode and then download in the Panasonic software,but nothing,the program cannot read my phone,I'm really tired of trying this,I will stuck in your Alek rom (btw,no matter how many times I flash your modem,I cannot get the lock screen ).Ty anyway Alek and keep it up!!!!
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
Click to expand...
Click to collapse
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
thorfr said:
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
Click to expand...
Click to collapse
Looks Like Problem With Motherboard and Battery ..you can try again with Panasonic Firmware Tool and if this not help Send it to Warranty Repair
ok i m gonna send it to warr:crying:antly
retry mobil q upgrage wo success bootloop again