Hello! This thread will likely be my first and last usage of this forum, given how previous questions and answers regarding the capabilities of the LG Q7+ went.
I've been having an incredibly specific issue with a cheap gamepad, and I have doctored up a replacement .kl file to solve my issue. However, despite following guides to get the Android Debug Bridge running and being able to detect the device using the commands, I cannot install the .kl file, since those are read-only Android system folders, and would require some form of root access. It's almost the end of 2019 and LG still hasn't provided any kind of end-user support for things like this... should I give up on trying to get this to work on my LG Q7+? Are there any avenues of attack I haven't looked at that could help me push this .kl file onto my device?
Related
Hello!
I recently bricked my MyPal A626. In the last weeks I tried several things but until now I weren't able to figure out how to fix this thing.
I know that you can flash the ROM via the USBLoader.exe over USB. But I need a .nb0 file for this.
Perhaps there is someone in this board who can help me out with this file?
You should be able to dump the rom with the itsutils over RAPI.
http://wiki.xda-developers.com/index.php?pagename=XdaUtils
It should be something like this:
1) pdocread -t
2) pdocread -l
3) pdocread 0x0 xxxxxx nk.nb0
One of the first commands gives you the length of the ROM.
I can't test it by myself because my device is bricked.
Perhaps it would be enough if somebody with an A626 can execute the first and second commands and post the output here.
It would be very great if somebody can help me!
BTW:
I have got a Backup... But the bootloader doesn't want this. It reads everything from USB but it isn't flashed. And I have absolutely no idea why.
I can upload this file to rapidshare if somebody wants to look at it.
I really hate to ressurect an old thread, but I am having the exact same problem. ASUS tech support has been rather less than helpful. They won't provide a NB0 file to end users, nor any fix tools that would work with the encrypted image or anything like that either. They told me I have to RMA the thing after passing me back and forth and giving me the runaround for about an hour or more even. Only, I STILL haven't gotten a response from the RMA department even... The person I tried to do this update for REALLY needs her PDA back already and I find this whole situation to be quite unacceptable. I only had to attempt to use the update in the first place because they made a screweup that makes the SD card inaccessable without reinserting after pressing the power button... A pretty big screwup IMO considering that good PDA practices really requires one to run as much as possible from the SD card for the sake of wasting less resources in a device that already has all too few resources to begin with... (Then again, MS still hasn't caught on to the fact that minimizing rather than closing programs on a device that has so little memory is rather less than ideal, so I guess there's nothing new in that area.) The funniest thing of all is that I wasn't trying to modify it or anything like that, I just did the update right by the manual needing only to get the SD card fix and it STILL went wrong (especially I find it annoying that the update process did a checksum on the update.img file and reported that the file was actually correct, then it fails AFTER completely flashing and doesn't bother to make any kind of recovery.
If anyone could help me out with a NB0 for this thing, I'd REALLY appreciate it. I just want to get it up and running again so she can use her PDA for getting organized as she has been desperately needing for so long.
BTW, should the OP ever read this, I have noticed that if you send the right things, it WILL try to flash. I once sent the update.dat file in the hopes that it might include information needed to make the flash work (it was my hope that the process was a little smart and that it would, therefore, use the DAT file for information on the flash and then include the needed image.) The device actually did make a flash with this file. Of course, the flash obviously didn't work, but the point is that it can do a flash through this method if you send what it's looking for.
GOOGLE this A696_dump_wm5_eng.rar
No good. All two links Google finds are dead (I see two different posts in two different forums, but actually each link to the same links and these are both dead.) I did see a reference to a "A696_dump_wm6_2_eng.rar" but it too is dead. (One of those two forums was this one, I see, surprisingly enough considering that the first thing I did was run a search as is evidenced by finding an old thread -- but then I must admit that I was searching for A626, not A696...) The next closest I can find through this search is a Russian dump for an A636N. I don't have an A636N and I can't read a word of Russian. That link is still alive, but I'm not even going to try it since even if it were actually compatible with the A626 (and I'm betting it's not) it still would be as good as a brick to me still.
But anyway, is the A696 ROM actually directly compatible with an A626 system?
EDIT: I stand corrected! The link for the 6.2 update on the A696 isn't dead after all. When I tried last night it would just spend a REALLY long time trying to load and eventually either time out or produce a database error. When I tried today though, it did sucessfully download. Looks like it does work. Thank goodness because the PDA's owner really needs a working PDA, and ASUS seems rather less than helpful...
Nazo said:
But anyway, is the A696 ROM actually directly compatible with an A626 system?
EDIT: I stand corrected! The link for the 6.2 update on the A696 isn't dead after all. When I tried last night it would just spend a REALLY long time trying to load and eventually either time out or produce a database error. When I tried today though, it did sucessfully download. Looks like it does work. Thank goodness because the PDA's owner really needs a working PDA, and ASUS seems rather less than helpful...
Click to expand...
Click to collapse
626,686,696 are same series.. aka. asus 6x6 or the cannes. if you go to asus website. there is a single rom for these 3 models.
what's the 6.2 update you are talking about ? anyway.. let me know if you still want the 6x6 wm5 dump file. I can upload it to somewhere..
Well, I went ahead and flashed despite worrying about model compatibility. I figured they were the same basic hardware, but I figured that it was always possible that there could be important differences such as memory latencies or such that could make it incompatible perhaps even to the point of danger. But, it's just the software end of things more than anything else, so I figured that it couldn't brick the PDA any worse than it was already bricked and went ahead. As you say though, I have noticed that you are correct that they do use the same ROM for all three models on the official site anyway, so it works 100%.
As for the 6.2, it's in the link I provided to a topic here on this forum. The only other result you'll find on google is just a site in Russian or whatever where they repeat the exact same links for each of the files so you might just as well use this one. It's hosted on MediaFire which was really screwed up when I posted that it was a dead link, but it seems to have recovered and I was able to download that updated ROM from there. I think that you may have to look on the previous page from the link I gave though.
I must say though, I'm glad to have found that one. I HAD to do the update. You see, it was more than just an update to WM6.2. It also included a lot of bugfixes. The most notable being that the system would no longer recognize the SD card after a suspend for a while (or several suspends -- I never was sure just which was the culprit.) Resetting or ejecting and reinserting fixes it, but she was having troubles with this because she isn't exactly the most technosavvy person I have ever known. The SD card dissapearing bug was a fatal flaw because she must load up things such as books and such via SD card and all of it together adds up to well over what can fit safely in internal memory and the file storage combined (but which easily fit an a 2GB SD card) and I needed that update, so if I had to get the WM5 ROM again I'd have to just update again and again as many times as it took to get past the bricking. This way I needed only load up the ROM once and that was it. ASUS really needs to create a tool that can load the encrypted ROM from a PC like HP has done (I've bricked my h1945 PDA while attempting to update it once before and was able to fix it quite easily just as soon as I figured out how to get into the so called "parrot mode.") and such so we don't have to resort to such means to fix them...
Anyway, now I need to get started on loading up all of the stuff she needs.
I just bricked my A363N - WM5.0->6.0 upgrade failed (SD card read error).
Now I'm trying to make it work again.
Russian WM5.0 doesn't work - stops on the calendar screen.
I wonder if I can try to upload update.dat file from the Asus wwe.rar
with SD card inserted and containing Update.img.
Is the update.dat file in .nb0 format ?
Is the A636 actually the same series? If not that post belongs in an appropriate thread instead. If it is, why are you trying to use the Russian update? Just use the plain English one. Here, it's in this post on this site: http://forum.xda-developers.com/showpost.php?p=1495484&postcount=126 I checked and the link is still alive right now.
Yeah, very cool.
I remembered this post 10 minutes ago.
I will try the 696 firmware... Lets see if we can get this ****ing machine running the moon
Meanwhile i tried several things with the update.img file. The "Encryption" is a simple xoring with 0xd0 ^^
But even if you xor the whole file with this value you still don't have a valid nb0. I tried it many times to cut out the firmware with an hex editor on the obvious places in the file (go and see yourself if interested) but all this didn't work.
edit:
It doesn't seem to work for me... The file gets flashed and the device reboots.
After that it still gets stuck at the blue asus screen but it is recognized by the computer as a RNDIS device.
another edit:
WOAH... I tried it again and now it works.
It seems that the battery was empty because of all the previous tries.
Unsuccesfull rom flash
Hello,
I bricked my 696 asus, trying to do un update from the asus site.
Can you tell me some methods to repair it, using the sd card, because the method with usbloader.exe and nk.nb0 is not working ("USB pipe opening error", I tried on several computer and many usb ports).
Also, how can I transform the nk.nb0 flashing image into a *.dio image (I understand the last one can be used to boot and repair automatically from the SD card, it is real???).
10x a lot
Still not working
any new idea to reflash rom foa a696 ?
Hello to you
any news about how to make rom upgrade foa asus a696 ?
Hi Everyone!
I have been given a Defy MB525 with Froyo installed
Apparently O2 and Motoblur don't like each other 'cos I can't locate the phone or do anything else using "My Motoblur" as Motoblur wants Microsoft Explorer and I have Linux on my computer.
I want to manipulate files and basically get full access to my phone using a nice friendly Linux GUI, but apparently I need to root the bloody thing.
I know this question has been asked before. The thread below is an example.
http://http://forum.xda-developers.com/showthread.php?p=9456771
The thread mentions Z4root as an answer.. It doesn't exist anymore.
It then talks about adb and pushing files into the phone.
In the most part this worked
The bit that didn't was "adb push exploit.bin /data/local/tmp/exploit.bin"
It doesn't exist on the zip file attached..
It did however have "rageagainsthecage-arm5.bin" instead
I changed the name to exploit bin in the vain hope that it might be the one and continued the instructions.
It obviously wasn't the one as :
a) it wouldn't come out of the program and
b) I got the $ sign instead of the # sign, which meant I was not root.
This was confirmed when I did the next step in the instructions and got permission denied.
After a switch off and on again (the phone) I cannot even get get back into the phone using adb. It just comes up "error: device not found" even though Linux is showing it as a directory.
So! What next?
Yours in anticipation
Fitchie
I use this http://forum.xda-developers.com/showthread.php?t=1044765 and work very fine with froyo
You can look at the stickies at the top of the forum before posting, see "Defy all-in-one beginner's guide", understand that it probably refers to you and most likely contains the answers to any beginner questions you'd want to ask, open it, read it in case you're serious or just look for "rooting" word if you're not.
Well, you already missed the first part and posted the thread, but you could still do the rest.
Given that you're running Linux on your PC, I'm a bit puzzled - I'd think that the described above is expected from someone with unorthodox OS that is likely used to searching for various guides.
Using "SuperOneClick" is the best way to do Root on your Defy MB525.
I've done this. .. hope it'll help
http://forum.xda-developers.com/showthread.php?t=1551472
I couldn't post this under the LG Flash Tool Developer Guide where I spotted the a question for a similar problem I was having. The original question was from 'tpoints' on 5 April 2012:
"i couldn't find the "SERVER" folder to launch the "shttp3.exe" file..also after installing shttp3 at c:\, no exe file appeared to launch the program"
I am sure this is a common noob issue in general, but I had a similar one. The server folder was there, but shttp3.exe file was not.
After re-extracting the flashing package .rar a couple of times I noticed MSE removing items as I was doing this. I turned it and other security off, and the file was finally there after re-re-extraction.
I'm sure many are already aware of this. I'm sure this has come up in other threads. Is it in a noob guide someplace? I don't know. But there was no immediate answer to be found to the problem (especially since I wasn't entirely sure what my question was in the first place): modding files sometimes seem to be 'recognized' as harmful by antivirus/ad/malware applications, so these need to have their live protection turned OFF during these procedures.
Hope this helps someone.
Hello XDA!
A quick thanks to those reading/interested and I apologize in advance if this belongs in the development section. I don't have permission to post their yet (perhaps with good reason!). After much searching, I've come to the conclusion there is, as yet, no free method of network unlocking the Galaxy Wonder GT-I8150.
I want to find a method to do this, test it, and then automate the process through a shell script and/or batch file. If it doesn't cost too much, I'll even try and make an app for it. I have two reasons for doing this: I own this model of phone (surprise!) and more importantly, I want to expand my portfolio of little computer projects because I want a job in IT, and I want it now.
So this thread will serve as a knowledge base and brainstorming place. Please -anyone with ideas about how to go about this - let me know!
Here's what I'm trying at the moment: based on a similar method used to unlock the HTC Sensation (and some other models), I'm going through the mmcblk virtual partitions after copying them to a .txt file (filetype is binary, .txt is just so my girl's Mac opens them with a text editor). Using a grep command with a regular expression I'm pulling every single 8 character long string of only digits and exporting the result to another txt file.
I then search the mmcblkXpXX file for these 8 long strings one at a time, trying to read through what I can of the binary file for giveaways like "isim_auth_key" or what not.
I started yesterday so I'm only up to mmcblk0p06.
If you have a network unlocked version of this phone, I might end up needing certain files to compare, but I won't ask unless I think I'm onto something.
Finally, if anyone has found an NV_data.bin, bml5 file (or equivalent) for this model, tell me what it's called! Or where I need to extract it from.
Thanks in advance,
GrayedFox
Info
Here are some links to information about unlocking various models of phones, using slightly different methods, for those interested. None apply directly to the gt-i8150 but I'm trying to tweak them just as a starting point.
http://forum.xda-developers.com/showthread.php?t=828534
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
http://forum.xda-developers.com/showthread.php?t=1693491
http://forum.xda-developers.com/showthread.php?t=1335548
http://forum.xda-developers.com/showthread.php?t=1064978
Here is some information from my mmcblk0p06 file... wrapped in spoilers.
PERSO: Failure to write: %sPerso Command can be handled only on a provisioned session or when Card is not present on slotmits/perso.txt
[first mention of a person.txt file I've found]
EFS file read successfully [this implies there IS an efs file somewhere…]
EFS: Creating ISN file
EFS store sequence number
EFS: ISN file not present
AMSS\products\7x30\core\securemsm\smetest\test_crypto\src\sectestcipher.c
if anyone knows how to access that perso.txt file listed, please post the linux command here!
I'm afraid to say I'm running out of ideas here I've pulled every single mmcblk file on the phone - on stock rom and on cyanogenmod - looking for some sort of reference to a network unlock key but it's just not there. I even got Vodafone to send me my unlock key and have been searching the files for the exact key but it's no where on the phone.
I've even data dumped each of these files too - with an authenticated and nonauthenticated sim (network unlocked and network locked) sim and searched using a hex editor. I will have to move on to another project soon, but perhaps this will serve as an informing post for some: let it be known, there are absolutely NO references to an unencrypted network unlock key for this model of phone on stock rom.
Not in any of the mmcblkXpXX files (where most unlock keys are found for other phones) - and I've searched hard.
if anyone has further suggestions I'll remain subbed to this thread. Peace.
Probably they save a lock code, and the unclock is calculated with that lock code and IMEI.
GrayedFox said:
I'm afraid to say I'm running out of ideas here I've pulled every single mmcblk file on the phone - on stock rom and on cyanogenmod - looking for some sort of reference to a network unlock key but it's just not there. I even got Vodafone to send me my unlock key and have been searching the files for the exact key but it's no where on the phone.
I've even data dumped each of these files too - with an authenticated and nonauthenticated sim (network unlocked and network locked) sim and searched using a hex editor. I will have to move on to another project soon, but perhaps this will serve as an informing post for some: let it be known, there are absolutely NO references to an unencrypted network unlock key for this model of phone on stock rom.
Not in any of the mmcblkXpXX files (where most unlock keys are found for other phones) - and I've searched hard.
if anyone has further suggestions I'll remain subbed to this thread. Peace.
Click to expand...
Click to collapse
Hello
while searching for sim unlock i found this method for galaxy s4 mini could you check if it work with our wonder device?
here -> http://forum.xda-developers.com/showthread.php?t=1693491
Regards
A brief history:
Several weeks ago my stock Gingerbread G2's touchscreen started dying. Replacing the touchscreen didn't solve the problem. I was able to continue using it via the keyboard for a little while and, in the meantime, enabled USB Debugging (thank the stars!) while I waited for a replacement phone to arrive. I could still access some functions using the keyboard & thumbpad, although usability was limited due to the inability to back out of an application. Cue lots of battery pulls to restart at the homescreen (a pox on designers who forget one of the fundamental rules of UI: It should always be possible to go back using the current input device!).
Then the screen started a somewhat frazzled HTC image loop during boot, shortly after I started testing ADB & fastboot. Curiously it was still booting the underlying OS, as evidenced by the various chimes telling me I had messages etc, and I could still access it via ADB.
My new phone arrived (a Sony Xperia Z3 Compact. I still would prefer a proper keyboard though. Another pox on designers/manufactures who focus on marketing fads instead of functionality. I don't give a rat's arse if my phone is only 2.48291mm thick and has a screen the size of my 1st laptop. I want something small enough to use in one hand, and that has a hardware keyboard) & happily downloaded my contacts from the Borg....I mean, Google, but not notes or SMS/MMS etc. Leading to today....
I tried Sony's transfer app, but without screen viewing let alone touchscreen ability it wouldn't work (PC version, due Android version on the problem phone wasn't acceptable). Ditto problems with other root exploits. Even trying to use a recovery image on the SD card wouldn't work due to the non-root status. The recovery menu would only accept a stock image. An overriding consideration was that I didn't want to just gain root by what ever method, but I wanted to preserve my notes & sms/mms data, so fastbooting a factory image wasn't satisfactory - as far as I could tell, that would delete everything. After over a week of 0300, 0400, 0530 bed times while reading & trying the methods given in some huuuge number of XDA threads and some other websites, last night I was able to get temp root using the fre3vo exploit! Yay! At one point I had 70 threads open. It was an XDA-dev. thread that gave me the exploit though. Still couldn't do a simple Linux/Unix cp command in ADB shell to save the data but at least the file system was accessible now. Bloody frustrating!
Anyway, a bit more Googling & XDA-ing to find file locations & command formats and tonight I was able to use the ADB pull command to download the whole of the /data directory to my PC. Data saved! Even better, the Linux distro on my PC already has SQlite software to open the files. Even more yay!
I haven't tried to upload to my Xperia Z3C, but I will soon. Meanwhile my data is now available in my PC so phone access isn't as important anymore.
Some thoughts on what I went through:
Manufacturers: You do your customers a vast dis-service by making it so hard to salvage the data.
Service providers: Ditto, due to your insistance on locking down the system on the phones you sell
XDA contributers: I couldn't have done this without you, however.....it would have been easier if you *always* specified what would change/be wiped when you describe your exploit/change/recovery process. I was hesitant to try some methods due to not knowing if my data would be wiped in the process.
And after all that: Who the hell would ever want a phone that wasn't rooted? I don't even install Linux OS on my systems unless root can be gained (Ubuntu & Mint, I'm looking at you! Sudo isn't sufficient...) so I've learnt a lesson on my phone. If only I'd rooted it while it was still fully functional!
Next task? Rooting my Z3C before something goes ' bzzzzt!' on it!