Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Thank you! I'll update my guides now you made some folks very happy today.
Sent from my VS980 4G using Tapatalk 4
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
WACOMalt said:
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
Click to expand...
Click to collapse
I am too LOL Thanks for all your help
I had nothing to do with it, all thanks go to thecubed/IOMonster
Sent from my VS980 4G using Tapatalk 4
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
jspradling7 said:
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
Click to expand...
Click to collapse
Yeah that's what I did yesterday as well used my s4 glad I didn't sell it yet
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
I could swear I said just nuke the FOTA partition sometime yesterday as usual awesome job.
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
Thank you!! Where do I send the beer money?
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
Click to expand...
Click to collapse
Nevermind I found it, not used terminal before in recovery, phone back up and running
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
I was upset yesterday worrying about you guys. I am happy to see you happy. Thanks much OP for the fix.
I am rooted and installed TWRP recovery but reverted back to the stock recovery before accepting the VZW OTA update. I'm now stuck in a boot loop and I can't get ADB to recognize my device when plugged in via USB. When I plug in my phone it shows the following:
Fastboot mode started
udc_start()
-reset-
-portcharge-
-reset-
-portcharge-
fastboot: processing comands
Any idea why this is happening and how I can get my phone to boot normally?
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Nevermind I found it, not used terminal before in recovery, phone back up and running
Click to expand...
Click to collapse
I too get the file folder. How do i get the terminal command in TWRP?
synplex said:
I too get the file folder. How do i get the terminal command in TWRP?
Click to expand...
Click to collapse
When you see the file folder just ignore that and hit "select "on the bottom right and that will bring it up. Just type the command from there
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
synplex said:
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
Click to expand...
Click to collapse
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Walter21026 said:
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Click to expand...
Click to collapse
Yea, let's just wait for a ROM worth flashing and "F OTA"
How can we get the OTA if we have TWRP installed?
Can we falsh stock recovery and then accept the Update?
If so can someone please post the Stock Recovery IMG?
My phone is at the LG screen and the notification light is blinking but thats it. How can I adb anything or get into twrp?
Related
I don't know what I did but after install the CWM successfully using PrimeTime 4.5, I couldn't get back into the system, but instead it keep boot back into Recovery mode after every single reboot. I have tried everything within my knowledge include: install the original zip file extracted from US_epaduser9_4_2_14UpdateLauncher.zip using recovery mod, and it stated successfully, but yeah still in a recovery loop; then I tried to install the Virtuous Prime Beta 1 through the CWM, it was also successfully but, guess what, still in the loop again, so I hope if anyone out there has this problem or know the solution, please help me, I am really appreciated... (I can get in to use adb in recovery mode also)...
SMH. Try this
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
I just knew several people were gonna brick device today once unlock tool came out. Already there has been alot..lol
@demandaring: what exactly should I do? download the file, rename it, then put to removable sdcard, then boot using power+ volume down?
I don't think I cant do it because it's will lead into CWM...
shinichikey said:
@demandaring: what exactly should I do? download the file, rename it, then put to removable sdcard, then boot using power+ volume down?
I don't think I cant do it because it's will lead into CWM...
Click to expand...
Click to collapse
If what I linked doesn't work, try looking in developement section in unlock bootloader thread. Someone else had something similar happen, his name Doktaplex. Post in that thread n they can help you. Or send him a pm to ask the method that helped him recover. He knows what to do. Check the unlock threads in general and especially developement section.
demandarin said:
If what I linked doesn't work, try looking in developement section in unlock bootloader thread. Someone else had something similar happen, his name Doktaplex. Post in that thread n they can help you. Or send him a pm to ask the method that helped him recover. He knows what to do. Check the unlock threads in general and especially developement section.
Click to expand...
Click to collapse
thanks, i stalked all the posts by Doktaplex and finally was able to boot out of the cwm...
http://forum.xda-developers.com/showpost.php?p=22850227&postcount=41
theprateik said:
thanks, i stalked all the posts by Doktaplex and finally was able to boot out of the cwm...
http://forum.xda-developers.com/showpost.php?p=22850227&postcount=41
Click to expand...
Click to collapse
Glad to hear the good news. Other guy in other thread might need your help applying this fix. He not sure how to implement it.
If someone who had success with this solution:
kmdm: right, in CWM recovery: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius
and knows how to execute it in CWM, please explain. I'm in the CWM menu on my prime, but I have no idea as to how to implement this solution. If someone could explain this to someone new like me step by step via navigating through screens on CWM, it would be appreciated.
richteratmosphere said:
If someone who had success with this solution:
kmdm: right, in CWM recovery: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius
and knows how to execute it in CWM, please explain. I'm in the CWM menu on my prime, but I have no idea as to how to implement this solution. If someone could explain this to someone new like me step by step via navigating through screens on CWM, it would be appreciated.
Click to expand...
Click to collapse
well, considering you have all the required drivers installed and u know general ideas (like i do) in ADB, then, type in followings in commands (hit ENTER after each line)
adb shell & su
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and then reboot.
and remember u r in cwm while doing this.....
if you still can't get it going, pm me and hopefully we can solve it....
I think commands are pushed with adb from a computer. You'll have first to install and configure adb (must be a thread on this in Prime General section), and then connect your prime to your computer, open cmd, and type: adb shell [enter] then su [enter] the commands from previous posts.
Edit: not fast enough.....
I installed android sdk appropriately to be able to use adb as far as I know. I rebooted the PC. Now I see a device "Full Android On Emulator" under other devices. Is this my prime? When I try the adb commands as suggested, I'm getting error device not found messages.
How do I get adb / my pc to recognize my prime? Since the firmware update messed everything up, my prime is no longer recognized by my pc. Thanks for anyone who is able to walk me through this.
You must have Adb drivers for prime, links must be in the thread about Adb (sticky in general section), and if you run windows 7 try to run cmd as administrator.
Test your connection by typing 'adb devices' first.
you need to download the driver package and install it, and then you can use adb
http://forum.xda-developers.com/showthread.php?t=1426502
i am manage to fix the recovery loop, i can see the logo from the Vicious rom, but when it booted into the OS, I got this message: Encryption Unsuccessful, and the only option there is to reset the tablet... and when i pressed that button, here you go, back to the recovery loop... can someone help me with this?
shinichikey said:
i am manage to fix the recovery loop, i can see the logo from the Vicious rom, but when it booted into the OS, I got this message: Encryption Unsuccessful, and the only option there is to reset the tablet... and when i pressed that button, here you go, back to the recovery loop... can someone help me with this?
Click to expand...
Click to collapse
I'd say do a complete data wipe from recovery. Then try flashing the rom again. Once it works and boots up into OS, give it like 5-10 mins to get settled. Then everything should be fast n smooth.
i did a complete data wipe and everything but same problem still, sigh.... I wonder what i am doing wrong....
Thank goodness. Came home from work today and was able to install the drivers and use the adb commands with success. Rebooted, and my prime was back to rooted .14 Asus firmware. I did a CWM backup of the now functional ROM, did a batch Titanium Backup job, flashed the current version of Virtuous Prime, restored some app data with Titanium Backup, and everything appears to be running fine now. Thanks to everyone who helped despite my critical blunder. Man, last night was a major bummer. Didn't get much sleep. Really glad its all been resolved.
We need to get a sticky going with these directions on how to get semi-bricked TP out of this predicament. Someone please do it soon. Otherwise there is gonna be a FLOOD of threads asking/stating the same things.
Sent from my Transformer Prime TF201 using xda premium
how did you do it, i still got stuck?
Ok... I dont consider myself a competely noob but I am screwed on this one...
So I had Virtuous Prime installed on my Prime and since it was getting slow I decided to do a factory reset (first mistake)
I didnt have a backup of my current settings (second mistake)
So after restore, I got surprised when my Prime rebooted on clockwork...when I rebooted back to recovery again.
So I started googling it and at the same time, I put the virtuous rom in a sd and tryed to flash on clockwork... but, even more surprised, that version of recovery wouldnt read my SD... I just have an option to install zip from sdcard and that will open my internal (clockworkmod "touch" 5.8.1.8)
So after googling all I could, I am now asking for the help of the forum.
In short: Apparently I have no rom installed, clockworkmod wont read my sd for the virtuous rom, and i dont have the rom on the internal.
How can I get out of recovery now?
Solutions I thought about but couldnt find any resort:
-push the rom to internal? how?
-flash any other rom with odin? which?
-flash a clockworkmod (via odin) that would read my sd? how?
Thanks guys
A factory reset would not remove you ROM. I had same issue whit EOS ROM after I updated GAPPs. Prime would always boot into Recovery. Run the following command from your PC then reboot and any new recovery should be flashed by the bootloader and then android should boot.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
musa13 said:
A factory reset would not remove you ROM. I had same issue whit EOS ROM after I updated GAPPs. Prime would always boot into Recovery. Run the following command from your PC then reboot and any new recovery should be flashed by the bootloader and then android should boot.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
Musa13 thanks for the reply.
The thing is... I never used adb before... when I type the command on cmd it wont work cuz i dont have adb... neither on my computer or prime...
I tried with prime connected to the computer with the recovery screen on it. But the computer doesnt say anything about the prime being connected....
do I still have any chance?
You will have to use ADB to fix this. Get ADB from here:
http://forum.xda-developers.com/showthread.php?t=1387527
You will need Windows Drives for Prime from here:
http://forum.xda-developers.com/showthread.php?t=1426502
If Windows give you warning that driver is from untrusted source just ignore it (install anyway).
After you done all of this use Command Prompt and navigate to you ADB folder and then run command:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Thanks for the walkthrough Musa13. First I will read a bit more about adb and will try it when I get home.
I confess I have little knowledge on adb. My experience on flashing/rooting didnt make adb necessary so far (cyanogenmod 7 and 9 on my old galaxy s. thats all).
If you can just answer me some curious questions in the meantime:
-Is that right that theres no CWR that reads SD cards on prime?
-Theres no rom flashable via Odin on the prime?
Thanks again and I will update that later.
diogofmaciel said:
Thanks for the walkthrough Musa13. First I will read a bit more about adb and will try it when I get home.
I confess I have little knowledge on adb. My experience on flashing/rooting didnt make adb necessary so far (cyanogenmod 7 and 9 on my old galaxy s. thats all).
If you can just answer me some curious questions in the meantime:
-Is that right that theres no CWR that reads SD cards on prime?
-Theres no rom flashable via Odin on the prime?
Thanks again and I will update that later.
Click to expand...
Click to collapse
Odin is only for Samsung devices
rogeriok said:
Odin is only for Samsung devices
Click to expand...
Click to collapse
yea... I should have guessed that...
anyway, I got adb running... but it wont see my device...
I have Asus Transformer Prime ADB Interface sucessfully installed on Device Manager...
when I run adb and run "adb devices" it gives me
"list of devices attached" with nothing in it.
When I try to run the comand that Musa13 gave, it says "device not found"...
What may be wrong now?
Thanks
diogofmaciel said:
yea... I should have guessed that...
anyway, I got adb running... but it wont see my device...
I have Asus Transformer Prime ADB Interface sucessfully installed on Device Manager...
when I run adb and run "adb devices" it gives me
"list of devices attached" with nothing in it.
When I try to run the comand that Musa13 gave, it says "device not found"...
What may be wrong now?
Thanks
Click to expand...
Click to collapse
try to uinstall all your's prime drivers from your computer and install 0nly adb naked drivers;this should works...
Ok guys, I am doing some progress....
I wasnt able to figure out why adb wasnt seeing my device, but when I tried this http://forum.xda-developers.com/showthread.php?t=1539352 and changed adb to recovery it worked.
so I put the command above in adb and.... now I am stuck in the splashscreen... no errors
still resarching.... i think i saw something about it in another post.... but any help here will be greatly appreciated
diogofmaciel said:
Ok guys, I am doing some progress....
I wasnt able to figure out why adb wasnt seeing my device, but when I tried this http://forum.xda-developers.com/showthread.php?t=1539352 and changed adb to recovery it worked.
so I put the command above in adb and.... now I am stuck in the splashscreen... no errors
still resarching.... i think i saw something about it in another post.... but any help here will be greatly appreciated
Click to expand...
Click to collapse
Trying to fastboot, but laptop will install drivers for ASUS Android Bootloader Interface but no sdcard...
anything I can do from here?
diogofmaciel said:
Trying to fastboot, but laptop will install drivers for ASUS Android Bootloader Interface but no sdcard...
anything I can do from here?
Click to expand...
Click to collapse
GOT IT!!
so, I realized I wouldnt be able to do anything on Fastboot (or nothing that my noobish knowledge can tell) so I tried boot into CWM again and it worked
so back to adb:
adb push C:\ROM.zip /sdcard/
after the push, i could see the rom in cwm and that was that!!
So lesson learned: DONT FACTORY RESET INSIDE SETTINGS IF YOU HAVE A CUSTOM ROM!
thanks for the fast intro to adb musa13! It really saved my TP!
Valeu Rogerio!
diogofmaciel said:
GOT IT!!
so, I realized I wouldnt be able to do anything on Fastboot (or nothing that my noobish knowledge can tell) so I tried boot into CWM again and it worked
so back to adb:
adb push C:\ROM.zip /sdcard/
after the push, i could see the rom in cwm and that was that!!
So lesson learned: DONT FACTORY RESET INSIDE SETTINGS IF YOU HAVE A CUSTOM ROM!
thanks for the fast intro to adb musa13! It really saved my TP!
Valeu Rogerio!
Click to expand...
Click to collapse
I was the first that hard bricked my prime,hard brick number 2 ,I was unable to fix it; but my my warranty payed a new motherboard for me and this time I will not unlock my bootloader...
rogeriok said:
I was the first that hard bricked my prime,hard brick number 2 ,I was unable to fix it; but my my warranty payed a new motherboard for me and this time I will not unlock my bootloader...
Click to expand...
Click to collapse
Yeah... actually when I saw the spashscreen hang I was like "I read some thread about this..." so I updated here and went to search for that thread... and It was the "How to unbrick (or not) your TP" and then it was the time for me to freeze... but I was thinking "It can't be... I don't get any error... so it can't be hard brick... so I rebooted with the recovery combo Vol_down + Power and I could go to recovery and my heart started beating again.
I am sorry about your brick... but I am wondering how ASUS covered your unlocked bootloader?
diogofmaciel said:
Yeah... actually when I saw the spashscreen hang I was like "I read some thread about this..." so I updated here and went to search for that thread... and It was the "How to unbrick (or not) your TP" and then it was the time for me to freeze... but I was thinking "It can't be... I don't get any error... so it can't be hard brick... so I rebooted with the recovery combo Vol_down + Power and I could go to recovery and my heart started beating again.
I am sorry about your brick... but I am wondering how ASUS covered your unlocked bootloader?
Click to expand...
Click to collapse
the store that I boucht has covered everything,I did not pay anything and
my gps is much better now
i had the same problem.
rogeriok said:
the store that I boucht has covered everything,I did not pay anything and
my gps is much better now
Click to expand...
Click to collapse
Thats interesting... cuz bootloader unlock should void your warranty..... at least is what they say....
Anyways good for you
Hey Folks,
Were you guys able to boot into CWM afterwards ? After I've done dd if=/ ... of=/ i couldn't boot into CWM anymore ... I tried to install CWM by the Rom Manager app and it didint work... tried to install via pc but didnt work .... tried to install via shell but guess what... didint work (i guess it is installed just doesnt work) Always when I try to boot into recovery (Vol DOWN then Vol up) i end up in a android picture with a red ?? triangle plus exclamation on it
Any thoughts on that??
Thanks
Please see this safer/easier/faster method instead of using the one below http://forum.xda-developers.com/showthread.php?p=36976137#post36976137
Original guide provided below for historial purposesonly, seriously use hte one above:
Please refrain from repackaging, or rehosting my materials, ask prior to deciding to.
If this guide fails, or the auto script (which I will not recommend you use) fails, please do a factory reset before attempting again.
If you appreciate this, please make sure you check out my original article on the AndroidPolice. Without the support of AP, I wouldn't spend nearly as much time doing this. To the bloggers who will chose to link to a forum post, rather than the original post on a better blog, you suck.
http://www.androidpolice.com/2012/11/24/exclusive-how-to-unlock-the-droid-dnas-bootloader/
Donations for new test devices can be made at the paypal link to the left. I reserve the right to send leftover funds to whatever charities I feel like. Generally I choose Boys and Girls club of america, sometimes I choose seasonal charity, or a medical related one.
Known Problems:
Adb server is out of date
Uninstall HTC Sync, Samsung Kies, etc any software that talks to the phone.
If you get stuck, please immediately find someone in our chat that knows what they are doing. It is very easy to brick your phone if you follow these directions incorrectly, or if a problem arises!
Need faster help? or Want to help visit our chat
http://chat.andirc.net:8080/?channels=#droid-dna
Credits:
Original development: jcase
Awesome saver of the day: Sean Beaupre
Crash test dummy: dsb9938 (I bricked his phone making this!)
Artem and all @AndroidPolice for putting up with my nonsense.
Special thanks to Fuses for recommending a better target, and the numerous testers that let me play with their new phones.
Click to expand...
Click to collapse
Warning: This is semi complicated, and is known to ruin phones if done incorrectly. Proceed at your own risk
Needed:
1gb free space on the phone.
Working adb, must support the adb restore feature (ICS and up!)
Downloads:
backup.ab (300mb) mirrors: http://d-h.st/tau - http://depositfiles.com/files/9c61r4lgo - http://www.filefactory.com/file/2va8yp2i1h99/n/backup.ab
DNA_TeamAndIRC mirrors - http://d-h.st/D4r - http://www.putlocker.com/file/F357F205F5235B3D - http://rapidgator.net/file/59342799/DNA_TeamAndIRC.zip.html
Unzip DNA_TeamAndIRC, put runme.sh, CIDGen.apk and backup.ab into the directory where adb is (or anywhere if you have your paths setup right).
Please Check the readme.txt before continuing!
Code:
adb install CIDGen.apk
Run the CIDGen app on your phone, enter the last digit of your IMEI (NOT YOUR MEID) and press generate. Then confirm the generated file exists.
Code:
adb shell ls -l /sdcard/CIDBLOCK.img
If CIDBLOCK.img does not exist, run the app and try again. Do not proceed without generating a CIDBLOCK.img, it is needed to repair the phone and unlock.
Once you have CIDBLOCK.img on your sdcard, open two terminals (command prompts) and continue
In the first terminal/cmd prompt run these commands:
Code:
adb push runme.sh /data/local/tmp/
adb shell chmod 755 /data/local/tmp/runme.sh
adb shell /data/local/tmp/runme.sh
runme.sh will continue to loop and spit out No such file or link failed errors, just leave it running for now.
In the other terminal/cmd prompt run this commands:
Code:
adb restore backup.ab
Then allow the restore on your phone. Once the process is finished, you can go back to the looping terminal and stop it with control + c, or close the terminal
At this point, do not continue unless you are certain you can do this. Past this point, is where people can brick if they do not follow the directions correctly. If you run into a problem, find someone to help you. Do NOT power your phone off or reboot it. Leave it charging and find someone.
Code:
adb shell rm /data/data/com.htc.usage/files/exploit/*
adb shell mv /data/DxDrm /data/DxDrm_org
adb shell mkdir /data/DxDrm
adb shell ln -s /dev/block/mmcblk0p5 /data/DxDrm/DxSecureDB
adb reboot
Once the phone is rebooted, open two terminals and repeat the restore exploit:
In the first one:
Code:
adb shell /data/local/tmp/runme.sh
This process will also loop forever and give out lots of "No such file" or "link failed" errors - again, just leave it running.
In the second terminal, restore the backup again:
Code:
adb restore backup.ab
After the restore is done, we will undo the DxDrm symlink attack and write the new CIDBLOCK.img:
Code:
adb shell mv /data/DxDrm /data/DxDrm_trash
adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5
If this returns an "out of space error" come to our chat, and find either jcase or beaups. Do not reboot. Do not continue.
Code:
adb reboot
After reboot, you can go to http://HTCDev.com, and unlock through their official process. Choose the "All other supported models" option when selecting your phone.
Cheers!
Is there a one-click for this?
Sorry, I couldn't resist!
Support chat: http://chat.andirc.net:8080/?channels=#droid-dna
D
.
no comment...
btw great job guys!! :good:
dsb9938 said:
Is there a one-click for this?
Sorry, I couldn't resist!
D
.
Click to expand...
Click to collapse
Awesome.....now I just need the actual phone.
UPS HURRY UP!!!
awesome
Awesome work J and D...
Aight D where is the "cubed" lol
gramsey1911 said:
Awesome work J and D...
Aight D where is the "cubed" lol
Click to expand...
Click to collapse
Next week! Sheesh.
D
.
dsb9938 said:
Next week! Sheesh.
D
.
Click to expand...
Click to collapse
I'm feenin ova here for the cubed...lol
dsb9938 said:
Is there a one-click for this?
Sorry, I couldn't resist!
Support chat: http://chat.andirc.net:8080/?channels=#droid-dna
D
.
Click to expand...
Click to collapse
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
typeriz said:
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I wouldnt trust a one click, i automated the PITA part already with the CIDGEN app
This is for the new bootloader right. Just wanna make sure.
Sent from my HTC Droid DNA
typeriz said:
Lol.... I'm going to wait for the one click, can't afford to brick my device while trying to unlock with 2 kids running around lol...
P.s. thank you j case and DSB for the unlock and root
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I just did it, and it's really not that hard, took maybe 10 minutes, just copy and paste the commands and you should be good :good:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Argumentation said:
I just did it, and it's really not that hard, took maybe 10 minutes, just copy and paste the commands and you should be good :good:
Click to expand...
Click to collapse
I'm going to wait till I put the kids to bed, tonight. Thanks again !!
Sent from my HTC6435LVW using xda premium
---------- Post added at 04:32 PM ---------- Previous post was at 04:29 PM ----------
TheBiles said:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=34551547
How unlock and root work on the Droid DNA.
I belive you have to manually update it
Sent from my HTC6435LVW using xda premium
jonah1234 said:
This is for the new bootloader right. Just wanna make sure.
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
Huh, this is for the htc droid dna in general.
TheBiles said:
So I was able to unlock with this method via HTCDev, I installed TWRP and the insecure kernel, but my SuperSU will not work after I flashed the file in recovery. None of my apps can get root access, and I cannot update the superuser binary via SuperSU. What's going on here?
Click to expand...
Click to collapse
Sounds like bad or incorrect su binary
Try Superuser instead of SuperSU
WHERE IS THE IMEI!?
madzozs said:
Try Superuser instead of SuperSU
Click to expand...
Click to collapse
That worked! I'm not sure why SuperSU doesn't work, but oh well!
jonah1234 said:
WHERE IS THE IMEI!?
Click to expand...
Click to collapse
On your box!
Never mind. Figured out the issue. Now it's just hanging at full restore. There's no password right? I selected restore my data and nothing happens.
thebiles said:
that worked! I'm not sure why supersu doesn't work, but oh well!
On your box!
Click to expand...
Click to collapse
found it haha i fail
So, i was in recovery to restore to a previous backup. I was wiping my system to prevent errors but unfortunately i wiped EVERYTHING, including the backup and the OS. So, i kept it in recovery till i got home hoping to just mount my storage and transfer a ROM over and ten install..sounds easy enough. However, i plug my phone in and click mount storage and it doesn't mount with twrp, or even clock work mod.
Soo....i have no OS, can't mount my storage..and i'm stuck.
Can i flash a ROM through command line? If so, how? And why isin't my Droid DNA mounting?
Wttttfff help asap please!
Aaannd...now i'm stuck in the boot screen and it won't turn off.
Just use either adb push or adb sideload
Sent from my HTC6435LVW using xda app-developers app
Nice! forgot about those commands, however it's telling me that adb is not a recognized command. I've forgotten how to fix that? Can you help with that?
Adb sideload starts up and says daemon not running, then start's it succesfully. then says device not found. I'm pretty sure i don't have the right drivers for my DNA, can you point me in the right direction for that?
I really need help, i don't think i can even turn on usb debugging because i have no OS to boot into.
FIXED. I got this
soundofcarnage said:
FIXED. I got this
Click to expand...
Click to collapse
What steps did you take?
I looked a little more into ad sideload. I sideloaded a zip of the Rom I wanted and then chose to flash through sideload.
You pretty much:
Download your rom and put it into your fasboot directory oin your.
Boot into recovery and choose "install" then "install zip from sideload"
It should say to now type into command promt "adb sideload romfilrname"
It then loads it, and you just hit flash after it loads.
soundofcarnage said:
I looked a little more into ad sideload. I sideloaded a zip of the Rom I wanted and then chose to flash through sideload.
You pretty much:
Download your rom and put it into your fasboot directory oin your.
Boot into recovery and choose "install" then "install zip from sideload"
It should say to now type into command promt "adb sideload romfilrname"
It then loads it, and you just hit flash after it loads.
Click to expand...
Click to collapse
with no o/s and im pretty much on the same boat, how did you get adb to read your device? when i type in adb devices it gives me a blank list of devices
It worked for without ever actually listing my device.
soundofcarnage said:
It worked for without ever actually listing my device.
Click to expand...
Click to collapse
Oh okay, this is basically my last step. Im stuck on cannot read sideload. is it because of the romfilename? or am i missing something.
IceAzures said:
Oh okay, this is basically my last step. Im stuck on cannot read sideload. is it because of the romfilename? or am i missing something.
Click to expand...
Click to collapse
Are you adding .zip after filename?
Sent from my HTC6435LVW using Tapatalk 2
rsims26 said:
Are you adding .zip after filename?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
no ill try that
IceAzures said:
no ill try that
Click to expand...
Click to collapse
That's kinda necessary.
Sent from my HTC6435LVW using xda app-developers app
Sorry if i am making things complicated. I havent done adb since January to unlock bootloader and install custom recovery
IceAzures said:
Sorry if i am making things complicated. I havent done adb since January to unlock bootloader and install custom recovery
Click to expand...
Click to collapse
you have old adb
just adb push it and then flash in recovery
adb push some_damn_rom.zip /sdcard/
beaups said:
you have old adb
just adb push it and then flash in recovery
adb push some_damn_rom.zip /sdcard/
Click to expand...
Click to collapse
The longer this happens the more i feel like an idiot. I can't push anything either. Where in sdk is a new adb and how much more will it help?
IceAzures said:
The longer this happens the more i feel like an idiot. I can't push anything either. Where in sdk is a new adb and how much more will it help?
Click to expand...
Click to collapse
hmm thought I replied.
cwr has issues with adb
download twrp recovery and flash it - http://techerrata.com/browse/twrp2/dlx
beaups said:
hmm thought I replied.
cwr has issues with adb
download twrp recovery and flash it - http://techerrata.com/browse/twrp2/dlx
Click to expand...
Click to collapse
You did, there's 2 different threads he's posting in.
Sent from my HTC6435LVW using xda app-developers app
I have been looking EVERYWHERE for a solution to this. I followed the {Unlock Bootloader for Noobs} to the letter http://forum.xda-developers.com/showthread.php?t=2277639
I get to where in the video guide the screen become's inverted and the touchscreen is all over the place. But I can't get my phone to boot into recovery. I have tried every single guide to no avail. I have the LG L9 P769 with Tmobile.
And right now my phone is useless.
Just a tid bit, when it first boot's up both the logo and everything is backwards, but if I suspend it and bring it back up, its all back to normal but the touch pad is still goofed up.
Any help would be greatly appreciated.
You need Roberts busybox installed, artas182x cwm install, and flash the fix with cwm.
You need the v6 bin the directions are with it.
Sent from my LG-P769 using xda app-developers app
I rerooted the phone, installed SU, gave root access to the recovery when it asked, installed and clicked "Boot into Safemode" and it did the exact same thing it always does.... nothing, it simply rebooted the phone to main screen, Even tried holding down the vol- button during a boot.. nothing. it only goes into safemode.
Feral_Sparky said:
I rerooted the phone, installed SU, gave root access to the recovery when it asked, installed and clicked "Boot into Safemode" and it did the exact same thing it always does.... nothing, it simply rebooted the phone to main screen, Even tried holding down the vol- button during a boot.. nothing. it only goes into safemode.
Click to expand...
Click to collapse
Do you know how to use ADB with your computer? Do you have android debugging enabled? Do it the old way
First extract the v6.bin to you SD card (external_SD). Open adb and enter the following
Code:
adb shell
su (give it root access on your phone, good luck)
cat /storage/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
once you do that the shell will freeze (can't use it anymore) So open a new cmd and enter this
adb reboot
This will fix the problem. Now go thank Lelus :thumbup:
CM 10.1 P769
Where do I find the v6.bin to copy to my phone?
Feral_Sparky said:
Where do I find the v6.bin to copy to my phone?
Click to expand...
Click to collapse
Meda808 posted it above.
CM 10.1 P769
I did just as you told me to, I copied the v6.bin to my external sd card, started up ADB, put in the commands but once I entered SU and gave it root on the phone the terminal stopped and would not allow any more commands, I rebooted and tried again as well as rebooting the phone. I am unable to enter the command to transfer the file.
Feral_Sparky said:
I did just as you told me to, I copied the v6.bin to my external sd card, started up ADB, put in the commands but once I entered SU and gave it root on the phone the terminal stopped and would not allow any more commands, I rebooted and tried again as well as rebooting the phone. I am unable to enter the command to transfer the file.
Click to expand...
Click to collapse
You might have thought you gave it access, but actually denied access. Try to open supersu, and check if adb was given su access.
CM 10.1 P769
kuma82 said:
You might have thought you gave it access, but actually denied access. Try to open supersu, and check if adb was given su access.
CM 10.1 P769
Click to expand...
Click to collapse
I checked supersu and it show's as given root access. And when I put in the SU command into adb it show's on the phone as giving root permission's via popup. And that's where it freezes.
Do you have team viewer setup, send me your info in a PM. I'll wait for 30 mins
CM 10.1 P769
kuma82 said:
Do you have team viewer setup, send me your info in a PM. I'll wait for 30 mins
CM 10.1 P769
Click to expand...
Click to collapse
Sorry it took so long to reply, I am setting it up now. Gotta love having kids
Go figure we couldnt get it to work, only been trying since I got the thing back in March to no success. But I do appreciate the help.... now im off to brick my phone to get a new one.
I removed because someone won't listen and just do what I posted Lol. I'm pm you
---------- Post added at 08:51 PM ---------- Previous post was at 08:23 PM ----------
Feral_Sparky said:
Go figure we couldnt get it to work, only been trying since I got the thing back in March to no success. But I do appreciate the help.... now im off to brick my phone to get a new one.
Click to expand...
Click to collapse
Lol, while you are at it, might as well remove the u-boot
CM 10.1 P769
kuma82 said:
Do you know how to use ADB with your computer? Do you have android debugging enabled? Do it the old way
First extract the v6.bin to you SD card (external_SD). Open adb and enter the following
Code:
adb shell
su (give it root access on your phone, good luck)
cat /storage/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
once you do that the shell will freeze (can't use it anymore) So open a new cmd and enter this
adb reboot
This will fix the problem. Now go thank Lelus :thumbup:
CM 10.1 P769
Click to expand...
Click to collapse
Thanks! This fixed the touch screen on P769 Tmobile. This is after using the LG support tool to update back to V20f from a failed attempt using carloswii5's noob guide. Could not get past "adb reboot oem-unlock."
If anyone can point me in the right direction to get the LG boot screen back to normal (not inverted/mirrored) i would appreciate it. -----Update:found u-boot.zip fix for boot screen.
Thank You!
Thank You!
I had given up on this a year ago, I tried it again on my phone and it worked!
Thanks Again