Database Develop

[question] root epe54b without touching boot loader for 2.2

I've seen the threads about rooting without unlocking, but I have a more specific question.
Could I root and flash to 2.2 without unlocking while reserving the option to flash back to completely stock including stock recovery and not touching boot loader back to 2.1 update 1.
I am asking specifically for epe54b on att. I've seen most threads were targeted for t mobile versions of n1.
Thanks for your help and pointing me in the right direction.
I really want my warranty kept intact.
Sent from my Nexus One using XDA app.

Another quick question, should I attempt to change the radio as well?
Sent from my Nexus One using XDA App

viper2g1 said:
Another quick question, should I attempt to change the radio as well?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
why don't you first try to see if adb can see you device in recovery first? 'cos i cannot
seems like that is the showstopper for me

So I tried what you suggested and I was unable to get into recovery, here are the steps I performed:
Step 0:
- Install the SDK
- Make sure there is no "update.zip" in SD card
- Connect your phone with the USB
- Extract all files I provided to your <SDK>/tools
Step 1:
Enable Debugging in Setting->Development
Then, shut down your phone
Step 2:
Booting into bootloader by holding vol- and press Power
Use vol- button to highlight "Recovery"
Step 3:
Open CMD, and cd to the <SDK>/tools
Run "loop"
Step 4:
Press Power to enter Recovery now, you will see the triangle and <!>
Hold Power and vol+ to show the menu
Step 4a:
If your CMD shows you the devices is in recovery, press control + c to stop the "loop"
Step 4b:
If there is nothing, reboot your phone and repeat step 2-4 until it shows up.
(This is 99% caused by the sd card, faster card make it easier to show up)
Click to expand...
Click to collapse
So is that it or should I try something else? Maybe a different SD card?

viper2g1 said:
So I tried what you suggested and I was unable to get into recovery, here are the steps I performed:
So is that it or should I try something else? Maybe a different SD card?
Click to expand...
Click to collapse
try without SD card first...
EDIT: you mean you cannot get into recovery or you cannot get adb to see your phone?

Problem was with adb seeing the phone. N1 went into recovery fine
Edit: I am able to see the device when it is powered on normally, but when I boot to recovery the device does not show up - SD card removed, driver set to sdk driver..
Sent from my Nexus One using XDA App

viper2g1 said:
Problem was with adb seeing the phone. N1 went into recovery fine
Edit: I am able to see the device when it is powered on normally, but when I boot to recovery the device does not show up - SD card removed, driver set to sdk driver..
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
that's exactly the same problem that i have....
guess we are stuck for now unless the official OTA for FRF83 will save the day...

I was afraid of that, well thanks for trying to help anyway

viper2g1 said:
I was afraid of that, well thanks for trying to help anyway
Click to expand...
Click to collapse
no worries, i also hope someone with a EPE54B can succeed too, but i guess we can only try again after we get the official OTA for FRF83...

kaiser_tytnii said:
no worries, i also hope someone with a EPE54B can succeed too, but i guess we can only try again after we get the official OTA for FRF83...
Click to expand...
Click to collapse
I am quite sure you guys can gain root shortly

Booker-T said:
I am quite sure you guys can gain root shortly
Click to expand...
Click to collapse
Yup let's work it out!
Sent from my Nexus One using XDA App

I heard it will be FRF85B for us EPE54B users. Hope root without unlock will still be possible. Google sucks in differentiating software builds for the same hardware (except for the radio!)...

[FIX] Enable download mode by force adb push update.zip without permission

MY Phone Condition:
My phone was previously install with voodoo rom and use clockwork recovery to restore to my stock rom that i backup and it crash half way.
My phone was hardware lock this mean no matter how i press the volume and power button , i will never get into download mode. non of the method posted work !
My phone cannot use "adb reboot download" because there is no OS and it was stuck in the recovery loop.
It does not have clockwork recovery because i formatted my internal sdcard
If i do have clockwork recovery and i use restore image or install new from zip , i still stuck in the recovery mode after reboot several times.
My phone does not mount to internal sdcard because i don't even know what i did on this part.
I believe i screw up my partition of the phone.
DO IT AT YOUR OWN RISK.
You need the Samsung USB driver and you can get it from Here
http://forum.xda-developers.com/showthread.php?t=728929
First Part
1. Download update.zip from the link below. This was post by another member.
The post is here http://forum.xda-developers.com/showthread.php?t=804305
2. Place the update.zip in tools folder so you can push it into your phone by using adb command
3. Plug usb into the phone and your phone should be on the Android system recovery <2e>
4. Use your volume button to select reinstall package, don't press power button yet.
5. constant "adb push update.zip /sdcard" from computer , you will get permission denied.
6. While you are constantly pushing the adb command from computer. press the power button on the phone so it install update.zip from sdcard.
7. This is the part where it force adb push into sdcard without permission
8. once the update.zip install completed. unplug the usb cable from the phone and take the battery out.
9. put the battery back to the phone then press on both volume button.
10. While holding both volume button , plug in your usb cable and it will boot to download screen.
If you need use Odin to flash your phone to original stock rom. Go to the Second Part

Second Part:
If you get black screen with only 4 light on the bottom after flashing from Odin.
Follow http://forum.xda-developers.com/showthread.php?t=728698
There should be T959-PDA.tar,T959-CSC.tar and T959-Phone.tar within the package.
Check "Re-Partition" , "Auto Reboot" and "F.Reset Time" check box. Use the PIT 0512 version. Use "PDA", "PHONE" and "CSC" from the link above.
After flashing with Odin, you will loose the download mode. repeat the first part and you are good to go.
Here is the link on rooting the phone
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Samsung_Galaxy_S_(Vibrant)

If your phone is hardware locked, how are you able to get into recovery? Hardware locked phone means no recovery and download mode.
Sent from my SGH-T959 using XDA App

mr2t32 said:
If your phone is hardware locked, how are you able to get into recovery? Hardware locked phone means no recovery and download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
my hardware lock mean cannot use the button method to get into download mode and using adb reboot download does not help too.

Im pretty sure hardware lock does not mean no recovery. Just no button download mode
Sent from my SGH-T959 using XDA App

you saved my life man. thank you so much. this was the only thing that worked, after days of frustration

No, it means both.
Sent from my SGH-T959 using XDA App

muncknr said:
you saved my life man. thank you so much. this was the only thing that worked, after days of frustration
Click to expand...
Click to collapse
i was about to give up. i was trying to push update.zip and do adb reboot download left and right and no luck untill i found this method. It took me a week to figure it out

wildklymr said:
No, it means both.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
my recovery was working because i was stuck in the a loop. ya , this update.zip pretty much do both download mode and recovery mode.

What the point of this? Does the other thread not cover this??

Master™ said:
What the point of this? Does the other thread not cover this??
Click to expand...
Click to collapse
Are you asking or you are insulting ?

jaex said:
Are you asking or you are insulting ?
Click to expand...
Click to collapse
probably asking. Considering there is another thread on the same topic that has been on the front page for over a week now, with several pages of replies.
http://forum.xda-developers.com/showthread.php?t=804305
EDIT: So you were bricked and hardware locked and got yourself out of it? If thats the case then yets its different than that thread and why didn't you just come out and say it?

nermie said:
probably asking. Considering there is another thread on the same topic that has been on the front page for over a week now, with several pages of replies.
http://forum.xda-developers.com/showthread.php?t=804305
EDIT: So you were bricked and hardware locked and got yourself out of it? If thats the case then yets its different than that thread and why didn't you just come out and say it?
Click to expand...
Click to collapse
You figure it out after all. I already stated the condition of my phone ! My phone was pretty bricked at that point. There is way for me to push any files into the phone because i don't have permission and my phone will not go to download mode by using the volume button. It just stuck at recovery mode.
There are guide out there teach you to use "adb push download". This method only work if you are in your phone and you turn on debug mode. My phone crash at the clockwork recovery bootloader. Then i formated my internal sdcard that hold the clockwork. next i push a stock update.zip that does not have su and busybox so i lost the capability to push anything into the phone.
no download mode , no permission, no sdcard --> You tell me how can i use the method that post few week ago ?

muncknr said:
you saved my life man. thank you so much. this was the only thing that worked, after days of frustration
Click to expand...
Click to collapse
Thank You

Thank ! You save my phone !

unfortunately, i was one of those careless people to brick my phone via Voodoo.
Firstly, i tried to "FLASH" the disable_voodoo zip file via Clockwork, i put it in root, and never created any folders. i knew i had to disable voodoo before flashing but my steps were wrong.
sadly enough, my phone was also HW locked, so i got it exchanged. now im not using voodoo YET and i my new vibrant can handle OC and has the recovery/download mode via buttons.

atlaswingpasaway said:
unfortunately, i was one of those careless people to brick my phone via Voodoo.
Firstly, i tried to "FLASH" the disable_voodoo zip file via Clockwork, i put it in root, and never created any folders. i knew i had to disable voodoo before flashing but my steps were wrong.
sadly enough, my phone was also HW locked, so i got it exchanged. now im not using voodoo YET and i my new vibrant can handle OC and has the recovery/download mode via buttons.
Click to expand...
Click to collapse
i use shell to create the file that disable voodoo. after disable voodoo , i was able to do restore and install new rom unfortunately after restore or install new rom , it still reboot into recovery.

I also forgot to disable voodoo, and this was before there were fix instructions posted. So i basically effed up my phone to the point of being stuck in the samsung recovery loop, no hardware download mode, no clockwork recovery, no update.zp, no adb download.
I really thought I had completely bricked my phone, I tried this just out of desperation and what do you know, push update.zip over and over and click and it goes through, which allowed me to get into download mode.

muncknr said:
I also forgot to disable voodoo, and this was before there were fix instructions posted. So i basically effed up my phone to the point of being stuck in the samsung recovery loop, no hardware download mode, no clockwork recovery, no update.zp, no adb download.
I really thought I had completely bricked my phone, I tried this just out of desperation and what do you know, push update.zip over and over and click and it goes through, which allowed me to get into download mode.
Click to expand...
Click to collapse
nice , you just have to re-root and install the new rom again , if it brick again , just use this method and you are good again.many of us forgot to disable the voodoo before we restore or install new rom and this crashes the phone.

Need some help really bad
Ok so I have a similar situation as you did (OP), only mine is a bit worse... In my irrational "in the moment" fear of the situation, I used adb reboot recovery to get into recovery mode (HW locked phone) and I did the option that deletes all the **** on the phone and restores the phone to its original format (I think it reinstalled the OS or something, because it looks brand new). So now, whenever I boot up, it does the annoying black screen with the 4 glowing buttons thing for a while, and then eventually the OS actually shows up on the screen. Then it does "scanning media" thing over and over again, but thats not the main problem. I figured, hey this isnt so bad atleast I found your thread and would be able to use your method to help restore my phone... the problem is that somehow my "settings" button is totally gone from the app menu, and I cant get it into debug mode, so I cant use either adb or your method or ANYTHING!! My phone is practically bricked as I cant do anything because its constantly laggy and turns back to the black screen thing, and then when it is showing the homescreen I cant do **** because even swiping to another screen takes like 5 minutes to do cause its so laggy. So basically I ****ed up, and I really need some help.. Im kinda a noob at this whole thing and im really outa options as far as I can tell.. does anyone know what I can do to repair my phone? Thanks!

[Q] wtf. I just CAN NOT get my phone into recovery mode

I was on Continuum and decided to flash back to stock. Of course Odin would freeze, forcing me to break out my jig.
I finally got it into download mode and flashed back to stock
I used SuperOneClick (like I have so many times before) to root and enable non-market installations
Well, it rooted just fine, but I couldn't enable the non-market stuff, it says "reloc_library[1251]: 2738 cannot locate '_ZNK7android6Parcel15setDataPositionEj'... CANNOT LINK EXECUTABLE
I cant get my captivate into recovery through 3-button boot, and ROM manager is completely unresponsive. When I click "reboot into recovery" it just does nothing. Same with installing a rom, or restoring a back-up. Any ideas?

Hmmm... It sounds like you might need to reflash the phone...
Can you try this alternate method to put your phone into Download Mode?
1. Turn off your phone, pull out the battery.
2. Hold both volume UP and DOWN buttoms (and keep holding them until the end).
3. Put in your battery.
4. Plug in the USB. (You won't need to ever press the power button using this method).
If that doesn't work, you might need to get a USB Jig somewhere (either buying one or making one yourself).

this can help, 3 button fix http://forum.xda-developers.com/showthread.php?t=812434

I think you missed the point where he said Rom Manager or CWM Recovery isn't working.

venomio said:
I think you missed the point where he said Rom Manager or CWM Recovery isn't working.
Click to expand...
Click to collapse
omg. I love you for that comment. I KNEW, just knew some idiot was going to say that. "um..blah blah..3buttonfix...blah"

demonblod said:
omg. I love you for that comment. I KNEW, just knew some idiot was going to say that. "um..blah blah..3buttonfix...blah"
Click to expand...
Click to collapse
If you are not bricked (means phone-!-computer screen) then you can use ADB method to go into recovery then just reinstall CWM.zip folder...that works for me....see the link for youtube video tutorial. if u need Clockworkrecovery.zip..just hollar
http://www.youtube.com/watch?v=2fMk0PhA_qc&feature=relmfu

demonblod said:
omg. I love you for that comment. I KNEW, just knew some idiot was going to say that. "um..blah blah..3buttonfix...blah"
Click to expand...
Click to collapse
nothing to say. just want to help. if it's not, dont need that aggressive. hope u can fix it

viny2cool said:
If you are not bricked (means phone-!-computer screen) then you can use ADB method to go into recovery then just reinstall CWM.zip folder...that works for me....see the link for youtube video tutorial. if u need Clockworkrecovery.zip..just hollar
http://www.youtube.com/watch?v=2fMk0PhA_qc&feature=relmfu
Click to expand...
Click to collapse
Not really sure if it would work, but I guess it depends on if he can get the phone's USB Debugging menu to turn on.

venomio said:
Not really sure if it would work, but I guess it depends on if he can get the phone's USB Debugging menu to turn on.
Click to expand...
Click to collapse
He didnt brick it, just not able to flash recovery or enable non market apps...so he can turn on USB debugging

viny2cool said:
He didnt brick it, just not able to flash recovery or enable non market apps...so he can turn on USB debugging
Click to expand...
Click to collapse
It's the "non market app" part that's concerning me. If he gets an error with that, you can't say for sure that he won't get another error with USB Debugging.

venomio said:
It's the "non market app" part that's concerning me. If he gets an error with that, you can't say for sure that he won't get another error with USB Debugging.
Click to expand...
Click to collapse
that's him to answer now...lol

demonblod said:
I was on Continuum and decided to flash back to stock. Of course Odin would freeze, forcing me to break out my jig.
I finally got it into download mode and flashed back to stock
I used SuperOneClick (like I have so many times before) to root and enable non-market installations
Well, it rooted just fine, but I couldn't enable the non-market stuff, it says "reloc_library[1251]: 2738 cannot locate '_ZNK7android6Parcel15setDataPositionEj'... CANNOT LINK EXECUTABLE
I cant get my captivate into recovery through 3-button boot, and ROM manager is completely unresponsive. When I click "reboot into recovery" it just does nothing. Same with installing a rom, or restoring a back-up. Any ideas?
Click to expand...
Click to collapse
well if you're on stock you can't enable non market app it's not included in the package plain and simple. but if you can push update zip into your internal sd and flash cwm recovery you maybe able to flash an app apk's there. the problem is you have unresponsive button combos. solve the button combos first. you will likely need a jig or if you can get into download mode try installing the leaked froyo maybe it will solve your unresponsive buttons.

I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on th

I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?

morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
Are you running stock, or did you root and customize?

Try plugging it in to a computer. A lot of us are finding better results when you do. You may end up having to do more. But just being connected to a computer has helped in the past. Quick fix before you start trying adb
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2

Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.

kiewee3 said:
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
Click to expand...
Click to collapse
Err ..... it won't boot.
Does ADB work at this stage? Assuming you are rooted with CWM recovery, try
Code:
adb reboot recovery
Then from recovery, power it off completely. If fastboot is the problem, this should workaround it for you.

morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
It's karma because of your ridiculous signature.
Anywho. What did you do to the device? Attempt to root it? What happened between it working and not working?

khaytsus said:
It's karma because of your ridiculous signature.
Click to expand...
Click to collapse
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.

it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!

wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
Right. I can't figure out why people think others want to see large pictures of their crap.

just lou said:
Right. I can't figure out why people think others want to see large pictures of their crap.
Click to expand...
Click to collapse
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).

Rock-&-Roll-Hedgehog said:
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Click to expand...
Click to collapse
Oh. Now I see.

The nice thing is that Signatures can be disabled if you so choose, it'd just be nice if everyone kept a modestly sized signature.

wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
XDA Signatures: The new Geociities
morell2 said:
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
Click to expand...
Click to collapse
wat?
When you oem unlock, data is deleted, it tells you that. Otherwise, no idea what you're talking about.

Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7

evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.

evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
wmoore said:
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
Click to expand...
Click to collapse
Not neccessarily true. I use an app called Quick boot. I can boot into recovery from it with Ease. Lets me set up Widgets/icon for recovery and I have one for reboot. No need for me to hook up to pc. Anywhere at anytime I can boot into recovery on my Nexus 7. I can also set one up for bootloader. If someone gets stuck on bootloader screen, the hardware button press for reboot works to get out of there.
They have a free version of the app and it works perfectly. Check it out. No need to run to a pc everytime you want to flash a rom or something. Battery is nothing to worry about. As long as you have 50%(really even less than that), you good to flash, wipe, or what ever.

demandarin said:
Not neccessarily true. I use an app called Quick boot.
Click to expand...
Click to collapse
Me too. Though I'm old school and still like to type commands rather than point and click. I'll be looking at Quick Boot but still go to PowerShell (which I always have open) and type adb reboot.:silly:

All the various apps that offer rebooting options will work as they are still executing the same terminal commands that you would've had to type in in order to reboot it.
The issue is that you would still require a working system partition in order to boot into recovery (stock/twrp/cwm) without any USB connection. Incase of a soft brick, you will need to connect to a computer in order to get into recovery so i would suggest people make sure they have one nearby when they're flashing stuff.

I just went through this. I boinked my setup and it was bootlooping. I couldn't get into CWM.
Just press and hold Power+VolDwn+VolUp until you get into the stock bootloader. Now plug in your USB to to a PC.
Stay in the bootloader. Mine actually kinda froze but it will unfreeze after a while. Don't select anything. Just stay there.
Now you can use Fastboot commands to reboot into CWM. ADB only works when the phone is on.
I think the command is "fastboot reboot recovery".
This will put you in CWM. You can also take this opportunity to reflash your recovery here too. I reflashed mine just to be on the safe side before rebooting it.
Sent from my Nexus 7 using xda premium

I cannot get in the CWM with my bricked Optimus 4X HD, need some help...

Hey guyz,
I have a problem with reflash a stock rom onto my phone, I tried to explain the issue on the video below, I really hope you can help me...
www.youtube.com/watch?v=sQD7xqgH4GI

memo357 said:
Hey guyz,
I have a problem with reflash a stock rom onto my phone, I tried to explain the issue on the video below, I really hope you can help me...
www.youtube.com/watch?v=sQD7xqgH4GI
Click to expand...
Click to collapse
First of all search. Everything is already explained.
Flash kdz and then set up again(root,bootloader,CWM..)

brunek said:
First of all search. Everything is already explained.
Flash kdz and then set up again(root,bootloader,CWM..)
Click to expand...
Click to collapse
The problem is that I can not connect the phone so I cannot flash the KDZ, do you have a good tutorial how I can flash it?

Have you already got CWM installed on your phone? If you have you need to do power on and volume up, not volume down so put a ROM on the SD card first, full wipe and flash a new ROM and gapps.. If that doesn't work then you need to try get adb access, and run commands such as adb reboot recovery etc, otherwise you need to reflash the .kdz of stock, if you search you'll find it!
Sent from my Nexus 7 using XDA Premium 4 mobile app

bionicsquirell said:
Have you already got CWM installed on your phone? If you have you need to do power on and volume up, not volume down so put a ROM on the SD card first, full wipe and flash a new ROM and gapps.. If that doesn't work then you need to try get adb access, and run commands such as adb reboot recovery etc, otherwise you need to reflash the .kdz of stock, if you search you'll find it!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey Bionic, do you know a good tutorial how I can get adb acces onto my phone?

@bionicsquirell It is volume DOWN + Power button don't spread misinfos.
@memo357 did you try holding Volume down while plugging into the PC? See if it will light up and show new devices on PC, then start searching here and you'll figure it out. If nothing happens, you're in too deep I'm afraid..

X610 said:
@bionicsquirell It is volume DOWN + Power button don't spread misinfos.
@memo357 did you try holding Volume down while plugging into the PC? See if it will light up and show new devices on PC, then start searching here and you'll figure it out. If nothing happens, you're in too deep I'm afraid..
Click to expand...
Click to collapse
Volume UP still works to boot to recovery, just tried it now, its not misinfo ^.^
If your bootlooping maybe you could use adb to reboot to recovery!

I had this problem. I had to flash the stock boot loader on. Google search should have an lg exe for it. And instructions. I found it pretty easy and once back it should work. You will have to root again and just make sure you unlock your bootloader before applying a custom recover. The exe is called LG mobile support tool, the exe to restore the bootloader.
Sent from my GT-I9000 using xda app-developers app