I tried flashing the CWM 3.1.0.1 PURPLE bzImage directly to /dev/block/bml8 using redbend_ua. It seemed to flash I think and then the phone soft rebooted. I tried to enter the recover menu by going to ROM Manger and selecting 'reboot into recovery. Which I think was where I may have messed up beyond repair. When booting the phone now gets stuck at the Samsung logo and won't go any further. I'm guessing since i didn't use the button shortcut for endering recovery mode now every time the phone boots it tries to boot the recovery partition which is now foobared it seems. Is there any way to make the phone boot normally or am I boned?
I don't think that works for us. Power off phone and press vol down, camera, and power st the same time to get to recovery.
you are NOT bricked.
You can also go into download mode and odin back to stock if necessary.
Check out qbking77's youtube to see how.
Sent from my SPH-D700 using XDA App
I've tried using the button shortcut to get to recover mode a few times.. Never loads. Just sits there forever.. tried the download mode shortcut too but that also just sits at the samsung logo. The download mode shortcut i tried was volume down and power.
No download mode is holding 1 on the keyboard and hold power. Then u can flash something with odin or heimdale. That's your only options if u can't get to recover. If the phone boots its nit bricked.
"The greatest respect you can earn is self respect" Louie Simmons
Oh sorry I was mistaken. I did try holding 1 on the keyboard to get to the download mode. Still only shows the samsung logo. Guess i'll be going by a store in the morning.
EDIT:
Anyone know where I might have gone wrong? I downloaded the oneclick root and copied all the recovery files to /system/bin/ as the oneclick would. Set permissions for all the recover files to 0755 as the one click would. Copied redbend_ua to /data/local and the zImage for CWM 3.1.0.1 PURPLE to /data/local/tmp and ran 'redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
I was fairly confident that would work but it seems I was wrong.
One click must be downloaded to your computer then extracted and run the run.bat plug your phone in and click enter. That's it. Not suposed to put files into the phone directly.
Sent from my SPH-D700 using XDA Premium App
If you are getting the Samsung logo you are doing it wrong. Turn off the phone. Pull the battery. Put the battery back in. Pull out the key board. Put your finger on the 1 key and hold it down. While holding the 1 key press and hold the power button. Download mode will appear.
And to get into recovery properly press and hold the camera button first, then add pressing and holding volume down, then add pressing and holding power button until the recovery menu appears. Order is important.
Esteway.619 said:
One click must be downloaded to your computer then extracted and run the run.bat plug your phone in and click enter. That's it. Not suposed to put files into the phone directly.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Exactly. Also, there is a flashable zip for cwm 3.1.0.1. Who gave you the idea of putting these things in files? You will need to odin to ec05 before using the oneclick root exploit. You can pm me if you want for faster responses
Sent from my Epic 4G using XDA Premium App
All the oneclick does is use adb or whatever to execute commands on the phone itself. I basically did the exact same thing except using shell on the device itself to do all the commands as at the time I didn't have a computer I could connect to to actually use the 'one click'. Also I've never been able to get the windows drivers to work.
I was actually able to get into the download mode. I then used heimdall on my linux box to flash Froyo EC05 Prerooted/ClockWorkMod v2.5.1.0 (RFS Filesystem) Odexed. NO DATA WIPE/LOSS !! using the below command.
I tried to link to the zip file I used but i can't link to outside sites yet.
Code:
./heimdall flash --cache cache.rfs --kernel zImage --recovery recovery.bin --factoryfs factoryfs.rfs --modem modem.bin
I probably didn't need to do the factoryfs or modem options.
After that I was able to easily install the clean kernel and CWM 3.1.0.1 and everything is all good now.
phaze82 said:
All the oneclick does is use adb or whatever to execute commands on the phone itself. I basically did the exact same thing except using shell on the device itself to do all the commands as at the time I didn't have a computer I could connect to to actually use the 'one click'. Also I've never been able to get the windows drivers to work.
I was actually able to get into the download mode. I then used heimdall on my linux box to flash Froyo EC05 Prerooted/ClockWorkMod v2.5.1.0 (RFS Filesystem) Odexed. NO DATA WIPE/LOSS !! using the below command.
I tried to link to the zip file I used but i can't link to outside sites yet.
Code:
./heimdall flash --cache cache.rfs --kernel zImage --recovery recovery.bin --factoryfs factoryfs.rfs --modem modem.bin
I probably didn't need to do the factoryfs or modem options.
After that I was able to easily install the clean kernel and CWM 3.1.0.1 and everything is all good now.
Click to expand...
Click to collapse
Glad you are back up and running.
kennyglass123 said:
And to get into recovery properly press and hold the camera button first, then add pressing and holding volume down, then add pressing and holding power button until the recovery menu appears. Order is important.
Click to expand...
Click to collapse
THANKS! Order is important and now I know that. I tried 3 times with the results the same... always hung at the Samsung logo.
Really appreciate the input!
Related
what do i do?
i rooted with wug fresh toolkit, no problem,
installed rom manager, backed up, no problem.
installed a new rom seemed to install ok but it got stuck on the splash screen...
couldnt turn off so pulled the battery just kept doing the same, so i used the toolkit to try and oem lock it back to factory but no joy.
im now getting phone...a yellow triangle with exclamation in and a computer screen
however it is showing up on odin but the stock flash fails every time
i cant get into download mode either.
any ideas?
wrong section.
Wrong section, but that's why you don't use toolkits to help you root and do stuff for your phone. Learning how to use adb can be very useful in solving these kinds of problems. Just try to find some more guides to help you flash back to stock.
acatabian said:
wrong section.
Click to expand...
Click to collapse
thanks for the help :S
big_mike_aka_mike said:
what do i do?
i rooted with wug fresh toolkit, no problem,
installed rom manager, backed up, no problem.
installed a new rom seemed to install ok but it got stuck on the splash screen...
couldnt turn off so pulled the battery just kept doing the same, so i used the toolkit to try and oem lock it back to factory but no joy.
im now getting phone...a yellow triangle with exclamation in and a computer screen
however it is showing up on odin but the stock flash fails every time
i cant get into download mode either.
any ideas?
Click to expand...
Click to collapse
As someone mentioned, this is wrong section.. But still would like to help you.
It is very hard to Brick Galaxy Nexus. It is a robust phone which i have seen.
1. Download and install http://forum.xda-developers.com/showthread.php?t=1392310
2. Put your phone to fastboot mode. (steps are, remove battery and put back, hold volume up and down together and press power button... It will take you to "Start" screen.. using volume up and down look for bootloader.. once seeing bootloader on the screen press power button.)
3. Connect to your PC having the Toolkit (see step 1 above) installed
4. Download factory image from here, https://dl.google.com/dl/android/aosp/yakju-imm76d-factory-c6e807a1.tgz
5. Copy the above factory image file to the folder "put_google_factory_image_here"
6. Open the "ToolKit.exe"
7. Select option 3
8. Select option 8
9. Wait for the flashing to complete
Your phone will be back to normal with 4.0.4 on it.
Hope it helps.
its step 2 im struggling with everything i try brings up the same screen
like this...
http://a4.sphotos.ak.fbcdn.net/hpho...195650660_613955659_11998868_2026245841_n.jpg
big_mike_aka_mike said:
its step 2 im struggling with everything i try brings up the same screen
like this...
http://a4.sphotos.ak.fbcdn.net/hpho...195650660_613955659_11998868_2026245841_n.jpg
Click to expand...
Click to collapse
I had issue few weeks ago.. Once you pull out the battery do not put in immediately. Leave it for few min. Now put the battery back. Press and hold both volume up and down together... Then press power button.. continue to hold all these three button until you see "start" in green colour appear..
smohanv said:
As someone mentioned, this is wrong section.. But still would like to help you.
It is very hard to Brick Galaxy Nexus. It is a robust phone which i have seen.
1. Download and install http://forum.xda-developers.com/showthread.php?t=1392310
2. Put your phone to fastboot mode. (steps are, remove battery and put back, hold volume up and down together and press power button... It will take you to "Start" screen.. using volume up and down look for bootloader.. once seeing bootloader on the screen press power button.)
3. Connect to your PC having the Toolkit (see step 1 above) installed
4. Download factory image from here, https://dl.google.com/dl/android/aosp/yakju-imm76d-factory-c6e807a1.tgz
5. Copy the above factory image file to the folder "put_google_factory_image_here"
6. Open the "ToolKit.exe"
7. Select option 3
8. Select option 8
9. Wait for the flashing to complete
Your phone will be back to normal with 4.0.4 on it.
Hope it helps.
Click to expand...
Click to collapse
it is a bit different step 2...after holding vol and power like you say,and you see "start" in bootloader screen's,you should not scroll until "bootloader" because there isn't this!(choice are reboot bootloader\recovery\start\power off i remember..)you are already on the fastboot mode.connect the phone on pc and go straight on with step 3.
smohanv said:
I had issue few weeks ago.. Once you pull out the battery do not put in immediately. Leave it for few min. Now put the battery back. Press and hold both volume up and down together... Then press power button.. continue to hold all these three button until you see "start" in green colour appear..
Click to expand...
Click to collapse
ok ill keep trying.
many thanks ill report back
sert00 said:
it is a bit different step 2...after holding vol and power like you say,and you see "start" in bootloader screen's,you should not scroll until "bootloader" because there isn't this!(choice are reboot bootloader\recovery\start\power off i remember..)you are already on the fastboot mode.connect the phone on pc and go straight on with step 3.
Click to expand...
Click to collapse
Yes. You are correct.. My fault..
Thanks
After you get to bootloader and flash factory (links in my guide under "panic")
Use my guide to get you rooted again.
im stuck cant get past this bloody image i posted earlier. battery in or out... plugged in or not plugged in... volume down or middle of volume button pressed!
im screwed .....
big_mike_aka_mike said:
im stuck cant get past this bloody image i posted earlier. battery in or out... plugged in or not plugged in... volume down or middle of volume button pressed!
im screwed .....
Click to expand...
Click to collapse
Can you access fastboot/adb?
Jubakuba said:
Can you access fastboot/adb?
Click to expand...
Click to collapse
abd? sorry but how do i do that? odin can see it when it plugged in if that helps.
Woah.
Adb sir.
You should stay away from those toolkits from here out.
You are NOT screwed.
And ODIN recognizing is a good thing.
Use it?
If it doesn't work...
Try my guide (siggy) to set up adb...and I'll follow through when you're done.
to make sure it worked...
Run "adb devices" rather than following the "how to root" steps.
It should list a number.
Jubakuba said:
Woah.
Adb sir.
You should stay away from those toolkits from here out.
You are NOT screwed.
And ODIN recognizing is a good thing.
Use it?
If it doesn't work...
Try my guide (siggy) to set up adb...and I'll follow through when you're done.
to make sure it worked...
Run "adb devices" rather than following the "how to root" steps.
It should list a number.
Click to expand...
Click to collapse
ODIN fail's doesnt pass like it should.
"Now, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder."
does the first .exe file create the C:\android-sdk-windows\platform-tools folder for you?
big_mike_aka_mike said:
ODIN fail's doesnt pass like it should.
"Now, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder."
does the first .exe file create the C:\android-sdk-windows\platform-tools folder for you?
Click to expand...
Click to collapse
use the latest odin and it will work
here a thread of a guy that solved it http://forum.xda-developers.com/showthread.php?t=1413779&page=3
here some info about odin http://forum.xda-developers.com/showthread.php?t=1394051&highlight=odin+stock
u can solve it if u want
big_mike_aka_mike said:
ODIN fail's doesnt pass like it should.
"Now, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder."
does the first .exe file create the C:\android-sdk-windows\platform-tools folder for you?
Click to expand...
Click to collapse
The ADB dummies app does.
Edit:
There is also a 1.3 of odin...
http://www.google.com/url?sa=t&rct=...vBed00cYo5qGMKjtg&sig2=TZqQcfklkJdfez4iwZFKuQ
The latest is 1.85 , in my previous post
Sent from my Galaxy Nexus using Tapatalk 2
big_mike_aka_mike said:
im stuck cant get past this bloody image i posted earlier. battery in or out... plugged in or not plugged in... volume down or middle of volume button pressed!
im screwed .....
Click to expand...
Click to collapse
I don't think you're booting into fastboot. To do so, hold down the VOL+ and VOL- keys while powering on. That should get you into fastboot where you can either flash the stock images or install CWM again (in order to wipe/flash another ROM).
Hi everyone.....
after trying to install CM7.2 using this Guide by ridder215215 I ran into a weird problem.
*I was running R800a 2.3.4 rooted and with an unlcoked bootloader.
after I flashed the Kernel and rebooted the phone (step #6,7) the phone just died after the reboot.
I couldn't get it into Clockwordmode what ever I do I only get a vibration and the screen turns on with a black background.
after a miracle I got my phone into recovery mode and flashed the R800a firmware using flashtool. then I tried to install CM7.2 again.
the same problem occurred.... but now, I can't even get the phone into recovery mod to flash a stock rom!!!
HELP!!!!!
how can I force a recovery mode???
if anyone can propose an idea on how to install CM7.2, I would really appreciate it!
Right, using flash tool, select the stock ftf you want to return to (2.3.4 by the look of it) and set it off preparing the file for flashing. When it prompts you, with the phone turned off, hold the back button and connect your USB. That should put you back to stock firmware.
Now for CM7:
With the CM7 zip on your computer, extract the "boot.img" file located within and drop it int your fastboot folder within your Android SDK folder (usually platform-tools folder within the SDK folder). Make sure not to unzip the file. If you're using WinRAR, just double click the file and drag the boot file onto your desktop then move it from there to your fastboot folder.
Move the CM7 zip (now minus the boot.img) onto your SD Card. Also download the Google Apps (Gapps) zip to your SD
Turn your phone off. In your folder with the boot.img hold shift and right click, open command window here.
Hold the search button on your phone and connect it to your PC. type the following: fastboot flash boot boot.img
After thats done type fastboot boot boot.img and you should hear the USB disconnected sound. Your phone will then reboot. Keep spamming the Volume Down and Back button (some kernels use either one so spamming both always works) and you should get into CWM.
From there, Factoryreset/data wipe...Wipe cache...Advanced, Wipe dalvik cache.
With those wiped, you can flash the ROM with CWM.
You want to "choose zip from sd" and select the CM7 zip file. Wait for it to do its stuff then using the same method, flash the gapps.zip package.
Reboot (first one takes a while) and enjoy
CTU_Loscombe said:
Right, using flash tool, select the stock ftf you want to return to (2.3.4 by the look of it) and set it off preparing the file for flashing. When it prompts you, with the phone turned off, hold the back button and connect your USB. That should put you back to stock firmware.
Now for CM7:
With the CM7 zip on your computer, extract the "boot.img" file located within and drop it int your fastboot folder within your Android SDK folder (usually platform-tools folder within the SDK folder). Make sure not to unzip the file. If you're using WinRAR, just double click the file and drag the boot file onto your desktop then move it from there to your fastboot folder.
Move the CM7 zip (now minus the boot.img) onto your SD Card. Also download the Google Apps (Gapps) zip to your SD
Turn your phone off. In your folder with the boot.img hold shift and right click, open command window here.
Hold the search button on your phone and connect it to your PC. type the following: fastboot flash boot boot.img
After thats done type fastboot boot boot.img and you should hear the USB disconnected sound. Your phone will then reboot. Keep spamming the Volume Down and Back button (some kernels use either one so spamming both always works) and you should get into CWM.
From there, Factoryreset/data wipe...Wipe cache...Advanced, Wipe dalvik cache.
With those wiped, you can flash the ROM with CWM.
You want to "choose zip from sd" and select the CM7 zip file. Wait for it to do its stuff then using the same method, flash the gapps.zip package.
Reboot (first one takes a while) and enjoy
Click to expand...
Click to collapse
I'll try that when I get my phone into recovery mode to flash the stock firmware....
thanks
I still can't get my phone into recovery mode.... anyone?
FRKD said:
I still can't get my phone into recovery mode.... anyone?
Click to expand...
Click to collapse
Did you install cwm from that "cwm installer" app from the market?
agraceful said:
Did you install cwm from that "cwm installer" app from the market?
Click to expand...
Click to collapse
YES!
is that the problem?
can anyone tell me a way of putting my phone into recovery(flash) mode???
it's just not working!
get your phone into flash recovery doing this:
Remove battery, connect usb cable, hold the back button and insert battery, your phone should start in flash recovery, flash a stock ftf
when thats done, youll have to root your phone(you can do it via flashtool) then install
busybox through flashtool then install this cwm : http://www.mediafire.com/?u26cuggxd2x54vb
inside the archive theres several files run the one that says cwm1
then when the sony logo appears check the led on your play as soon as it turns blue, tap the volume - button on a rampage, it will get you inside clockworkmod recovery.
i find it easier to flash the boot image through flashtool might want to give it a shot. hope i helped.
elnacho said:
get your phone into flash recovery doing this:
Remove battery, connect usb cable, hold the back button and insert battery, your phone should start in flash recovery, flash a stock ftf
when thats done, youll have to root your phone(you can do it via flashtool) then install
busybox through flashtool then install this cwm : http://www.mediafire.com/?u26cuggxd2x54vb
inside the archive theres several files run the one that says cwm1
then when the sony logo appears check the led on your play as soon as it turns blue, tap the volume - button on a rampage, it will get you inside clockworkmod recovery.
i find it easier to flash the boot image through flashtool might want to give it a shot. hope i helped.
Click to expand...
Click to collapse
The flash recovery method didn't work ;(
does the phone boot at all?
elnacho said:
does the phone boot at all?
Click to expand...
Click to collapse
I get nothing but a vibration and the screen lights up with a black backround
but when I plug it to the computer, I don't get the vibration
if you turn your phone off, then hold the back key while connecting the usb, does the led on your power button light up on any color?
no light, no color );
how about fastboot, if you turn the phone off and while you hold the search button you plug the usb is there a blue light?
elnacho said:
how about fastboot, if you turn the phone off and while you hold the search button you plug the usb is there a blue light?
Click to expand...
Click to collapse
nope.... i even tried the circle, X, triangle, and square buttons...
HAHA... Thanks elnacho!!!
I was so desperate I started blowing at the buttons and it worked!!!
now, i have another question.
I flashed the stock att rom (R800at) unlocked and rooted, can I install CM9 or CM7.2 without having to flash an R800i rom? or it doesn't matter?
another problem, even though my phone is from att the touch screen isn't working with (R800at). I also had the same problem when I flashed 2.3.4 R800i, and R800a
whats wrong?
FRKD said:
HAHA... Thanks elnacho!!!
I was so desperate I started blowing at the buttons and it worked!!!
now, i have another question.
I flashed the stock att rom (R800at) unlocked and rooted, can I install CM9 or CM7.2 without having to flash an R800i rom? or it doesn't matter?
another problem, even though my phone is from att the touch screen isn't working with (R800at). I also had the same problem when I flashed 2.3.4 R800i, and R800a
whats wrong?
Click to expand...
Click to collapse
Was the rom rooted? or you flashed a stock ftf and then rooted?
elnacho said:
Was the rom rooted? or you flashed a stock ftf and then rooted?
Click to expand...
Click to collapse
no the rom isn't rooted yet
plus, I can't charge or connect to computer unless I turn off the phone then plug it in..... and if I unplug the usb or charger, it restarts :/
so..... can anyone help?
Hi, I bricked my Phone (I can get access to CWM v6.0.1.9) whilst changing the Build.Prop file (which I know I'm meant to be careful with) I rebooted my phone and after 10 minutes it was still siting on the "Google" screen. I can get into Bootloader and CWM 6.0.1.9 but cant get it to display on my Laptop (win7) as I can't turn on USB debugging..
Any help? I'm stuck right now! It wont show up on ADB or Nexus Toolkit (I found a thread elsewhere with some links but couldnt read them as I wasnt a member)
Fast boot, flash factory image
do this: http://forum.xda-developers.com/showthread.php?t=1626895
Or reflag custom ROM
I'm getting no response when typing in "Fastboot Devices" when I put "ADB Reboot bootloader" its saying "No device found"
If the device cant be seen Can I still flash?
to use fastboot you need to be in the bootloader, not recovery.
I've tried in the bootloader but nothing ever shows up? I havent seen anything pop-up on the bottom of my start bar.. Hmnn If I could get access to my USB/SDcard I could put a zip file to flash -_-
I'll see if I can get it to show up onn fastboot again
if nothing shows up, that means you dont have the fastboot drivers.
Exactly that's what I thought at first place. Forgive me if you find it way too basic but have you tried re-install fastboot drivers? (or even samsung usb drivers....u can also reflash your Gnex via Odin Mode...after all you've got nothing to lose)
I managed to get it working, It wasn't the drivers (I've been using them recently) It was the latest version of ADB/Fastboot I downloaded the latest version and its now flashing
If you can get into CWM like you say, just flash the ROM again. It should fix whatever changes you made to the build.prop file.
EDIT: Nevermind, I guess you got it working. For future reference, if you ever get to where you messed something up and you can still boot into CWM, a simple reflash of the ROM should fix it. Or always make a backup before you go messing with stuff that might ruin something.
...and as long as u can boot into bootloader, download, recovery mode device is usually nowhere near to brick
Ok so my 3 yo. son likes to play games on my GNex. I have not rooted or made ANY modifications whatsoever. He was in the middle of playing a game when it randomly reboots. He hands it to me on the google screen. It never boots. just sits. I have been from forum to forum. If i hold:
pwr + - volume i get the odin mode download screen. I have tried loading stock images through odin but it always gets to CDMA-Radio the very last step and hangs there forever (15+min.) battery pull.
pwr + + volume I get a black screen with a lock at the bottom. ( i have read that this means i have unlocked the bootloader but I have not, on purpose at least) battery pull
pwr + both volume i get a black screen. It kinda looks like the screen is on but just completely black. no fastboot mode. Battery pull.
the stock images i have found either do not work in odin or have broken links.
i am not sure if usb debugging is on like i said i usually dont mod phones. adb wont recognize. I just want a stock GNex back. Any tips tricks files or suggestions will be greatly appreciated and I have no problem donating to the cause
Also if i plug my phone into my pc and dont touch anything the battery symbol with the lightning bolt comes up. cant get rid of it unless battery pull. HELP!! :crying:
jsgraphicart said:
If you can get into CWM like you say, just flash the ROM again. It should fix whatever changes you made to the build.prop file.
EDIT: Nevermind, I guess you got it working. For future reference, if you ever get to where you messed something up and you can still boot into CWM, a simple reflash of the ROM should fix it. Or always make a backup before you go messing with stuff that might ruin something.
Click to expand...
Click to collapse
Good advice...
regal513 said:
Ok so my 3 yo. son likes to play games on my GNex. I have not rooted or made ANY modifications whatsoever. He was in the middle of playing a game when it randomly reboots. He hands it to me on the google screen. It never boots. just sits. I have been from forum to forum. If i hold:
pwr + - volume i get the odin mode download screen. I have tried loading stock images through odin but it always gets to CDMA-Radio the very last step and hangs there forever (15+min.) battery pull.
pwr + + volume I get a black screen with a lock at the bottom. ( i have read that this means i have unlocked the bootloader but I have not, on purpose at least) battery pull
pwr + both volume i get a black screen. It kinda looks like the screen is on but just completely black. no fastboot mode. Battery pull.
the stock images i have found either do not work in odin or have broken links.
i am not sure if usb debugging is on like i said i usually dont mod phones. adb wont recognize. I just want a stock GNex back. Any tips tricks files or suggestions will be greatly appreciated and I have no problem donating to the cause
Also if i plug my phone into my pc and dont touch anything the battery symbol with the lightning bolt comes up. cant get rid of it unless battery pull. HELP!! :crying:
Click to expand...
Click to collapse
If you want to flash img files via Odin you must first create tar or tar.md5 packages. Download and install cygwin. Once u opened cygwin navigate to your factory image folder where all your img files are. (it's a good idea to make a copy of your bootloader-xxx-img and radio-xxx.img and to rename them to simple bootloader.img and radio.img) and use the following commands:
Code:
tar -H ustar -c boot.img bootloader.img radio.img recovery.img system.img userdata.img > name-of-odin-flashable.tar
md5sum -t name-of-odin-flashable.tar >> name-of-odin-flashable.tar
mv name-of-odin-flashable.tar name-of-odin-flashable.tar.md5
flash this newly created package under "pda" , and do NOT check re-partition!
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Guys, I have an immediate problem with my SM-T705 Galaxy Tab S 8.4. It is in Odin mode and it wouldn't power off no matter what buttons I press. I've pressed the power button for 30 seconds, home and power button combo, etc.
Background story:
I have already rooted it, but seeing edan1979's SelambA ROM NG2 V1.1.0 20140820, I thought flashing it would be a good way to get rid of bloatware.
Thinking I need to backup my existing firmware, I used Flashify to get TWRP Recovery but Flashify said there's no TWRP for my device. So I went to http://teamw.in/project/twrp2/238 and downloaded openrecovery-twrp-2.8.0.0-klimtwifi.img, put it in my internal storage, used Flashify to install it. Once done, I had the option to reboot, which I did. Thereafter, my tablet went into a boot loop. So I thought I might as well flash the SelambA ROM immediately. I went into Odin Mode, connect my tablet to my PC with a USB cable, launched Odin 3.0.7 and it detected my tablet. Unfortunately, I discovered Odin (unlike Sony's Flashtool) wouldn't read .zip files, which is the file format of SelambA ROM.
Now I've found and downloading the original stock firmware, hopefully that .zip contains the .md5 format. It's a super slow download that will take about 8 hours more to complete. In the mean time, my tablet screen is switched on, stuck in Odin mode.
What else can I do to rectify this situation?
Press Power, Volume - or + i dont remember :> , Home at the same time
sku|| said:
Press Power, Volume - or + i dont remember :> , Home at the same time
Click to expand...
Click to collapse
3 buttons at the same time?
Other than that, would something like Kies detect my device and download the proper firmware for it?
Edit: That I did home+power+volume up. Got to Recovery mode. The I pressed and hold the power button to get to the boot loop. Now charging it while it boot loops.
coffee black said:
3 buttons at the same time?
Other than that, would something like Kies detect my device and download the proper firmware for it?
Edit: That I did home+power+volume up. Got to Recovery mode. The I pressed and hold the power button to get to the boot loop. Now charging it while it boot loops.
Click to expand...
Click to collapse
Yes, heimdall (open source) will be an alternative for kies/odin. But:
1) identify your device and region (to guess proper firmware archive)
2) you need to download your device firmware yourself (http://www.samdown.com or others)
3) enter into download mode by POWER+VOL DOWN+HOME
4) run heimdall as single command or via frontend
5) before flashing with heimdall, you can use heimdall print-pit option to test working interaction between heimdall and your device
6) the heimdall flash command looks like this:
Code:
# heimdall flash \
--CACHE cache.img \
--BOOT boot.img \
--SYSTEM system.img \
--RECOVERY recovery.img \
--RADIO modem.bin \
--HIDDEN hidden.img \
--BOOTLOADER sboot.bin
If needed after flashing take a full reset/wipe via recovery mode (POWER+VOL UP+HOME).
Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.
Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?
I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!
anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )
Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!
np...