I'm trying to load RV27RC03 image to my A1-810 however Toolkit is advising that it can't write to cache/system.img.gz as 'permission denied'
I've seen a couple of posts having the same problem but can't find how they solved it.
I'm hesitant to randomly try stuff in fear of bricking it.
I've already tried several times running Toolkit as an Administrator.
Any assistance is appreciated.
Thank you
Fixed.
Turned out the predictive text dictionary was causing an error when 'the screen gets taken over'
Was writing Telstra instead of telnet.
Related
Hey everyone, this is my first post here so I'm not entirely sure this is the right place to pose this question. Earlier today, I made the decision to upgrade my Dash to WinMobile 6.1 using the resources here at this forum. The upgrade went nearly flawlessly with the excption that I need to copy the correct keyboard settings cab file still. However, I'm unable to do that because of Activesync.
I had 4.2 installed on my laptop and it never gave me any problems. Unfortunately, the phone displayed a message that I needed to upgrade to 4.5 in order to connect to the PC using Activesync. I downloaded the file from Microsoft's website and tried to run the install program. After clicking the "install" prompt, I get the following error message: "The System Cannot Open the Device or File Specified" Retry or Cancel. Retry gets me no where. I have spent at least 5 hours not trying to find a solution to this problem including a LOT of searching on Google, here, Microsoft's site and other places. NOTHING. I've seen a couple of references to this problem but no definitive solution to the problem.
A few things I have tried: Disable Firewall; uninstall Activesync 4.2 (curiously, after using the Add/Remove Program tool in the Control Paner, there was still an Activesync folder and dozens of files on my hard drive...I manually deleted as many of these as I could); Ran a file called "fixmapi.exe"; and I downloaded the upgrade file from multiple sources, all of which were suggestions I came across during the day.
I'm sooo frustrated because I can't update the keyboard map, I cant synchronize the hundreds of contacts and calendar items I have in Outlook, the phone feels completely useless to me at the moment and I cant believe that this is such an unusual problem (which is my conclusion based on such a complete lack of guidance on this issue).
anything anyone can offer will be HUGELY appreciated!
I get this error after typing "./rageagainstthecage-arm5.bin" into the command prompt. I tried deleting files and starting over, I pretty much tried everything and still get this error. Even if I try starting all over I get this error right from the start. Plz help! Thanks in advance!
I get this. It just started happening. I have no freakin clue how i created this problem but I am sorely annoyed by it.
Anyone got any ideas on how to get rid of the "offline" status of my EVO?
C:\android-sdk-windows>adb devices
List of devices attached
HT05THL04973 offline
mindcrime11 said:
I get this. It just started happening. I have no freakin clue how i created this problem but I am sorely annoyed by it.
Anyone got any ideas on how to get rid of the "offline" status of my EVO?
C:\android-sdk-windows>adb devices
List of devices attached
HT05THL04973 offline
Click to expand...
Click to collapse
I'm also getting this on a Droid X running Android 2.2.1, using the Android SDK Tools Revision 8.
It happened after I ran rageagainstthecage-arm5.bin as part of the "DarkOnion Root for Droid2" procedure for rooting the Droid X. This error is preventing me from completing the procedure. Does anyone know how to fix this error?
EDIT: I was able to correct the error by rebooting my phone (powering down and then powering up). Afterwards, I was able to complete the root procedure, although I'm not sure how to test it.
EDIT2: Just tried running the Wifi Tether app for root users. It says I'm still not rooted. :::sigh:::
If you have hboot 2.10 then you have to do things differently. Namely you need to use Android Terminal Emulator on your phone instead of adb on a command prompt after you push the files over.
It seems that adb gets permanently killed by rage exploit. Check the Hboot 2.02 thread for more details in the dev section.
When I first got this phone, I was having a hard time getting an RUU to image the phone and I loaded a zipped image from one of the threads that automatically loaded when the phone was rebooted. That worked fine even though I figured out my RUU issue later on.
Anyway, when I go into download mode, I get the following warning and I have no idea how to remove it, any ideas???
"Security Warning
If you flash this phone with any ROM that was not officially released by HTC you take the risk of releasing your personal and financial information to unknown sources.
FILE /mnt/media_rw/ext_sd/2PS6IMG.zip
File NOT FOUND"
I still get this message even after flashing a bunch of different images and even doing a factory reset and other wipes. Any help would be greatly appreciated. I searched high and low for an answer, but couldn't find one.
That is just the standard message you get when you unlock your bootloader. Its nothing to worry about. There are a couple of ways to get rid of it -- using a hex editor, and so on, but why bother? You could end up damaging your phone in the process. I've become rather fond of that red text. Looks pretty cool.
what about that file not found crap? why the hell is it looking for something.
It automatically looks for that file as an OTA update. If the file is found it is executed. If not, you get the file not found msg. Again, this is totally normal. Its all good.
ETA: I don't see a way to delete this topic so I'm just updating it. I didn't want to risk waiting another day to not have an answer since I'd already posted other places over the weekend with no response and we need it working for tomorrow morning, so I just went ahead and flashed the factory image from here:
https://developers.google.com/android/images
Everything is in order now! Tips for anyone else doing this, don't skip the step of adding the platform tools to the path environment variables. I did the first time and the flash script wasn't able to find some files because of it and aborted. Everything pushed to the tablet and installed fine after I added the tools folder to system variables.
**********************************************************
This is the only place where I see detailed answers so I registered to ask this.
Status locked/not rooted, just however I bought it when it released plus whatever OTA updates before I stopped using it. Dead in a drawer for maybe two years, I got it powering on again by disconnecting/reconnecting the battery then charging on my PC overnight via USB, but it kept booting to a black screen, no logo, no splash.
I went into recovery mode and did the wipe data/factory reset. I can now get to the welcome setup screen but there are two problems:
1) Errors immediately pop up blocking the screen, making it hard to choose anything because as soon as I hit ok to make an error go away, another pops up. It bounces between "android.process.acore/gapps/media has stopped" with "calendar has stopped/email has stopped" sometimes appearing too but it's mainly the first ones.
2) If I'm fast enough after dismissing an error, I can click next from the language screen to the wifi connection screen. SKIP is greyed out. I can select my wifi but when the password prompt comes up, no keyboard appears after clicking the field to enter one. It's just the blinking cursor.
Keep in mind the errors are still popping up too so I don't know if they're blocking things. I sometimes used a bluetooth keyboard with it, so I grabbed that and tried typing with it just in case and no luck.
Attempts​
I found a fix to try sideloading a factory image via the apply update via adb option in recovery mode, but the google site said it's safer to try sideloading a whole image OTA, so I tried that instead using the zip file there for Nexus 7 2013 wifi (I have 1st Gen but don't see that anywhere so this may be the issue too). After it hit 100% it was aborted for some reason I can't remember now.
But I do remember when I looked up whatever it said, most responses were that sideloading a whole image OTA won't work on devices that haven't been "unlocked" or something.
I found another response to someone with my problem, not having a keyboard after resetting, which said to sideload a keyboard app through adb. I found some gboard apk listed as the version for the Nexus 7 but when I did the adb thing, it aborted because of something to do with e-signature not being verified.
Question​
I can figure out trying to copy over a factory image but since I suspect the main issue now is the Nexus not having wifi access to complete setup then update/install what it needs to stop those errors, I consider that a last resort. So my question for now is for further help on getting a keyboard app or another way so I can type. If I still can't get things working after that, then I'll ask about the factory image.
Thanks!
Good morning, afternoon or evening depending on where you are reading me from. As the title says, it seems that my LG G8 Verizon has become a paperweight since it remains in a recovery loop. My LG G8 has the bootloader unlocked with Firehose and QFIL (https://forum.xda-developers.com/t/...nlock-and-magisk-root-using-firehose.4221793/), I followed the guide (https://forum.xda-developers.com/t/...wos-12-1-for-lg-g8-alphaplus-alphalm.4354847/) months ago to install the Arrow OS rom and everything worked correctly.
Now the matter in question, days before this week most of my accounts were tried to be violated by a hacker, I don't know where I could have caught the ware but it's done already. Today after several hours in front of the laptop I moved all my accounts, changed passwords and started with one and only gmail and outlook account. To finish everything I decided to factory reset my device, everything seemed to be going well until I saw that it started in the recovery and not in the typical screen after a factory reset. I have little experience in flashing custom roms, the previous times I've flashed everything went as it should and I lived without any problem so right now I don't know what to do.
Every time I enter recovery I get a message on the bottom log saying
"E:failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
When I try to make a factory reset from the recovery it says
"Wiping data...
Formatting /data...
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/userdata
Success
Formatting /metadata
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/metadata
Success
Data wipe failed.
E: failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
I really don't know what the problem could be, I already tried to use LGUP to try to go back to my original rom but it stops at 4% and the executable closes. Days before, I deactivated the developer options since it was a requirement of the Malwarebytes app and I know that it is partly my fault for not having activated it again. I can go into download mode by pressing volume up but to the best of my knowledge without debugging and oem unlocked I can't do much. [Edit: Reading the firehose and qfil guide hours later I discovered that the Verizon variant doesn't mention as necessary to turn the oem unlock so maybe a little hope?]
If it helps, I still have the backups of sysnand_00.bin, essential.exefs and some others I made before unlocking the bootloader with firehose and qfil, as well as a zip called "Arrow36backup1647621938922" with a .bak named "launcher_backup_main".
Right now I have no way to upload images of the recovery log that is in the advanced settings of the arrow recovery, I will try to do it later but notice that it is quite long.
I sincerely hope that someone has the slightest idea that it could be happening and I will gladly read it and appreciate your time for giving me a hand.
At the end of it all it wasn't that hard to solve my problem, it was just that I was afraid of messing it up even more.
After rereading the guides that I had followed months ago and also the various comments, I came to the conclusion that LGUP could solve it, only that I had done it wrong before. It was thanks to this thread that I was able to download a better version of the tool (https://forum.xda-developers.com/t/lgup-1-16-3-patched-found-and-works-with-lg-wing.4357211/) and after following the instructions everything was like new on my device.
If someone else is going through the same problem as me, you can write to me and I will help you with what worked for me.