Hi there. I did search but could not find a solution to my self inflicted issue. I've never used a Sony device so I messed up. I got the Bootloader unlocked and then got TWRP 2.8.7.0 installed and all was good.
I then decided to flash Omni as I use it on my other devices. I made a nandroid then proceeded to do a reset without data.
So now I can get into TWRP but it will not allow me to input. I also have fastboot and tried flashing a newer TWRP but while it says successful, it never changes the TWRP version.
I do have a US image but without a system, I can't seem to get any of the programs that allow flashing to work.
I was up all night trying to get the tablet working with no luck. Anyone have any ideas on how to fix? Fastboot works fine.
Any help would be greatly appreciated.
I fixed it. EMMA did the trick. Guess I need to read more before flashing anything
Related
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
Welcome everyone,
Last week I got second hand Asus Tf201. I was disappointed with the stock rom that was installed on it and I decided to do something with that. I have unlocked bootloader, unlocked root, installed twrp recovery and finally installed AndroWook rom. Then I made a full system backup with twrp. After all, I made a decision to install KatKiss. I have read that to do this I need newer recovery than I had before so I installed the newest version of twrp. Then the problem appeared. When I wanted to get into the recovery twrp asked me for password I had never set. I've read loads of many topic on many different forums about it but unfortunately I was unable to connect my Tf201 to PC because of the broken USB cabel. I have opened android terminal and changed the version of twrp to another but the problem didn't dissappear. By mistake I got into recovery and pushed the "wipe data" button, I even didn't know that it will erase all my data with OS from the device. Right now I'm stuck on twrp asking me for password, when I tap on cancel and get into the menu, then into "restore" it says that it's unable to mount external storage, on which I have my backup files. I bought a new USB cabel, PC sees it in adb, but actually I don't have the faintest idea what can I do more with it. I have already tried some different unbrick methods but some of them need nvflash installed, which I don't have. Could anyone please help me with my problem?
Jackobtone said:
Welcome everyone,
Last week I got second hand Asus Tf201. I was disappointed with the stock rom that was installed on it and I decided to do something with that. I have unlocked bootloader, unlocked root, installed twrp recovery and finally installed AndroWook rom. Then I made a full system backup with twrp. After all, I made a decision to install KatKiss. I have read that to do this I need newer recovery than I had before so I installed the newest version of twrp. Then the problem appeared. When I wanted to get into the recovery twrp asked me for password I had never set. I've read loads of many topic on many different forums about it but unfortunately I was unable to connect my Tf201 to PC because of the broken USB cabel. I have opened android terminal and changed the version of twrp to another but the problem didn't dissappear. By mistake I got into recovery and pushed the "wipe data" button, I even didn't know that it will erase all my data with OS from the device. Right now I'm stuck on twrp asking me for password, when I tap on cancel and get into the menu, then into "restore" it says that it's unable to mount external storage, on which I have my backup files. I bought a new USB cabel, PC sees it in adb, but actually I don't have the faintest idea what can I do more with it. I have already tried some different unbrick methods but some of them need nvflash installed, which I don't have. Could anyone please help me with my problem?
Click to expand...
Click to collapse
Give this command a try
Code:
adb reboot-bootloader
Does it boot to the bootloader screen ?
Thx Josh
bootloader tf201
lj50036 said:
Give this command a try
Code:
adb reboot-bootloader
Does it boot to the bootloader screen ?
Thx Josh
Click to expand...
Click to collapse
Yes it did!
okey, OS is installed, and what is more it works properly. Many Thanks to You!
Now I have a little problem. I can`t remove twrp recovery. I have installed rom manager and installed cwm recovery, but when i reboot tablet to recovery menu the twrp starts as it did before.. What now?
Update:
I did everything mentioned in this post http://forum.xda-developers.com/showthread.php?t=2459711&highlight=twrp+mount&page=4 and have restored my backup. All works fine now. Thanks again!
Jackobtone said:
Now I have a little problem. I can`t remove twrp recovery. I have installed rom manager and installed cwm recovery, but when i reboot tablet to recovery menu the twrp starts as it did before.. What now?
Update:
I did everything mentioned in this post http://forum.xda-developers.com/showthread.php?t=2459711&highlight=twrp+mount&page=4 and have restored my backup. All works fine now. Thanks again!
Click to expand...
Click to collapse
Great to see you up and running ...... :good:
Can you add 'SOLVED' to the thread tittle ....
Thx Josh
I've searched through the forums, but haven't found an answer, so I'm starting a new thread.
I received a G Watch as a gift last weekend, and it had a problem on the initial configuration. It wasn't able to connect and download any updates, so I manually flashed the updated firmware. Everything is working fine, and I'm on build LDZ22D. I was able to use G Watch Restore Tools V9 to flash system and recovery (and, in fact, boot, although that didn't seem to do anything), which got my watch up to an earlier version.
I then tried LG G Watch Return to Stock LDZ22D to get to my current build. However, I'm notified that there's an update available, but I'm not able to install it. When I try to install it through the regular user interface, it boots to recovery.
I've tried using the stock recovery, but had no luck with getting anything other than the android with the sore tummy appearing. I've used TWRP to try to flash update.zip (the stock downloaded update) and also tried this image.
When I try to apply update.zip through TWRP recovery, it gives me an error.
E: Error executing updater binary in zip '/cache/update.zip'
Package expects build fingerprint of lge/platina/dory:5.1.1/LDZ22D/19259530:user/release-keys or lge/platina/dory:5.1.1/LCA43/2160025:user/release-keys; this device has lge/cm_dory/dory:4.4.2/KVT9L/561735d166:eng/test-keys
It looks like the release keys are set to a nexus 7 build number (I don't understand how that's even possible). Is there a way to rewrite those keys? I understand they're part of the digital signing process, but I'm not sure why they didn't reset when I used the return to stock tool to flash my current image, which is the actual LDZ22D build. I appear to have a key mismatch. I've tried reflashing boot.img, system.img, and recovery.img manually (the ones included in the return to stock download), but they don't seem to work.
I get the same error when I try to flash the update I downloaded through ADB sideload. I'm frustrated, since my watch gives me this error, then after I reboot, it goes ahead and downloads the update.zip again, killing my cell data plan.
I'd love any help or insight into this. Is there a way to turn off the verification of the keys, or write the actual keys associated with my build? I'm new to working with a watch, and I've got limited experience working with phones/tablets through custom recovery. I'm not interested in a custom rom for my watch - I just wanted to get it to run properly on the stock image, and had a whack at getting it set up through developer options instead of letting it error out when I first got it.
Thanks in advance!
Still working on it
Okay, after quite a bit more research, it appears that my recovery.img doesn't match the rest of the build. I've tried the LDZ22D recovery.img, but it doesn't respond to any user input.
I'm now trying the factory image files from this post.
It seems there are a few people having problems getting to LCA43 recently. If you have an unlocked bootloader by now, you can try this method (TWRP restore from my LCA43 system+boot backup).
Hope this helps.
Hello there,
I was having trouble flashing a custom rom on my Oneplus X. I'm not an expert on these things but I've been rooting phones for years (following directions, etc). I'm rooted, unlocked bootloader, etc. From TWRP I tried flashing several roms including Sudamod 6.01, unofficial CM13 and 12.1, and Exodus. Nothing worked. I kept getting like "E: error executing updater binary in zip".
Foolishly, I didn't have my glasses on when I found this page here: https://forums.oneplus.net/threads/e-error-executing-updater-binary-in-zip.387944/ . Users there appeared to have success "updating the firmware", so I attempted to follow suit. Accordingly I downloaded and flashed the following file: https://www.androidfilehost.com/?fid=23991606952604019 linked in the thread. Not seeing well, I didn't realize this was for OPO, not OPX. I admit I didn't quite understand what "updating the firmware" meant in this case--ordinarily I would have thought that meant updating a ROM, but since that was exactly what OP was having trouble doing I assumed it must have been some other BIOS type system I didn't know about (foolish, I know).
After flashing that zip I still couldn't install a ROM. The next thing I tried was to update TWRP. I downloaded an update to 3.0.1 on my PC and transferred it over via USB without rebooting TWRP and updated it. Still couldn't install roms.
The next thing I tried was to do a data wipe. Still didn't work. Finally, I thought I'd try rebooting TWRP (first time I rebooted since upgrading to 3.0.1).
I've been bricked ever since. I still appear to have connectivity with my PC via fastboot but no ADB. When I hold down VOL- and PWR it might give me a little vibration pulse, but the screen doesn't come on. It doesn't appear to be booting no matter what I do. I've tried installing different recoveries (via fastboot), including stock, TWRP version 2.8.7.0 and 3.0.1. Though it reports to finish flashing, when I try fastboot boot <filename.img>, but then it said "cannot load 'recovery'"
So right now I'm just lost. Can something be done?
(deleted)
Did you see this thread? http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
If not, you'll find what you want I think
(deleted)
pedrof1991 said:
That thread is for unbricking hard bricked devices (that mean that you won't even get a boot logo, or recovery, or fastboot, etc.) but OP's device is only softbricked because we can boot into recovery and flash stuff :]
Click to expand...
Click to collapse
Then try flashing last OOS
Nexx_ said:
Then try flashing last OOS
Click to expand...
Click to collapse
You were right, the OP's is hardbricked... I misread the last bit of the tread.:/
The the link you post should be it OP CHECK THE LIST POSTED BT NEXX
try flashing Twrp in fastboot again in fastboot mode iff you can get in to fastboot.
Thanks all. I followed the hard unbricking thread. Worked. Saved me a couple hundred bucks. Learned stuff.
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks