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?
Related
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, 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"
}
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
mike4peace said:
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, nothing.
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
Click to expand...
Click to collapse
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
palmbeach05 said:
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
Click to expand...
Click to collapse
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
You also need drivers.
All of that has been covered already. Did you search?
ravilov said:
You also need drivers.
All of that has been covered already. Did you search?
Click to expand...
Click to collapse
yes mate i have motorola device manager, as far as i know this the same thing right? just like samsung's kies
i really did tons of search but im almost hopeless. guys who have the same problem did solved it by just taking device to fastboot but mine is not going in that mode. when i plug the device its charger it says same problem and also says battery too low to flash. so im just gonna go and buy a new battery
mike4peace said:
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
Click to expand...
Click to collapse
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
palmbeach05 said:
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
Click to expand...
Click to collapse
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
mike4peace said:
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
Click to expand...
Click to collapse
That's rsd mode, I think. From there you can flash an full sbf and start over
Enviado desde mi MB860
ravilov said:
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
Click to expand...
Click to collapse
not hard brick? oh thank god, i said so because the phone does nothing
yeah i searched it before and its calldd factory cable, i havent done it yet but i tried usb jig which was a failure. no one owns an atrix around me, so i just need a external charger and right now im onto it
guys, i really appreciate your helps, im very glad to have you here thanks a lot. i will post here the results
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
Here is short explanation what hard brick is:
Hard bricks are more or likely that you won’t be able to fix it. If you get a hard brick, your phone will not be repaired, there will be absolutely no way to without sending it to the manufacturer. This could be from wiping the entire system without flashing a rom, no way into recovery and no way to get it back. This could be also caused from bad installation files, or turning off/removing the battery from your device during the first installation or boot up sequence. Sometimes you can fix a hard brick, but more often than not your device is going to be broken. This is a fix that is required by the manufacturer of the device. Honestly if you get this, it may just be simpler to go get the device replaced instead of even trying to fix it. HOWEVER make sure you go out and read about it, typing in the exact problem and doing lots of research for your specific device as there may be some hope for the device somewhere.
Click to expand...
Click to collapse
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
palmbeach05 said:
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
Click to expand...
Click to collapse
im not quite sure cause i bought this phone intentionally via ebay-like web site
yanick76 said:
Here is short explanation what hard brick is:
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Click to expand...
Click to collapse
okay soft brick it is, but my phone doesnt do anything but show an error screen (and goes)
andresrivas said:
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
Click to expand...
Click to collapse
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
mike4peace said:
[...]
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
Click to expand...
Click to collapse
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
andresrivas said:
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
Click to expand...
Click to collapse
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
mike4peace said:
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
Click to expand...
Click to collapse
JTAG depends heavily on your ability to solder tiny surface mount components. Good luck.
So tried downloading the 6.0 ota. after it installed it, it got stuck in a bootloop. tried doing factor reset and deleting cache and data.
nothing has worked so far.
heres the rub, i never unlocked my bootloader and i cant get into the OS to set the developer options. it seems my only solution is to RMA it. but im hoping maybe there is a hack of some sort.
heres to hoping.
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
WoodroweBones said:
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
Click to expand...
Click to collapse
No it was an OTA update. got the notification this morning and had it install the update. it obviously didnt take. i have not rooted my tablet or done anything like that. its actually the first device ive ever not rooted....
I had the exact same problem. I installed the OTA last night, and now it sits at the boot animation for hours. I tried to wipe cache, but I got an error saying it couldn't mount the partition. I tried to sideload it, and it failed, saying it couldn't mount it. I just (reluctantly) performed a wipe and hopefully that will work, but I'm not optimistic.
Update: no luck. So I permanently deleted a lot of stuff for no reason. =/
Yeah my problem is I can't sideload because my computer doesn't recognize it . I mean this whole unlocking the boot loader from within the OS thing is the stupidest design I've ever seen.....
since i can still get into hboot and fastboot can i side load the OTA? adb isnt seeing it in recovery but it sees it in fastboot.
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
I'm caught in the boot loop as well after having downloaded the OTA... I must say, over the past couple weeks I was stuck in boot loops on several occasions, and only after a bunch of restarts would it load fully (and "update apps").
When this device works properly, I have no qualms. But it's incredibly irritating for a $600 tablet to be so shoddy...
stevesmithis said:
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
Click to expand...
Click to collapse
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
wesmagyar said:
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
xworld21 said:
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
Click to expand...
Click to collapse
Will I'll be a mother effer I was able to get it to recognize my device by installing the Samsung ADB driver and from there I was able to sideload the OTA and it is now working.......
The very first thing I'm doing as soon as I actually get it start it is I am going to enable OEM unlock. Everybody who has one of these devices should do that immediately.
Thank you so much man you are awesome
{
"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"
}
Sent from my SM-N910T using Tapatalk
I tried again and it failed. Sadness. Guess I'll just have to swap it out.
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
thegeneralfamily said:
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
Click to expand...
Click to collapse
I was having the same problem I installed the Samsung ADB driver, , and all of a sudden my computer recognized my Nexus 9 in a adb mode
Sent from my SM-N910T using Tapatalk
Mine wouldn't show up until I was in recovery and actually picked the "install from adb" or whatever from the menu.
yeah it doesn't actually go into adb mode until you select the sideload option. just as it doesn't go into fastboot untill you are in fastboot.
I was able to download the OTA from android authority. just made sure that the upgrade matched the one that i was upgrading from, i have a galaxy note so when i couldnt get windows to recognize the nexus 9 in adb mode i selected search my computer for the drivers and selected select from installed drivers and out of sheer desperation selected the Samsung ADB driver and sure enough the worked. from there i was able to adb sideload the update and install it and it rebooted into beatiful android 6.0 tablet has been working fine so far with no issues.
First thing i did however was allow unlocking of the bootloader in the developer options.
Edit: nvm
stevesmithis said:
Edit: nvm
Click to expand...
Click to collapse
Yeah I was going to say because I'm the op, I had no access to the operating system either but I was able to accomplish two steps I laid out above and it fixed my problem.
Sent from my SM-N910T using Tapatalk
Also also misread your post. I thought you were saying that unlocked the bootloader before you fixed it. Lol
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
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.
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
try clean flashing a fastboot global stable rom using mi flash tool(dont forget to choose clean all in the pc flash tool).
Thanks for your reply, I have tried MiFlash app but I am getting error "Erase boot error"
{
"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"
}
put your phone in fastboot mode.request anther unlock code if that dont work create new account on pc try again might work then you could use flash tool
Unlocking even with new account does not work because I am unable to link my phone to MI account
there is way with locked bootloader look up EDL mode on youtube you have to take phone apart or shop might fix it that way for you.
---------- Post added at 04:20 PM ---------- Previous post was at 03:57 PM ----------
here read up on edl mode
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
Click to expand...
Click to collapse
You need a windows pc for this method.
Download latest miui recovery rom from here.
http://bigota.d.miui.com/V10.3.6.0.PEJMIXM/miui_POCOF1Global_V10.3.6.0.PEJMIXM_0ba4120b12_9.0.zip
Rename it to stockrom.zip and save to desktop of pc
Reboot phone to recovery. Select mi assistant.
Install google adb drivers and download platform tools from here. http://goo.gl/zTGVyM (32 bit)
http://goo.gl/el03X5 (64 bit)
run command from pc(cmd)
Adb devices
Now if u see any device showing sideload .you have successfully installed adb drivers. If not, search more on xda for adb installation.
Now this if your device appear in list.
adb sideload <path_to_stockrom.zip>
Wait for few minutes to install and boot. Report back if found any error in cmd. I have other method too.
---------- Post added at 05:33 PM ---------- Previous post was at 05:29 PM ----------
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
Click to expand...
Click to collapse
http://en.miui.com/thread-835254-1-1.html this is the other method. Will definitely work
Thanks for your guide but I dont think it would work since there in no recovery in the phone, only fastboot is available. I will try EDL mode
Aealo said:
Thanks for your guide but I dont think it would work since there in no recovery in the phone, only fastboot is available. I will try EDL mode
Click to expand...
Click to collapse
You don't need unlocked bootloader for flashing stock ROM through Mi Flash Tool. If you get errors, change the cable, change the PC/Laptop, use an Intel machine instead of AMD Ryzen, use USB 2.0 port instead of 3.0 port etc.
So I have tried EDL mode but that gives me error that my account is not authorized and also normal flash on different PC and that says that I cannot erase while in LOCK state
here youtube video on edl flashing with err
might work give try
https://www.youtube.com/watch?v=p0O2PqUnem8
berty321 said:
here youtube video on edl flashing with err
might work give try
https://www.youtube.com/watch?v=p0O2PqUnem8
Click to expand...
Click to collapse
Thanks for the advice but its too late
Already got it flashed for 10eur by someone with EDL authorized account
Aealo said:
So I have tried EDL mode but that gives me error that my account is not authorized and also normal flash on different PC and that says that I cannot erase while in LOCK state
Click to expand...
Click to collapse
try to flash it with adb
Aealo said:
Thanks for the advice but its too late
Already got it flashed for 10eur by someone with EDL authorized account
Click to expand...
Click to collapse
can you teach me how did you do that? were same problem
Aealo said:
Thanks for the advice but its too late
Already got it flashed for 10eur by someone with EDL authorized account
Click to expand...
Click to collapse
Need help... Same problem "System destroyed with locked bootloader"
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advanchi9
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
Click to expand...
Click to collapse
Hi buddy can you give me the contact of your friend whose helped you with the EDL authorized account because I have same problem with my phone
Click to expand...
Click to collapse
hi, sorry I dont remember who flashed my phone but you can definitelly find someone using google. there are many telegram channels for that