Hi guys. Please help someone. Where can I download the factory firmware? Not available in the system since the downgrade AiO R5A. Just by skipping the wifi or mobile election I get after each restart. The recovery work, but one could not install firmware as update.zip. You'll have to do something, or take it in for repair?
kolbaszmen said:
Hi guys. Please help someone. Where can I download the factory firmware? Not available in the system since the downgrade AiO R5A. Just by skipping the wifi or mobile election I get after each restart. The recovery work, but one could not install firmware as update.zip. You'll have to do something, or take it in for repair?
Click to expand...
Click to collapse
See my signature for current list of ota updates and older links.
stifilz said:
See my signature for current list of ota updates and older links.
Click to expand...
Click to collapse
please help me SGPT131E2 / S Sony Xperia S Tablet is installed. Which firmware to do this? Thank you for your help.
.....
I tried a few times but still in the "Verifying update package ..." first trimester getting "installation aborted" message and aborts the installation.
kolbaszmen said:
please help me SGPT131E2 / S Sony Xperia S Tablet is installed. Which firmware to do this? Thank you for your help.
.....
I tried a few times but still in the "Verifying update package ..." first trimester getting "installation aborted" message and aborts the installation.
Click to expand...
Click to collapse
After update fail use adb pull /tmp/recovery.log
Then post it here
stifilz said:
After update fail use adb pull /tmp/recovery.log
Then post it here
Click to expand...
Click to collapse
I'm sorry, but to me that's high. The temp directory is empty, there is no recovery.log so I can not write here
--------
in recovery write - 0123456789abcdef recovery
normal boot - list of attached
---
"/tmp/recovery.log does not exist"
kolbaszmen said:
I'm sorry, but to me that's high. The temp directory is empty, there is no recovery.log so I can not write here
--------
in recovery write - 0123456789abcdef recovery
normal boot - list of attached
---
"/tmp/recovery.log does not exist"
Click to expand...
Click to collapse
In recovery after an update fails wait 1 minute and use adb pull /tmp/recovery.log
/tmp is only there in recovery in normal boot it is /cache/recovery/last_log
BTW normal boot - list of attached means that your driver is not properly installed in normal boot, although it installed in recovery.
I thik yours is Spain model ES? Therefore you should need that update
SGPT131E2/S (in Hungary)
I do not understand, does the recovery mode, the switch-off function, and that
kolbaszmen said:
SGPT131E2/S (in Hungary)
I do not understand, does the recovery mode, the switch-off function, and that
Click to expand...
Click to collapse
Ok then. With the tablet ON and running normal. Use a file explorer to open /cache/recovery/last_log then move that file to your PC. Then rename it to last_log.txt and copy and paste the text here.
stifilz said:
Ok then. With the tablet ON and running normal. Use a file explorer to open /cache/recovery/last_log then move that file to your PC. Then rename it to last_log.txt and copy and paste the text here.
Click to expand...
Click to collapse
The problem is that there is nothing, just SGPT13 of a blank
kolbaszmen said:
The problem is that there is nothing, just SGPT13 of a blank
Click to expand...
Click to collapse
Okay. We will try this another way. Can you copy the text from the /vendor/vendor.prop file
stifilz said:
Okay. We will try this another way. Can you copy the text from the /vendor/vendor.prop file
Click to expand...
Click to collapse
not allowed to copy anything there
kolbaszmen said:
not allowed to copy anything there
Click to expand...
Click to collapse
Or copy the file (vendor/vendor.prop) to PC then rename to build.txt instead of build.prop
stifilz said:
Or copy the file (vendor/vendor.prop) to PC then rename to build.txt instead of build.prop
Click to expand...
Click to collapse
ok, and now?
------
copied to the SD card, but it failed to update
----
SGPT13
If I click on the property, it is
SGPT13
build TISU0143
sn 00000000000000000000000000000876
::::::::::::::::::::::::::::::::::::::::::::
may be that the Tablet S 3G firmware installed R5a for me is the Xperia Tablet S
The whole story started JB, and with motochopper root and install Flasher R6B with 3G, but there was no network. Here have been trying to somehow bring back if you manage to get a factory upgrade, but since there was no pile of failed JB managed to put together but that did not work properly, as there was only wifi, and the update did not go because, according to the latest software on it. Then I went down to the R5A 4.0.3 3G, but that might have been on the Tablet S, and it is not Xperia.
any suggestions ?
Related
Where can I get stock firmware for the at&t Tablet P? I might have bricked my device after trying to use the flasher
I also need one original rom 3.2.1 r4a pleazzz
Greenarcher707 said:
Where can I get stock firmware for the at&t Tablet P? I might have bricked my device after trying to use the flasher
Click to expand...
Click to collapse
My signature links
stifilz said:
My signature links
Click to expand...
Click to collapse
your links not have 3.2.1 OS Sony TABLET P AT&T(SGPT211US/S),it only have 3.2 hixhix.
wanmap said:
your links not have 3.2.1 OS Sony TABLET P AT&T(SGPT211US/S),it only have 3.2 hixhix.
Click to expand...
Click to collapse
signed-nbx02_001-ota-0045.010.zip is the one you need. Not online that I can find btw
stifilz said:
signed-nbx02_001-ota-0045.010.zip is the one you need. Not online that I can find btw
Click to expand...
Click to collapse
I was looking for and did not see anything (
alo_tongdaiday said:
I was looking for and did not see anything (
Click to expand...
Click to collapse
Will have to hope that someone has it and can upload it.... I have been looking for a long time
Now, we look 1 machines at&t then back full backup to up is not feasible?
to P users - most cases (99%) of bricks can be fixed.
I will prepare guide how to fix P tab after failure flash.
Today or tomorrow I think I will have some time.
Just wait
br
condi
condi said:
to P users - most cases (99%) of bricks can be fixed.
I will prepare guide how to fix P tab after failure flash.
Today or tomorrow I think I will have some time.
Just wait
br
condi
Click to expand...
Click to collapse
I hope you soon have guidelines
my phone
http://forum.xda-developers.com/showthread.php?t=2131779
Hi,
I've got fix for P users who updated from 3.2 fw without hidden (kernel etc.),
and used FLASHER.
Download:
_hack_recovery.zip
custom_prerooted_R1A-nbx02_002.zip
How-To:
1. Put that two files on SD.
2. Run AiO - choose 'Custom ROM and Flashing', and 'Flash signed zip [straight from recovery]'.
3. Be sure to have installed correctly adb driver in recovery mode.
4. Follow AiO instructions and flash fw.
5. After successfull fix, you can switch to R5A - just reflash via FLASHER like before,
now it will work for sure
Post results.
br
condi
cann't update mtp driver for win 7 (
@condi : please guide me how to install the driver, I did refer to the way but failed
condi said:
Hi,
I've got fix for P users who updated from 3.2 fw without hidden (kernel etc.),
and used FLASHER.
Download:
_hack_recovery.zip
custom_prerooted_R1A-nbx02_002.zip
How-To:
1. Put that two files on SD.
2. Run AiO - choose 'Custom ROM and Flashing', and 'Flash signed zip [straight from recovery]'.
3. Be sure to have installed correctly adb driver in recovery mode.
4. Follow AiO instructions and flash fw.
5. After successfull fix, you can switch to R5A - just reflash via FLASHER like before,
now it will work for sure
Post results.
br
condi
Click to expand...
Click to collapse
file download is corrupt,when i extract ,it erro.
wanmap said:
file download is corrupt,when i extract ,it erro.
Click to expand...
Click to collapse
its not supposed to be extracted . .
wanmap said:
file download is corrupt,when i extract ,it erro.
Click to expand...
Click to collapse
You say corrupt.... We know ENCRYPTED
AIO instruction said to enable usb debugged but I can't enable it since my tablet is bricked. I can only go to recovery mode using vol + and power combo. And when I tried to run hack recovery from recovery it gives me "Prohibit update as a result of checking version or base sku". Please help!!
phoangkhoae said:
AIO instruction said to enable usb debugged but I can't enable it since my tablet is bricked. I can only go to recovery mode using vol + and power combo. And when I tried to run hack recovery from recovery it gives me "Prohibit update as a result of checking version or base sku". Please help!!
Click to expand...
Click to collapse
Use _hack_recovery, then wait 1-2min, and copy recovery.log from device via adb,
and post it here. We need to see your SKU/incremental values, and what exactly error you have.
br
condi
condi said:
Use _hack_recovery, then wait 1-2min, and copy recovery.log from device via adb,
and post it here. We need to see your SKU/incremental values, and what exactly error you have.
br
condi
Click to expand...
Click to collapse
cann't update mtp driver for win 7
please guide me how to install the driver, I did refer to the way but failed
ps : my tab orror http://forum.xda-developers.com/showthread.php?t=2131779
How can I fix without the rom ship ( sony tablet p at&t )??
condi said:
Use _hack_recovery, then wait 1-2min, and copy recovery.log from device via adb,
and post it here. We need to see your SKU/incremental values, and what exactly error you have.
br
condi
Click to expand...
Click to collapse
how do I get the recovery.log via adb?
phoangkhoae said:
how do I get the recovery.log via adb?
Click to expand...
Click to collapse
Adb pull /tmp/recovery.log
Okay xda, I'm in a bit of a pickle here. Last night I tried to flash the Siyah kernel, Siyah-s3-v1.9.1.tar using Odin3 v3.09 on my Galaxy S3 which was currently running Android 4.4.2 on Slimkat, with stock everything else. As soon as I tried this I knew it was completely the wrong thing and knew something was going to go wrong. Sure enough, the Siyah splash screen comes on for a couple of seconds, then goes to a black screen and gets stuck there.
At this point all I can do is watch it do a couple of seconds of the splash screen, put it into Download mode, or put it into recovery mode. The first time I tried recovery mode it was the CWM recovery, but I can no longer get this to happen, so I'm stuck with stock recovery. When just plugged in my phone has a red LED, and the battery status screen you get when you start charging a turned off phone comes up.
I read a guide on here about how to fix a failed flashing with Odin (I forget which one), which led me to flashing I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 I believe, or if that's not it the stock Samsung firmware. So that goes down, and now I get stuck in the stock Samsung bootloader.
I've since tried to flash a .zip of Stock samsung firmware and Cyanogenmod 11 with another phone's SD card (which I no longer have access to), to no avail. At least that hasn't made it any worse.
What should I do? Ideally I want to get my phone back without losing any data, but I feel a reset may be the only way. Eventually, I want to be able to use it on Cyanogenmod11 with the Boeffla kernel.
Thanks!
Do you get any error messages in stock recovery?
ArkThompson said:
Do you get any error messages in stock recovery?
Click to expand...
Click to collapse
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Obesidia said:
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Click to expand...
Click to collapse
You're trying to flash custom ROMs in the stock recovery?
ArkThompson said:
You're trying to flash custom ROMs in the stock recovery?
Click to expand...
Click to collapse
Pretty much, yeah, I was trying anything.
What next?
Obesidia said:
Pretty much, yeah, I was trying anything.
What next?
Click to expand...
Click to collapse
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
ArkThompson said:
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
Click to expand...
Click to collapse
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Obesidia said:
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Click to expand...
Click to collapse
Use ADB (USB debugging is enabled by default in custom recoveries).
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
Okay thanks! I'll try that and get back.
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Obesidia said:
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
ArkThompson said:
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
Click to expand...
Click to collapse
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Obesidia said:
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Click to expand...
Click to collapse
I think you probably lost your messages when you flashed a stock ROM with Odin. Your pictures could be ok, check with adb and pull them if they are still there.
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
Hi guys... after an upgrade with firmware finder and hisuite, my honor won't boot up... I have access on e-recovery(useless because i can't download anything), recovery (with only wipe reset/cache) and fastboot... I don't have unlocked bootloader and i never do something like this previous operation... how can i solve and reset the phone?
Xethere said:
Hi guys... after an upgrade with firmware finder and hisuite, my honor won't boot up... I have access on e-recovery(useless because i can't download anything), recovery (with only wipe reset/cache) and fastboot... I don't have unlocked bootloader and i never do something like this previous operation... how can i solve and reset the phone?
Click to expand...
Click to collapse
My friend and I have this problem, I tried everything and I did not succeed. I did not get help, and my phone is still in eRecovery. Please, if you can find the solution, tell me how.
Hope that someone answer this topic... Actually I don't have another phones...
PS: I try wipe/data factory reset and wipe cache partition... but nothing happen...
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
oslo83 said:
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
I've download the package and i installed it into SD card (folder dload etc..) but when i try to installation package (Pow butt + vol up, down) he get the error.
ok so what's do you mean by "after an upgrade with firmware finder and hisuite"?
What was your previous version?
What's the error given? did you use an external sdard wirth dload folder?
oslo83 said:
ok so what's do you mean by "after an upgrade with firmware finder and hisuite"?
What was your previous version?
What's the error given? did you use an external sdard wirth dload folder?
Click to expand...
Click to collapse
So, version before update was b183 Nougat
I format an sdcard on exfat, put the dload folder that you given to me and I try to install while pressing the Shutdown+Vol Up+Vol down... The error is "Software Install failed! - Get Help from emui.com/emotiondownload.php?mod=restore"
Obviously the URL doesn't work.
Have you tried to wipe cache partition in Erecovery ??
Edit : error in dload method , 5% error ??
What error bad packages ?
you were on C432B183 and tried with the C432B130 files?
k1ks said:
Have you tried to wipe cache partition in Erecovery ??
Edit : error in dload method , 5% error ??
What error bad packages ?
Click to expand...
Click to collapse
Yep 5% stuck and after that the error
oslo83 said:
you were on C432B183 and tried with the C432B130 files?
Click to expand...
Click to collapse
Nope the 360a
oslo83 said:
you were on C432B183 and tried with the C432B130 files?
Click to expand...
Click to collapse
Yes need to know original packages installed on it.
And with same packages that update ??
Xethere said:
Nope the 360a
Click to expand...
Click to collapse
????? are you a trolling bot?
k1ks said:
Yes need to know original packages installed on it.
And with same packages that update ??
Click to expand...
Click to collapse
My package was C432B183 and i think i use the C10B360
oslo83 said:
????? are you a trolling bot?
Click to expand...
Click to collapse
No man, please im not here for trolling...
I dont know if it work on it but for know which version with this command adb
adb shell getprop
I think you have crossed two versions
So let's start again.
Check the link i gave you earlier, read its op carefully.
You'll see they are not any B360 files on it...
So when you're telling:
Xethere said:
put the dload folder that you given to me and I try to install while pressing the Shutdown+Vol Up+Vol down...
Click to expand...
Click to collapse
It seems you didn't.
So i'm sorry...
When i was on Android i update my package (b183) with b360.
Now i have the b130... what i need to do?
So you were on C432B183.
You may have tried upgrade to C10B360.
Now your device won't boot into system.
Are the statements are right?
You're telling to have download B130 firmware on the link provided... which one? C10B130 or C432B130?
oslo83 said:
So you were on C432B183.
You may have tried upgrade to C10B360.
Now your device won't boot into system.
Are the statements are right?
You're telling to have download B130 firmware on the link provided... which one? C10B130 or C432B130?
Click to expand...
Click to collapse
Yes, The C432B130
Hello everyone!
I am in the process of rooting this device. I need to do this since I need to test / develop AR Apps. So either I buy a new phone or I root this one and try if it works (and by trying that avoiding buying one). After some driver issues - I solved them by using Linux instead of Windows - I ended up with TWRP. In TWRP - Install I was not able to install anything since I got some permission errors. Now I seem to be unable to even install TWRP by using
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
but the device is still recognized while in fastboot.
When I enter recovery I get a long list of errors. Like:
E: [libfs_mgr] Failed to open '/dev/block/platform/bootdevice/by-name/cache': No such file or directory.
Click to expand...
Click to collapse
or
E: [libfs_mgr] Failed to format /cache:No such file or directory
Click to expand...
Click to collapse
Is there anything left I could try to get a working TWRP with permissions?
Thanks for any hints!
Andreas