Z3c: cannot install ROMs from TWRP, fastboot mode broken - Xperia Z3 Compact Q&A, Help & Troubleshooting

Hey all, I've been messing around with my Sony Z3 Compact (D503) and I think I broke something when I forcedfully tried to install a ROM. My problem is this, I have no system to boot to and fastboot mode dosen't work (it boots to recovery instead). Just to be clear, my drivers for ADB and fastboot are installed and working fine.
When I try to install a zip file from TWRP, i get the error message "Failed to mount '/system' (invalig argument)
When I try to boot to fastboot mode to install a new image through fastboot, I simply get back to recovery mode (TWRP).
Being curious to see if there is anything in /system or if the permissions there are broken, I used adb shell to enter /system and it shows as empty. using "ls -la" inside /system yiels the following results:
Code:
/system # [6nls -la
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Jan 1 1970 .
drwxr-xr-x 23 root root 0 Mar 14 18:40 ..
I have also tried to sideload a ZIP-file to my device, which yielded in another error
Code:
(E3004: This package is for "D5803,D5833,z3c,aries" devices
this is a "".
My gut tells me that the bash or shell commands are broken, and therefore it dosen't execute the install script properly (and perhaps also explains the garbled shell-prompt). Another possible case is that the installed TWRP version is errornous and need to be replaced (and how is that possible without fastboot...).
Would appriciate to get some help to get it up and running!

Flashtool. It comes with Xperifirm, so you can download the latest stock ROM.
http://www.flashtool.net/index.php

temporary2010 said:
Flashtool. It comes with Xperifirm, so you can download the latest stock ROM.
http://www.flashtool.net/index.php
Click to expand...
Click to collapse
Dosen't flashtool require the phone to be in fastboot mode? Because that's on of the problems stated in my first paragraph

Flashtool also allow devices in flash mode. I'm in the process of restoring mine because i royally screwed up my z3c today. Problem is that no matter what official rom i throw at it, it won't boot to Android all the way and can't get fastboot to work.
Frigging stuck.

liberteus said:
Flashtool also allow devices in flash mode. I'm in the process of restoring mine because i royally screwed up my z3c today. Problem is that no matter what official rom i throw at it, it won't boot to Android all the way and can't get fastboot to work.
Frigging stuck.
Click to expand...
Click to collapse
Got flashtool to work in flashmode. Tried several official ftf files until one worked, the unbranded german one for me did the trick. Others remained stuck during boot. At LEAST I can put the phone to adb from there and then to fastboot through adb. Give it a try.

liberteus said:
Got flashtool to work in flashmode. Tried several official ftf files until one worked, the unbranded german one for me did the trick. Others remained stuck during boot. At LEAST I can put the phone to adb from there and then to fastboot through adb. Give it a try.
Click to expand...
Click to collapse
Good job on un-bricking your phone! Got a link to the german FTF files and the tutorial/guide you followed?

KhaaL said:
Good job on un-bricking your phone! Got a link to the german FTF files and the tutorial/guide you followed?
Click to expand...
Click to collapse
Sure I can find that pretty quickly.
There you go, entire post is just links to various ftf files that you can flash using flasthool in flashmode mode:
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
The one that finally saved my z3c after tinkering (too much) with fastboot too much is this very one:
https://forum.xda-developers.com/showpost.php?p=68132744&postcount=2175
From there I set up developer options, enabled adb, used adb to reboot to bootloader, tested each twrp image to see whether I could load them safely (fastboot boot image.img instead of fastboot flash recovery image.img).
Since all versions were ok, I flashed the LOS16 recommended 3.3.1, and flashed LOS16 from there, wiping system, data etc. It works perfectly now.

Related

[Q] Nexus One stuck on reboot screen

My Nexus One is stuck on boot screen and keeps recycling/vibrating. To condense information, here are bullet points of the situation:
-Nexus One 2.3.6 with unlocked bootloader
- PASSIMG.IMG is wrong or missing in HBOOT
-Can't access the sd root because I lost my sd adapter
-I've tried to fastboot recovery-RA-v2.2.1.img and Clockorange but I think that because I don't have the SU files in a folder titled SU on my sd, it doesn't go into the recovery menu
-When I cmd fastboot devices the serial comes up, but when I cmd adb devices, nothing comes up
-Can't access sd storage to move the SU folder via cmd
I've been working on this the past two days and searching and trying anything and everything. And nothing has worked. Any help would be great.
You don't need anything on your sdcard (or your sdcard itself for that matter) to put a custom recovery on your phone. Try this after putting your phone into fastboot mode and getting your cmd prompt up on the computer:
Code:
fastboot flash recovery "c:\location\to\recovery.img"
fastboot boot recovery "c:\location\to\recovery.img"
From here, try a factory reset.
And adb won't be able to see your phone until you are either in recovery or fully booted up in Android (only with USB Debugging enabled).
When I do "fastboot boot recovery recovery-RA-v2.2.1.img" it comes up cannot load recovery.
Any ideas?
And once that goes through, do I boot through recovery on the phone or through command prompt?
Thank you for the reply.
Is the recovery in the folder where you are typing the command? And have you verified that the md5 sum of the recovery is correct?
And, I always just change the command from flash to boot to boot into the recovery the first time. Otherwise, if you are running a stock Android version, your recovery might get restored back to the stock recovery (Android has checks in place for that).
Nevermind, I did get it to go through, but then my N1 reboots on its own and is still stuck at the bootscreen
Ok, do you want to continue running stock, or would you like to try a custom ROM? Because, it sounds like you will need to reload your ROM (assuming the Factory Reset/Data Wipe didn't work). They have a couple of rooted extremely close to stock versions on here, or you might want to give CM7 or MIUI a shot. I would also go and get temasek's system-only format since Amon_RA doesn't give you the option to format your /system partition. You can find the file in his mediafire folder http://mediafire.com/temasek
My original intentions were to put CM7 on my phone because Gingerbread began to crash a lot. So in that case, how am I supposed to install the CM7 ROM onto my phone if I can't get past the bootscreen?
So, the fastboot boot command doesn't work?
fastboot does work, adb doesn't
No, does the
Code:
fastboot boot recovery "c:\location\to\recovery.img"
get you into recovery? Or does it still freeze on the X screen (when you say bootscreen, I assume you mean the X)?
Sounds like the recovery isn't installing with fastboot? Do you get any error messages?
It will still freeze at the X and never boots into recovery.
seb0 said:
It will still freeze at the X and never boots into recovery.
Click to expand...
Click to collapse
I got exactly the same problem as you. Didn't you see my post?
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
I got an idea, but not sure about it:
Get someone who has a working Nexus One to make an nandroid backup, and send the boot.img and system.img and fastboot it into our devices?
mrBira said:
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
Click to expand...
Click to collapse
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?
bassmadrigal said:
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?
Click to expand...
Click to collapse
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"
mrBira said:
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"
Click to expand...
Click to collapse
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?
bassmadrigal said:
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?
Click to expand...
Click to collapse
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.
I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.
mrBira said:
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.
Click to expand...
Click to collapse
Have you tried any additional recoveries? It has been awhile since I used that command, but I know it has worked in the past.
seb0 said:
I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.
Click to expand...
Click to collapse
You won't have adb access unless you are in recovery or booted into Android with USB Debugging enabled.
Where did you get the system.img and boot.img files from?
http://forum.xda-developers.com/showthread.php?t=1061648
This was the only system.img and boot.img file I could find.

Problem with flashing new ROM

Hi all,
A while ago I rooted my Z3C and flashed a custom ROM. Today I wanted to update to a new version and I messed up very bad. I always was a die-hard flasher so I did things as always. Downloaded the ROM as usual, wiping as usual (I always wipe everything). Tried to install the new ROM and got the message that it can't mount /system. Looked this up and it seems that Sony got a kernel protection for /system and /cache, which I didn't know.
But now the actual problem. For some reason my system partition did got wiped, as result I can only acces recovery. But I still can't flash ROMs due the kernel protection. I tried to sideload the RICDefeat to disable the protection but this didn't work. Also tried to go back to stock with the EMMA tool but this didn't work either as the application doesn't detect the phone.
Anyone has a good idea what I can do now? I didn't backup my system partition, but I guess it doesn't matter as I don't have R/W for system.
So I assume you didn't unlock your bootloader before you tried flashing a custom ROM? Which Recovery do you use?
If you hold volume up while the phone boots up (enter fastboot), does it detect your phone there?
Did you install the proper z3c driver and does your device show up in device manager (maybe as unknown?) ?
This guide might help even if you don't want to root but flash a fresh firmware: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
MyPictures said:
So I assume you didn't unlock your bootloader before you tried flashing a custom ROM? Which Recovery do you use?
If you hold volume up while the phone boots up (enter fastboot), does it detect your phone there?
Did you install the proper z3c driver and does your device show up in device manager (maybe as unknown?) ?
This guide might help even if you don't want to root but flash a fresh firmware: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
Sorry, I should have mentioned this.
Bootloader is unlocked by the Sony website. For recovery i use XZDual, but for some reason I can only acces TWRP.
Fastboot is detectable and all drivers are installed correctly. Normally it wouldn't been a problem, but I also didn't have my system authorized for ADB as I just upgraded to W10.
You could try to flash cyanogenmod over fastboot now and see what happens (hope you backed up your TA partition first). I usually just prepare the flashtool (select image and press flash so it waits for device), then I hold down volume down and plug in the USB cable.
First I used to have some issues because of Windows driver signature enforcing but after disabling that it seemed to be fine.
Ohh and: Does TWRP print a log when you try to mount /system ? It might help to flash a kernel in fastboot then (could extract the cyanogenmod one from the zip [boot.img]), not too sure since I havent used a Sony Frimware for months now.
MyPictures said:
You could try to flash cyanogenmod over fastboot now and see what happens (hope you backed up your TA partition first). I usually just prepare the flashtool (select image and press flash so it waits for device), then I hold down volume down and plug in the USB cable.
First I used to have some issues because of Windows driver signature enforcing but after disabling that it seemed to be fine.
Ohh and: Does TWRP print a log when you try to mount /system ? It might help to flash a kernel in fastboot then (could extract the cyanogenmod one from the zip [boot.img]), not too sure since I havent used a Sony Frimware for months now.
Click to expand...
Click to collapse
I am trying now as I typ this. The only log I get from TWRP is that it can't mount system.
@ edit: Didn't help. Still getting message that system isn't readable/writeable.
Braindamage1989 said:
I am trying now as I typ this. The only log I get from TWRP is that it can't mount system.
@ edit: Didn't help. Still getting message that system isn't readable/writeable.
Click to expand...
Click to collapse
Did you try to go in TWRP and repair/change /system ? Also make sure you dont have the rm -rf option selected instead of properly formatting.

phone bricked

Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.

Seemingly endless string of issues while trying to root

Hey guys, I've decided I'm going to root my Moto X Unlocked Edition. I've been following this guide: http://www.theandroidsoul.com/2014-moto-x-2nd-gen-marshmallow-root-86348/ (as well as many others) and I'm running into issue after issue.
I've managed to unlock my bootloader. I'm on step 8: "fastboot flash boot boot.img" and have tried with so many techniques but keep getting this "mismatched partition size (boot)" error after each attempt. I've tried using .img files from CMod, from the guide that I'm following, etc. I've googled the error with no useful result coming up. I'm at a loss here and really hoping someone is able to help me out. Searching is turning up nothing and I'm about to start tugging at my hair. If anyone has a one click installer that would work, please pass it along!
Thank you all very much!
Edit 4/29/16 13:01 ET: I've switched from trying to use the 'fastboot flash boot' command and started trying to use 'fastboot update <romname.zip >' with various different ROMs. I'm getting this error.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I'm not sure what to do now. I feel like I'm getting reckless in trying an overwhelming amount of solutions to no avail. I'm going to wait, now. I'm starting to think that these phones can't be rooted or flashed with a new ROM.
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Thank you for the help @viper74656!
I'm struggling to even get the TWRP installed. When I try to install TWRP-3.0.0-0-victara.img, I get
cmd: getvar: partition-type:recovery
cmd: getvar:max-download-size
cmd: download:0096c000
cmd: flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
I was having this problem earlier too when I was trying to work around that. I'm going to try an alternate way of installing TWRP.
Really, all I want to do is get CMod. When I rooted my HTC Inspire 4G, it was a cakewalk... I didn't expect all this LOL
viper74656 said:
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Click to expand...
Click to collapse
Yeah, btw, I have an xXT1095
So I managed to get TWRP installed on my XT1095 using the "WinDroid" toolkit I found somewhere on XDA. It seems to push the right fastboot commands, but I had to manually download and select an older TWRP version. Read something about our recovery partition not working with the newer versions. I still got the mismatch error, but when I rebooted into recovery TWRP was there.
I haven't ventured back to try it again after having to wipe and start over...bleh.
Twrp manager (from the playstore) is what I had to use to install recovery. Windroid wouldn't push it for some reason.
Sent from my XT1096 using XDA-Developers mobile app

PRA-LX1 I want to install stock firmware.

I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
I have the same problem but with a different firmware.. now only thing i can do is use dc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
MobileTechArena said:
I have the same problem but with a different firmware. now only thing i can do is usedc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
Click to expand...
Click to collapse
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
barnabaXXX said:
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
Click to expand...
Click to collapse
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Thanks for making it clear. Please tell me if it worked or not. Thanks.
barnabaXXX said:
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
Click to expand...
Click to collapse
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
barnabaXXX said:
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
Click to expand...
Click to collapse
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
barnabaXXX said:
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
Click to expand...
Click to collapse
Unfortunately I can't help you further than what I already posted.
But keep updating in case someone more knowledgeable peeks in.
similar problem....I was fairly good but play store was stuck in pending download....
I did a wipe in TWRP, and ended with a black screen...
I can boot to eRecovery, but it fails.and also to TWRP.
when attached to PC it keeps being seen and unseen as if its stuck in a power on cycle
Any help would be greatly appreciated.
Already Tested
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Hello did you already test ???
Here is the solution for every PRA-LX1: [http : // www . htcmania . com / showthread . php ? t=1326478] (sorry for the spaces, but I don't have enough posts written to post external links )
Unfortunately, it's from a spanish forum. I didn't found any problem to follow this tutorial, but maybe for someone it could be a little difficult.
Anyway, it works!
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Where did you find the C432 firmware? I can't succees to find it
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Iocere said:
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Click to expand...
Click to collapse
Yeah, that's the way! It worked for me too!
juanmemo said:
Yeah, that's the way! It worked for me too!
Click to expand...
Click to collapse
Also i noticed everytime a OTA fails you get the full version offered on next boot. So you should get a full B164 aswell after it failed
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
how can you boot into recovery ? i can only boot into twrp or fastboot & rescue or if i plug the huawei to the pc erecovery ???
---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------
i have an huawei pra-lx1 c530 it used to boot into pra-lx1c530b111 rooted and twrp but now it doens't boot anymore, i'd like to flash to c530b160 but i can't find the firmware images
tiagoggama said:
Hello did you already test ???
Click to expand...
Click to collapse
Thanks men
I CONFIRM IT WORK PERFECTLY
For the second part go to this link for more detail :
https://boycracked.com/2016/03/14/h...-unbrick-firmware-any-huawei-android-devices/

Categories

Resources