[Fastboot] ("FAILED (remote: Command not allowed)") - Xperia Z5 Compact Q&A, Help & Troubleshooting

Hi everybody,
As you see in the title I am having problems with Fastboot. When I am trying to flash (or boot) my recovery.img/boot.img am getting this Error: "FAILED (remote: Command not allowed)"
I have done much research on the internet and tried all of this options (And more):
-Factory resetting phone
-Updating drivers
-Tried on both two Windows 10 computers and one Linux (Kubuntu)
-Different USB ports USB 2.0, 3.0 and 3.1
-Tried with Flashtool
My bootloader is unlocked with the IMEI. And I have installed Drives for the Sony Xperia z5 compact in Fastboot mode(using device manager and google ADB driver)
Exact code I used and got:
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31916 KB)...
OKAY [ 0.882s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.903s
Trying to install TWRP
Thanks, any advice would be appreciated!

Did you disable driver verification in the advanced start up settings?? If not then go into advanced start up!! Recovery, Advanced Startup, Troubleshoot, Advanced Options and option 7 on restart! I'm sure I had this problem a while back on my My Z2! I'm sure this is your problem judging by the log
Press Thanks if this helps

Chronic2k13 said:
Did you disable driver verification in the advanced start up settings?? If not then go into advanced start up!! Recovery, Advanced Startup, Troubleshoot, Advanced Options and option 7 on restart! I'm sure I had this problem a while back on my My Z2! I'm sure this is your problem judging by the log
Press Thanks if this helps
Click to expand...
Click to collapse
Thanks for your answer, I have also tried that but unfortunately it didn't work.

Sony user 16 said:
Thanks for your answer, I have also tried that but unfortunately it didn't work.
Click to expand...
Click to collapse
Sorry I can't help you any further
---------- Post added at 07:06 AM ---------- Previous post was at 07:03 AM ----------
What version of Flashtool are you using?

Chronic2k13 said:
Sorry I can't help you any further
---------- Post added at 07:06 AM ---------- Previous post was at 07:03 AM ----------
What version of Flashtool are you using?
Click to expand...
Click to collapse
I am not sure but I think it's up to date. But shouldn't I be able to use adb fastboot?

[fixed] (almost)
I got it working!!!
by updating flashtool and then re locking, unlocking, re locking (bootloader) and then factory reseted the device. And then unlocking. I got in to twrp and clicked on reboot system.
The only problem now is that when I start my phone I get the Sony Xperia boot screen and nothing happens

Sony user 16 said:
I got it working!!!
by updating flashtool and then re locking, unlocking, re locking (bootloader) and then factory reseted the device. And then unlocking. I got in to twrp and clicked on reboot system.
The only problem now is that when I start my phone I get the Sony Xperia boot screen and nothing happens
Click to expand...
Click to collapse
That is a boot loop. Flash in TWRP a new kernel and ROM that are compatible with each other.
(don`t forget to wipe /system and /data)

I tried to flash a rom and Kernel but now i get three errors in TWRP:
-e:find_file: error opening /sys/class/backlight
-e:unknown command [log]
-e:error executing updater binarin in zip

Related

BOOTLOADER REPAIR - help please

hello guys
I have Xperia P, rooted, bl unlocked ( for my bad ) CWM non bootable
first thing first I know there are similar posts on xda but I find my problem quite unique!
I think that my bootloader partition is corrupted or something,
this is what i get everytime flashing (doesn't matter what kind of kernel):
c:\Program Files\adt-bundle-windows-x86-20130729\sdk\platform-tools>fastboot flash boot kernel.elf
sending 'boot' (12436 KB)...
(bootloader) USB download speed was 21695kB/s
OKAY [ 0.609s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.631s
is that a hardware problem that can be repaired somehow, or I screwed up my phone for good?
funny thing is that I am able to boot my phone and work with it for a few minutes without any problem, but after that a bunch of "stopped working app" pop-ups appear making me unable even to click OK and only hard reset can get me out of that missery. The other thing is, that data on my phone are by some miracle always restored after every reboot. I delete app, reboot, app is back. I take photo, reboot, photo is not there.
Next funny thing- I managed to munt my sd card as mass storage, so I was able to format it with tools like SDformatter, HP USB disk storage format tool. After format I rewriten sd card with bunch of crap (movies and so on) just to make sure, old data are not there anymore. For my excitement, after reboot, old data which was on sd card before formating was back - every single one openable (and crap nowhere). Where does it recover from?
please guys help me, I'm struggling with my phone over one week now :crying:
skynetko said:
hello guys
I have Xperia P, rooted, bl unlocked ( for my bad ) CWM non bootable
first thing first I know there are similar posts on xda but I find my problem quite unique!
I think that my bootloader partition is corrupted or something,
this is what i get everytime flashing (doesn't matter what kind of kernel):
c:\Program Files\adt-bundle-windows-x86-20130729\sdk\platform-tools>fastboot flash boot kernel.elf
sending 'boot' (12436 KB)...
(bootloader) USB download speed was 21695kB/s
OKAY [ 0.609s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.631s
is that a hardware problem that can be repaired somehow, or I screwed up my phone for good?
funny thing is that I am able to boot my phone and work with it for a few minutes without any problem, but after that a bunch of "stopped working app" pop-ups appear making me unable even to click OK and only hard reset can get me out of that missery. The other thing is, that data on my phone are by some miracle always restored after every reboot. I delete app, reboot, app is back. I take photo, reboot, photo is not there.
Next funny thing- I managed to munt my sd card as mass storage, so I was able to format it with tools like SDformatter, HP USB disk storage format tool. After format I rewriten sd card with bunch of crap (movies and so on) just to make sure, old data are not there anymore. For my excitement, after reboot, old data which was on sd card before formating was back - every single one openable (and crap nowhere). Where does it recover from?
please guys help me, I'm struggling with my phone over one week now :crying:
Click to expand...
Click to collapse
try flashing stock ICS rom using flashtool
skyfast said:
try flashing stock ICS rom using flashtool
Click to expand...
Click to collapse
is it possible to flash stock rom using flashtool after unlocking bootloader?
Sent from my ST25i using xda premium
abyisforyou said:
is it possible to flash stock rom using flashtool after unlocking bootloader?
Sent from my ST25i using xda premium
Click to expand...
Click to collapse
Flashtool and pcc are different
Sent from my LT22i using xda premium
abyisforyou said:
is it possible to flash stock rom using flashtool after unlocking bootloader?
Sent from my ST25i using xda premium
Click to expand...
Click to collapse
yeah if it is a ftf file through flashboot mode.
didnt try .img file using fastboot mode though.
skyfast said:
try flashing stock ICS rom using flashtool
Click to expand...
Click to collapse
nope, it's no-go
I was trying to flash it with for about 3 different (ICS, JB) .tft
it always stucks at reading device information
27/005/2013 17:05:21 - INFO - <- This level is successfully initialized
27/005/2013 17:05:21 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
27/005/2013 17:05:21 - INFO - Device connected in flash mode
27/005/2013 17:05:54 - INFO - Selected Sony Xperia P LT22i / 6.1.1.B.1.54 / Sony
27/005/2013 17:05:54 - INFO - Preparing files for flashing
27/006/2013 17:06:32 - INFO - Please connect your device into flashmode.
27/006/2013 17:06:33 - INFO - Opening device for R/W
27/006/2013 17:06:34 - INFO - Reading device information
it will be like that for eternity
skynetko said:
nope, it's no-go
I was trying to flash it with for about 3 different (ICS, JB) .tft
it always stucks at reading device information
27/005/2013 17:05:21 - INFO - <- This level is successfully initialized
27/005/2013 17:05:21 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
27/005/2013 17:05:21 - INFO - Device connected in flash mode
27/005/2013 17:05:54 - INFO - Selected Sony Xperia P LT22i / 6.1.1.B.1.54 / Sony
27/005/2013 17:05:54 - INFO - Preparing files for flashing
27/006/2013 17:06:32 - INFO - Please connect your device into flashmode.
27/006/2013 17:06:33 - INFO - Opening device for R/W
27/006/2013 17:06:34 - INFO - Reading device information
it will be like that for eternity
Click to expand...
Click to collapse
try installing the driver in the flashtool first and also flashboot/fastboot driver as well if done.
flash the ftf file then
hard turn-off your phone by hitting power button and up volume then wait for 3 vibrations...
hold down-volume button before inserting the cable (light green indicator)
-feedbacks
@skynetko
And the phone is still operational?
skyfast said:
try installing the driver in the flashtool first and also flashboot/fastboot driver as well if done.
flash the ftf file then
hard turn-off your phone by hitting power button and up volume then wait for 3 vibrations...
hold down-volume button before inserting the cable (light green indicator)
-feedbacks
Click to expand...
Click to collapse
don't worry I am not that noob
drivers are installed properly, I know how to enter flashmode, fastboot, how to hardreset, but anyway I did what you told...reinstalled drivers, turned off device, holdin power+ volume up button until three continuos vibrations, connected in flashmode with green led indicator...still the same - READING DEVICE INFORMATION
ChikeD said:
@skynetko
And the phone is still operational?
Click to expand...
Click to collapse
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
skynetko said:
don't worry I am not that noob
drivers are installed properly, I know how to enter flashmode, fastboot, how to hardreset, but anyway I did what you told...reinstalled drivers, turned off device, holdin power+ volume up button until three continuos vibrations, connected in flashmode with green led indicator...still the same - READING DEVICE INFORMATION
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
Click to expand...
Click to collapse
i used to have this problem..when i inserted it to USB3.0 port...try changing to 2.0 port..
that should fix the problem..!
regards
kantry123
skynetko said:
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
Click to expand...
Click to collapse
That's why I asked, because I wonder how it's working after earasing boot partition.
Did you flash stock kernel with fastboot (kernel.sin) and had those errors too?
I know there is format command in fastboot but never tried it, though bad blocks are usually at the device level and not sure there anything can be done about it.
kantry123 said:
i used to have this problem..when i inserted it to USB3.0 port...try changing to 2.0 port..
that should fix the problem..!
regards
kantry123
Click to expand...
Click to collapse
not my case...running on 4 years old laptop with 2.0 USB ports only...I made a new try on everyone, no change...
ChikeD said:
That's why I asked, because I wonder how it's working after earasing boot partition.
Did you flash stock kernel with fastboot (kernel.sin) and had those errors too?
I know there is format command in fastboot but never tried it, though bad blocks are usually at the device level and not sure there anything can be done about it.
Click to expand...
Click to collapse
yes, I made attempt with it, the same old story with every kernel - too many bad blocks as in the #1 post
skynetko said:
don't worry I am not that noob
drivers are installed properly, I know how to enter flashmode, fastboot, how to hardreset, but anyway I did what you told...reinstalled drivers, turned off device, holdin power+ volume up button until three continuos vibrations, connected in flashmode with green led indicator...still the same - READING DEVICE INFORMATION
yes it is, check my #1 post in this thread...I described the strange behaviour of my phone. I really don't understand. I can make phone calls,send messages, connect my laptop to its internet through its hotspot- in other words, everything works fine, but just for few minutes...
Click to expand...
Click to collapse
ohh silly me, well i was talking to your earlier response. i thought you cant detect your device on the flashtool, anyway whats your device current Rom and kernel?
skyfast said:
ohh silly me, well i was talking to your earlier response. i thought you cant detect your device on the flashtool, anyway whats your device current Rom and kernel?
Click to expand...
Click to collapse
Flashtool detect my device allright.
Android 4.1.2
FW: 6.2.A.1.100 Stock ROM
Kernel don't know if it has some name, it's the one from the doomlord root method
in phone it says
3.0.8+
[email protected]))
#1 SMP PREEMPT (and unimportant date numbers)
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:12 PM ----------
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
Same with my Xperia T. It's like recovery restore a previous functional image and only works for few minutes.
My T can boot in flash and fastboot mode but halt on flashing
Enviado desde mi Nexus 10 usando Tapatalk 4
... some problem with my kids Xperia Sola. Has someone found a solution???? Please?
jack15381 said:
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:12 PM ----------
Is your Problem solved ?
I Have Your problem exactly in android 4.0.4 ...
Any Solution ?
Click to expand...
Click to collapse
Same problem with my old Xperia Sola... Has someone found a solution?
I did a google search and it seems to be due to bad blocks, and it seems that no one can recover the bad blocks. Thus, Flashtool can't install any firmware because not enough space. If you try with fastboot flash xxx.img it will say just that:
E:\Droid_XperiaSola\fastboot>fastboot flash boot boot.img
sending 'boot' (6148 KB)...
(bootloader) USB download speed was 11202kB/s
OKAY [ 0.582s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.624s
jpmaroco said:
Same problem with my old Xperia Sola... Has someone found a solution?
I did a google search and it seems to be due to bad blocks, and it seems that no one can recover the bad blocks. Thus, Flashtool can't install any firmware because not enough space. If you try with fastboot flash xxx.img it will say just that:
E:\Droid_XperiaSola\fastboot>fastboot flash boot boot.img
sending 'boot' (6148 KB)...
(bootloader) USB download speed was 11202kB/s
OKAY [ 0.582s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 32768 bad blocks encountered
FAILED (remote: Image won't fit, too many bad blocks!)
finished. total time: 0.624s
Click to expand...
Click to collapse
I also have this problem with my Xperia Sola. For two months I can't use my phone anymore due continues booting loop.
If there is anyone who's fixed the same issue, kindly share it with us.. Thank you in advance.

Help Stuck In Boot Loop

Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
sguy156 said:
Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Click to expand...
Click to collapse
Hold vol down as it goes through the next loop, and it will put you in bootloader. From there, you can go to fastboot mode and flash custom recovery. Then adb sideload, adb push a ROM, or load a ROM to the removable SD if you have a card reader you can connect to your computer. Then boot custom recovery and flash the ROM.
sguy156 said:
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
Click to expand...
Click to collapse
It means you are trying to run the RUU for another carrier version. What version do you have (this section is for AT&T) and what RUU are you trying to run?
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
sguy156 said:
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
Click to expand...
Click to collapse
Yes if your S-OFF you can put recovery on your sdcard
http://forum.xda-developers.com/showthread.php?t=2951030
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
I thought you had S-OFF so no you can't load a custom recovery to your sdcard.
---------- Post added at 08:45 AM ---------- Previous post was at 08:36 AM ----------
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
Try the universal drivers from the link below.
http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/#asus
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
sguy156 said:
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Click to expand...
Click to collapse
The PC can see the phone, otherwise you wouldn't get the Model ID error message you indicated in the first post.
So no response if you type the following in command prompt?: fastboot devices
Fastboot and/or adb connectivity issues are rather common.
Another trick you can try, is to uninstall all HTC software (Sync and drivers) from your PC. Then connect the phone. DO NOT accept any prompts to automatically install drivers or Sync. Go to Device Manager, find the device, and pick the option to manually select the drivers, and pick the generic Android MTP device drivers.
Also try different USB ports. IN particular, if the ports are USB 3.0, that is known to cause issues (you may be able to disable the 3.0 drivers).
And if your PC is Win8.1, that is also known to be problematic.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
sguy156 said:
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
Click to expand...
Click to collapse
fastboot erase cache
fastboot flash recovery filename.img
(where filename.img above is replaced with the actual name of the desired recovery file)
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
sguy156 said:
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
Click to expand...
Click to collapse
Fastboot and adb connectivity issues are almost always a problem on the PC's side (ports, Win version, drivers, USB 3.0). Warranty replacement isn't going to help you.
I've given you a few suggestions on addressing the connectivity issues. You haven't indicated whether you have tried them yet, or not.
i tried your sugestions phone is showing up as HTC andriod device and running adb devices doesn't show anything. Not sure what else I can try , I am trying this on a windows 7 PC as windows 8 gave me so many issues .
@sguy156
So your running adb commands from c:\user .
I think your not navigating to adb properly.
I go to where adb and fastboot lives and Shift+right-click so I can open the cmd there
Thats what i did ran it from the location where adb and fastboot are installed same issues .
I hate to ask but do you have usb debugging on wile trying to use adb ?
Please keep an open mind as I'm trying to help ?
---------- Post added at 08:57 AM ---------- Previous post was at 08:30 AM ----------
Try this out if you can't get anything going.order the cable and use a second rooted Android device (no drivers needed at a all)
http://forum.xda-developers.com/att...c-fastboot-t2965030/post57315448#post57315448
USB debugging was on when phone was rooted not sure if its on ss I
Cannt check it now ..
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
sguy156 said:
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
Click to expand...
Click to collapse
I'm not trying to be rude but now that you have fastboot figured out I suggest you put the phone down in another room and start reading on what procedures to take next.
You learn the hard way by not looking in the "General section" where all the information is posted.
Yes you need the bootloader unlocked to push a custom recovery.
Thanks for your help , I found the other steps on other section . Hit post too quickly ..... Learning experience ..
sguy156 said:
Thanks for your help , I found the other steps on other section . Hit post too quickly .....
Click to expand...
Click to collapse
I like shortcuts when I drive ,I just don't advise taking them with the hacking of my devices.
If you use the "Tapatalk app" or the "XDA app" the forum is easier to read through

Vodafone Smart Tab 4G = Alcatel OneTouch POP 8S p353x

Please help - Vodafone gives customers the tablets, but unfortunately it can not make phone calls. Apparently it is consistent with Alcatel mentioned above. I need to get the best official ROM ....
Vodafone Smart Tab 4G ROMs and rooting
stir62 said:
Please help - Vodafone gives customers the tablets, but unfortunately it can not make phone calls. Apparently it is consistent with Alcatel mentioned above. I need to get the best official ROM ....
Click to expand...
Click to collapse
See this:
http://forum.xda-developers.com/general/rooting-roms/vodafone-smart-tab-4g-t2992870/page5
First download and decompress:
SmartTab4G_Recovery_KK_benjaminwan_EN.zip
switch on the smart tab 4g
and in command line in a terminal type:
adb reboot bootloader
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip file which must be copied on the microSD TF card you inserted in the tablet. When the flashing is over, reboot and you're ready to go.
This ROM is pre-rooted. No need to root after.
Good luck.
Here is the full list of ROMs and tools for the Vodafone Smart Tab 4G
This should be unzipped on the PC:
http://www.mediafire.com/download/3mr2zgx27x2arst/SmartTab4G_Recovery_KK_benjaminwan.zip
And the following are all pre-rooted ROMs that are copied on the microSD card we insert in the tablet:
http://www.mediafire.com/download/hdra4r5j48lbl7j/cm-11-20150714-M12-pop8lte.zip
http://www.mediafire.com/download/t29mkypa6poloc4/LS-KK-KTU84Q-2015-07-17-pop8lte.zip
http://www.mediafire.com/download/19e3za4l223rhkk/aokp_pop8lte_kitkat_unofficial_2015-07-17.zip
http://www.mediafire.com/download/1y2o3wywvu7rp4a/CARBON-KK-KTU84Q-20150716-BJW-pop8lte.zip
http://www.mediafire.com/download/57pitjl3yezm33z/FIUI_for_pop8lte_beta_2.28.0.zip
http://www.mediafire.com/download/2r119sl8kpaoc24/IUNI-pop8lte-BetaV3.0.05-201504130001.zip
http://www.mediafire.com/download/lgckk71dpdfvnp5/MIUI6_pop8lte_BJW_KitKat_15.07.26.zip
http://www.mediafire.com/download/c25p2oj01wf8wlo/MK44.4-pop8lte-20150715-KTU84Q-bjw.zip
the following are the Google Apps (GAPPS) packages that are also copied on the microSD card we insert in the tablet:
http://www.mediafire.com/download/aem9d5c6xsmj96p/pa_gapps-modular-nano-4.4.4-20150410-signed.zip
http://www.mediafire.com/download/qmico727b57v2qj/pa_gapps-modular-pico-4.4.4-20150410-signed.zip
Finally, this is the Vodafone stock ROM:
http://www.mediafire.com/download/dgc6655bjf05kje/vodafone-smart-tab4g-stock-full.zip
enjoy!
tried to install stock ROM and cm-11-20150714-M12-pop8lte ROM with Android system recovery but after verifing update package had this message :
failed to verify whole-file signature
signature verification failed
installation aborted
what is the mistake?
my Tab is every time on booting logo Vodafone
vodafone smart tab 4g
cratilo said:
tried to install stock ROM and cm-11-20150714-M12-pop8lte ROM with Android system recovery but after verifing update package had this message :
failed to verify whole-file signature
signature verification failed
installation aborted
what is the mistake?
my Tab is every time on booting logo Vodafone
Click to expand...
Click to collapse
Excuse me, what Android system recovery do you mean? The system recovery menu that the vodafone smart tab 4g has by default?
I didn't mention this recovery method in my writing. Other method I explained. The CWM recovery method as follows:
First download and decompress:
SmartTab4G_Recovery_KK_benjaminwan_EN.zip
switch on the smart tab 4g and connect it via USB to your PC. USB debugging should be turned ON!
and in command line in a terminal type:
adb reboot bootloader
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip file which must be copied on the microSD TF card you inserted in the tablet. When the flashing is over, reboot and you're ready to go.
---------- Post added at 04:59 PM ---------- Previous post was at 04:42 PM ----------
cratilo said:
tried to install stock ROM and cm-11-20150714-M12-pop8lte ROM with Android system recovery but after verifing update package had this message :
failed to verify whole-file signature
signature verification failed
installation aborted
what is the mistake?
my Tab is every time on booting logo Vodafone
Click to expand...
Click to collapse
Now you need to go into the bootloader mode on the tablet.
So,
1. Switch it OFF
2. Press and hold the volume DOWN button together with the power ON button and keep them pressed for 5 seconds until you see on the tablet screen the black screen with the writing "POWERED BY android" in white at the bottom. You are now in bootloader mode.
3. Connect the tablet via USB to your PC
4. Download and decompress: SmartTab4G_Recovery_KK_benjaminwan_EN.zip
5. In command line in a terminal window on your PC type:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip or any other ROM file which must be copied on the microSD TF card you inserted in the tablet. The Google APPS (nano and pico) zip files should also be present on the TF MicroSD. After installing the ROM file from zip on the SD card we need install one of the GAPPS files. I personally installed the pico to have more space on the /system partition.
[/COLOR]
Now you need to go into the bootloader mode on the tablet.
So,
1. Switch it OFF
2. Press and hold the volume DOWN button together with the power ON button and keep them pressed for 5 seconds until you see on the tablet screen the black screen with the writing "POWERED BY android" in white at the bottom. You are now in bootloader mode.
3. Connect the tablet via USB to your PC
4. Download and decompress: SmartTab4G_Recovery_KK_benjaminwan_EN.zip
5. In command line in a terminal window on your PC type:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip or any other ROM file which must be copied on the microSD TF card you inserted in the tablet. The Google APPS (nano and pico) zip files should also be present on the TF MicroSD. After installing the ROM file from zip on the SD card we need install one of the GAPPS files. I personally installed the pico to have more space on the /system partition.[/QUOTE]
I did the whole procedure but has not been successful
this is the detail
c:\vodafone>fastboot -i 0x1bbb oem unlock
...
okay [ 0.004s]
finished. total time: 0.005s
c:\vodafone>fastboot -i 0x1bbb boot cwm.img
downloading 'boot.img'
FAILED (command write failed (unknown error))
finished. total time: 5.005s
Please can you help me?
what is wrong?
Thanks
I did this same procedure that I mentioned with exactly the same files that you downloaded from the mediafire links I gave out and here is the results the tablet returned to the PC terminal. My PC is running Linux by the way but the result should be the same in Windows if the drivers for the tablet are installed correctly:
Latitude-D820# fastboot -i 0x1bbb oem unlock
...
OKAY [ 0.003s]
finished. total time: 0.003s
Latitude-D820# fastboot -i 0x1bbb boot cwm.img
downloading 'boot.img'...
OKAY [ 0.497s]
booting...
OKAY [ 0.090s]
finished. total time: 0.587s
Please make sure you have installed all drivers correctly, that all the files are accessible in their permissions and privileges and that all the files are in the same folder in your PC. What ROM is your smart tab 4 G now running?
cratilo said:
[/COLOR]
I did the whole procedure but has not been successful
this is the detail
c:\vodafone>fastboot -i 0x1bbb oem unlock
...
okay [ 0.004s]
finished. total time: 0.005s
c:\vodafone>fastboot -i 0x1bbb boot cwm.img
downloading 'boot.img'
FAILED (command write failed (unknown error))
finished. total time: 5.005s
Please can you help me?
what is wrong?
Thanks
Click to expand...
Click to collapse
Connect ONLY the Vodafone Smart Tab 4G to your PC and in command line in a terminal window on your PC type:
fastboot oem unlock
fastboot boot cwm.img
all the unzipped files should be in the SAME folder/directory on the PC.
I hope this works for you
---------- Post added at 12:48 PM ---------- Previous post was at 12:38 PM ----------
I also advise you to unplug/remove ALL other USB devices from your PC before booting it up and before trying anything with the tablet.
The only plugged USB device to the PC should be the Vodafone Smart Tab 4G
good luck
solved
I solved with your procedure and the right drivers.
Thanks
cratilo said:
I solved with your procedure and the right drivers.
Thanks
Click to expand...
Click to collapse
good job! I'm glad to have helped you
skaramazoo said:
good job! I'm glad to have helped you
Click to expand...
Click to collapse
cratilo said:
I solved with your procedure and the right drivers.
Thanks
Click to expand...
Click to collapse
And where is the right drivers? My Vodafone Smart Tab 4g P353X is bricked and the only connection that i have is for QDLoader 9008 with QPST. How to establish connection for ADB?
Now in device manager i can get Android Bootloader Interface after installing official POP 8S drivers, but i still can`t get the device to be listed in ADB... and to see the tablet in device manager i have to hold power+vol down. Power+vol up=recovery mode and vol up+vol down= qdloader 9008(download mode for Qualcomm).
m.slavov said:
And where is the right drivers? My Vodafone Smart Tab 4g P353X is bricked and the only connection that i have is for QDLoader 9008 with QPST. How to establish connection for ADB?
Now in device manager i can get Android Bootloader Interface after installing official POP 8S drivers, but i still can`t get the device to be listed in ADB... and to see the tablet in device manager i have to hold power+vol down. Power+vol up=recovery mode and vol up+vol down= qdloader 9008(download mode for Qualcomm).
Click to expand...
Click to collapse
How did your Vodafone Smart Tab 4G get bricked?
I would propose you to consider to connect it to a Linux PC (running Linux Mint for example) and install the latest ADB package on it and then connect your Vodafone Smart Tab 4G.
In Linux you don't need any drivers.
Hi everyone, a little bit off topic but related to this tablet: does this tablet have the vibration and and the brightness sensor?
Thanks
sverza said:
Hi everyone, a little bit off topic but related to this tablet: does this tablet have the vibration and and the brightness sensor?
Thanks
Click to expand...
Click to collapse
This tablet does not support vibration. Automatic brightness, yes.
skaramazoo said:
This tablet does not support vibration. Automatic brightness, yes.
Click to expand...
Click to collapse
Thanks, about display why I can't see any options related to the automatic brightness?
sverza said:
Thanks, about display why I can't see any options related to the automatic brightness?
Click to expand...
Click to collapse
oops no! automatic brightness is not available on this tablet. my mistake. I am using other ROM which has such an option in the picture you sent but it does not work
so, no. auto brightness is not supported here. no such sensor.
skaramazoo said:
oops no! automatic brightness is not available on this tablet. my mistake. I am using other ROM which has such an option in the picture you sent but it does not work
so, no. auto brightness is not supported here. no such sensor.
Click to expand...
Click to collapse
Thanks again.
Are other roms extremely better than the stock Vodafone?
sverza said:
Thanks again.
Are other roms extremely better than the stock Vodafone?
Click to expand...
Click to collapse
you're welcome.
my personal view is that, yes, they are better because they work much faster with less computing overhead for the tablet providing at the same time more features.
one however, need be extra careful when flashing those ROMs to the tablet in order not to cause damage and brick it.
skaramazoo said:
Connect ONLY the Vodafone Smart Tab 4G to your PC and in command line in a terminal window on your PC type:
fastboot oem unlock
fastboot boot cwm.img
all the unzipped files should be in the SAME folder/directory on the PC.
I hope this works for you
---------- Post added at 12:48 PM ---------- Previous post was at 12:38 PM ----------
I also advise you to unplug/remove ALL other USB devices from your PC before booting it up and before trying anything with the tablet.
The only plugged USB device to the PC should be the Vodafone Smart Tab 4G
good luck
Click to expand...
Click to collapse
Hello!
I have an issue with the process.
I have unziped the file SmartTab4G_Recovery_KK_benjaminwan_EN , on my desktop , and then I'm opening the cmd on my pc and then I'm typing the 2 commands :
fastboot oem unlock
fastboot boot cwm.img , but I'm getting a message :
C:\Users\djsbe>fastboot oem unlock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Can you please help me?
Also , what is the purpose of the SmartTab4G_Recovery_KK_benjaminwan_EN ? Do I have to execute a file in order to proceed?
djbeast said:
Hello!
I have an issue with the process.
I have unziped the file SmartTab4G_Recovery_KK_benjaminwan_EN , on my desktop , and then I'm opening the cmd on my pc and then I'm typing the 2 commands :
fastboot oem unlock
fastboot boot cwm.img , but I'm getting a message :
C:\Users\djsbe>fastboot oem unlock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Can you please help me?
Also , what is the purpose of the SmartTab4G_Recovery_KK_benjaminwan_EN ? Do I have to execute a file in order to proceed?
Click to expand...
Click to collapse
Inside the folder of the unzipped SmartTab4G_Recovery_KK_benjaminwan_EN file there are all the commands necessary. fastboot, adb... see the attached png file.

[SOLVED] Xposed bricked my Huawei Mate 10, please help fixing it

Greetings…
W̶i̶l̶l̶ ̶d̶o̶n̶a̶t̶e̶ ̶2̶0̶ ̶U̶S̶D̶ ̶t̶o̶ ̶w̶h̶o̶e̶v̶e̶r̶ ̶c̶a̶n̶ ̶f̶i̶x̶ ̶m̶y̶ ̶p̶h̶o̶n̶e̶ Fixed and contacted both Bordo_Bereli51 and Ante0.
My Huawei Mate 10 got in a bootloop after installing Xposed Framework
It was on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Leaving the device to boot normally: HUAWEI logo then reboots.
Vol up+power: eRecovery mode … doesn’t work (wiped data and cache .. tried to download firmware through wifi .. nothing works). ... then tried this method it worked while downloading the firmware .. but after verifying the firmware then installing it when it gets from 0% to 1% it fails and a red exclamation mark appears. :crying:
Vol down + power: fastboot: always get: FAILED (remote: Command not allowed) ). even though the bootloader is supposed to be unlocked. :crying:
Vol up and down: download mode .. on USB: stuck at 5% … without USB connection to computer: nothing happens (a red exclamation mark appears).
The device has an SD card slot: I tried placing the UPDATE.APP in dload folder and pressed both volume buttons but nothing appeared .. did I do something incorrectly?
Here are more info:
product-model: ALP-L29
vendorcountry: hw/meafnaf
build-number: System 8.0.0.38(0310)
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ALP-L29 8.0.0.128(C185)
Please help.
thanks in advance
====================
FIXED: Thanks to Bordo_Bereli51 who wrote this post and thanks for Ante0 for recommending DC Pheonix and for taking a lot of his time explaining a lot of things to me privately. contacted both as promised.
How I fixed it (credits to Bordo_Bereli51 for the guide .. I only modified it a bit and added some info from my experience):
1- I purchased a 19 euro -3 days pass for DC Pheonix.
2- Download Firmware Finder and click the "Common Base" tab, then download a FullOTA-MF firmware (all 3 files) which is approved for installation ( I copied the "changelog" link and pasted it in the 6th icon at the top "Firmware Checker" and it returned "Firmware approved for install" I' was not able to repack other non approved firmwares).
3- extract UPDATE.APP from update.zip
4- run DC Phoenix program .. tap the "Standard" button in Update mode .. select "update" and choose the UPDATE.APP you just extracted.
5- let it flash everything successfully then redo step 4 again.
6- Here's the trick before it flashes anything ... as soon as you see "utilizing backdoor" (or something like that) open Task Manager and force close DC Phoenix (it has to be BEFORE flashing anything, otherwise you might get errors like:
"error: exec '/system/bin/sh' failed: No such file or directory"
and AFTER utilizing backdoor (so you can use fastboot commands)
7-Download HWOTA8_Mate10 , place the 3 files you downloaded in step 2 in the "repack" folder, and rename "update_data_full_public.zip" to "update_data_public.zip" and "update_full_*ALP-L29*_hw_*meafnaf*.zip" to "update_all_hw.zip". Then run "repack.bat" and wait for it to finish.
8- run "ota.bat" in "ota" folder.
9- When it flashes the recovery_ramdisk and kernel plug your usb cable out and Reboot to recovery by pressing volume up + power button
10- When the phone is in recovery now ADB works (in case you need to do things manually).
11- When this process also finishes, the command center will tell you to press enter, so it boots to erecovery, which will flash the files.
12- Now your phone is unbricked after the flash.
Do not forget to do factory reset by pressing again at boot: (power + volume up) and selecting (factory reset).
After boot allow (OEM Unlock) under (developer settings) or otherwise the FRP will still be locked but the phone will work.
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
I have the same problem.
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
No, I don’t have TWRP.
hero3210 said:
No, I don’t have TWRP.
Click to expand...
Click to collapse
What does fastboot mode say, unlocked on both phone and frp?
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
yes both are unlocked
Dolev234786 said:
yes both are unlocked
Click to expand...
Click to collapse
Post input & output when you try to flash using fastboot
ante0 said:
Post input & output when you try to flash using fastboot
Click to expand...
Click to collapse
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
hero3210 said:
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
Click to expand...
Click to collapse
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
ante0 said:
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
Click to expand...
Click to collapse
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
hero3210 said:
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
Click to expand...
Click to collapse
Dc phoenix is what you'll need, Mate 10 is not supported in DC Unlocker. (Though DC Unlocker made DC Phoenix)
You'd just want it to flash stock anyway.
And it's cheaper than FunkyHuawei... FH "only" cost 1 credit to flash, but minimum to buy is 5 credits which is $41.
FH is easier though as you'd only need to setup DNS, but it's up to you
HCU/DC Phoenix pass for 3 days is €19, and then you have unlimited usage.
If you need further help you can find me at the telegram group https://t.me/HuaweiMate
as it's easier to do it live than through messages.
There is a "DC Phoenix repair tutorial" if you google it, use Method 1. Basically you just download the firmware update zip you're on now (and hw data zip) from http://pro-teammt.ru/firmware-database/ then extract update.app from it and select it in Phoenix, then extract update.app from hw data zip and select it as customization.
Alternatively you can downgrade to factory build using images from DC Phoenix (the build your phone came with) then update from there when you have a booting phone.
Thank you sooo much man. I really appreciate your help.
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
tokoam said:
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
Click to expand...
Click to collapse
yeah the bootloop was fixed in beta4 (original comment by dev) which wasn't officially released to the channel when I installed it, so I didn't know about it until I got the bootloop.
Anyways, I just managed to fix my issue. I'll post about it now.
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
what would happens if it says unlock on frp? i cant load twrp i have flashed many times but i does not take it.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
Spamming every thread won't help you fix your issue.
Pretoriano80 said:
Spamming every thread won't help you fix your issue.
Click to expand...
Click to collapse
I apologize. I panicked since I don't know what to do. I will continue on the thread which I received a response.

Xperia Tablet Z - cannot get into recovery

Hi there! My old Sony Xperia Tablet Z is running Resurrection ROM (Android 8), I use the tablet as a travelling companion. I also have TWRP as recovery.
Today I flashed the latest version of TWRP via the TWRP app, tried rebooting into it using a "quickboot" app (the tablet is rooted) but I ended up on a black screen. I can reset and Android runs no problem.
I then tried flashing TWRP via USB. I type
Code:
adb reboot bootloader
- it goes on a black screen and the status light is solid blue. I then run
Code:
fastboot flash recovery twrp.img
- the outcome is
Code:
sending 'recovery' (11796 KB)...
OKAY [ 0.379s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
Then I tried
Code:
fastboot boot twrp.img
- and I get
Code:
downloading 'boot.img'...
OKAY [ 0.376s]
booting...
OKAY [ 0.032s]
finished. total time: 0.411s
but nothing happens.
Someone suggested to use
Code:
fastboot flash recovery_ramdisk twrp.img
instead (as I am on Oreo) but same error
I am stuck. Any help please? Thank you!
If bootloader is not working Use QPST Flash Tool to reflash everything back to stock.
Thanks. Too bad I don't have the original ROM backup anymore. I will try to download one, I hope all works well.
Can you just refresh me: when into "bootloader" I am supposed to see the bootloader menu on screen?
Edit: it seems that I am unable to install the Qualcomm drivers - Windows 10 reverts to generic drivers or ADB drivers. The drivers I downloaded don't seem to work with Windows 10?
any help on this please? Thank you!
Sorry for insisting - any help please? Can you point me to the right direction?
edit: I've done some homework and here is where I am.
Following some threads I tried flashing the stock ROM using flashtool. I used both the latest version and the "Emma" version from Sony.
I can connect to the tablet but I receive a the bundle does not match the connected device as - I reckon - the device is seen as an unknown device. The same with the Emma version, unknown device and as such, a No matching services as a reply.
Edit2: I found the solution for the above, I had to use the previous version of Flashtool. I flashed a stock ROM. Now it does not boot anymore. I have the SONY static logo and then a black screen. I tried again and also another version for my device but no luck.
Please help!
I am a bit lost here. Any help is appreciated. BTW, I can boot up the tablet perfectly fine and it works ok.
I'll just complete my very lonely thread for future references.
The issue was that I needed an older stock ROM as I was coming from Android 8 - a known issue apparently. I found a very old ROM (10.1 "store front"), that worked ok. From that one, I can do whatever I want. I ended up installing LineageOS which I find much faster than Resurrection.

Categories

Resources