Related
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Thank you sooo much. This brought life back to my tablet!
jmonster141 said:
Thank you sooo much. This brought life back to my tablet!
Click to expand...
Click to collapse
I'm really glad to hear it! I almost thought I had posted this for nothing.
Yea man. I was set on me having a $500 paper weight. You're my tablet's savior. Thanks again
Sent from my myTouch 4g using xda app-developers app
thank you
i wanted to thank you so very much i was at my wits end stayed up for hours trying to fix a simple mistake and you saved the day with this if you where standing here i think i would prob kiss ya cause im that happy that i didn't mess up my only real toy i have
:good: I can't thank you enough, I've been working on mine for a few days now, bad rom download messed it up, then one click fix made things worse, was starting to think hardware issues when nothing was saving or taking, you just saved my tab and made my day than you
Happy to hear it. Have fun with custom roms! I'm on cm10 jellybro, I highly recommend it.
Sent from my Transformer Prime TF201 using xda app-developers app
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Did you download the stock .28 rom and take out the system blob? Have you checked the MD5's to make sure they're downloaded without any corruptions?
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Assuming you have access to adb, put the rom file in your adb folder you have been working from, in windows, right click the rom file, go to properieties, copy the name of the file.
In your adb command box you opened from within your adb folder (pressand hold shift while right clicking select command prompt here) type adb push then right click and paste the name of the rom you copied followed by .zip
This should take about 5 minutes to transfer, go get a coffee or something.
Once done, boot into recovery (twrp)
Under install you should see the rom, install, after the reboot you should be good....
i got stuck in a bootloop trying to unbrick, i can boot into recovery using this but when i try to transfer a rom with adb it gives an error that /sdcard is read-only so i cant put my rom on it. i tried using the stock .28 blob but im still in the same bootloop. not sure what else to
Deleted... whew!
Thanks guys for the help. I'm back up and running
Sent from my Transformer Prime TF201 using Tapatalk 2
Thank you soooo much. I have a working tablet again!
Worked!!
geo.z said:
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Click to expand...
Click to collapse
:good::good: Thank you soooo much..My prime is alive !! very much appreciated!!!
Dead link
The link for the ubuntu for android kernel is dead...
Can someone post it back please ?
When I attempt to flash the blobs through fastboot it gives me FAILED unknown error. Anyone help me please? The recovery flashes fine but the boot image gives me the failed error. When i try to access recovery it gives me unrecoverable bootloader error
im trying to flash main kernel i get error that says fastboot.exe has stopped working. Any help?
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash recovery twrp.blob
sending 'recovery' (7462 KB)...
OKAY [ 2.037s]
writing 'recovery'...
OKAY [ 1.006s]
finished. total time: 3.045s
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash boot prime-sdlinux.blob
error: out of memory
I'm working on rooting my very first android phone for the very first time, and I've run across a snag. I've been following Luckythirteen's guide to rooting found here, but so far I've been unable to flash the TWRP recovery. Here's what I posted in the original thread:
Help! I've followed the steps to the T, but I'm struggling with installing the recovery. I've unlocked my bootloader, downloaded the TWRPrecovery.img, put it in the right folder. As soon as I boot into the bootloader, my phone seems to disconnect from the computer. I still have fastboot usb selected, but my device no longer shows up under adb devices. When I try to >fastboot flash recovery TWRPrecovery.img, I get an error "error: cannot load 'TWRPrecovery.img' : Unknown error"
I've got the international HOX+ and a computer running Win7. Any assistance in the matter would be super appreciated.
I hope I've provided enough information for someone to help me out here. I'm a complete Android beginner so this is all a little overwhelming. Thanks.
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
reaper90 said:
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
Click to expand...
Click to collapse
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
christmas_time said:
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
Click to expand...
Click to collapse
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
reaper90 said:
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
Click to expand...
Click to collapse
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
christmas_time said:
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
Click to expand...
Click to collapse
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
reaper90 said:
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
Click to expand...
Click to collapse
I must admit to my embarrassment that yes, it turns out I was trying to flash the wrong recovery (HOX instead of HOX+) and now I feel like an idiot, but I've finally gotten it to work, and I'm finally rooted! Thanks so much!
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
Hi everyone,
I have a Wileyfox Swift 2 which came up with and update available. So I went ahead and installed the new update.
I hated it.
So I tried to install a ROM of the previous update using TWRP Recovery. Problem was I accidentally wiped the original OS the phone was running one without having the ROM I wanted to install on the phone (It was my first time doing something like this). I had no access to the phone apart from the fastboot and TWRP Recovery Screens. I emailed Wileyfox Tech Support and told them what happened. They sent me several versions of the stock OS (the new one I wanted to get rid of, but I would be glad to get it working at all at this point).
I ended up having to use ADB Sideload to get the ROM on the phone and I'm pretty sure it is installed properly. Problem is: when I boot it up these messages come up:'your device software can't be checked for corruption, please lock your bootloader' and then 'dm verity not started in enforcing mode' for 5 seconds, and then it just gets stuck on the white booting up screen until I turn it off or go into Recovery. I know how to fix the bootloader lock error but that erases all user data on the phone. I really need to sort this out so what should I do?
Would appreciate any help,
Thanks!
By the way I don't really care about any data on the device, everything is backed up elsewhere.
After flashing the rom you can use adb in twrp recovery with the following command: adb reboot "dm-verity enforcing"
This should remove the dm verity message and allow your phone to boot.
Thank You
But do you mean have TWRP Recovery open on the phone and have ADB command window open on the computer and type the command because I've done that and it comes up with 'error: device null not found'.
I'm completely new to this sort of thing so as much detail as possible would be appreciated.
Yes, you have to have twrp open and on your pc the adb windows. First type adb devices to see if windows recognizes your phone. Mine says 50580003 recovery, when I type the command. If you get an error, you'll probably need to install the driver in device manager.
Ok thanks for confirming that for me. The problem is that my phone doesn't even show up as being connected to my computer and I can't access the phone's OS to turn on USB Debugging, so when I type the command 'fastboot devices' nothing comes up. Is there a way to do this from TWRP Recovery?
Hmm.... You could try installing the old cyanogen of and use that to enable usb debugging. Alternatively you could try flashing Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 . I never tried it but it should work also.
BlueSheep274 said:
Ok thanks for confirming that for me. The problem is that my phone doesn't even show up as being connected to my computer and I can't access the phone's OS to turn on USB Debugging, so when I type the command 'fastboot devices' nothing comes up. Is there a way to do this from TWRP Recovery?
Click to expand...
Click to collapse
Reboot your phone to fastboot mode from TWRP (reboot>bootloader) or the wileyfox boot menu then flash this file
(https://drive.google.com/open?id=0B34ZucLt1HQ9YjFRQ0otbmFRc28)
from your computer with fastboot.
It will also overwrite your recovery, system, data and internal storage partitions.
Facing same/similar problem
boa05 said:
Reboot your phone to fastboot mode from TWRP (reboot>bootloader) or the wileyfox boot menu then flash this file...
(link removed to allow first-time post)
from your computer with fastboot.
It will also overwrite your recovery, system, data and internal storage partitions.
Click to expand...
Click to collapse
Unfortunately the download link you provided is no longer available, would you mind reposting please?
I got the link working. Thanks for sharing. Unfortunately, flashing them failed with the following:
"Updater process ended with ERROR: 7"
Googling the error code, I found this: //.lineageosdownloads(dot)com/fix-error-7-lineage-os/ but I'm still just going round in circles trying to get OTA updates, re-flashing, rebooting into dastboot, losing adb connections and on and on....
markusmunch said:
Unfortunately the download link you provided is no longer available, would you mind reposting please?
Click to expand...
Click to collapse
Sorry about it, here is a reuploaded version.
Exact same problem
Having made exactly the same mistake as the OP, I've managed to re-install the old version of CyanogenOS but I can't get updates OTA or get rid of this dm-verity enforcing error on boot up. Any help would be massively appreciated.
markusmunch said:
Having made exactly the same mistake as the OP, I've managed to re-install the old version of CyanogenOS but I can't get updates OTA or get rid of this dm-verity enforcing error on boot up. Any help would be massively appreciated.
Click to expand...
Click to collapse
Just download the nougat ROM from Wileyfox, they will send you a link if you ask them. Then you can flash boot and system (and if you like all other partitions and radios) and it will then be on nougat and working correctly.
Scott
Worked
RedNas74 said:
After flashing the rom you can use adb in twrp recovery with the following command: adb reboot "dm-verity enforcing"
This should remove the dm verity message and allow your phone to boot.
Click to expand...
Click to collapse
I have been living in dm-verity hell for the past 4 hours trying to fix my phone after a bad firmware flash (4.1.3 replacing a bad SuperSU uninstall), even trying various 4.0.2 firmwares and full packages, as well as a full-phone restore to a previous TWRP backup I had from a few days ago.
I have absolutely no idea why none of the other methods at all worked (such as the simple fastboot oem disable_dm_verity then re-enable command), but this one finally did it on 4.1.3 *fingers crossed it stays that way*
**XT2041-4**
hey folks,
i have the gpower/g8power (XT2041-4) and i was able to unlock the bootloader and i have been able to do the fastboot commands but it fails when i do the fastboot system, product, vbmeta commands for the crdroid, lineage and havok. i got into twrp and tried installing the zips for those roms but those failed too.
i got to the android OS start screen but the touchscreen is unresponsive. i have looked through a lot of the threads for this device and can't find anything that works.
any help will be much appreciated because this is my daily driver.
edit: title should be XT2041-4
your best option would be to connect an otg cable, ( best is to make sure you can have a double connection, one for mouse , on connected to the pc) then get into the phone with the non-touchscreen booted rom, connect it to LMSA , and extract the boot.img image that comes with the rom LMSA downloads. you should have a working touchscreen with the version LMSA downloads .
Reason you need a double connection: you need to accept the connection to your pc from the phone
you could also browse to the settings --> about this phone and take a look at the exact ROM that is installed, and find that image on lollinet , then extract and boot the boot.img from that rom.
Hey, I'm having the same problem but I found a workaround.
you can either go in fastboot mode and enter
fastboot set_active b
or go in TWRP and change the active slot to B then proceed to boot up the phone.
In my case, it showed warning saying "cannot boot into system......file maybe corrupted" etc etc, just choose "factory reset" on that screen and your phone should boot into slot B with stock ROM.
That way you can have a functional phone while waiting for the developers to figure out the kernel problem
Cheers
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
Chosimise said:
waiting for the developers to figure out the kernel problem
Cheers
Click to expand...
Click to collapse
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
I had a completely different issue with the exact same model. I made a post here asking if anyone had an easy fix, but my guess is that these are just growing pains. Give it a couple months and the roms will likely be much more stable. One of the reasons I bought this phone in the first place is because it usually gets official Lineage OS support at some point. With time, I'm sure things will work great. If you use Windows, going back to stock everything is pretty dead simple with the Lenovo Rescue and Recovery tool, so you can kind of experiment safely if you back everything up.
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
After some tinkering, I actually figured out my problem. There's a big difference between "fastboot mode" (the one you enter by pressing power and vol-) and "Fastbootd" mode.
I did all my flashing in "fastboot mode" and I got no touch screen afterward.
Then there's another hiccup for me (which is why I didn't go in "fastbootd" mode in the first place): When I type in the command in regular "fastboot mode"
Code:
fastboot reboot fastboot
I got an error message saying "reboot fastboot" is not a valid destination or something down those lines.
The problem being, they only added that option in fastboot version r30, so I had to update my ADB and fastboot environment.
And I ran into yet another problem, no matter what I do, the fastboot command is still run with the older version. I guess I messed up the previous installation and the pathing got messy. I ended up using my work laptop for a clean installation of all drivers and it finally solved my problem. I guess I'm saying you need to clean up previous adb and fastboot drivers before using the new ones, especailly if you installed it systemwise.
Anyways, after I booted into "fastbootd" mode and flashed everything with the latest version of fastboot driver, the phone worked flawlessly.
Hope it helps!
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
uglyaf said:
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
Click to expand...
Click to collapse
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Beetle84 said:
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Click to expand...
Click to collapse
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
uglyaf said:
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
Click to expand...
Click to collapse
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Beetle84 said:
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Click to expand...
Click to collapse
ok thanks i did that and got version 1.4.3 it sees my device but when i did the fastboot reboot fastboot i got
fastboot: usage: unknown reboot target fastboot
and nothing happened. does anyone know what that means?
ok yes indeed im a huge idiot. i finally got into fastbootd because i downloaded ADB version R30. THATS the most recent adb version and that did the trick! now i got the fastbootd recovery screen!
regardless, thank you all SOOOOO much for taking the time to respond. much appreciated.
im so excited to get flashing!
peace and love
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
brucedroid031 said:
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
Click to expand...
Click to collapse
good look thank you