Can't figure out how to do factory reset since I can't get into the settings. The error pops up (process.com.sec.android blah blah blah) and when I press the "Force Close" to get rid of the error it tries to load the homepage back up but vibrates and the error appears again. Tried to tap the Apps icon real quick to possibly get into the settings but no dice. Tried the power button and down volume button to try to hard factory reset it that way but it just sits at this "Downloading" Do not shut off target" screen. Requires battery removal to start back up. Kies doesn't even see the phone... Any ideas???
This is stock, no rooting has taken place. Ugh.
Here is how to perform a factory reset whithout having to go into the settings.
i will provide you the steps to reset the phone.
Pearl: Power off the handset (for best results, remove the battery, and then put the battery back in).
Pearl: Press and hold both Volume keys, then press and hold the Power key at the same time. Release the Power Key when the Samsung Logo appears. Use the Volume keys when the Android system recover menu appears and use the Volume Keys to scroll to delete all user data.
Pearl: Press the Camera key to select then the Volume Up key to continue.
Pearl: When the reset process is complete, press the Camera key to reboot the headset
Try this out and you should be all set.
Continuum is in bootloop.idk way to do.I was modding the system icons and I think I screwed up something in the framework.any suggestions??
Sent from my T-Mobile G2 using Xparent ICS Blue Tapatalk 2
travis2387 said:
Continuum is in bootloop.idk way to do.I was modding the system icons and I think I screwed up something in the framework.any suggestions??
Sent from my T-Mobile G2 using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Three options
1. Restore a nandroid
2. Adb push a good copy of your framework, then reboot (you can boot into recovery for the push.)
3. Reflash the rom.
Sent from my SCH-I400 using Tapatalk 2
Txwolf1980 said:
Three options
1. Restore a nandroid
2. Adb push a good copy of your framework, then reboot (you can boot into recovery for the push.)
3. Reflash the rom.
Sent from my SCH-I400 using Tapatalk 2
Click to expand...
Click to collapse
How do I adb push and do u know where to find the link for the stock framework?
Sent from my Precedent using Xparent ICS Blue Tapatalk 2
Right here!
The database is right here:
http://forum.xda-developers.com/showthread.php?t=1316769
You can get all the stock stuff from the downloads.
Samsung continuum
Good Luck
travis2387 said:
How do I adb push and do u know where to find the link for the stock framework?
Sent from my Precedent using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
If you have a deodexed rom saved to your computer, open it, and go into framework, and find framework-res. It needs to be from the same rom that you are on, though. No mixing and matching.
copy that to your desk top.
Now, if you don't have Adroid SDK (which adb is a part of) installed, do so. There are a plethora of tutorials on where to get it, and how to install it.
Once you have that done, boot to recovery, and enter the following commands
cd c:\users\your_computer_name\desktop
adb.exe
adb shell mount
mount -o remount,rw -t rfs /dev/block/st19 /system
adb push framework-res.apk /system/framework
Let it push, (you will get a line of text saying 1234kbs transferred in 1.2 seconds) then type in
exit
adb reboot
From there, your phone will reboot into the rom
If there is someone a little more familiar with adb than me, cross check me on my command line structure. I don't recall if you can push from inside shell mount, or not. If not, correct me.
Thanks.
All that being said, the simplest solution is to wipe dalvik, and reflash the rom. All of your bloat ware will have to be debloated, again. And you'd lose any themes you've flashed. But, as long as you don't wipe data, you won't lose any of your apps, settings, or personal data. As for the rest, consider it an object lesson to remember to nandroid before you flash, next time. (And no, I'm not jumping your butt. I did the same thing, once... and only once.).
Related
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Clearly you haven't done any searching in the Android Development section.
But that's OK. Go ahead and get an Epic. Enjoy your screwed-up GPS and all that, and make sure to change your password on here to something you won't remember, so we never have to see you again.
mainguy21 said:
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045
there you go. Just follow the directions and make sure you use the correct file locations.
real problem
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
thats funny i just typed in the search bar root evo hboot 2.02 and the first thread was the guide on how to do it.
@op if you are going to lie about searching the forum do it somewhere else. we know when a search isnt performed.
mainguy21 said:
and ive searched everywhere
Click to expand...
Click to collapse
Sure you have, buddy... sure you have.
ohhhhhhhhhhhhhh
You have been misinformed due to stupid people making stupid and false posts such as this one:
http://forum.xda-developers.com/showpost.php?p=9578042&postcount=8
Kingmac38 said:
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I am 20 and have ADHD and search is my best friend plus I've followed many rooting guides successfully so op has no excuse
Second that my girls epic is a pain in the ass and she kinda of.wish she got my phonr instead
Sent from my PC36100 using XDA App
thanks for help even though i searched everywhere.
but since i cant root my phone im stuck in the middle of it with a red triangle can i atleast go back to my phone? like unroot or something even though i didnt get all the way to root? please thanks
Follow these revised instructions from illogos pg 121 of hboot 2.02 root guide and everything should work. I've already rooted two hboot 2.02 hw 004 and in process of doing another one now. Everything works just fine if you understand and follow the instructions. Anyways, this was a lot simpler than the old school toast part 1 and 2 root methods so acquire some knowledge so you can someday help others and not be such a newbie.
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
mainguy21 said:
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
Click to expand...
Click to collapse
Which instructions though? Please follow these ones by illogos-
illogos said:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V8.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V8 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
Click to expand...
Click to collapse
my wife got an evo on black friday from radio shack and i rooted it with unrevoked in like 5 minutes.
I have adhd... I wonder if 4g transmissions cause an increase in autistic spectrum disorders!?!?
Sent from my PC36100 using XDA App
animal7296 said:
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Click to expand...
Click to collapse
he wouldn't regret getting the epic, it's a cool ass phone. if you want a crisper lcd and a keyboard get the epic.
fixxxer2008 said:
If you want a cheap-ass plasticky POS, get the epic.
Click to expand...
Click to collapse
Fixed that for you.
tejasrichard said:
Fixed that for you.
Click to expand...
Click to collapse
Thank you. It seems all these Samsung phones feel like garbage. Way too flimsy. Now I have a friend with an LG Optimus S which I just rooted for her, and I have to say the build quality is very nice.
Hello,
I have a pb with my acer Iconia.
The tablet is blocked on the screen "Android" ...
I tried the button "reset" but nothing better ...
Is there a way to make a hard reset (factory reset) with a combination of buttons ?
Thanks a lot !
PS : My Acer Iconia Tab is "rooted".
Try holding the power key down till the unit shuts off, then let go and hold it down again till it restarts. Good luck.
I've found holding the volume button closest to the corner and power button at the same time forces a restart. Of course, I haven't tried just holding down the power button alone when it's frozen, so the volume button may not be necessary.
I am having the same problem with mine. My widgets started acting weird and disappearing. I thought a reboot might help but now it gets stuck on the Android load screen. I have tried hard reset and holding volume up during reboot. The latter takes to a recovery boot but seems to search on the SD card which doesn't really help. Acer tech support is absolutely worthless and it is too late to return to best buy so now I have to ship it to acer for service. Sucks.
Try this. Plug in a usb keyboard and power on while holding volume down. Keep holding both buttons until you see clearing cache in the upper left and you can then enter a menu by hitting HOME on the keyboard. There is an option to do a factory reset. You will lose all user data by doing this factory reset of cache and data but it may just get your tablet back. There are some other posts on this in dev if you search. Good luck.
maybe.you,both have a bad app that is causing this
try comparing installed apps .might.find what is the.cause
_motley said:
Try this. Plug in a usb keyboard and power on while holding volume down. Keep holding both buttons until you see clearing cache in the upper left and you can then enter a menu by hitting HOME on the keyboard. There is an option to do a factory reset. You will lose all user data by doing this factory reset of cache and data but it may just get your tablet back. There are some other posts on this in dev if you search. Good luck.
Click to expand...
Click to collapse
I did this and it will boot now but during setup the setup wizard FCs and starts over. I checked the Dev sections and I didn't see anything on factory resets? I'm running out of options.
I would try a couple times to boot since cache has been cleared, sometimes it will fix itself after the programs have a chance to JIT compile...it is typical in Android to see some FCs after the cache is cleared. If after a couple boots things aren't working their way out then you may have to flash a system image for your build, however this shouldn't be necessary unless you rooted and changed some stuff like uninstalled system apks etc.
What I did before the factory reset was replace the whole /system/app folder ( that I deleted some bloat ) with one that was complete like stock. I got a bunch of FCs, followed by a black screen. So I followed the steps you provided because the symptoms fit.
I've also done multiple restarts and the setup wiizard is still FCing.
this is my build Acer_A500_1.104.02_COM_GEN1 doubt this will help me.
daswahnsinn said:
What I did before the factory reset was replace the whole /system/app folder ( that I deleted some bloat ) with one that was complete like stock. I got a bunch of FCs, followed by a back screen. So I followed the steps you provided because the symptoms fit.
I've also done multiple restarts and the setup wiizard is still FCing.
Click to expand...
Click to collapse
If I were you (note the disclaimer), I would find and flash the complete system.img file for your build (see the [Dev] System Images thread). Once you have the proper system.img for your build in hand, then you can write the system partition in it's entirety. You can find examples of this in the same dev thread.
Cliff's notes:
Use adb to connect via usb and place the the system.img into /mnt/sdcard (adb push command), or you can do this another way if you have access to your storage via USB. It will take some time to copy, several minutes at least.
You will need root to do the rest, but obviously you already do if you overlaid system/apps. Using the adb shell as su, mount the partition as writable and use the dd command within the adb shell to restore the system partition. It will take several minutes to write, so don't panic.
Here is an example of the dd command if your .img is called system.img in /mnt/sdcard:
>adb shell
# su
# dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
# reboot
do i need to try adb i cant get my android market to load it force closes every time, i wished i could just load an factory image from older version and then let it grab the updates and start from fresh, i am rooted which may have been a mistake. i can hook an usb keyboard up hold home key get into recovery but if i put an rom.zip on sd card it doesn't see it.....what am i doing wrong.
Hi There,
I have also the problem that when I booting my tablet it stucks on the Android logo. I have tried to hook up an usb keyboard but he can´t find him. I get the Androidman with a note of exclamation.
Can someone tell me where I did go wrong? If I try it I see the cache messages etc. in het left corner.
My tablet is not rooted.
if you want to do hard reset first of all make sure you have an appropriate upate.zip on you external sd-card preferably use a stock rom.
after you do volume+ (up) and power once it vibrates keep your finger on volume + and toggle the screen switch few times. then let it go it will update.
Thank you for your answer.
I have searched for a update.zip and I have download and ecrypt this file: Acer_A500_1.104.02_1.141.07_COM_GEN1_1305615165779_f0150ee4
If I put this file on my SDcard I still get the androidman with the ! in it.
Jznwlnl said:
Thank you for your answer.
I have searched for a update.zip and I have download and ecrypt this file: Acer_A500_1.104.02_1.141.07_COM_GEN1_1305615165779_f0150ee4
If I put this file on my SDcard I still get the androidman with the ! in it.
Click to expand...
Click to collapse
That file is an incremental update and is ONLY for updating FROM 1.104.02 TO 1.141.07.
If your version doesn't match exactly, the update will fail. You'd be better off grabbing one of the 3.1 OTA updates in the thread in the dev section, as these are full ROMs.
I have tried the HC 3.1 ROM. This ROM was 487 mb but I still get the Androidman with the ! in it.
I have tried the file: Acer_A500_4.010.38_COM_GEN1.
The other files were 47mb
Reformat your SD card, or try a different one.
Locked at the android screen
_motley said:
Try this. Plug in a usb keyboard and power on while holding volume down. Keep holding both buttons until you see clearing cache in the upper left and you can then enter a menu by hitting HOME on the keyboard. There is an option to do a factory reset. You will lose all user data by doing this factory reset of cache and data but it may just get your tablet back. There are some other posts on this in dev if you search. Good luck.
Click to expand...
Click to collapse
I have a similar problem. Tried this and was able to do factory reset. However, after that, the same.The tablet is still stuck on the screen "Android" ...
During factory reset, I noticed the following messages on the screen:
E:/dev/block/mmcb1k1 does not exist
E:/dev/block/mmcb1k1 does not exist
E:/dev/block/mmcb1k1 does not exist
E:/dev/block/mmcb1k1 does not exist
E:failed to mount/sdcard
E:can't mount/mnt/sdcard/update.zip
What does this mean? Is there a way to fix it?
Somebody, please help! Thank you!
http://forum.xda-developers.com/showthread.php?t=1276227
Try step 2
Also, advice for a hard reset.
Hi folks,
Have tried following the advice below, downloaded: Acer_A500_4.010.38_COM_GEN1.
Added it to my SD card and then tried to boot whilst holding volume down.
It seems temperamental. Sometimes the Android with the ! appears and there's no progress bar. Sometimes the Android with the ! appears and there is a progress bar, but it never makes it past 25%.
I've tried formatting my SD card and redoing it but no joy.
Any suggestions?
Cheers.
I think I bricked my brand new Nexus 4 I was trying to follow the rooting directions here:
http://forum.xda-developers.com/showthread.php?t=1993331
I was using the Clokcworkmod and I was unable to see the super su folder in the sd connection. and i rebooted it anyways. Now after reboot the phone doesnt start up It just hangs at the X symbol at the startup.
As suggested, I also tried to reboot recovery, which also hangs
I'm super new to this, anybody, please help
I need 10 posts before I can post in the developer thread...so posting away
getsky said:
I need 10 posts before I can post in the developer thread...so posting away
Click to expand...
Click to collapse
Just start again, sometimes it messes up, but you generally just start again with flashing the clockworkmod. Make sure the download wasnt corrupted by doanloading everything again though, although ignore the bit about adb rboot bootloader, you need to start the phone manually by use power + volume-down key combination to get into bootloader when its powered off and continue from point 5.
Thanks, I will give that a try
Ya dun goofd
Sent from my Nexus 4 using Tapatalk 2
getsky said:
Thanks, I will give that a try
Click to expand...
Click to collapse
Relac, its actually pretty hard to completely bust these things. Dont quote me on that though lol
Don't freak out. I'm sure you're fine.
Unlocking the bootloader on my N10 caused me to hang at the X. Wiping data fixed it for me. Try the following:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time.
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
TheBishopOfSoho said:
Just start again, sometimes it messes up, but you generally just start again with flashing the clockworkmod. Make sure the download wasnt corrupted by doanloading everything again though, although ignore the bit about adb rboot bootloader, you need to start the phone manually by use power + volume-down key combination to get into bootloader when its powered off and continue from point 5.
Click to expand...
Click to collapse
So I didn't originally flash the recovery image, just booted into it. So I tried that again, but there is nowhere to find the SU_BusyBox_Pack.zip. I tried the sideload method, but ADB can't find my device any more. It shows nothing when I do adb devices.
what else can I try ?
Were you able to try wiping data through the stock recovery?
Sent from my Nexus 10 using XDA Premium HD app
getsky said:
So I didn't originally flash the recovery image, just booted into it. So I tried that again, but there is nowhere to find the SU_BusyBox_Pack.zip. I tried the sideload method, but ADB can't find my device any more. It shows nothing when I do adb devices.
what else can I try ?
Click to expand...
Click to collapse
I got stuck after just booting into recovery as well and immediately exit. Just use the volume key and change it until you see recovery, without going into it, I just fastboot flash recovery recovery.img from pc, then factory reset.
nyijedi said:
Don't freak out. I'm sure you're fine.
Unlocking the bootloader on my N10 caused me to hang at the X. Wiping data fixed it for me. Try the following:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time.
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
Click to expand...
Click to collapse
Yes that seemed to work. Thank you Thank you Thank you
I almost had a heart attack
getsky said:
Yes that seemed to work. Thank you Thank you Thank you
I almost had a heart attack
Click to expand...
Click to collapse
Ha. No problem, man. I'm glad it worked. I've been there before.
nyijedi said:
Unlocking the bootloader on my N10 caused me to hang at the X. Wiping data fixed it for me. Try the following:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time.
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
Click to expand...
Click to collapse
hi,
first timer here. i tried to get root using clockword mod following http://forum.xda-developers.com/showthread.php?t=2019273, but failed and get android mascot with the red exclamation point. following the above till #4 : Press Power and Volume Up at the same time, didn't bring me anywhere but turn off the device.
what should i do to get root ?
thank you,
After rooting ATT GS4 today, when I reboot the device, there is no longer a samsung Galaxy S4 on the first boot screen.
There is a unlock picture and a word "custom" under that. Anyone knows how can I get the original pic back to the first boot screen.
By the way, if there will be any rom having chinese display language for ATT i337?
Thanks!!
uclaxiwen said:
After rooting ATT GS4 today, when I reboot the device, there is no longer a samsung Galaxy S4 on the first boot screen.
There is a unlock picture and a word "custom" under that. Anyone knows how can I get the original pic back to the first boot screen.
By the way, if there will be any rom having chinese display language for ATT i337?
Thanks!!
Click to expand...
Click to collapse
This issue has already been widely discussed in the existing root threads for the i337 root method. As of yet, there is no way to restore the boot screen to original, or install custom ROMS, or reset (if any exist) flash counters, or install custom recoveries. Give it some time and I'm sure all will be taken care of. It's always a good practice to read through 100% of the posts in threads before doing anything to your phone. Just some advice.
In order to remove this icon you have to do a factory reset but before you that you will need to delete busybox from system bin /bin/
Use root explorer, delete busybox
Back up all data on the internal memory.
Turn off the device.
Press and hold the following three buttons at the same time:
Volume Up key
Home key
Power key.
When the phone vibrates, release the Power key but continue to press and hold the Volume Up key and the Home key.
When the Android System Recovery screen appears, release the Volume Up and Home keys.
Press the Volume down key to highlight 'wipe data / factory reset.'
Press Power button to select.
Press the Volume down key to highlight 'delete all user data.'
Press Power button to select and start the master reset.
When the master reset is complete, 'Reboot system now' is highlighted.
Press the Power key to turn the restart the device.
Then the icon will be gone
XsMagical said:
In order to remove this icon you have to do a factory reset but before you that you will need to delete busybox from system bin /bin/
Use root explorer, delete busybox
Back up all data on the internal memory.
Turn off the device.
Press and hold the following three buttons at the same time:
Volume Up key
Home key
Power key.
When the phone vibrates, release the Power key but continue to press and hold the Volume Up key and the Home key.
When the Android System Recovery screen appears, release the Volume Up and Home keys.
Press the Volume down key to highlight 'wipe data / factory reset.'
Press Power button to select.
Press the Volume down key to highlight 'delete all user data.'
Press Power button to select and start the master reset.
When the master reset is complete, 'Reboot system now' is highlighted.
Press the Power key to turn the restart the device.
Then the icon will be gone
Click to expand...
Click to collapse
Can anyone confirm that this works?
delete
I'm rooted. I don't get a different boot up sequence.
Perhaps it's because I installed SuperSU and deleted Superuser.
Sent from my Galaxy S4 using Tapatalk 2.
Didn't work for me =(
nvm it worked after another reboot
Sent from my iPad using Tapatalk HD
Baldilocks said:
I'm rooted. I don't get a different boot up sequence.
Perhaps it's because I installed SuperSU and deleted Superuser.
Sent from my Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
You also updated binaries first right after you installed supersu? Then you deleted supersu?
Because I followed that and it worked.
The only thing I'm getting upon boot up is this:
# Install Superuser
The su binary is out of date
I downloaded root explorer, but I dont see busybox
Which backup do I use?
THANKS
Use root explorer, delete busybox
Back up all data on the internal memory.
I have the same issue I need to put it back too 100% stock it's bother the heck out of me I tried
XsMagical Turtual I cannot get it fixed...... Do I need to reroot the device again and start over?
I couldn't find Busy Box also can anyone provide step by step guide please......
Thanks.....
Baldilocks said:
I'm rooted. I don't get a different boot up sequence.
Perhaps it's because I installed SuperSU and deleted Superuser.
Sent from my Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
Awesome find!
Sent from my GT-N7000 using xda premium
I found it
its in:
system/xbin
but I cannot get it to delete, I keep getting the read only error.
I did mount it as r/w so I dont know why I cannot delete it....
---------- Post added at 02:13 PM ---------- Previous post was at 01:56 PM ----------
After uninstalling superuser and installing supersu I still had the locked message.
That went away after a few reboots though...... so no more message, just the 'custom' message under device status......
I'm uploading a video right now. Give me a few to post it. It shows how to remove icon and keep root. And how to fully unroot too.
Stroked from my Dirty Nocturnal'd Galaxy S4
how do you grant permission to overwrite it or delete busy box file?
nvm figure it out....
animeware said:
how do you grant permission to overwrite it or delete busy box file?
Click to expand...
Click to collapse
If you hang till i get the video posted, it will answer all your questions.
XsMagical said:
In order to remove this icon you have to do a factory reset but before you that you will need to delete busybox from system bin /bin/
Use root explorer, delete busybox
Back up all data on the internal memory.
Turn off the device.
Press and hold the following three buttons at the same time:
Volume Up key
Home key
Power key.
When the phone vibrates, release the Power key but continue to press and hold the Volume Up key and the Home key.
When the Android System Recovery screen appears, release the Volume Up and Home keys.
Press the Volume down key to highlight 'wipe data / factory reset.'
Press Power button to select.
Press the Volume down key to highlight 'delete all user data.'
Press Power button to select and start the master reset.
When the master reset is complete, 'Reboot system now' is highlighted.
Press the Power key to turn the restart the device.
Then the icon will be gone
Click to expand...
Click to collapse
This fixed my problem thank you so much pale A++++
i have a better way to fix with out having to do a factory reset.
I made thread here to better help lost souls lol
http://forum.xda-developers.com/showthread.php?t=2257058
Please tell me not to flip out... lol. So here's the history. I rooted my phone, installed CWM w/ loki images, and next step was to get LMT pie control working. I have not installed any custom roms yet, still on stock. I had read that I needed to mod my build.prop file by adding the line "qemu.hw.mainkeys=1" to the bottom. Well, I couldn't get it to work by doing it on my phone, so i pulled it off of my phone using ADB "adb pull" / "adb push". I moved it to my computer, modded the file, and pushed it back. then i rebooted my phone and now i'm up the creek...
Please help me!!! I have no idea what to do... access the recovery somehow?
Ok... I can't get into CWM recovery (press and hold vol down and power until lg logo appears, release and press and hold again until access)... But I can get into download mode. So would you recommend I follow this guide? http://forum.xda-developers.com/showthread.php?t=2471370&highlight=boot+screen
in_dmand said:
Please tell me not to flip out... lol. So here's the history. I rooted my phone, installed CWM w/ loki images, and next step was to get LMT pie control working. I have not installed any custom roms yet, still on stock. I had read that I needed to mod my build.prop file by adding the line "qemu.hw.mainkeys=1" to the bottom. Well, I couldn't get it to work by doing it on my phone, so i pulled it off of my phone using ADB "adb pull" / "adb push". I moved it to my computer, modded the file, and pushed it back. then i rebooted my phone and now i'm up the creek...
Please help me!!! I have no idea what to do... access the recovery somehow?
Click to expand...
Click to collapse
Power + Volume Down until the LG logo disappears and appears again. Let go of Power+Vol Down for a moment and press them back again. Should bring you to a white screen asking if you want to factory reset your phone. Press Power button to confirm and it should then bring you to recovery. http://forum.xda-developers.com/showpost.php?p=46772831&postcount=8
I ran into the same issue with editing the build.prop. I created a restore point with twrp not sure if you did the same with CWM. You might need to add a new build.prop or remove the new line.
KD5SGS said:
Power + Volume Down until the LG logo disappears and appears again. Let go of Power+Vol Down for a moment and press them back again. Should bring you to a white screen asking if you want to factory reset your phone. Press Power button to confirm and it should then bring you to recovery. http://forum.xda-developers.com/showpost.php?p=46772831&postcount=8
I ran into the same issue with editing the build.prop. I created a restore point with twrp not sure if you did the same with CWM. You might need to add a new build.prop or remove the new line.
Click to expand...
Click to collapse
I should have but didn't create any restore point or nandroid... but it doesn't really matter because I can't access recover it doesn't seem... not with that method
Found the guide to flash it back to stock for verizon... gonna give this a shot when I get home on a pc (on a mac now).
Just wanted to give a quick update in case anyone has trouble =) The verizon guide didn't seem to work for me, but this method did! I'm back up and running =)