Related
Hi folks,
as my post in the dev section just remained unanswered I try to communicate it here...apparently bin4ry found a way to root many ICS and JB phones, but as I don't own a 4xHD (yet), I would like to know if it works?
http://forum.xda-developers.com/showthread.php?t=1886460
Download latest version and please report back!
Greets
What's wrong with current rooting method for the 4X?
Nothings wrong with the current way,but why just having only 1 way to root the phone? I thought we are here to experiment instead of staying on the same old method the whole time..maybe there are easier ways to root, and if someone says that this method works,then it IS much easier to root the o4x hd.
Well devving and modding can really only go so far with a locked bootloader. And the thing is that, no one is that crazy to try out other things without completely knowing what they're doing or what they're getting into. Yah we want to try other methods, but why risk your $500+ investment with only a 50/50 chance of working/not working, when you can use the other method with 100% chance to work?
coz its a locked bootloader.. u cant brick ur device with that.. coz u can always flash the firmware back
not working here v10f
oktay50000 said:
not working here v10f
Click to expand...
Click to collapse
Thanks for the feedback. At least we can rule out this way of rooting.
This is the only method worked for me Thx !!
This is the only method worked for me Thx !!
EDIT : NVM I GOT IT TO WORK! Thank you for finding this and sharing it .
To get it to work I had unplugged the usb at boot and reconnected right away, seems to have done the trick.
justfortest, can you explain exactly wat you did?
I have a p880g as well and i got mount error...
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
1170 KB/s (1085140 bytes in 0.905s)
Pushing su binary ....
847 KB/s (91980 bytes in 0.106s)
Pushing Superuser app
688 KB/s (996704 bytes in 1.413s)
Making busybox runable ...
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Click to expand...
Click to collapse
Congratulation
Jasonliw93 said:
EDIT : NVM I GOT IT TO WORK! Thank you for finding this and sharing it .
To get it to work I had unplugged the usb at boot and reconnected right away, seems to have done the trick.
justfortest, can you explain exactly wat you did?
I have a p880g as well and i got mount error...
Click to expand...
Click to collapse
Good that it worked for you too Jason
If it works for you, give the author a "thank" click
I can't believe it, so this method works??? This should be made sticky in dev-section then I think...
thanks for you feedback all...
I posted this ages ago -
http://forum.xda-developers.com/showthread.php?p=32471389
Tapatalked Xperia S
Ben36 said:
I posted this ages ago -
http://forum.xda-developers.com/showthread.php?p=32471389
Tapatalked Xperia S
Click to expand...
Click to collapse
Good! A pity that the most O4x users aren't willing to try out new things...
A question: I'm getting permission denied when the script tries to remount with r/w rights...I already tried to disconnect and connect the USB cable during the reboot, but without success...what am I missing?
Reply on the main thread for it, he'll probably write a fix for the phone
Tapatalked Xperia S
TheSSJ said:
Good! A pity that the most O4x users aren't willing to try out new things...
A question: I'm getting permission denied when the script tries to remount with r/w rights...I already tried to disconnect and connect the USB cable during the reboot, but without success...what am I missing?
Click to expand...
Click to collapse
Try to root it with "Root_with_Restore_by_Bin4ry_v15".
Here you can see how it works... Its in portuguese but you'll understand, I think...
(select HD and full screen)
http://www.youtube.com/watch?v=buqfV8nLZFw&feature=g-upl
Didn't work here with brazilian V10C
It does give all the success messages, but doesn't work
Brazilian 10C has some bug that doesn't allow us to root. I have 10C Brazil, profyler has and we have the same error. We (Me, profyler and RuedasLocas) have already tryed 2 methods in this firmware, but all of them were without sucess.
Optimus 4X HD on Wind Canada
Confirmed working on Optimus 4X HD running on WIND Mobile in Canada! The original method did not work for me but this one did! Running version V10c.
Did this work on v10h?im from serbia?Thanx allot
igorstoja83 said:
Did this work on v10h?im from serbia?Thanx allot
Click to expand...
Click to collapse
Didn't worked for me...
If it doesn't work for you too, try the 1st methode:
http://forum.xda-developers.com/showthread.php?t=1818502
hello all ive got myself into a problem with my phone where its only booting into apx mode which at the moment isnt much use, ive found one way that may fix it but i would need someone to extract there APP and LNX and SOS from there phone, if someone is willing to help id be very grateful and can give instructions if needed
thankyou in advance
bish
nvm ive tried this way and not succeeded., if anyone has any ideas please let me know.thanks
does anyone know if nv flash even works with our phones, ive tried a few commands but always the same thing about write failed
Please give some details ,, what did you tried ?? ,, what happend ?? ,, tried reflash the *.KDZ or not ?? ,, Tried to *.DZ by LG flash tool or not ?? .
Of course I'm willing to help , but what do need ??
I'm ready to help any one needs help as well as I can .
Sent From My LG-P880 (O4X) .
By Pressing "THANKS" You Will Help Me .
hi thankyou for replying. basically all im able to do is get into apx mode (nvflash), stupidly i decided to test the thing that i found where the phones with the unlockable bootloaders(23400) could use the chinese kdz v20a and id stumbled across that we could apparently unlock the bootloader. although we had the it saying it was unlocked we had the problem of the system acting otherwise, so i dumbingly thought right if its not actually unlocked i shouldnt be able to remove the bootloader and done the command fastboot erase bootloader and now am stuck in this position
i have backups of of the main partitions( APP and SOS LNX) ect but not sure if useful) and the problem is currently im getting usb write failed with nvflash
i cannot boot into s/w mode or recovery although sometimes i can connect to my pc and it says that a usb composite device cannot start
thankyou for replying i deeply appreciate it
There are at least two ways to get into SW, with or without battery. Did you tried both? Pressing vol+ instead of vol- gives you another mode, you tried? Try them all after re-install the drivers and with LGFlash Tool. Select all ports and see if you have communication.
Sent from my LG-P880 using xda app-developers app
hmm... as I know you full-bricked your device ...
you need to enter download mode by an external action (from PC) using ''usbboot.exe'' to load two files that will turn on your phone into download mode by the command :-
Code:
usbboot <2ndstage> <image>
for example (for LG-P920 (LG Optimus 3D)) :-
Code:
usbboot p920-aboot.2nd p920-u-boot_fastboot.bin
then flash the bootloaders :-
Code:
fastboot flash x-loader x-loader.img
fastboot flash u-boot u-boot.img
this will force the phone into download mode or fastboot . by fastboot flash bootloader and by download mode flash *.DZ system .
but the problem is ...
we don't have these two files (*.2nd & *.bim or *.img) those are nessesery for this process .
I don't have the skill to port/make/compile them ..
Try contact a good Tegra 3 Developer so every CPU family has its own files to boot .
If your device was from OMAP44xx family I could help you because the files are exist , but Tegra 3 ... it's a little new .
Good Luck
there is some u-boot.img and x-loader.img for the p880 here in the forums.i have my normal boot.img ect and even the contents of sys and the dev folder alll backed up also back nandroid backups if any of them would be useful.
thankyou OS_HACKING you have at least give me something that i can look into and a glimmer of hope. if i manage to fix it i need to learn to not meddle with the phone and leave any hacking to the pro's. really gutted as my phone is like my right arm,its with me 24/7 and im usually always on it.. ive had to use my old acer a500 of my daughter for now and its such a big change
@RuedasLocas
yeah mate ive tried both methods, the only thing apart from apx mode is occassionally it says there is a device that cannot start when connected to pc,.thankyou also mate i appreciate help from you both
friartuckme said:
there is some u-boot.img and x-loader.img for the p880 here in the forums.i have my normal boot.img ect and even the contents of sys and the dev folder alll backed up also back nandroid backups if any of them would be useful.
thankyou OS_HACKING you have at least give me something that i can look into and a glimmer of hope. if i manage to fix it i need to learn to not meddle with the phone and leave any hacking to the pro's. really gutted as my phone is like my right arm,its with me 24/7 and im usually always on it.. ive had to use my old acer a500 of my daughter for now and its such a big change
@RuedasLocas
yeah mate ive tried both methods, the only thing apart from apx mode is occassionally it says there is a device that cannot start when connected to pc,.thankyou also mate i appreciate help from you both
Click to expand...
Click to collapse
In mine (V20A), APX doesn't work.
It was already hard to do something in V10x, in V20A the device is not even recognized...
Probably the best change will be using (or try it) LGFlash Tool or Official B2CApp to flash a V10x version, and probably the best
will be a V10A.
Don't forget to check if you're using the correct .dll.
Check if you have the latest drivers:
http://www.4shared.com/file/rPpP2btT/LGUnitedMobileDriver_S4981MAN3.html
http://www.4shared.com/file/ZSMf2x6n/LGUSBModemDriver_Eng_WHQL_Ver_.html7
Goog luck on that. :fingers-crossed:
my pc finds it in apx and installs the drivers , also i can get it too recognise there is a device there for nvflash, i think that i would have to use Wheelie along with nvflash. when ive tried one way to revive my phone with nvflash it stated that the partition couldnt be found. which i guess is because im using the flash.bct and flash.cfg from ICS Bootloader which was extracted a while ago, il need to get them from the jb bootloader
ive got the u-boot.img and x-loader from our phones if they are needed
if not i guess il just have to save money to buy another 4x hd.i cannot see myself loving a phone as much as i like the 4x
thankyou
ive done some more looking around and trying different things, and it seems to even have the chance to get anywhere il need the following extracted from jb, the flash.cfg and the BCT and bootloader.bin. i found an nvflash that didnt give me the unknown device error but it stopped at it couldnt find the partitions mentioned the current partition table i was using(it was from ICS which i think some partitions was named different
friartuckme said:
ive done some more looking around and trying different things, and it seems to even have the chance to get anywhere il need the following extracted from jb, the flash.cfg and the BCT and bootloader.bin. i found an nvflash that didnt give me the unknown device error but it stopped at it couldnt find the partitions mentioned the current partition table i was using(it was from ICS which i think some partitions was named different
Click to expand...
Click to collapse
And how can I extract that?
You tried ADB? Maybe (if it works of course) pushing those unsecure img to unlock the EUR-XXX can bring it to life somehow...
I'm really out of ideas.
I tried APX with several drivers but the only thing I got was a bluescreen and a computer crash... device remains unknown
I think that nvflash for our phone needs some encryption keys (SBK keys) and AFAIK nobody has founded what they are so far. They may be Imei or sn dependant. So I think you can't use nvflash and maybe its better to send device to LG service if you can.
thats what wheelie is for, also id have thought that if the bootloader could be erased from within fastboot wihtout an sbk and, which isnt as low level as nvflash wouldnt it be different,
remember i dont have a bootloader thats signed with an sbk or communicates to the fuse, i know that on the transformer (tegra 3) they had the work around of something to do with wheelie
RuedasLocas said:
And how can I extract that?
You tried ADB? Maybe (if it works of course) pushing those unsecure img to unlock the EUR-XXX can bring it to life somehow...
I'm really out of ideas.
I tried APX with several drivers but the only thing I got was a bluescreen and a computer crash... device remains unknown
Click to expand...
Click to collapse
from what ive read when you fully unlock your bootloader like yours its possible that theyve blocked nvflash, mine was done with the chinese kdz and i had it saying unlocked in fastboot getvar all but it wasnt saying unlock in S/W or within android its self
i think skydev managed to extract the bct ect from the bootloader so il ask him if he still has them or if not then how to extract them
ive managed to get the bootloader.bin. i think i should able to progress when i have the others, adb doesnt also work mate, as the bootloader is at the very beguinning of all processes except nvflash
could you look and see what your odm files say, they are in sys/firmware/fuse/ i think, thankyou
another thing that il look into is someone mentioned about enabling jtag or write access by bridging two points inside the phone, this would obviously be the last thing when all else fails i just need to look in the lg service pdf for the schematics
friartuckme said:
could you look and see what your odm files say, they are in sys/firmware/fuse/ i think, thankyou
another thing that il look into is someone mentioned about enabling jtag or write access by bridging two points inside the phone, this would obviously be the last thing when all else fails i just need to look in the lg service pdf for the schematics
Click to expand...
Click to collapse
I made a copy of my "fuse" folder, forget about "secure_boot_key" cause is always "empty"...
http://www.4shared.com/rar/Y5AU8ZGl/fuse.html
I think that Nvidia have some specific android toolkits but to download them, you need to register, etc... I gave up in the midle of all that but, you can try it.
RuedasLocas said:
I made a copy of my "fuse" folder, forget about "secure_boot_key" cause is always "empty"...
http://www.4shared.com/rar/Y5AU8ZGl/fuse.html
I think that Nvidia have some specific android toolkits but to download them, you need to register, etc... I gave up in the midle of all that but, you can try it.
Click to expand...
Click to collapse
thankyou mate, as i said from when i first come to the lg 4x part of xda forums, your a good bloke, always helping people as much possible
after some more thinking,im struggling to understand why if the bootloader was unlocked could we not use unsecured boot and dexters cwm on the chinese kdz, and why was it saying unlocked in fastboot getvar all but saying locking in android and no unlocked text in S/W mode
what else apart from the bootloader can give the error of boot image signature error, and if the bootloader wasnt unlocked would it be possible to physically delete it, or could it have told whatever was saying it was unlocked that its erased while its actually not been but all link to it erased
i mananged to find my sys folder which i copied to my pc and noticed a difference in our odm_reserved files, which i think is to do with bootloaders
yours is
0x00000000000000000000000000000000000000000000000000000040000000c0
while my odm_reserved was
0x0000000000000000000000000000000000000000000000000000008000000000
not sure exactly what that means but strange
------------ does anyone known of what the load address and entry address is about,
bct file: flash.bct
booloader file: bootloader.bin
load addr 0x300d8106
entry addr 0x300d8106
device id: 0x7130
uid: 0x015d25648c57f00e
RCM version: 0.4
downloading miniloader to target...
Error downloading miniloader
ive just guessed a number for both addresses and obvously wrong
RuedasLocas said:
I made a copy of my "fuse" folder, forget about "secure_boot_key" cause is always "empty"...
http://www.4shared.com/rar/Y5AU8ZGl/fuse.html
I think that Nvidia have some specific android toolkits but to download them, you need to register, etc... I gave up in the midle of all that but, you can try it.
Click to expand...
Click to collapse
yeah mate im a member of the tegra development and have the tool kit. too be honest i havent found much of any use but that could be because ive an untrained eye
friartuckme said:
yeah mate im a member of the tegra development and have the tool kit. too be honest i havent found much of any use but that could be because ive an untrained eye
Click to expand...
Click to collapse
Probably will be enough the correct driver for APX mode on v20a, than with nvflash try to rollback whatever you made.
Sent from my LG-P880 using xda app-developers app
Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
stream1313 said:
Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
Click to expand...
Click to collapse
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
sbdags said:
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
Click to expand...
Click to collapse
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Help needed
stream1313 said:
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Click to expand...
Click to collapse
Hey people... Nobody can help me?
Asus help us
Hello ASUS !!!
You have to HELP us, in order to keep your consumer with you. Other vice people will start to think that your ASUS brand is not a trustful brand anymore. Using such tricks as providing consumer with possibility to open a "Pandora's box" with bootloader unlock, and after you pushing consumer to pay about 300 $ for "motherboard replacing".
Following such kind of policy you will collect some money but definitely you will loose much more.
Sincerely,
Stream1313
PS: I was started to use the "unlock" etc not because I do not have other business t do but because of the serious problem in your DEFAULT STOCK software.
To: Moderator - please do not delete this post, hopefully some ASUS people will read it.
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol
ebildude123 said:
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
Click to expand...
Click to collapse
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
stream1313 said:
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
Click to expand...
Click to collapse
Haha no relationship with Asus. I guarantee it. While I agree unlock tool shouldn't be thrown around, that's not what bricks your device, it's what you flash that does. Personally I think they should use fastboot unlock instead but meh. Yes of course everyone has their own opinions. I respect yours and hope you respect mine as well. Good luck with nvflash but I have doubts your current blob would work even if they made a tool compatible with tf701 tegra4.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol, hope your post do not really had any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Pls, if somebody already experienced, reply me!
Sent from my Xperia Arc S using xda app-developers app
stream1313 said:
lol, hope your post do not really has any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Please, if somebody already experienced, reply me...
Sent from my Xperia Arc S using xda app-developers app
Click to expand...
Click to collapse
anybody here?
stream1313 said:
anybody here?
Click to expand...
Click to collapse
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
sbdags said:
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
Click to expand...
Click to collapse
Hi sbdags,
Thanks for your message, currently I just trying to keep my brick charged, to prevent battery dead.. Will wait till smb from ASUS or from outside will broke the bloody encrypted bootloader, because I do not have possibility to replace he main board ((
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Kashban said:
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Click to expand...
Click to collapse
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
Sorry for being late.
That would be great and yes, I do have the tech skills. What do you want me to test?
Kashban said:
That would be great and yes, I do have the tech skills. What do you want me to test?
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
I also have recently experienced a hard brick on an asus tf700t running KatKiss-7.1_TF700T_026
APX mode & only a TWRP backup
I would also like to try your method to unbrick
Thanks in advance
perpetualxda said:
I also have recently experienced a hard brick on an asus tf700t
Click to expand...
Click to collapse
my solution works only for tf701t not tf700t
mr.bin said:
my solution works only for tf701t not tf700t
Click to expand...
Click to collapse
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
jeneral69 said:
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
If your tab "soft" bricked, then that must help...
Now first of all let me get started. I really will tip over PayPal for a beer for anyone who helps with that, because I've spent the whole day and can't get it to work.
Let me first of all explain my situation. I bought a Kindle 7 yesterday for the family business so that the staff can consult e-mails and access Google while being able to block most apps such as Facebook so they don't mess around (they already do it enough with their personnal phones ) and having read a bit about applications that would allow me to creates multiple users, I realised that I had to be rooted.
Now I had rooted my Galaxy S4 in the past and remembered it being an incredibly easy process so I figured, eh, might aswell give it a go, and that's when all the issues started.
I realised that this needs to be done using Bin4ry's method after installing the ADB drivers (hopefully I got all of this right). But here's where the first issue starts.
When I try to install the ADB drivers, I get the following error code :
So at first I was trying to restart my computer but came to the conclusion that it wasn't the issue. So I tried another method !
I tried installing the ADB directly from the Android SDK, using the link and such, which seemed to work well since I didn't have an error message and now the device was actually asking me to authorize for usage as ADB or whatever the message it says.
So I was optimistic and all, but then came the second problem... I tried running Bin4ry's program but now the issue was something else. When it tried running it, instead of saying device absent, it was now saying the the ADB was out of date (see below). After reading online, I was told thats its because the Android ADB and Bin4ry's one are conflicting, so some people suggested killing them in task manager, which I tried but also said they would come back automatically (which they also did). After that I found an ADBFIX little program, but had no clue where to find the Android ADB....
The reason I'm saying all that and making such a long post is to basically say that I've tried as far as my knowledge goes... I've checked the forums and everything, but most ''killing issues'' applied to HTC devices and not directly Amazon...
Please, I'd love help of any kind ...
Thanks..
Simon
s15.postimg(dot)org/ccwn8hbaz/ADB1.jpg
s14.postimg(dot)org/uf795dlz5/ADB2.png
s24.postimg(dot)org/y4ni1pf05/ADB3.jpg
I was told that since I had under 10 posts, I couldn't post any links, but had taken screenshot of my error messages.. Please replace the (dot) in the links above to hopefully help you understand my issues.
You may just want to use Towelroot and not mess with ADB at all. I've seen reports that it works on the newer hdx, so it might work on our kindles as well.
http://lifehacker.com/towelroot-roots-android-kitkat-devices-in-one-tap-no-p-1592226618
Just tried, unfortunately was told that this device isn't supported ...
What generation Kindle did you buy?
Korgot said:
Let me first of all explain my situation. I bought a Kindle 7 yesterday . . .
Click to expand...
Click to collapse
You know the newest Kindle (4th gen) isn't rootable yet. 2013 models (3rd gen) use Firerooter (KFSOWI modding community on Google+). This forum is for earlier models.
Hi guys, maybe I found a way to unlock the bootloader, I'll test it and report back, stay tuned.
Awesome
Thank God. The device isn't getting android 10 and was hoping that the bootloader could be unlocked and custom roms development could start.
Hopefully you succeed. Cheers
If everything works good, I will post the guide here.
I couldn't try it yet, because I've been at work.
When i will have my pc under my hands I'll keep you updated
devilyuri said:
If everything works good, I will post the guide here.
I couldn't try it yet, because I've been at work.
When i will have my pc under my hands I'll keep you updated
Click to expand...
Click to collapse
If you just didn't invented this method you could give some links to the guides you're using. May be your attempt has been tried already with no success
Anyway, please update this thread with additional information despite the results
Tried some minutes ago and... Nothing, at least I Tried.
I found a program that uses scripts created with pyton
Here is it
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
I saw that he asked for IMEI and can boot phone into rescue mode, but than it gives an error..
I made the script work but it's way too slow. It test around 10 codes peer minute. It's not worth it considering there are few (if none) custom rom for this phone.