Related
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
Hi,
It's not CWM, but this is the stock 3e recovery + adb root access, allowing you to use adb to back up other partitions, restore, etc. etc.
Flash the pda-recovery-root.tar with Odin using the same instructions as for the Root kernel.
If someone who has not yet rooted could flash this and do the following from adb in recovery after:
Code:
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
adb pull /tmp/stock-kernel.img
adb shell rm /tmp/stock-kernel.img
then upload stock-kernel.img that would be good for making a return-to-stock odin image
Keep up with the awesome work brotha.
You're a maniac!!
<insert witty signature here>
I wake up to this! Nice! I cant wait for proper CWM.
Tomorrow will be a great day as I'm holding mine
Sent from my MB860 using xda premium
telus galaxy note
hi, i tried to back up the kernel for the canadian telus galaxy note with the adb root you have there but when i use adb to run the commands i get an error message saying permission denied. does it work with the canadian version?
Hi, I haven't tested with anything other than the AT&T GNote. Do you get the # root prompt in adb? You likely wouldn't even have adb without the mod working, what error do you get for what command exactly?
when i run
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
i get
/dev/block/mmcblk0p8: cannot open for read: Permission denied
then again do i have to be in recovery mode fir before i run adb? just figured out how to get into recovery.
Since I'm in Canada with the Rogers variant I was going to upload the stock kernel, but somehow I just cannot get into recovery to pull it, I've tried vol up+power, both volumes+power, and obviously vol down+ power is download mode. It's almost embarrassing haha.
I've always made good use of what the dev's have done for us since my N1, I figured I could give back at least a little
looks like i had to be in recovery mode. how big is the kernel suppose to be mine shows about 10MB
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
to get into recovery mode hold vol + and vol - and turn on the phone holding the volume keys and release the power key
Da_G...
I have been a big fan of yours for a long time... You had the BEST Windows 6.5 ROMS I ever used and have always done a lot for the community...
I cannot tell you how happy I was to see that you have this phone and are working on it!
Just wanted to sing your praises
Can't wait to see your new stuff!
Da_G said:
Hi,
It's not CWM, but this is the stock 3e recovery + adb root access, allowing you to use adb to back up other partitions, restore, etc. etc.
Flash the pda-recovery-root.tar with Odin using the same instructions as for the Root kernel.
If someone who has not yet rooted could flash this and do the following from adb in recovery after:
Code:
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
adb pull /tmp/stock-kernel.img
adb shell rm /tmp/stock-kernel.img
then upload stock-kernel.img that would be good for making a return-to-stock odin image
Click to expand...
Click to collapse
Thank you for the fantastic work.. Do you have a github or other place we can fetch sources?
Guess this is my cue to get in for the Bell variant.
I'm guessing flashing this will also hit the counter too? Right...
Sent from my Galaxy Nexus using Tapatalk
Ignore me. I goofed up.
@FarBeyond: Thanks!
@runandhide05: yep.
Much appreciated, pattmyn
(unfortunately it looks like you pulled p8 which is the kernel, but had already flashed the root kernel, overwriting the bell stock kernel.)
(however, you can get the bell rom by following the same directions but substituting p24 instead of p8. note that it will be much larger!)
Da_G said:
@FarBeyond: Thanks!
@runandhide05: yep.
Much appreciated, pattmyn
(unfortunately it looks like you pulled p8 which is the kernel, but had already flashed the root kernel, overwriting the bell stock kernel.)
(however, you can get the bell rom by following the same directions but substituting p24 instead of p8. note that it will be much larger!)
Click to expand...
Click to collapse
F***. I've already got your kernel back installed again, and started debloating the Bell one. Tell ya what, if nobody hops on it by tomorrow evening, I'll nuke and reboot back in and pull the larger ROM file. I've just run out of time tonight and have to get back to working on work related stuff.
Edit: As a funny aside, my counter's gonna be in the double digits at this rate. I REALLY hope I don't have to send this thing back lol
I'm already in the 20s myself Can't concern yourself about such things as a dev!
Sent from my SAMSUNG-SGH-I717 using Tapatalk
http://www.mediafire.com/?6atiy1dddr42hp3
telus kernel
G, if i pull the whole rom from the device does that include all the stuff i have put on it already? or just the factory image?
Thanks for the stock TELUS kernel
I've incorporated some of the ramdisk components into my ramdisk for the next version (I used ramdisk from Skyrocket there) - differences are minor.
I'll get an odin-to-stock-TELUS-kernel image up tomorrow!
So basically i got the ICS Encryption unsuccessful error and now my phone wont get past the vibrant splash screen. I tried odining back to stock but it just goes to splash screen and then turns off. i cant get into recovery mode. please please pleaseeee help!
jig or get to download mode
odin EUGENE373_SamsungS_Froyo_PDA (read directions)
then flash back to stock then try not too "brick" the unbrickable vibrant again.
this does not fix the problem. the /data partition is the cause of the problem and i dont know how to fix it. repartitioning in odin doesn't fix it either. :/
I had the same thing happen to me.. ive tried everything i could think of
enter download mode
dvryu said:
enter download mode
Click to expand...
Click to collapse
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Unfortunetly there is no fix as of now. The problem seems to be the internal flash memory 16gb is unable to mount. SD card (External) mounts perfectly fine as i was able to pull some files using adb commands. Hope you have a spare phone cuz there is no way to fix your phone as of today.
A warning to ICS rom users. You phone could potentially become paperweight so be extremely careful. You might want to consider using Gingerbread or some other rom other than ICS until someone finds a solution to this problem.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Nirmalspeed said:
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Click to expand...
Click to collapse
The buttons in recovery don't work after flashing Eugene's rom.
You can only reboot your phone through the adb command:
adb reboot
Of course you must also have the android debugging bridge installed on your computer to issue these commands. Including the SDK. Good luck.
i have two other vibrants in my family right now. what do you think i could do with those to fix mine?
http://forum.xda-developers.com/showthread.php?t=1447303
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Woodrube said:
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Click to expand...
Click to collapse
i was running ICS Passion 13 with the Kiss kernel that came with it. and i've looked around and many people with ics have gotten this problem both on our device and on the AT&T's captivate.
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
cotbu said:
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
Click to expand...
Click to collapse
that wouldn't work as the /data partition isn't being red by the phone. Nothing happens when i try that command.
These are the instructions, Eugene's rom write like a lowlevel format, either you are not following directions or you actually bricked the vibrant.
But....you say you've made it to Eugene's recovery if you did you should be good to go.
Okay, Now with the Caution Posted, Lets Begin with the Froyo that Don't Brick
I have Tested this 5 Time's to Make Sure! Only install What I Post!
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Do Not Select Repartition In ODIN Flasher
Quote:
Installing...
Extract the .zip file
Open ODIN Flasher, Select the Pit File.
Select Eugene373_GalaxyS_Froyo_PDA.tar
Select start..
Second,
Once Odin had Done Flashed, & you are in Recovery Mode you will not be able to Access anything & need to be at a Computer with Samsung Driver's installed & a working SDK pre-installed..
Side note: you will get an error in recovery, Don't be worried!!!! Ignore this!
Third,
Open a CMD Prompt & type:
Quote:
adb reboot
Froyo with Downgrading back to Stock Possible:
Download here > EUGENE373_SamsungS_Froyo_PDA.zip
*Stock Froyo with*
~ Root
~ SuperUser.apk
~ Build.prop now Correct
~ Defualt.prop Also Correct
****
*Issue's
Volume Key are Reversed
****
*Not working*
~ Rom Manager via reboot to Recovery!
~ Selectable Menu in Recovery
~ 3.5 Head-jack
~ Hot Spot Tethering
sorry for stressing but, I have a 4yr old that loves playing with the vibrant and I think I've brought it back from every brick situation possible. As long as the vibrant has power, it will not stop! xd!
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.
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!