Hi,
as the title says: I am running in circles when it comes to my ZU and me trying to get things done and to run...like Viper4Android.
But first things first:
I bought my ZU nearly one year ago, KitKat 4.4 was installed and I unlockes the bootloader via Sonys Webpage for that.
But soon after it got bricked, as it wouldn't charge anymore. So I sent it to Sony and when I got it back, Lollipop 5.0.1 was installed *hurray*
I don't know it they locked the bootloader again, but it say, I'm still allowed to unloak it.
So first question: is there a way to check, if the bootloader is locked or not?
"fastboot devices" doesn't give any errors, but it also give absolutly no message back. So I'm not sure if the phone is correctly recognized.
Coming to root:
For now, only KingRoot (yeah, I know...) can get me root access, at least without flashing. Flashing is a procedure I have always the highest respect of, because for me it seems quite risky to turn the phone into a brick.
But anyway. Now I got root, but Viper4Android needs also BusyBox, but installing that fails because of Sony RIC. So second questins: There is really no way of disabling RIC without flashing?
So I tryed installing a Recovery, this is called "ZU-lockeddualrecovery2.8.26-RELEASE.combined" and it seems to be the most recent one. But when trying to install that, it says it wont run on 5.1.1. Yeah, I upgraded some days ago, damn...
You see, one single thing (wanting Viper) produces such a tail of problems and I have now absolutly no idea where I should start to get any further.
Now I'm at a point where I think about really flashing a new completly new ROM, perhaps even Android M, but as seems one of the ones avaible yet supports ZU's hardware completly, right?
So what am I doing to do?
Sony Xperia Z Ultra
C6833
Android 5.1.1
Build 14.6.A.1.236
CosmicBlue2000 said:
Hi,
as the title says: I am running in circles when it comes to my ZU and me trying to get things done and to run...like Viper4Android.
But first things first:
I bought my ZU nearly one year ago, KitKat 4.4 was installed and I unlockes the bootloader via Sonys Webpage for that.
But soon after it got bricked, as it wouldn't charge anymore. So I sent it to Sony and when I got it back, Lollipop 5.0.1 was installed *hurray*
I don't know it they locked the bootloader again, but it say, I'm still allowed to unloak it.
So first question: is there a way to check, if the bootloader is locked or not?
"fastboot devices" doesn't give any errors, but it also give absolutly no message back. So I'm not sure if the phone is correctly recognized.
Coming to root:
For now, only KingRoot (yeah, I know...) can get me root access, at least without flashing. Flashing is a procedure I have always the highest respect of, because for me it seems quite risky to turn the phone into a brick.
But anyway. Now I got root, but Viper4Android needs also BusyBox, but installing that fails because of Sony RIC. So second questins: There is really no way of disabling RIC without flashing?
So I tryed installing a Recovery, this is called "ZU-lockeddualrecovery2.8.26-RELEASE.combined" and it seems to be the most recent one. But when trying to install that, it says it wont run on 5.1.1. Yeah, I upgraded some days ago, damn...
You see, one single thing (wanting Viper) produces such a tail of problems and I have now absolutly no idea where I should start to get any further.
Now I'm at a point where I think about really flashing a new completly new ROM, perhaps even Android M, but as seems one of the ones avaible yet supports ZU's hardware completly, right?
So what am I doing to do?
Click to expand...
Click to collapse
ric is probably needed to disable... yep
Flash the zip in recovery: disable_ric_file.zip
And then install the app: SELinuxModeChanger.v.3.2.b.42.crk.Dependencies.Removed.apk
Set the app to permissive.
And Viper4Android will work.
Can't guarantee it will work on locked bootloader.
SÜPERUSER said:
ric is probably needed to disable... yep
Flash the zip in recovery: disable_ric_file.zip
Click to expand...
Click to collapse
Okay, thanks so far, but how do I get into recovery?
You see, I have no recovery installed and when I tryed to install DualRecovery, it failed...
CosmicBlue2000 said:
Okay, thanks so far, but how do I get into recovery?
You see, I have no recovery installed and when I tryed to install DualRecovery, it failed...
Click to expand...
Click to collapse
flash twrp:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-recovery-2-8-7-0-2016-02-03-t3307043
MusterMaxMueller said:
flash twrp:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-recovery-2-8-7-0-2016-02-03-t3307043
Click to expand...
Click to collapse
Tried, Screen remain black if I try to boot in recovery.
p.s.:
TWRP Manager App give me an error "something went wrong". Great.
https://twrp.me/devices/sonyxperiazultra.html
Doesn't work either.
I'm frustrated. Trying for over one week now to get it running. Half of my vacation. I didn't thought, I would spent so much time with it. 3 to 4 hours a day.
I think it starts the with the fact, that I can't tell if bootloader is unlocked or not.
CosmicBlue2000 said:
Tried, Screen remain black if I try to boot in recovery.
p.s.:
TWRP Manager App give me an error "something went wrong". Great.
https://twrp.me/devices/sonyxperiazultra.html
Doesn't work either.
I'm frustrated. Trying for over one week now to get it running. Half of my vacation. I didn't thought, I would spent so much time with it. 3 to 4 hours a day.
I think it starts the with the fact, that I can't tell if bootloader is unlocked or not.
Click to expand...
Click to collapse
To check if you bootloader is locked or unlocked. Try this below:
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
Source: http://forum.xda-developers.com/showpost.php?p=22341848&postcount=4
SÜPERUSER said:
To check if you bootloader is locked or unlocked. Try this below:
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
Source: http://forum.xda-developers.com/showpost.php?p=22341848&postcount=4
Click to expand...
Click to collapse
Okay, last time I unlocked it (under Kitkat), it didn't change.
If that behaviour has changed, then it is still locked.
CosmicBlue2000 said:
Okay, last time I unlocked it (under Kitkat), it didn't change.
If that behaviour has changed, then it is still locked.
Click to expand...
Click to collapse
"last time I unlocked it"?... You lost me there.
Have you unlocked bootloader before? Can you remember if you once have written the command: fastboot oem unlock 0x ?
SÜPERUSER said:
"last time I unlocked it"?... You lost me there.
Have you unlocked bootloader before? Can you remember if you once have written the command: fastboot oem unlock 0x ?
Click to expand...
Click to collapse
Let me quote my first post:
I bought my ZU nearly one year ago, KitKat 4.4 was installed and I unlocked the bootloader via Sonys Webpage for that.
But soon after it got bricked, as it wouldn't charge anymore. So I sent it to Sony and when I got it back, Lollipop 5.0.1 was installed *hurray*
I don't know it they locked the bootloader again, but it says, I'm still allowed to unloak it.
Click to expand...
Click to collapse
And here is, what the Sony webapage told me. Last time and now again:
Install the Android SDK and the device drivers
1. Download and install the Android SDK.
2. If you’re running Windows, you also need to download and install an updated Fastboot driver. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony & Sony Ericsson devices. Replace the original android_winusb.inf-file with the downloaded file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. If you can’t find the usb_driver folder, make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. If not, install the Google USB Driver Packager using the Android SDK manager.
Note! If you’re running OSX or Linux, you are not required to install any additional drivers.
3. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging.
As of Android Jelly Bean 4.2 the Developer options are hidden by default. To enable them tap on Settings > About Phone > Build Version multiple times. Then you will be able to access the Settings > Developer options.
Connect to Fastboot
1. Turn off your Xperia™ Z Ultra.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z Ultra, press the Volume up button at the same time as you connect the other end of the USB-cable. For Windows users, when asked for a driver, point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command:
fastboot devices
6. Verify that you get an answer back without any errors.
Enter unlock key
WARNING! The command below contains your unlock key. If you perform this step, you will unlock the boot loader. This may void your warranty and/or any warranty from your operator.
1. If you still want to unlock the boot loader of your device, enter the following command:
fastboot -i 0x0fce oem unlock 0x6C88871CBAABD41D
2. Verify that you get an answer back without any errors.
Done!
You have now unlocked the boot loader of your device. Return to Developer World for the latest developer news from Sony.
Click to expand...
Click to collapse
So yes, I remeber using the fastboot command then and now.
I did exactly a told, but the problem is #5 when trying to connect with fastboot for the first time. I enter
fastboot devices
Click to expand...
Click to collapse
and no message appears, no error or anything else. I'm just back at the prompt, nearly immediatly.
Trying
fastboot -i 0x0fce oem unlock 0x6C88871CBAABD41D
Click to expand...
Click to collapse
then will lead to nothing too, no error. But this time I don't get back to prompt. I waited about 2 Hours yesterday befor I gave up with CRTL+C.
So there must be a problem. The problem.
CosmicBlue2000 said:
Tried, Screen remain black if I try to boot in recovery.
p.s.:
TWRP Manager App give me an error "something went wrong". Great.
https://twrp.me/devices/sonyxperiazultra.html
Doesn't work either.
I'm frustrated. Trying for over one week now to get it running. Half of my vacation. I didn't thought, I would spent so much time with it. 3 to 4 hours a day.
I think it starts the with the fact, that I can't tell if bootloader is unlocked or not.
Click to expand...
Click to collapse
follow thread instructions....
read op carefully.
then it will work
---------- Post added at 06:14 PM ---------- Previous post was at 06:12 PM ----------
CosmicBlue2000 said:
Let me quote my first post:
And here is, what the Sony webapage told me. Last time and now again:
So yes, I remeber using the fastboot command then and now.
I did exactly a told, but the problem is #5 when trying to connect with fastboot for the first time. I enter
and no message appears, no error or anything else. I'm just back at the prompt, nearly immediatly.
Trying
then will lead to nothing too, no error. But this time I don't get back to prompt. I waited about 2 Hours yesterday befor I gave up with CRTL+C.
So there must be a problem. The problem.
Click to expand...
Click to collapse
seems like fastboot drivers arent installed correctly ( see device manager in windows)
so you didnt flash twrp?
MusterMaxMueller said:
follow thread instructions....
read op carefully.
then it will work
I will. Again.
---------- Post added at 06:14 PM ---------- Previous post was at 06:12 PM ----------
seems like fastboot drivers arent installed correctly ( see device manager in windows)
so you didnt flash twrp?
Click to expand...
Click to collapse
Well, at least I tried to flash twrp.
The way it is descripted in the Thread above didn't work, because the download link is broken for me.
So I went to the Play Store and installed TWRP Manger App - at least I have root thanks to KingRoot. But that app gave me an error when trying to install twrp recovery.
So I went here https://twrp.me/devices/sonyxperiazultra.html
I put the .img on sdcard, connected the phone, gave in the commands and there was no error message. No success either, there was just something like "has written x block in y seconds" or something like that. So I just thought I'll give it a try, but as written, when trying to ent recovery on boot, the screen remained black.
/edit:
Speaking of drivers, I forgot.
You were right, the wrong one was used. I don't know why, because since last time I haven't deleted the drivers or anything. Windows should have used the correct one again, but it didn't.
Damn, I'm so stupid, thanks a lot
CosmicBlue2000 said:
Well, at least I tried to flash twrp.
The way it is descripted in the Thread above didn't work, because the download link is broken for me.
So I went to the Play Store and installed TWRP Manger App - at least I have root thanks to KingRoot. But that app gave me an error when trying to install twrp recovery.
So I went here https://twrp.me/devices/sonyxperiazultra.html
I put the .img on sdcard, connected the phone, gave in the commands and there was no error message. No success either, there was just something like "has written x block in y seconds" or something like that. So I just thought I'll give it a try, but as written, when trying to ent recovery on boot, the screen remained black.
Click to expand...
Click to collapse
My apology. I was on my phone in direct sunlight and did not read the whole post.
Yes if you have sent it to SONY and gotten it back. It is for sure a new motherboard with locked bootloader.
Even if they used JTAG to fix your motherboard. Unlikely that staff would spend time doing this. Either way the bootloader would be locked.
Your bootloader is locked. This is why flashing any .img will not work.
First thing. Unlock your bootloader.
The universal tool to flash files from phone without a computer is this app:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
The link for for TWRP 3.x is here: http://forum.xda-developers.com/devdb/project/dl/?id=18690
NOTICE: Since TWRP V3. The procedure to enter recovery has changed.
New instructions is to power off the phone, hold volume down and power button until phone vibrates.
Let go of the buttons when the SONY logo appears.
A few seconds later the TWRP logo will appear.
But as MusterMaxMueller mentioned. You don't have the correct driver installed if you see an empty line if you type fastboot devices in cmd.
Try follow the post I wrote yesterday to get fastboot working:
Source: http://forum.xda-developers.com/showpost.php?p=67897097&postcount=12
Type these commands in cmd. Run CMD as Administrator:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Then "Disable driver signature enforcement" on boot:
Press windows key + R
Type: shutdown -o -r -t 0
Press enter
You will now be here:
{
"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"
}
Select "Troubleshoot"
Select “Advanced options” and “Startup Settings”.
Click "Restart":
When computer reboots and you see this screen: Press F7
Install systemwide ADB
http://forum.xda-developers.com/showthread.php?p=48915118
Direct link: www14.zippyshare.com/d/ufYG71o0/4863743/adb-setup-1.4.3.exe
Download Flashtool driver pack:
http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS41LTIwMTQwMzE4
Run the file
Scroll down the list until you se Xperia Z ultra C68xx whatever your model is.
Install the drivers
Done
On your desktop: Hold "shift" and right click. Choose Open Command Window here
In the CMD type: Fastboot.
IF you see a list of text describing what fastboot is. You are fine.
Boot the phone to fastboot: Power off, Hold Volume up and plugin the usb cable and blue LED should be constant on.
SÜPERUSER said:
My apology.
Click to expand...
Click to collapse
Nevermind.
The universal tool to flash files from phone without a computer is this app:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
Didn't know that, thanks . As I don't like flashhing, I love apps
The link for for TWRP 3.x is here: http://forum.xda-developers.com/devdb/project/dl/?id=18690
Click to expand...
Click to collapse
And again, this link seems broken. Nothing to download there. Just an empty page.
NOTICE: Since TWRP V3. The procedure to enter recovery has changed.
New instructions is to power off the phone, hold volume down and power button until phone vibrates.
Let go of the buttons when the SONY logo appears.
Click to expand...
Click to collapse
I know that and have done that, but
A few seconds later the TWRP logo will appear.
Click to expand...
Click to collapse
didn't happen.
But as MusterMaxMueller mentioned. You don't have the correct driver installed if you see an empty line if you type fastboot devices in cmd.
Click to expand...
Click to collapse
Yeah, seems so.
Just tryed unlocking again, no I got a factory reset, so I'll tell if it's unlocked in some minutes.
Thanks!
CosmicBlue2000 said:
Nevermind.
The universal tool to flash files from phone without a computer is this app:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Didn't know that, thanks . As I don't like flashhing, I love apps
And again, this link seems broken. Nothing to download there. Just an empty page.
I know that and have done that, but didn't happen.
Yeah, seems so.
Just tryed unlocking again, no I got a factory reset, so I'll tell if it's unlocked in some minutes.
Thanks!
Click to expand...
Click to collapse
The link is fine. But here is a mirror:
http://www103.zippyshare.com/v/KjOWHpFf/file.html
If your device starting a factory reset when you trying to unlock bootloader. This is the correct reaction.
All android devices do this when receiving bootloader unlock command to prevent system errors. Hopefully it goes well for you
Click to expand...
Click to collapse
Click to expand...
Click to collapse
"Bootloader unlocked: yes"
Thank you so much
Related
WARNING
USE INFORMATION AT YOU OWN RISK
There is no known perfect method to RELOCK the bootloader. So beware you will loose warranty of device. This warning is also shown while unlocking by LG.
This guide may have errors and may not work for some in various scenario. If you report them, I may try to correct them.
Read properly and DON'T SEND PM, I will simply ignore PM and laugh on you.
Just sharing information. See now how easy it is to flash+CWM+Root V20* on Unlocked Bootloader (UL BL)***
Thanks and Huge rounds of applause for Aremcee (aka RC or Ricardo Cerqueira).
This is completely based on Aremcee's Unlock and CWMRoot method as explained here. Please read is carefully before starting.
=============================================
Things to remember while proceeding.
Not for Newbies. (need some experience in flashing and installing fastboot drivers)
.
IMPORTANT: You must have P760/P765 with P760 V20B EUROPE OPEN rom flashed on it....or OTHER UNLOCKABLE ROMS. @Gh0sT.RPG tried unlocking on P765 V20B, V20C & V20D all unsuccessful. But He unlocked on P65 V20A Indian in just 20min.
.
You must have P768 with P768 JB (e.g.Mexico) Not tested but should work as per JB feature added in other variants. If this method does not work for P768 then try this method.
Phone might be already Bootloader Unlocked or you may Unlock it while in following process.
P769x owners please visit this thread for unlocking bootloader.
Unlock Bootloader and Easy Rooting of L9 P760/765/P768
0) Preparations:-
Install latest LG Driver.
Download fastbootdrivers.zip (old) OR New Fastbood Drivers and find installation instructions in this thread OR this new thread (Tip for Win98)
Download Android.zip and extracted anywhere on computer, preferably C drive. The folder "C:\Android" will be created with all necessary files.
Download recovery-clockwork-touch-6.0.3.1-p760.img and save in "C:\Android" folder
Download UPDATE-SuperSU-v1.25.zip and save on external sdcard.
See post number 10 below for some information on fastboot drivers.
1) Connect phone to pc and change USB Mode to "LG Software Mode". Now wait for 30 minutes if you want to unlock bootloader (IMPORTANT Read post) and then open command prompt and give following commands in "lower case" because adb command is case sensitive.
C:\>cd \android
C:\Android>adb devices
Click to expand...
Click to collapse
This should show the list of attached devices in ADB mode like shown below
{
"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"
}
Now pass this command and phone will restart in fastboot mode like this... in "lower case" because fastboot command is case sensitive.
C:Android\>adb reboot oem-unlock
Click to expand...
Click to collapse
Phone will start in fastboot mode. You may be asked to install fastboot drivers at this point. See driver download from this this NEW download thread and install with instructions from this OLD install method or this New install Method.
2 A) AT THIS POINT, YOU CAN UNLOCK BOOTLOADER IF STILL LOCKED: You get option to press VOLUME UP key to unlock the bootloader permanently. If already unlocked, skip to next step.
2 B) When your phone comes in fastboot mode, then PC will install fastboot drivers, if not installed before. If automatic installation fails, you can manually install fastboot drivers as instructed in this post or this post. Strangely my device manager shows only one entry like this screenshot. (click for screenshot). If fastboot drivers are not installed this rooting will not work.
3) Now staying in Fastboot mode, install Recovery Software (CWM Touch) like shown below. All in "lower case", because fastboot command is case sensitive and will fail if you type carelessly.
C:\Android>fastboot devices
Click to expand...
Click to collapse
This will show if phone is connected to your pc in fastboot mode or not by showing device entry result like "1234567 fastboot". Then give next command.
C:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.3.1-p760.img
Click to expand...
Click to collapse
This will install Recovery Software (CWM) in your phone. When finished you can disconnect phone from pc (remove usb cable).
To switch off phone, PRESS POWER FOR 15 SECONDS or REMOVE BATTERY and INSERT AGAIN.
4) Reboot phone in Recovery (CWM) Mode (with Vol+ and Home and Power button, all together for 5 secs) and flash UPDATE-SuperSU-v1.25.zip which was already copied before on sdcard. Reboot normally and enjoy.
Your are done.
For me everything went smooth in single attempt like a charm.
PS: The Rom I flashed before did perfectly worked well with all features and options Super Smooth as usual.
==============================================
EDIT: JUST FLASHED P765 V20D HongKong ON P765 INDIA WITH NO ISSUE. (14-Apr-13) See this related thread for more information
==============================================
What different between v20b and v20c?
help
i have unlocked boot loader and when i try to flash kdz it shows no device foun ...i have installed the drives correctly..or can you give me the cwm backup?
hkfree said:
What different between v20b and v20c?
Click to expand...
Click to collapse
Not much. Everything seem same as V20B. Could be some minor unknown changes/bugfixes in the deep inside rom, which we may not want to know. But ROM is solid good and function well.
Actually at the moment, there is no solid reason with me for, why one should update to V20C? I am still exploring and trying to know whats difference lol
karthickkatta said:
i have unlocked boot loader and when i try to flash kdz it shows no device foun ...i have installed the drives correctly..or can you give me the cwm backup?
Click to expand...
Click to collapse
I wanted to but I have pathetic upload speed right now and it will take around 8/9 hours to upload 550+ mb CWM Backup. Practical not possible for me
Please wait for someone with FASTER upload speed.
cmahendra said:
Not much. Everything seem same as V20B. Could be some minor unknown changes/bugfixes in the deep inside rom, which we may not want to know. But ROM is solid good and function well.
Actually at the moment, there is no solid reason with me for, why one should update to V20C? I am still exploring and trying to know whats difference lol
I wanted to but I have pathetic upload speed right now and it will take around 8/9 hours to upload 550+ mb CWM Backup. Practical not possible for me
Please wait for someone with FASTER upload speed.
Click to expand...
Click to collapse
thanks ..but i flashed it succesfully ..another thing i cant see my pics or videos in the player ..what happened and i even did a factory reset ..
Couldn`t it improve battery life? For me on stock v20b with root is impossible stand more than 17 hours. Another thing whats bother me is wake up time from sleeping. When i press home or wake up button, it takes about 2 or 3 seconds to switch on display!!! And i didn´t change any frequencies or governor. I didn´t notice that problem on v10h ICS...
Manek66 said:
Couldn`t it improve battery life? For me on stock v20b with root is impossible stand more than 17 hours. Another thing whats bother me is wake up time from sleeping. When i press home or wake up button, it takes about 2 or 3 seconds to switch on display!!! And i didn´t change any frequencies or governor. I didn´t notice that problem on v10h ICS...
Click to expand...
Click to collapse
Now its almost two days and approximately I got 1 and half day in single charge with moderate use. For me V20C is really better than V20B. Of course i use music and video very very less and mostly its for call and emails on 3G data.
Camera clarity is same (poor) as V20B but flash brightness is better than it.
So far, I have found out, that there is different layout when you are answering call and maybe background in SMS app... In question of battery life, its too early to say.
command write failed unknown error
cmahendra said:
1) As usually I do, P760V20C Europe Open was out so flashed it on P765 India. :good:
Then started phone in fastboot mode with following...
In fastboot mode my device manager show only one entry like this screenshot. (click for screenshot).
Click to expand...
Click to collapse
in this step yu have mentioned, can yu tell me the driver installed for the usb device connected in the screenshot - for me in the device manager it shows as some asus driver installed ... i guess maybe this is the reason for that command write failed error :crying:
rkn989 said:
in this step yu have mentioned, can yu tell me the driver installed for the usb device connected in the screenshot - for me in the device manager it shows as some asus driver installed ... i guess maybe this is the reason for that command write failed error :crying:
Click to expand...
Click to collapse
Asus? From where did you get that? Strange.
I am not sure right now, but these drivers problems are not occurring to me after I have installed Android SDK Tools (long time back) and installed original Google USB driver from Google Android Developers. See what items are installed in following image. And I think the platform tools and Google USB Drivers include FASTBOOT drivers too. Worked always for me.
cmahendra said:
Asus? From where did you get that? Strange.
I am not sure right now, but these drivers problems are not occurring to me after I have installed Android SDK Tools (long time back) and installed original Google USB driver from Google Android Developers. See what items are installed in following image. And I think the platform tools include perfect FASTBOOT drivers too. Worked always for me.
Click to expand...
Click to collapse
i din install them ... it was automatically installed .. im using win8 pro 32 bit .... and my phone is rooted by lelus method which yu posted ... and now its running p760 v20b ROM ....
Is hindi present in European firmware? ??
Sent from my LG-P765 using xda app-developers app
Techgod said:
Is hindi present in European firmware? ??
Sent from my LG-P765 using xda app-developers app
Click to expand...
Click to collapse
There is no hindi OS support even in Indian version of ROMs. You cannot select interface language in hindi.
But you can read hindi/gujrathi/etc in apps like facebook in European roms too. All fonts are built in roms folder.
cmahendra said:
There is no hindi OS support even in Indian version of ROMs. You cannot select interface language in hindi.
But you can read hindi/gujrathi/etc in apps like facebook in European roms too. All fonts are built in roms folder.
Click to expand...
Click to collapse
I meant hindi font rendering in messages and other apps....like reading ओप्टीमस in European firmware..
thnx a lot....i dont want the os in hindi.
Sent from my LG-P765 using xda app-developers app
Techgod said:
I meant hindi font rendering in messages and other apps....like reading ओप्टीमस in European firmware..
thnx a lot....i dont want the os in hindi.
Sent from my LG-P765 using xda app-developers app
Click to expand...
Click to collapse
Then yes, have read hindi in european roms also. I only have seen hindi text in SMS several times but the text appears bit erroneous. But in Facebook the text appears perfect like we see in pc. I dont know may be Facebook installs its own Hindi TTF font.
FLASHED P765 V20D HongKong ON P765 INDIA WITH NO ISSUE. (14-Apr-13) See this related thread for more information
Can you root the rom?
And any changes can find?
Sent from my LG-P765 using xda app-developers app
cmahendra said:
==============================================
EDIT: FLASHED P765 V20D HongKong ON P765 INDIA WITH NO ISSUE. (14-Apr-13) See this related thread for more information
==============================================
*** THIS IS NOT GUIDE, Just sharing. Just telling all noob-pals, that how easy it is to flash+CWM+Root V20D on Unlocked Bootloader (UL BL)***
I have P765 with UL BL and was on P760 V20D Europe.
1) As usually I do, P765V20D HongKong was out so flashed it on P765 India. :good:
Then started phone in fastboot mode with following...
In fastboot mode my device manager show only one entry like this screenshot. (click for screenshot).
2) In Fastboot mode, pushed CWM Touch like following.:good:
C:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.2.9-p760.img
3) Rebooted in CWM Mode and flashed UPDATE-SuperSU-v1.25.zip:good:
Everything went smooth in single attempt like a charm
Rom is Perfectly fine with all features and options Super Smooth as usual.
Click to expand...
Click to collapse
i have read your thread about lelus method of rooting L9。now i want to flash V20D version of Hongkong on my p765. but the recovery is needed in your thread,but i cant find it in another thread. so i just wonder whether your Attached File of “recovery-clockwork-touch-6.0.2.9-p760.img” can be used on mine.
mylk said:
i have read your thread about lelus method of rooting L9。now i want to flash V20D version of Hongkong on my p765. but the recovery is needed in your thread,but i cant find it in another thread. so i just wonder whether your Attached File of “recovery-clockwork-touch-6.0.2.9-p760.img” can be used on mine.
Click to expand...
Click to collapse
Yes, only two files attached here are enough. Remember this procedure is only for unlocked bootloader, which does not need lelus method to be performed.
PS: You will need flashing tool for flashing rom and fastboot files, available in other threads. You can get fastboot files in Android SDK Tool package.
Hi there, im having trouble getting into fastboot mode on my phone? I have already unlocked my bootloader, I have a P768 on ICS V10E and I unlocked the bootloader using P760 V20C. How do I switch to fastboot?
I tried to flash latest rom from Asus website to my new Zenfone C because it had a weird issue, it came the user interface in taiwanesse, but when trying to change to english, it stayed in taiwanesse, so I wasnt able to setup it in first place.
Then, it came to my mind to flash the latest rom, and I used this guide in absence of a Zenfone C guide for flashing:
http://en.zenfoneasus.com/zenfone-recovering-returning-stock-rom-downgrade-clean-update-guide/
I did all the steps listed there first, and then tried the steps but with the red marked steps, flashing the dnx and ifwi also, no result.
The problem is that now im stuck in a bootloop, and cant advance from there, the Asus logo stays there forever.
What happened during flashing is this:
When I sideloaded the update.zip containing latest rom from Asus website, it said:
-Installing update
-Device image SKU: ww
OTA image SKU: WW
and suddenly after that it restarted, showed a huge Intel Inside logo that I never saw and then went to the dead android image. After waiting a while, the phone restarts, this time only showing the Asus logo with the Intel Inside logo beneath it (not the Intel Inside logo only that I mentioned earlier), and stays there forever.
I dont know what else to do, I dont know if Im doing something wrong.
Were you ever able to fix the problem?
No, until now, no
Sent from my Nexus 5 using Tapatalk
Solved!!!
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
kkdevta said:
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
Click to expand...
Click to collapse
I still need the fix man, I will really appreciate the posting of the solution! thanks in advance!
Sent from my Nexus 5 using Tapatalk
The Fix!
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
{
"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"
}
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Spartan Legionnaire said:
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Click to expand...
Click to collapse
Hopefully it should, I did it on a Windows 7 Professional 64 bit machine.
The USB drivers you download has Windows 8 drivers in it. I think that's all that is needed.
Yeah, I will try it then, and report back, thanks again.
Sent from my Nexus 5 using Tapatalk
kkdevta said:
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Click to expand...
Click to collapse
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Tjecing said:
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Click to expand...
Click to collapse
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
kkdevta said:
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
Click to expand...
Click to collapse
I don't know how to thank You.. But thanks a lot you safe my days..
Can any one plz give me the link of any custom recovery for asus zenfone c.....i badly need it plz help me...thnks in advance.....plz give me..and tell me how to flash it.....
do you know where i can find the correct .raw file for asus zenfone 5 A501CG ? i use lollipop, i dont know if that's matter =s
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Sent from my Mi 4i using XDA Free mobile app
hello brother...can you help me...
my zenfone 5 a500cg has been softrick and bootloop to...
if i'm turn on my phone
logo asus and then usb logo and then dead again...
i can't log into fastboot(power on+vol up)..
but i can log into cwm philz...
i try flash via adb sideload but always error bla bla bla tmp/updated.zip
if i try other ROM always like this ( please upgrade to image 4.3 first)
i try xftsk but always windriver error( i am use notebook win7)
i try asus flashtool with .raw zip rom but my serial number error just 12345678abcdef...
if i click start always device not detect...
help me bro
disappear3896 said:
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Click to expand...
Click to collapse
power and volume up (+)
Spartan Legionnaire said:
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
Click to expand...
Click to collapse
First and foremost, follow Spartan about how to deal with the driver install error. Read above. Second, those are the links for the raw images:
ww_A500CG_3.23.40.60_20150630.raw and many other phones. It was posted by thanhthuy. 500CG Lollipop: https://mega.nz/#!jwBDUKzJ!x3VD9VJrMe0CBs353DVnXlHr2dHQXepjcqtrR0gQDdU
500CG kitkat:
https://mega.co.nz/#!H8YkyLba!4Ye52JKAjzogGRVvCx2r9XoJIhou_uY3z6YH1xBges8
400CG 6.6.3 - https://mega.co.nz/#!HoRRnLCL!CV-iCMEUgRd_LwDc4QgNkevxKIGOKtFGDYrytt59EVE
400CG 7.3.3 - https://mega.co.nz/#!G8hRwYqR!Eu_l6r_6QSbhjID-MtYQU3v0q0voQ0GYkFeayy-3MFI
451CG: https://mega.co.nz/#!794U1TpT!rermqclZOpPKcYZY8z2YezUkQE-MWjYJgqyKMUAjYDo
600cg Kitkat: https://mega.co.nz/#!S1wlnYhC!doCPvf7ukeEFStcJPgqaEViE5oiHb_hpGSGnIh3n1IQ
Here for 600cg lollipop: https://mega.co.nz/#!3p4wBQAY!KUx26zaGdCBU6CGa4g68zT_iX9NxmIQCUvHiolfa_Oo
ZE550ML Lollipop 40.23 : https://mega.co.nz/#!HgBSySZA!EOxpsmPvHgCfl-9jUVRAv624Uq9LG4uvxuN83j6-P-k
ZE550ML Lollipop 40.40: https://mega.co.nz/#!P4RmXIwb!-xrDe8AYXdprZgUG4Ehs8fLNHhrdKpXdmaV3FBWPC_0
ZE551ML Lollipop: https://mega.co.nz/#!i4JRAQDR!9DzxtSd1oxDuCV6oc0rEhm-1sF4SA-94YPG9fLVw_lw
Source using Google cache (Vietnamese): http://webcache.googleusercontent.com/search?q=cache:w5AS-N1JrAoJ:zenphoneviet.com/threads/all-zen-stock-rom-firmware-kk-l-update-hang-tuan-chay-bang-asus-flash-tool.7066/+&cd=1
---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------
Those raw files are extremely difficult to find so if you pretend to have any of those phones i recommend to download. It works easily if you have fastboot. If you only have adb i did not saw working but i am trying.
---------- Post added at 07:38 AM ---------- Previous post was at 07:31 AM ----------
If you try to do that under adb they give a serial number mistake.
4 days trying to solve this bootloop using adb. At least one person here saved his phone with the raw links i found using google webcache in this vietnamese link so it was worth it. Looks like i will need to lose 40 days sending to Asus in Sao Paulo. What a hell folks, those asus firmwares are really crap. Set a great hardware for set poor software.
why my phone does not give any reaction when press power button+vol
I had same problem but different situation....I tried to make an experiment by changing systemui and I had done it with a wrong step .lucky I make a backup and tried to recover it.
But Things get worst when it failed to backupbang now my phone get stuck to Asus logo.I tried to follow the method that your all give in this thread but I can go to fastbootode with it must press power button+col down button.
CAN ANYBODY HELP ME WITH THIS PROBLEM
Sorry for my bad English
And I'm a newbie and try to learn something from pro
I have a big problem.
I unlocked the bootloader through Sony's developer-site, then tried to flash AndroPlus' kernel and TRWP. I had to try numerous times, since for some reason it refused to boot to TWRP, even though system booted fine.
Each time I started with flashing (Nordic) stock with Flashtool.
I finally got the tablet to boot to TWRP, but after trying to boot to system, it got stuck in a bootloop. I had to flash to stock again.
Now no matter what I try to fastboot, I get "FAILED (Remote: command not allowed". Flashtool seems to be able to re-unlock the bootloader, but it makes no difference.
If I try to unlock it through Sony, it gives the same error (so fastboot doesn't work _at all_).
Still boots to system fine.
Any help or maybe a solution even..?
USB-Hub?
@IlariJ
I had the same problem when I hooked up the tablet to my USB-Hub at the monitor.
Diving under the desk and connecting to an USB port at the PC did magic
DHGE said:
@IlariJ
I had the same problem when I hooked up the tablet to my USB-Hub at the monitor.
Diving under the desk and connecting to an USB port at the PC did magic
Click to expand...
Click to collapse
I tried with different cables and different ports, still the same error.. I even resorted to Sony PC Companion's fix-tool, so I guess I have the regular stock now. I tried to unlock the bootloader again the "official" way, but that error persists.
Flashtool seems to be able to unlock (and relock) the bootloader, but this makes no difference for fastboot.
This is weird since if it had bricked for some reason, the solution would be to wipe my ass with it, but since the system boots and works fine, a little hope still lives.
@AndroPlus , any suggestions?
IlariJ said:
I tried with different cables and different ports, still the same error.. I even resorted to Sony PC Companion's fix-tool, so I guess I have the regular stock now. I tried to unlock the bootloader again the "official" way, but that error persists.
Flashtool seems to be able to unlock (and relock) the bootloader, but this makes no difference for fastboot.
This is weird since if it had bricked for some reason, the solution would be to wipe my ass with it, but since the system boots and works fine, a little hope still lives.
@AndroPlus , any suggestions?
Click to expand...
Click to collapse
I'm still stuck with this.. Any help?
IlariJ said:
Any help?
Click to expand...
Click to collapse
Unfortunately not.
http://forum.xda-developers.com/z4-tablet/help/fastboot-getvar-retrieves-t3264589
IlariJ said:
I'm still stuck with this.. Any help?
Click to expand...
Click to collapse
Did you do anything with MyXperia?
@DHGE @jelbo
I can honestly say I don't recall doing anything with or to MyXperia. If I accidentally "let" it trigger itself, would this mean that fastboot becomes unusable? For good? Not even a full wipe + reflash could salvage?
Did you accidentally read the link I provided?
IlariJ said:
@DHGE @jelbo
I can honestly say I don't recall doing anything with or to MyXperia. If I accidentally "let" it trigger itself, would this mean that fastboot becomes unusable? For good? Not even a full wipe + reflash could salvage?
Click to expand...
Click to collapse
Reading the thread DHGE linked to it seems that MyXperia interference can result in the device being unable to unlock it's bootloader again. That's all I can say, I don't even have my Z4T yet
DHGE said:
Did you accidentally read the link I provided?
Click to expand...
Click to collapse
I'm sorry to ask this, but could you please be a bit more friendly? While IlariJ didn't mention he read your linked topic, he does provide useful info about what he's tried so far. If you know a solution or an answer, it's much more positive to just give him that, even though that might be 'you're out of luck'.
@DHGE Sorry, I didn't know I wasn't supposed to. My bad.
@jelbo ok, bummer. I really just found (and still find) it hard to believe that fastboot could get permanently messed up, so that even a total reset wouldn't, well, reset it. Thanks, though!
@AndroPlus @[NUT]
How-to get that TWRP recovery image flashed, so I can get recovery access on my Z4T?
Enter fastboot mode on Xperia z4. Then type in cmd: fastboot flash recovery <path to twrp_file>
U need the fastboot binary from Google
Hundsbuah said:
Enter fastboot mode on Xperia z4. Then type in cmd: fastboot flash recovery <path to twrp_file>
U need the fastboot binary from Google
Click to expand...
Click to collapse
Already tried with that..
Only gettings this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What to do..? :/
Destroyedbeauty said:
@AndroPlus @[NUT]
How-to get that TWRP recovery image flashed, so I can get recovery access on my Z4T?
Click to expand...
Click to collapse
Hi
You can get it at: https://dl.androplus.org/Xperia Z4 Tablet SGP712_SGP771/
Download twrp_2.8.7.0_(not)fixed.img
you must have the usb driver installed in your PC and adb and fastboot installed from google sdk
Is there still any update or solution to having MyXperia f'd up fastboot?
I tried to contact Sony that to my knowledge only unlocking the bootloader voids warranty, and since that's impossible because fastboot doesn't work, I should get this fixed. They didn't really refuse (at least after my hard convincing) and told me to contact the seller.
I did, and the seller said fastboot is more of a gimmick-possibility than a "assumed-to-work"-feature of Android (safe to say I don't agree). They sent links to different YouTube-videos on older devices, but I couldn't really find any solution or even a 100%-matching problem.
They also said that if I send this for repairing, the service company would only do a wipe/reset and then bounce the tablet back. Given that the Finnish Sony-service is notorious for making up water damage and/or "mechanic damage" to get to refuse warranty, I'm not really confident to send it there.
And also, to my knowledge the problem is much deeper than what a simple reset would solve, since I've done that and even re-flashed the firmware.
..how is it even possible for a simple software to break the whole fundament of the tablet? So bad even a complete wipe and reflash doesn't help?
IlariJ said:
Is there still any update or solution to having MyXperia f'd up fastboot?
I tried to contact Sony that to my knowledge only unlocking the bootloader voids warranty, and since that's impossible because fastboot doesn't work, I should get this fixed. They didn't really refuse (at least after my hard convincing) and told me to contact the seller.
I did, and the seller said fastboot is more of a gimmick-possibility than a "assumed-to-work"-feature of Android (safe to say I don't agree). They sent links to different YouTube-videos on older devices, but I couldn't really find any solution or even a 100%-matching problem.
They also said that if I send this for repairing, the service company would only do a wipe/reset and then bounce the tablet back. Given that the Finnish Sony-service is notorious for making up water damage and/or "mechanic damage" to get to refuse warranty, I'm not really confident to send it there.
And also, to my knowledge the problem is much deeper than what a simple reset would solve, since I've done that and even re-flashed the firmware.
..how is it even possible for a simple software to break the whole fundament of the tablet? So bad even a complete wipe and reflash doesn't help?
Click to expand...
Click to collapse
Lets unconfuse me here, i was never in the loop of your issue, but maybe I can help:
Your device won't boot to fastboot at all?
What's the status of your bootloader?
[NUT] said:
Lets unconfuse me here, i was never in the loop of your issue, but maybe I can help:
Your device won't boot to fastboot at all?
What's the status of your bootloader?
Click to expand...
Click to collapse
This is still the situation :
IlariJ said:
I have a big problem.
I unlocked the bootloader through Sony's developer-site, then tried to flash AndroPlus' kernel and TRWP. I had to try numerous times, since for some reason it refused to boot to TWRP, even though system booted fine.
Each time I started with flashing (Nordic) stock with Flashtool.
I finally got the tablet to boot to TWRP, but after trying to boot to system, it got stuck in a bootloop. I had to flash to stock again.
Now no matter what I try to fastboot, I get "FAILED (Remote: command not allowed". Flashtool seems to be able to re-unlock the bootloader, but it makes no difference.
If I try to unlock it through Sony, it gives the same error (so fastboot doesn't work _at all_).
Still boots to system fine.
Any help or maybe a solution even..?
Click to expand...
Click to collapse
So it seems like it boots to fastboot fine, even Command Prompt shows it listed as a fastboot device, but no command goes through.
[NUT] said:
Thanks for testing @Hundsbuah and @jelbo.
I'll have a new guide to follow on the same TWRP image later, let's see if I can get it to work properly with a little wiggling, trying to proof-of-concept here... and that isn't easy without the device at hand
---------- Post added at 10:36 AM ---------- Previous post was at 10:33 AM ----------
Ok, so your bootloader is 'unlocked' but fastboot still refuses to flash anything.
That's partially a good thing:
Can you boot to fastboot and then execute run 'fastboot oem unlock' on your pc/mac.
What does fastboot say about that?
Click to expand...
Click to collapse
{
"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"
}
:crying:
IlariJ said:
:crying:
Click to expand...
Click to collapse
Can you try:
Code:
fastboot command list
if that says "command not allowed" as well, then your bootloader is probably relocked by means of flashmode.
Try to unlock your device again using @Androxyde's flashtool. After trying that, please attach the log from flashtool.
---------- Post added at 11:38 AM ---------- Previous post was at 11:24 AM ----------
jelbo said:
Code:
C:\Windows\system32>adb shell
~ # ←[6nbusybox lsof | grep touch
603 /system/vendor/bin/touch_fusion /dev/kmsg
603 /system/vendor/bin/touch_fusion socket:[1879]
603 /system/vendor/bin/touch_fusion /vendor/firmware/max11945.bin
~ # ←[6nkill -9 603
~ # ←[6numount /system
~ # ←[6n/vendor/bin/touch_fusion
/sbin/sh: /vendor/bin/touch_fusion: Permission denied
~ # ←[6nbusybox lsof | grep touch
~ # ←[6n/vendor/bin/touch_fusion /vendor/firmware/max11945.bin
/sbin/sh: /vendor/bin/touch_fusion: Permission denied
~ # ←[6n
Click to expand...
Click to collapse
Oh crap... should have known
I'm going to modify my step-guide...
[edit]
now updated.
[NUT] said:
Can you try:
Code:
fastboot command list
if that says "command not allowed" as well, then your bootloader is probably relocked by means of flashmode.
Try to unlock your device again using @Androxyde's flashtool. After trying that, please attach the log from flashtool.
Click to expand...
Click to collapse
Lists the commands as supposed to(?).
Should I try to unlock anyway?
I've already tried many apps, such as kingoroot, kingroot, one click root, framaroot, etc. i really need help. Thx in advance
kebakkaran said:
I've already tried many apps, such as kingoroot, kingroot, one click root, framaroot, etc. i really need help. Thx in advance
Click to expand...
Click to collapse
I have same problem
Sent from my SM-J320FN using Tapatalk
imrandewana said:
I have same problem
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Same issue here as well, nothing I try works on this phone, it's driving me insane.
EDIT: It's android 6, so you can't root the phone without a custom recovery.
WELP. So I just spent the past 2 days wasting my time on this god awful phone. I can't even access fastboot on this piece of crap, it comes up for 2 seconds and then disappears and no amount of "properly" installing usb drivers for it has helped. I even tried disabling driver signing and installing the drivers through adding legacy hardware. Nothing worked at all. So I thought I'd just install a custom recovery with sp flash tool. So I downloaded a stock rom for the vfd300 (my phone) from here: https://androidmtk.com/download-vodafone-stock-rom-models and ported TWRP using an ASUS Zenfone GO's TWRP.img.
Custom Recovery works fine, the phone does not. It is now stuck in a bootloop. Tried formatting everything (from TWRP) doesn't work. Tried flashing the rom again (even with the stock recovery) still stuck at bootloop, tried about 3 other vfd300 stock roms that people have uploaded to http://forum.gsmhosting.com and none of them have worked either. Currently downloading yet ANOTHER one and tbh I don't have high hopes. (EDIT: It didn't work)
Any help at this point would be appreciated.
Holy crispy crap it started............................. So I managed to find a working rom from (what appeared to be) some Vietnamese file hosting website .
You follow the instructions below at your own risk. No one is responsible for any damage done to your device but you.
I officially have root working on this device.
Now that I've done it, it's a surprisingly simple procedure. As I stated in the edit in my reply above, the VFD300 has Android 6 on it, which requires (afaik) a systemless root to be installed from recovery.
I ported the custom recovery from this thread (since the Z00VD has the same chip as the VFD) which you can download here.
Download the latest version of Chainfires beta SuperSU installer from this thread and transfer it to either your phones internal storage or SD card.
Also download a copy of SP Flash tool (if your fastboot works, use that instead). Finally, you will need this scatter file.
Unplug your phone from the computer and shut it down. Open SP Flash tool and click the download tab at the top.
{
"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"
}
Click "choose" next to the Scatter-loading file box and select the path to the scatter file you downloaded. IMPORTANT Make sure all boxes below except recovery are unchecked and select Download Only in the drop-down box. Double click on recovery in the Location column and point it to the custom recovery image you downloaded.
Click the Download button at the top and then plug your phone back in. The bottom bar will turn red, then purple, then yellow and once it is fully done flashing you will get a pop-up box with a green tick as confirmation.
Unplug your phone and reboot into recovery (Power+Vol-Up). In the custom recovery, select install, go to the directory you transferred Chainfires beta SuperSU.zip to, install it and reboot. TWRP will ask you if you want it to install root, DO NOT LET IT INSTALL ROOT. Your phone may loop a few times and can take up to 10 minutes to boot the first time, but it will be successfully rooted.
If you need a copy of the stock rom, download this one. If you want to flash this rom, make sure you use the scatter file in the roms archive and select firmware upgrade from the Download Only box on SP Flash Tool.
EDIT: I'm so sorry I borked the hyperlink order. Instead of linking to the scatter file I linked to the entire rom and vice versa with the stock rom link
Vikeyev
vikeyev please contact me at [email protected]
Hey ummm, this is a great tut. I have problem with mine though unfortunately :/. I've done all steps correctly, with each of them followed thoroughly but then I get to the point where my device isn't identified when I connect it to the computer. None of those colored 'bottom bars' pop up nor the green tick as confirmation concept. PLEASE HELP ME !
[UPDATE] When I disconnect my device, some BROM error comes up but idek what it means.
InevitableDefeat276 said:
Hey ummm, this is a great tut. I have problem with mine though unfortunately :/. I've done all steps correctly, with each of them followed thoroughly but then I get to the point where my device isn't identified when I connect it to the computer. None of those colored 'bottom bars' pop up nor the green tick as confirmation concept. PLEASE HELP ME !
[UPDATE] When I disconnect my device, some BROM error comes up but idek what it means.
Click to expand...
Click to collapse
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
kathy9911 said:
vikeyev please contact me at [email protected]
Click to expand...
Click to collapse
....why?
stuck on loading
hi i'm a bit stumped here i followed all the steps to root my vfd 300 i got custom recovery installed but now when i reboot it the phone just sits on the loading part about 30 minutes i been waiting is there any thing i have missed or can do to solve this
thanks in advance
putzwon said:
hi i'm a bit stumped here i followed all the steps to root my vfd 300 i got custom recovery installed but now when i reboot it the phone just sits on the loading part about 30 minutes i been waiting is there any thing i have missed or can do to solve this
thanks in advance
Click to expand...
Click to collapse
Sounds like a boot loop. You need to download the stock rom (it should be about 700mb or so and in rar format). Once you've downloaded the stock rom, extract the archive to a folder somewhere (you will need something like 7zip or Winrar). Open SP Flash tool, load the scatter file from the extracted folder and make sure you select every box. There should be a check mark in each box. Change SP Flash tools dropdown box to firmware upgrade (by default it is on Download Only) and then flash it similar to how you did with the recovery (make sure you change the recovery to the custom one from above).
If my instructions aren't clear enough, I can do it again to my phone and take pictures of the entire process to make it easier to follow.
vikeyev said:
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
....why?
Click to expand...
Click to collapse
Yeah man! I've done that as well but had no luck .
1. I've enabled USB Debugging Mode and I've shut my phone down (NOTE: It has not been connected to the computer)
2. I opened the SP Flash tool and I clicked the download tab at the top
3. I then choose next to the scatter-file thing and have relocated it to the scatter file that I've downloaded from your link
4. ALL boxes are unchecked except recovery with download-only in the drop-down box
5. I've done the recovery image and everything and then...
6. I plug my phone in (Yes, it's completely shut down from step 1) with the USB cable and nothing shows up (Colored bars, tick etc.)
7. When I unplug it, an error comes up and then I'm completely stuck with no idea of what to do next
[UPDATE] - Does my phone have to be on the latest version?
Same problem
I'm having the same issue. I follow the instructions, phone off, press download, etc. I dont get any bars changing colours.
Did you manage to sort it out yet?
[update] managed to work it out. the MT65xx drivers werent installed properly. Use the instructions here (I cant post links!!! google: sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices) to get them working first, make sure the battery is out of your phone and the main instructions in this thread work first time.
huggies15 said:
I'm having the same issue. I follow the instructions, phone off, press download, etc. I dont get any bars changing colours.
Did you manage to sort it out yet?
[update] managed to work it out. the MT65xx drivers werent installed properly. Use the instructions here (I cant post links!!! google: sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices) to get them working first, make sure the battery is out of your phone and the main instructions in this thread work first time.
Click to expand...
Click to collapse
My brother, you're a genius . Thanks for helping out! It was worked. God bless!
stuck with a white circle runs
hi bro, i met the same issue.
I've done all the step successfully, and after i reboot my phone, it shows up with the logo of Vodafone, then a big circle became a smaller one, and then, the small circle runs endlessly.
I can go in recovery, but cannot boot the system.
I also did a memory test, got tow error
ERROR: NAND Flash was not detected!
ERROR: UFS was not detected!
I tried many times, and format whole flash and download all of them again.
it just doesn't work.
please help, thank you in advance.
frepeak said:
hi bro, i met the same issue.
I've done all the step successfully, and after i reboot my phone, it shows up with the logo of Vodafone, then a big circle became a smaller one, and then, the small circle runs endlessly.
I can go in recovery, but cannot boot the system.
I also did a memory test, got tow error
ERROR: NAND Flash was not detected!
ERROR: UFS was not detected!
I tried many times, and format whole flash and download all of them again.
it just doesn't work.
please help, thank you in advance.
Click to expand...
Click to collapse
Bro I got the EXACT same issue now because I accidentally installed Supersu through TWRP (which is pretty stupid because it was mentioned to AVOID the Supersu prompt when exiting TWRP). I've been stuck on bootloop for a couple of days now .
---------- Post added at 11:39 PM ---------- Previous post was at 11:14 PM ----------
vikeyev said:
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
....why?
Click to expand...
Click to collapse
Bro, I accidentally installed Supersu when the prompt came up as I tried to exit TWRP. I know you said to NOT let it install, which was pretty stupid that I didn't read carefully what you wrote. Now I'm stuck in bootloop -_-.
Please help bro; I've tried flashing it to the stock rom, removing dalvik cache and everything etc. Nothing's working. Please help!
successfully got a rooted vfd 300
InevitableDefeat276 said:
Bro I got the EXACT same issue now because I accidentally installed Supersu through TWRP (which is pretty stupid because it was mentioned to AVOID the Supersu prompt when exiting TWRP). I've been stuck on bootloop for a couple of days now .
---------- Post added at 11:39 PM ---------- Previous post was at 11:14 PM ----------
Bro, I accidentally installed Supersu when the prompt came up as I tried to exit TWRP. I know you said to NOT let it install, which was pretty stupid that I didn't read carefully what you wrote. Now I'm stuck in bootloop -_-.
Please help bro; I've tried flashing it to the stock rom, removing dalvik cache and everything etc. Nothing's working. Please help!
Click to expand...
Click to collapse
I was stuck in bootloop, but we don't share the same reason. I think there is something wrong with the rom above.
I found another rom, flash it, and problem solved, pretty simple. Now, I have a rooted vfd 300, even better than the stock rom, but you need to delete some app you don't like before you enjoy it.
you can find this rom by searching MT6580_S00_EMMC_MRA58K__6.0_VFD-300_Vodafone.zip
frepeak said:
I was stuck in bootloop, but we don't share the same reason. I think there is something wrong with the rom above.
I found another rom, flash it, and problem solved, pretty simple. Now, I have a rooted vfd 300, even better than the stock rom, but you need to delete some app you don't like before you enjoy it.
you can find this rom by searching MT6580_S00_EMMC_MRA58K__6.0_VFD-300_Vodafone.zip
Click to expand...
Click to collapse
can you provide link please google z not giving results for me
Vodafon VFD300 Firmware + TWRP + ROOT
As recommended above, Vodafon vfd 300 as a result of the phone turned on until the endless download -TWRP was not requested, sr1-SuperSU-v2.82 - sr120170608224931 and flash driver SP Flash Tool 3.1352.01 (5.1352.01) did not fit. I decided to solve the problem - the vfd 300 flashed through the firmware MT6580_S00_EMMC_MRA58K__6.0_VFD 300_Vodafone_356774071726533_08_19_2016_09_02_53 (1) (2), the flash driver SP_Flash_Tool_v5.1648_vin - the next way (remove the battery, hold the volume (-) until the end of the firmware, Download, connect the cable to the phone (the firmware will go to Emergency port about 8 minutes)
****************Next, we flash the TWRP - the flash driver SP_Flash_Tool_v5.1648_ the scatter and the TWRP are recommended - (MT6580_Android_scatter.Tht and
*Recovery-TWRP-VFD300.img) flashing.
**********We check TWRP (we clamp simultaneously ON-volume (+) release ON-opens TWRP.
**********Get Root rights ---- copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to the phone folder, turn off the phone, go to TWRP find Install - SuperSu - Swaipe to instal - Dj not Install. All made happy, good luck. There will be questions [email protected]
InevitableDefeat276 said:
Yeah man! I've done that as well but had no luck .
1. I've enabled USB Debugging Mode and I've shut my phone down (NOTE: It has not been connected to the computer)
2. I opened the SP Flash tool and I clicked the download tab at the top
3. I then choose next to the scatter-file thing and have relocated it to the scatter file that I've downloaded from your link
4. ALL boxes are unchecked except recovery with download-only in the drop-down box
5. I've done the recovery image and everything and then...
6. I plug my phone in (Yes, it's completely shut down from step 1) with the USB cable and nothing shows up (Colored bars, tick etc.)
7. When I unplug it, an error comes up and then I'm completely stuck with no idea of what to do next
[UPDATE] - Does my phone have to be on the latest version?
Click to expand...
Click to collapse
you need to make sure you click download on flash tool then plug the usb in to phone and pc (also remember the battery has to be out of the phone for it to flash)
then you should see the red,yellow, green colours.
Hi all. I will be attempting to root my Vodafone VFD-300 tomorrow,after reading through the entire thread there seems to have been many issues with getting it done successfully. I also saw that it was suggested to provide step by step screenshots of the entire process. If anyone who managed to do the whole rooting with no problems could please do so again and provide us with the step by step screenshots,it would be greatly appreciated. Thanks in advance.
Hello guys, I was one the unfortunate guys who tried to downgrade from an updated XLOADER version FW to an older and failed to do so, resulting a hard brick. I managed to get my phone up and running again with free tools without DC-Phoenix, I include everything detailed in my post, even a preconfigured virtualbox linux system for the initial steps. I also included an UPDATE.app splitter too.
So, this is not an XLOADER downgrade tutorial, with this you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
What you need for this whole thing:
This archive, it contains the firmware, the tools, the preconfigured linux, and the drivers.
VirtualBox downloaded and installed, just google it.
A physically opened phone, unscrewed motherboard, as the testpoint is on the other side, and something to short your testpoint.
First steps:
After you downloaded the archive, just unzip the whole thing to a folder where you have enough space ( the archive is ~7.8GB unzipped)
Now you need to download and install VirtualBox, and import the HIKEY.ova virtual system I included in the zip.
Here's how you can do it
Step one, The HIKEY.ova file is located in the virtual machine folder
{
"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"
}
Step two, Leave the settings at default and import it
Setting up your phone and computer:
You need to open up your phone physically, here is a good video of the disassembly https://www.youtube.com/watch?v=Zkj7YVeSzS4
Now, if you got your motherboard unscrewed, you must leave the cable with the big arrow connected to it.
Plug your usb cable into your phone and into your computer, now you must short your testpoint, I included an image about where the testpoint is. https://i.imgur.com/q9ZNGgx.jpg
Just use metal tweezers or a bent metal paperclip, one end on the test point, and the other end to something you can ground it with, the metal shields next to it are good to use.
If you did everything right, your computer should recognize a new device named USB SER, if this is the case, you now must install the huawei android phone drivers. Now the USB SER is now recognized as HUAWEI USB COM 1.0 in the device manager.
Starting the revive process:
After you got the HUAWEI USB COM 1.0 set up, you need to start the virtual linux machine.
The first thing it will ask for is hw login, just type this with lowercase letters.
Code:
hw
hw (again)
Now, you need to add your HUAWEI USB COM 1.0 to the virtual machine.
To do this you need to click the USB icon in the lower right corner and select HUAWEI USB COM 1.0.
.
.
It should have connected as ttyUSB0, you can check it with the command
Code:
dmesg
Now you need to type
Code:
cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0
(if it asks for sudo password its hw again, also if your device is connected as other ttyUSB number, then you should use that number)
You should see this written from the console if it succeded
With this, you now have a special fastboot booted in your phone.
Flashing the system:
You can now exit the virtual machine, and run first batch, named 1. revive flasher.bat.
It will give you two options after it finished flashing the system, check the one you need, VTR-L29 or VTR-L09.
After the batch is done and you felt that the phone rebooted from the fastboot mode, you can now disconnect the phone from the computer.
You now need to connect the LCD cable, the battery cable, and buttons cable back to your motherboard, no need to re screw the mobo yet, just leave everything hanging in case you need to do the process again with the testpoint.
Now manually boot back into fastboot, Hold volume down while connecting your usb to your computer.
Now you need to flash a TWRP with 2. TWRP recovery.bat.
After that, boot into TWRP, wait for it to completely boot up, and flash an oeminfo with one of the oeminfo batches 3a or 3b.
With this, you should now be able to boot into the system, if there are still problems like bootlooping, do a factory reset from recovery.
Big thanks to:
@goodwin_c for the special fastboot/hikey_idt combo.
@Pretoriano80 for the TWRP recovery
@ante0 for the splitupdate.exe
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
NowLearn said:
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
Click to expand...
Click to collapse
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
yoghurt13 said:
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
Click to expand...
Click to collapse
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
NowLearn said:
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
Click to expand...
Click to collapse
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
yoghurt13 said:
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
Click to expand...
Click to collapse
bro, u didnt have to do that, but I appreciate it. Let me pm u. Thank you again
Would it be possible to rebrand VTR-L09 to VTR-L29 using this method?
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
volpula said:
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
Click to expand...
Click to collapse
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Ekenfo said:
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Click to expand...
Click to collapse
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
I can give you only my instagram.beacause I dont have a backup phone rightnow just waiting to fix my phone.if I can fix that buy a new phone but never huawei again.
yoghurt13 said:
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
Click to expand...
Click to collapse
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
volpula said:
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
Click to expand...
Click to collapse
Then there is the problem, try to install HiSuite, or my android driverpack, and try to see if the phone shows up in device manager.
Ekenfo said:
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
Click to expand...
Click to collapse
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
yoghurt13 said:
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
Click to expand...
Click to collapse
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Ekenfo said:
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Click to expand...
Click to collapse
There is currently no way to downgrade from XLOADER2, huawei did some black magic with it, and there is a checker built in the phone that checks if its a loader1 or 2.
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Ekenfo said:
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Click to expand...
Click to collapse
I literally have no ideai yet how to fix our IMEI, since the NVME partition does not contain the information we need, I just tested one from a working phone, and it was the same as before, zeroed out IMEI.