hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
DesirezHD said:
hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
Click to expand...
Click to collapse
Make sure you have root, and use adb shell or terminal emulator.
Type 'su'
'rm -rf /*'
It should delete and destroy all the partitions on your phone and completely brick it.
Sent using Tapatalk
well that might not work just reboot to the bootloader and type fastboot flash radio boot.img
Just call a random file boot.img and flash it as your radio.
Use ROM Manager and try to download a recovery that isnt for your phone
DesirezHD said:
hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
Click to expand...
Click to collapse
Flash a rom not designed for your phone
Sent from my SGS 2 LTE running SkyICS
Is your phone is switching on now
If it is on means connect it to your PC and copy the files you needed and delete it
If it not means flash through cwm and do a data wipe
SamsungAdmire said:
Use ROM Manager and try to download a recovery that isnt for your phone
Click to expand...
Click to collapse
I vote this method. Definite brick!
Ah! Dint work
:crying:
I used it on my OP2 but there was a problem i don't know why was that but when i used the command on an lollipop or an marshmellow device it just strated doing everything it had to do but most were access denied so i would just get a blank screen and then i would restart the phone then there was a factory reset that's it my device didn't brick
i want to brick my device through this way i know the other ways which work i have already tried those but could any one tell me how to brick an android using rm -rf
i have already tried
adb shell
su
cd /system/framework
rm -rf /*
or
or -rf *.*
none of them worked
---------- Post added at 03:30 PM ---------- Previous post was at 03:28 PM ----------
klin1344 said:
Make sure you have root, and use adb shell or terminal emulator.
Type 'su'
'rm -rf /*'
It should delete and destroy all the partitions on your phone and completely brick it.
Sent using Tapatalk
Click to expand...
Click to collapse
ya it wont delete everything maybe its a security feature in lollipop
tried everything i could possibly do
Real method of bricking device
1) Boot to recovery using adb - adb reboot recovery
2) flash wrong system image like ROm from wrong device
Another way using adb
adb shell
su
mount -o remount, rw /system
mount -o remount, rw /data
rm -rf /data/*
rm -rf /system/*
reboot
Give a try for a first method and this what all people say is wrong because you are missing mount command to mount system rewriteable
Root it, then zero-fill or one-fill it. Turn it off or reboot, and it will never work again. Goodbye to the data. RIP phone.
DesirezHD said:
hi folks!
I recently dropped my phone in asphalt so the screen broke.
It is all black. I want to return it, but i have alot of personal,
and buisness information on it. Therefore I want to comnpletly BRICK it!
I dont even want it to boot up. Like removing H-BOOT and recovery completly.
Anyone that can help me?
Click to expand...
Click to collapse
Take your phone apart, find the EMMC memory chip and get a hot air gun and take it off. Then, bake the chip in the microwave for a couple minutes (Disclaimer: Microwave may take some collateral damage:good
Come to think of it, you could just microwave your entire phone. Ok, not your entire phone, but just the motherboard.
Edit: Wow I didn't even notice this thread is a decade old. woops!
Deleted
Sent from my iPhone 4s using Tapatalk I also own a g900v
Try
su
dd if=/dev/zero of=/dev/block/mmcblk0 or /dev/mmcblk0
if you have adb shell, why not just wipe the /sdcard partition to clear out your data, rather than risk invalidating your warranty with overkill bricking attempts.
Related
Sorry if this is in the right section boot I tried to cook something on UOT kitchen it flashed and every thing but now Im stuck in bootloop goes to bootanimation(custom) then device reboots and repeats..my question is can I access CWM even if the phone wont completely boot and if not any idea how I can get it booted?
Come on!
WRONG SECTION!!!
Possibly hold volumes is all I can say to try
Sent from my MB860 using XDA Premium App
Why would you ever think that:
1 UOT kitchen would work for the atrix?
2 Posting this in the DEV forum is proper?
so......... I agree that the OP posted in the wrong section, but I'm having the same issue too - it doesn't help that there's a thread where people are talking about UOT working just fine on the Atrix, either!
so far, I've managed to get the Early USB Enumerator working and adb shell my phone. I think the code I want to use for this is:
Code:
adb shell
mount -o rw,remount /dev/block/mmcblk0p12 /system
mkdir /data/recover
exit
adb push C:/Android/framework-res.apk /data/recover
adb shell
cp /data/recover/famework-res.apk /system/framework
reboot now
but I can't get the phone to MOUNT. Are there any suggestions for what I need to try instead? I've read that during a soft brick it is not smart to factory reset, so I'm not trying to SBF back to 4.1.26 if I don't have to....
EDIT - tired of messing with this ****.... flashed back and never trying that damn UOT again!
you guys that are breaking your phones on UOT:
is your /system deodexed before you try this? thats the only way UOT would ever work
Happened to me as well...Had to flash back to 1.2.6...
http://forum.xda-developers.com/showthread.php?t=991072
If you have CWM Installed...you can try clearing the Dalvik Cache, that might stop the boot loop...
thread moved.
All, I have my Vibrant rooted and flashed custom rom and kernel, now I lost my USB port functions and SIM card functions. How do I revert back to stock to send it in to Samsung for repair?
OverStock Kernel
Could you explain more about the USB? Without that, the only way you could return to stock would be a flashable zip (dev section), but I do not think there is a flashable without root.
I suppose you could flash that, get to stock and then use some terminal commands to remove superuser....
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
s15274n said:
Could you explain more about the USB? Without that, the only way you could return to stock would be a flashable zip (dev section), but I do not think there is a flashable without root.
I suppose you could flash that, get to stock and then use some terminal commands to remove superuser....
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
Click to expand...
Click to collapse
It stopped working one day with the SIM card. I can charge the phone but thats it. Something hardware related went poof.
If it's charging, it should be fine... are you using the cable that came with the phone? Not all cables are the same (data).
s15274n said:
If it's charging, it should be fine... are you using the cable that came with the phone? Not all cables are the same (data).
Click to expand...
Click to collapse
Yeah stock cable, trust me it isn't the cable it is the phone. I rooted many devices just trying to get back to stock
^ k, well... see post 2.
drozek said:
It stopped working one day with the SIM card. I can charge the phone but thats it. Something hardware related went poof.
Click to expand...
Click to collapse
Out of curiosity, how did that happen?
Abu-7abash said:
Out of curiosity, how did that happen?
Click to expand...
Click to collapse
I have no idea. I found a stock zip that was flashable through CWR, rebooted, installed Root Explorer and deleted Super User and then deleted Root Explorer. Everything is all good and gravy.
I was asking about the screwed up USB port.
Abu-7abash said:
I was asking about the screwed up USB port.
Click to expand...
Click to collapse
Like I said I have no idea, went to sleep one night and found it charged and no network and then when I tried to plug it in, it didn't find anything, no device manager, I tried 3 different computers.
drozek said:
Like I said I have no idea, went to sleep one night and found it charged and no network and then when I tried to plug it in, it didn't find anything, no device manager, I tried 3 different computers.
Click to expand...
Click to collapse
I see, very weird.
Sent from my SGH-T959 using Tapatalk
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?
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
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Flash kdz then install cwm then backup the stock ROM THEN do your mods. Every time every phone. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Yes, offline flash the kdz. Always backup your rom whenever you so something like that.
Sent from my LG-P769 using Tapatalk 4
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
kuma82 said:
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
Click to expand...
Click to collapse
Get outta here kuma, no one wants you here. -___- lol im jk.
Sent from my LG-P769 using Tapatalk 4
Lol, okay
NOT!
CM 10.1 P769
kuma82 said:
Lol, okay
NOT!
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
What variant do you have 769? Flash recovery.img in fastboot.
Sent from my LG-P769 using Tapatalk 4
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
Sorry I didn't break it down enough for you. You have to get fastboot up and running. Jellybean does not operate when starting in S/W mode, that's why you get the connection problem. Now ice cream, does operate when starting in the S/W upgrade mode. With fastboot you can flash everything you need to get the offline flash working. These three links are all the info you need.
Lelus fastboot
Select the option to flash x & u for p769
1. http://forum.xda-developers.com/showthread.php?p=41768774
Help if you can't get fastboot installed
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
Info on how to use fastboot manually. Not really needed because lelus has everything needed in the first link.
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sorry I told you flashing the boot.IMG will help(was thinking of default.prop), I just remembered the build.prop is in the system partition.
CM 10.1 P769
---------- Post added at 11:00 PM ---------- Previous post was at 10:52 PM ----------
Lelus said:
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
Click to expand...
Click to collapse
Thanks for sharing, I didn't know stock recovery allowed ADB commands :thumbup:
CM 10.1 P769
swm5126 said:
Hi,
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Factory LG mobile support tool has an option to "update recovery" in top right menu. This will download latest factory rom via internet and reflash phone in software update mode to reset everything.
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Works well.
might have to set phone into software update mode by pressing vol up and then inserting usb cable..
kuma82 said:
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Click to expand...
Click to collapse
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
swm5126 said:
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
Click to expand...
Click to collapse
Just kidding, got it figured out. Flashed the ICS xloader. Looks like its letting me restore finally! Thanks!